Skip to content
#small language model Open access

The Length That Sets How Thick an Atmosphere Is Also Sets Whether It Stays ── Earth's Scale Height Is 7.319 km, 0.1149% of the Radius ── The Number Deciding Escape Is the Reciprocal of That Ratio ── [Paper 321]

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)
Science and Climate Studies

Abstract

An atmosphere has one length in it, H=kT/(mg). This paper asks what that length decides──the answer is both the thickness and whether the atmosphere stays. No new mathematical theorem and no new law is claimed. Scope of this paper (scope note): No new mathematical theorem and no new law is claimed──scale height, the isothermal barometric law, and the Jeans parameter as an escape criterion are all standard. We do not build atmospheric science──all we use is one length and one ratio. We assume isothermality──a real atmosphere changes temperature with height, and H with it. We compute at one representative temperature. We do not treat escape mechanisms──hydrodynamic escape, non-thermal escape and solar-wind stripping are not entered. lambda is a guide, not a verdict. We do not follow compositional evolution──which gas leaves first, and when, is not treated. We claim no accuracy for the representative values──T and mean molecular weight are numbers for seeing orders of magnitude. Relation to earlier papers: Paper 309 showed that l_c=sqrt(gamma/rho g) is the length dividing gravity from surface tension──this is a third of the same kind, dividing gravity from heat this time. Paper 291 showed three lengths inside one ocean──this paper is the reverse: one length answering two questions. Paper 268 showed that the triple point’s being a “point” is settled by the phase rule before measurement──the same territory, pressure, and this paper looks at the distribution inside a single phase. Paper 276 showed the decibel is a ratio and not a quantity──R/H is a ratio too, and carries no dimension. Paper 316 showed the same integer returning from three counts──this paper is its mirror: one ratio answering two questions. What is added is computing the scale height for five bodies, tabulating H/R as a percentage, giving the pressure profile and the cumulative mass in numbers, and showing that the Jeans parameter equals R/H. First, on Earth it is 7.319 km.0.1149% of the 6371 km radius (Section 2). Second, pressure falls by 1/e every H. At Everest’s height, 0.2985 (Section 3). Third, 63.2121% of the mass sits below one H (Section 3). Fourth, this is the core of the paper. The number deciding escape is R/H itself (Section 4). Fifth, the Moon is at 25.20 and leaks. Earth 871.65, Titan 124.90 (Section 4). Sixth, the separator is which of gravity and heat wins, and it can only be written as a ratio (Section 5). An isothermal atmosphere has one length in it, H=kT/(mg), a ratio of heat to gravity that has come out as a length. On Earth it is 7.319 km──only 0.1149% of the 6371 km radius, 0.17 mm on a 30 cm globe, thinner than a sheet of paper. Pressure falls by 1/e every H, reaching 0.2985 at the summit of Everest──and 63.2121% of the mass sits below a single H. That 1-1/e depends on neither T nor g nor mu, and is the same on Venus, Jupiter and Titan. And the number deciding whether the atmosphere escapes comes out of that same H──putting g=GM/R^2 into the Jeans parameter lambda=GMm/(kTR) makes it exactly lambda=R/H. Earth stays at 871.65, Mars at 313.60, Titan at 124.90, and the Moon leaks at 25.20──Titan is smaller than the Moon and keeps its atmosphere because 94 K of cold compensates for the smallness. One thing separates them──which is larger, kT or mgR. And that can only be written as a ratio. H alone settles nothing──Jupiter’s H exceeds Earth’s, and at R/H=2804.51 it is far safer, so the ordering by length runs opposite to the ordering by safety. This is a third of the kind Paper 309 began with “the length dividing gravity from surface tension is not the size of the material”──H is not the size of the body but what the body is compared with. One last thing──one ratio is answering two questions. “How thin is it” and “does it stay” look different, and the answers are the two faces of one number. A thin atmosphere is an atmosphere in the act of leaving. On the making of this work: The ideas and content of this work stem from the author's own considerations. Assistance from an AI (a large language model) was used for structuring, English translation, and checking the algebra. Any remaining errors or misinterpretations are solely the author's. Feedback and corrections are sincerely appreciated. ----- 大気には H=kT/(mg) という長さが一つある。本稿が問うのは、この長さは何を決めているのかである──答は、厚さと、残るかどうかの両方である。新しい数学定理も新しい法則も主張しない。 本稿の射程(射程注記):新しい数学定理も新しい法則も主張しない──スケールハイト、等温大気の気圧分布、ジーンズ係数による散逸の目安は、いずれも標準的である。大気科学を作らない──使うのは一つの長さと、一つの比だけである。等温を仮定する──実際の大気は高さで温度が変わり、H も高さで変わる。本稿は一つの代表温度で計算する。散逸の機構を扱わない──ジーンズ散逸以外(流体力学的散逸・非熱的散逸・太陽風の剥ぎ取り)には立ち入らない。 lambda は目安であって判定ではない。組成の進化を追わない──どの気体が先に逃げるかの時間発展は扱わない。代表値に精度を主張しない──T と平均分子量は桁を見るための値である。既刊との関係:論文309 は l_c=sqrt(gamma/rho g) が重力と表面張力を分ける長さだと示した──本稿は同じ型の三本目であり、今度は重力と熱を分ける。論文291 は同じ海に三つの長さがあると示した──本稿は一つの長さが二つの問いに答えるという、逆向きの話である。論文268 は三重点が「点」であるのは相律が測る前に決めていると示した──気圧の話をする場所が同じであり、本稿は一相の中の分布を見る。論文276 はデシベルが比であって量ではないと示した──R/H も比であり、次元を持たない。論文316 は同じ整数を三つの数え方が返すと示した──本稿は一つの比が二つの問いに答えるという、鏡像である。加えたのは五つの天体でスケールハイトを計算したこと、H/R を百分率で並べたこと、気圧の高度依存と質量の累積を数で出したこと、ジーンズ係数が R/H に一致することを示したことである。 第一に、地球では 7.319 km である。半径 6371 km の0.1149%(第2節)。 第二に、高度 H ごとに 1/e になる。エベレストの高さで 0.2985 倍(第3節)。 第三に、H 一つぶんの下に 63.2121% が入っている(第3節)。 第四に、これが本稿の芯である。逃げるか残るかを決める数は R/H そのものである(第4節)。 第五に、月は 25.20 で漏れる。地球は 871.65、タイタンは 124.90(第4節)。 第六に、分離子は「重力と熱のどちらが勝つか」であり、それは比でしか書けない(第5節)。 等温の大気には H=kT/(mg) という長さが一つあり、熱と重力の比が長さになったものである。地球では 7.319 km──半径 6371 km の0.1149%にすぎず、直径 30 cm の地球儀なら 0.17 mm、紙一枚より薄い。高度 H ごとに気圧は 1/e になり、エベレストの頂上で 0.2985 倍──そしてH 一つぶんの下に 63.2121% の質量が入っている。この 1-1/e は T にも g にも mu にも依らず、金星でも木星でもタイタンでも同じである。そして大気が逃げるか残るかを決める数は、この H そのものから出る──ジーンズ係数 lambda=GMm/(kTR) に g=GM/R^2 を入れるとlambda=R/H に厳密になる。地球は 871.65、火星は 313.60、タイタンは 124.90 で残り、月は 25.20 で漏れる──タイタンが月より小さいのに大気を持つのは、94 K という冷たさが小ささを補っているからである。分けるものは一つ──kT と mgR のどちらが大きいか。そしてそれは比でしか書けない。 H 単独では何も決まらない──木星の H は地球より大きいのに R/H=2804.51 で地球よりずっと安泰であり、長さの大小と安泰さの大小が逆を向いている。論文309 が「重力と表面張力を分ける長さは材料の寸法ではない」と書いたのと同じ型の三本目である──H は天体の寸法ではなく、比べる相手である。最後に一つ──同じ一つの比が、二つの問いに答えている。「どれだけ薄いか」と「残るか」は別の問いに見えて、答は同じ数の表と裏であった。薄い大気とは、逃げかけている大気のことである。 作成にあたって:本稿の着想と内容は、著者自身の考察に基づくものです。文章の構成整理や英訳、数式の確認には AI(大規模言語モデル)の助力を得ました。最終的な内容の解釈や誤りがあれば、それらはすべて著者の責に帰します。お気づきの点があれば、ご教示いただければ幸いです。

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 179 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Open access Feb 2018

