Skip to content
#small language model Open access

Two Curves Agree to Within 0.083 Per Cent and Are Not the Same Curve ── What Divides the Catenary from the Parabola Is Not Shape but Which Length the Load Is Counted Along ── [Paper 327]

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)
Structural Engineering and Vibration Analysis

Abstract

A hanging chain and a suspension-bridge cable cannot be told apart by eye. This paper asks what divides them──the answer is not the shape, but which length the load is counted along. 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 catenary equation, the parabolic-cable theory of suspension bridges, and the Taylor expansions of both are all standard. We do not do structural design──all we use is two curves and one difference of measure. We do not treat deflection──cable stretch, thermal movement and live-load deflection are not entered. This paper looks only at the idealised static shape. We do not adjudicate which is correct──a real bridge lies between the two, and this paper does not locate it. We claim no engineering accuracy──the sag ratios are values for comparing shapes, not those of any particular bridge. We do not discuss optimal shape──which is structurally better is not treated. Relation to earlier papers: Paper 198 showed that “straight” does not mean “shortest”──198 says one curve has two characters; this says two curves look alike. The direction is reversed. Paper 326 showed the square-cube relation is an identity──both are of the “same appearance, different content” kind, but 326 is about a ratio and this is about functions. Paper 300 showed whether two things share a root is decidable──this is a worked instance of “numerical closeness is not sameness of root”. Paper 245 showed two limits have no answer until their order is written──here too, the curve is undetermined until the measure of integration is written. Paper 183 showed one table having two correct answers──one shape having two correct equations is its counterpart. What is added is computing the difference at six points, stating that it begins at fourth order, giving the maximum difference for each sag ratio, and putting the separator on the measure. First, they agree exactly through second order. At x=0.1 the difference is 0.083292 per cent (Section 2). Second, far out they are different things. At x=5, 82.925818 per cent (Section 2). Third, the difference begins at fourth order. x^4/24 against 0 (Section 2). Fourth, this is the core of the paper. What divides them is counting along arc length or along horizontal length (Section 3). Fifth, on a real bridge the difference is only 0.082674 per cent (Section 4). Sixth, the separator is whether the deck or the cable is the heavier (Section 5). A hanging chain and a suspension-bridge cable cannot be told apart by eye. Expanding cosh shows the leading term to be the parabola itself, so they agree exactly through second order──with a=1 the difference is 0.083292 per cent at x=0.1 and 82.925818 per cent at x=5, and both figures are correct about the same two curves. “How different are they” is undetermined until you say where you are looking. The difference begins at fourth order──first, second and third all agree, and the parabola is the second-order Taylor polynomial of the catenary, not a curve fitted to it. And what divides them is not shape but measure──both come from the same balance H y''=w, and all that differs is whether w is constant against arc length ds or horizontal length dx. Constant along the arc makes the steep ends weigh more per horizontal foot, and so the catenary rises faster. So “a parabola close to a catenary” has it backwards──each is the exact answer to a different physics, and the approximation relation is something mathematics noticed afterwards. At the 1/10 sag of a real suspension bridge the maximum difference is 0.082674 per cent of the sag──8.3 cm on a 1000 m span, sometimes smaller than the construction tolerance. And they are still two different curves. One thing separates them──whether the suspended deck or the cable itself is heavier. A real bridge is neither ideal, and this paper does not locate it. Against Paper 198 the direction is exactly reversed──198 says one curve has two characters, this says two curves have one appearance, and both obey the same discipline: appearance is not evidence. One last thing──Galileo wrote that a hanging chain is a parabola. He was wrong, by 0.083 per cent. Not an error the eye could correct, and with no cosh yet in existence there was nothing to correct it to. Writing the right shape needs the words for it to exist first. 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. ----- 垂れた鎖の形と、吊り橋のケーブルの形は、目では区別がつかない。本稿が問うのは、では何が二つを分けているのかである──答は、形ではなく、荷重をどちらの長さで数えるかである。新しい数学定理も新しい法則も主張しない。 本稿の射程(射程注記):新しい数学定理も新しい法則も主張しない──懸垂線の方程式、放物線ケーブルの吊り橋理論、両者のテイラー展開はいずれも標準的である。構造設計をしない──使うのは二つの曲線と、一つの測度の違いだけである。たわみを扱わない──ケーブルの伸び、温度変化、活荷重によるたわみには立ち入らない。本稿は理想化された静止形状だけを見る。どちらが正しいかを判定しない──実際の橋は両者のあいだにあり、本稿はその位置を決めない。数値に工学上の精度を主張しない──たるみ比は形を比べるための値であって、特定の橋のものではない。最適形状を論じない──どちらが構造として有利かは扱わない。既刊との関係:論文198 は「まっすぐ」は「最短」を意味しないと示した──198 は同じ曲線に二つの性格があると言い、本稿は二つの曲線が同じに見えると言う。向きが逆である。論文326 は二乗三乗が恒等式だと示した──どちらも「見かけが同じでも中身が違う」型だが、326 は比の話、本稿は関数の話である。論文300 は同根か別根かは判定できると示した──本稿は「数値が近いだけでは同根でない」の実例になっている。論文245 は二つの極限が順序を書くまで答を持たないと示した──ここでも、どの測度で積分するかを書くまで曲線が決まらない。論文183 は同じ表が二つの正しい答を持つと示した──同じ形が二つの正しい方程式を持つという、対になる例である。加えたのは両曲線の差を六点で計算したこと、差が四次から出ることを明示したこと、たるみ比ごとの最大差を出したこと、分離子を測度の違いに置いたことである。 第一に、原点では二次まで完全に一致する。 x=0.1 で差は 0.083292 パーセント(第2節)。 第二に、遠くでは別物になる。 x=5 で 82.925818 パーセント(第2節)。 第三に、差は四次の項から出る。 x^4/24 対 0(第2節)。 第四に、これが本稿の芯である。分けているのは、弧長で数えるか水平長で数えるかである(第3節)。 第五に、実際の吊り橋では差は 0.082674 パーセントしかない(第4節)。 第六に、分離子は「桁とケーブル、どちらが重いか」である(第5節)。 垂れた鎖と吊り橋のケーブルは、目では区別がつかない。 cosh を展開すると最初の項が放物線そのもので、二次まで完全に一致する──a=1 とすると x=0.1 での差は 0.083292 パーセント、x=5 では 82.925818 パーセントであり、同じ二本について両方とも正しい。「どれだけ違うか」は、どこを見るかを言わないと決まらない。差は四次の項から出る──一次も二次も三次も一致しているので近くでは見分けようがなく、放物線は懸垂線の二次のテイラー多項式そのものであって、当てはめた曲線ではない。そして二つを分けているのは、形ではなく測度である──どちらも H y''=w という同じ釣り合いから出て、違うのは w が弧長 ds について一定か、水平長 dx について一定かだけである。弧長で一定なら傾いた所ほど水平方向に重くなり、だから懸垂線のほうが速く立ち上がる。だから「懸垂線に近い放物線」という言い方は順序が逆である──どちらも別々の物理から出た正確な答であって、近似関係は後から数学が見つけたものである。実際の吊り橋のたるみ比 1/10 では、最大差はたるみの 0.082674 パーセント──スパン 1000 m・たるみ 100 m の橋で 8.3 cm であり、施工の誤差より小さいこともある。それでも二つは別の曲線である。分けるものは一つ──吊られた桁とケーブル自身の、どちらが重いか。実際の橋はそのあいだにあり、本稿はその位置を決めない。論文198 とは向きがちょうど逆である──198 は一つの曲線が二つの性格を持つと言い、本稿は二つの曲線が一つの見かけを持つと言う。どちらも「見た目は根拠にならない」という同じ規律に服している。最後に一つ──ガリレオは垂れた鎖を放物線だと書いた。間違いだが、0.083 パーセントの間違いである。目で見て直せる誤りではなく、cosh という関数がまだ無かったのだから直しようもなかった。正しい形を書くには、書くための言葉が先に要る。 作成にあたって:本稿の着想と内容は、著者自身の考察に基づくものです。文章の構成整理や英訳、数式の確認には 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