Skip to content

One Sea Holds Three Lengths, Spanning a Factor of 4.39x10^4 ── All Contain the Coriolis Parameter, and Nothing Else in Them Overlaps ── The Bathtub Vortex Has Rossby Number 3232, and Seeing Rotation There Needs Flow Below 0.031 mm/s ── [Paper 291]

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)
Oceanographic and Atmospheric Processes

Abstract

A rotating ocean has several characteristic lengths. Each is called “the length set by Coriolis.”This paper asks whether they are the same thing──the answer is that they are different things. 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──the Ekman layer, the Rossby deformation radius, the Rossby number, and geostrophic balance are all standard. We do not build ocean dynamics──all we use is three length formulas and one dimensionless number. We do not derive the Ekman spiral──we do not enter the boundary-layer equations. We do not take a roll call of forces──the classification of centrifugal, Coriolis, and pressure-gradient forces is not treated. This is a roll call of lengths. We claim no accuracy for the representative values──eddy viscosity A_z=0.01 m^2/s, stratification N=0.005 /s, and depths H=1000 / 4000 m are values for showing orders and move by an order with place and season. A_z in particular ranges from 10^-4 to 10^-1. We assert no values for the bathtub vortex──U=0.1 m/s and L=0.3 m are representative of a typical drain vortex. What this paper asserts is Ro much greater than 1, not the value 3232. We do not explain the drain vortex’s sense of rotation──what actually decides it (residual initial circulation, vessel shape, how the plug is pulled) is not treated. We show only that it is not Coriolis. Relation to earlier papers: Paper 256 showed that the only scale at which dynamical similarity holds exactly is 1──the Ro here is likewise a dimensionless number that cannot be held when the scale changes, so a bathtub cannot be a model of an ocean. Paper 117 treated scale invariance fixing an exponent in four ways and wrote the condition that there be exactly one Pi group──this paper is a case failing that condition, with three lengths standing independently. Paper 140 separated symmetry fixing ratios from dynamics fixing the scale──all three lengths here are on the dynamics side. Paper 112 counted “distinct roots sharing one rhyme”──the three lengths share the rhyme f and differ in root. What is added is lining up three lengths in one table and measuring the span 4.3905x10^4, confirming that the ratio 39.6182 is set by stratification, computing the Rossby numbers of five phenomena, and deriving the flow speed 0.031 mm/s needed to see rotation in a bathtub. First, we line up three lengths. At latitude 45^ deg: Ekman layer 43.75 m, baroclinic deformation radius 48.48 km, barotropic deformation radius 1920.86 km (Section 2). Second, this is the core of the paper. Smallest to largest spans 4.3905x10^4, and though all contain the Coriolis parameter f, nothing else in them overlaps (Section 2). Third, what separates baroclinic from barotropic is not depth. The ratio is 39.6182, and what sets it is the stratification N (Section 3). Fourth, whether rotation acts is settled by one number. The Rossby number Ro=U/(fL): Gulf Stream 0.0970, typhoon 0.5818 (Section 4). Fifth, the bathtub vortex has Ro=3232. A force 3232 times stronger than Coriolis is turning it (Section 5). Sixth, the separator is Ro. To see Coriolis in a bathtub the flow must be below 0.031 mm/s (Section 5). One sea at one latitude holds three “lengths set by Coriolis.”Ekman layer 43.75 m, baroclinic deformation radius 48.48 km, barotropic deformation radius 1920.86 km──spanning 4.3905x10^4. All contain the Coriolis parameter f, yet not one of their other ingredients overlaps──viscosity, stratification, gravity. Even the exponent of the dependence on f differs──only the Ekman depth goes as f^-1/2, so changing the latitude changes the ratios among the three. What separates baroclinic from barotropic is stratification, not depth──f cancels in the ratio, and doubling N turns 39.6 into 19.8. And whether rotation acts is settled by one number, the Rossby number Ro=U/(fL)──Gulf Stream 0.0970, typhoon 0.5818, and the bathtub vortex 3232.29. One thing separates them──whether U/L is smaller than f. Seeing Coriolis in a bathtub requires flow below 0.031 mm/s, and a real drain vortex is 3232 times faster. Changing the latitude moves f by at most sqrt2, so that route cannot close the gap. 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. ----- 回転する海には、特徴的な長さが複数ある。どれも「コリオリで決まる長さ」と呼ばれる。本稿が問うのは、それらは同じものかである──答は、別のものである。新しい数学定理も新しい法則も主張しない。 本稿の射程(射程注記):新しい数学定理も新しい法則も主張しない──エクマン層、ロスビー変形半径、ロスビー数、地衡流平衡は、いずれも標準的である。海洋力学を作らない──使うのは三つの長さの式と、一つの無次元数だけである。エクマン螺旋を導出しない──境界層方程式には立ち入らない。力の点呼をしない──遠心力、コリオリ力、圧力傾度力の分類は扱わない。本稿は長さの点呼である。代表値の精度を主張しない──渦粘性 A_z=0.01 m^2/s、成層 N=0.005 /s、深さ H=1000/4000 m は桁を示すための代表値であり、場所と季節で一桁動く。とくに A_z は 10^-4 から 10^-1 まで動く。風呂の渦の値を主張しない──U=0.1 m/s、L=0.3 m は典型的な排水渦の代表値である。 Ro=3232 という値ではなく、Ro much greater than 1 という事実が本稿の主張である。排水渦の回転向きを説明しない──何が実際に向きを決めているか(初期の残留渦、容器の形、抜き方)は扱わない。コリオリでないことだけを示す。既刊との関係:論文256 は力学相似が厳密に成り立つ縮尺が 1 だけだと示した──本稿の Ro も縮尺を変えると保てない無次元数であり、風呂は海の模型になれない。論文117 はスケール不変性が四通りに指数を選ぶことを扱い、Pi 群がちょうど一つという条件を書いた──本稿はその条件を満たさない場合であり、三つの長さが独立に立つ。論文140 は対称性が比を決め力学が尺度を決めると分けた──本稿の三つの長さはどれも力学の側である。論文112 は「同じ韻の別根」を数えた──三つの長さはf という韻を共有し、根が違う。加えたのは三つの長さを一表に並べて 4.3905x10^4 倍の開きを測ったこと、傾圧と順圧の比 39.6182 を決めているのが成層だと確かめたこと、五つの現象のロスビー数を計算したこと、風呂で回転を見るのに要る流速 0.031 mm/s を出したことである。 第一に、三つの長さを並べる。緯度 45^ deg で、エクマン層 43.75 m、傾圧変形半径 48.48 km、順圧変形半径 1920.86 km(第2節)。 第二に、これが本稿の芯である。最小と最大は 4.3905x10^4 倍ひらいており、どれもコリオリ因子 f を含むのに、f 以外の要素が全部違う(第2節)。 第三に、傾圧と順圧を分けているのは深さではない。比は 39.6182 倍で、決めているのは成層 N である(第3節)。 第四に、回転が効くかどうかは一つの数が決める。ロスビー数 Ro=U/(fL) で、メキシコ湾流 0.0970、台風 0.5818(第4節)。 第五に、風呂の渦は Ro=3232 である。コリオリより 3232 倍強い力が回している(第5節)。 第六に、分離子は Ro である。風呂でコリオリを見るには、流速を 0.031 mm/s 以下にせねばならない(第5節)。 同じ海の同じ緯度に、三つの「コリオリで決まる長さ」がある。エクマン層 43.75 m、傾圧変形半径 48.48 km、順圧変形半径 1920.86 km──4.3905x10^4 倍ひらいている。どれもコリオリ因子 f を含むが、f 以外の要素は一つも重なっていない──粘性、成層、重力である。 f への依存の指数さえ違う──エクマン深さだけが f^-1/2 で、緯度を変えると三つの比そのものが変わる。傾圧と順圧を分けているのは深さではなく成層である──比の中で f が約分され、N を二倍にすると 39.6 倍が 19.8 倍になる。そして回転が効くかどうかは、ロスビー数 Ro=U/(fL) という一つの数が決める──メキシコ湾流 0.0970、台風 0.5818、そして風呂の渦は 3232.29。分けるものは一つ──U/L が f より小さいかどうか。風呂でコリオリを見るには流速を 0.031 mm/s 以下にせねばならず、実際の排水渦はその 3232 倍速い。緯度を変えても f は高々 sqrt2 倍しか動かないので、そちらでは埋まらない。 作成にあたって:本稿の着想と内容は、著者自身の考察に基づくものです。文章の構成整理や英訳、数式の確認には 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

Google DeepMind Blog Aug 12, 2026

Putting sign language AI into users’ hands

Introducing sign-language-to-text (SL2T), our breakthrough model powering new sign language features for Deaf and hard of hearing users.