Lean Internal Startups for Software Product Innovation in Large Companies: Enablers and Inhibitors

To compete in this age of disruption, large companies cannot rely on cost efficiency, lead time reduction and quality improvement. They are now looking for ways to innovate like startups. Meanwhile, the awareness and use of the Lean startup approach have grown rapidly amongst the software startup community in recent years. This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors. A multiple case study approach is followed in the investigation. Two software product innovation projects from two large companies are examined, using a conceptual framework that is based on the method-in-action framework and extended with the previously developed Lean-Internal Corporate Venture model. Seven face-to-face in-depth interviews of the employees with different roles are conducted. Within-case analysis and cross-case comparison are applied to draw the findings from the cases. A generic process flow summarises the common key processes of Lean internal startups. The findings suggest that an internal startup that is initiated management or employees faces different challenges. A list of enablers of applying Lean startup in large companies are identified, including top management support and cross-functional team. Both cases face different inhibitors due to the different process of inception, objective of the team and type of the product. Our contributions are threefold. First, this study is one of the first attempt to investigate the use of Lean startup approach in large companies empirically. Second, the study shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context. The third is a general process of Lean internal startup and the evidence of the enablers and inhibitors of implementing it, which are both theory-informed and empirically grounded.

Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al. · 78 citations · ⚡6
#computer vision Conference Sep 2010

Exploring the Sources of Waste in Kanban Software Development Projects

The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.

Marko Ikonen, Petri Kettunen, Nilay V. Oza et al. · 67 citations · ⚡9

Related blog posts