Skip to content
#small language model Open access

That the Same Ellipse Was Three Months Out Was the Evidence of a Different Cause ── Aberration Is 20.49552 Arcseconds Whatever the Distance, While Parallax Goes as Its Reciprocal ── A Factor of 26.6442 at Proxima and 20495 at a Kiloparsec ── [Paper 328]

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Over a year a star traces a small ellipse on the sky. This paper asks whether that ellipse is one thing──the answer is that there are two, and they are told apart by phase. 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──aberration, annual parallax, Bradley’s observation of 1728, and the definition of the constant of aberration are all standard. We do not build celestial mechanics──all we use is two angles and the phase between them. We do not treat this relativistically──the relativistic formula for aberration is not entered. We look only where first order in v/c suffices. We do not treat proper motion──a star’s own motion is not periodic and so separates from both of these. It is mentioned and no more. We do not adjudicate the history──who first saw what is not entered. We do not treat the distance ladder──the rungs beyond parallax belong to Paper 297. Relation to earlier papers: Paper 297 showed the cosmic distance scale to be a ladder of seven rungs with only the first measured directly──that first rung is parallax, and this paper looks at the other ellipse standing beside it. Paper 325 showed the radius not entering the angle of a rainbow──the same form, with distance not entering aberration here. Paper 300 showed whether two things share a root is decidable──this is an instance of “same shape, different root”, and what decided it was not a value but a phase. Paper 327 showed two curves agreeing to within 0.083 per cent──there the appearance is the same and the things differ; here the size can be the same and the things differ. Paper 313 showed the corpus using “synchrony” in several senses──phase is again the tool that decides. What is added is giving the constant of aberration from both a simple calculation and the literature and stating the difference, tabulating the ratio across three decades of distance, solving for the distance at which the two would be equal, and putting the separator on position against velocity. First, aberration is 20.49552 arcseconds (Section 2). Second, this is the core of the paper. Aberration does not depend on distance; parallax goes as its reciprocal (Section 3). Third, even the nearest star opens by 26.6442. At a kiloparsec, 20495 (Section 3). Fourth, amplitude cannot always separate them. At some distance the two would be equal (Section 3). Fifth, their phases differ by a quarter. That is how Bradley told them apart (Section 4). Sixth, the separator is whether the effect is set by position or by velocity (Section 5). Over a year a star traces a small ellipse on the sky, and two causes are possible──annual parallax, because the Earth’s position changes, and aberration, because its velocity does. Both have a period of one year, both are ellipses, and the shape does not distinguish them. Aberration follows from tanalpha=v/c and is 20.49552 arcseconds, about 1/88 of the apparent diameter of the full moon──(the simple calculation here, 20.492697, differs by 0.0138 per cent, because kappa is defined to include the eccentricity, so this paper uses the literature value). And the distance to the star is nowhere in that formula──it contains only the observer’s speed and the speed of light, not one piece of information about the thing being looked at. Even Proxima is out by 26.6442, and at a kiloparsec by 20495.5200. The distance at which the two would be equal is 0.159135 light years, and no such star exists──so on amplitude alone, aberration always wins. What separated them was not amplitude but phase──in circular motion the velocity points a quarter period ahead of the position, so the two ellipses are exactly three months apart. In 1728 Bradley, hunting for parallax, found an ellipse in the wrong season and knew it was not his quarry. A mismatch in amplitude would have been weak evidence──without the distance there is no predicted parallax to compare against, whereas the phase can be predicted without knowing the distance at all. One thing separates them──whether the effect is set by the observer’s position or by the observer’s velocity. Settle that and the distance dependence and the phase follow automatically, so three apparently independent differences are one. Paper 297 wrote that the first rung of the distance ladder is parallax──this paper says that immediately beside it sits an ellipse of the same shape containing no distance at all. The first rung does not stand by itself. One last thing──Bradley failed to find what he was looking for and found what he was not. And it became a measurement of the speed of light, because v/c can be read off from an angle of 20 arcseconds. A failure to find became the ruler for something else. 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. ----- 恒星は一年かけて空に小さな楕円を描く。本稿が問うのは、その楕円は一種類かである──答は、二種類あり、位相で見分けられるである。新しい数学定理も新しい法則も主張しない。 本稿の射程(射程注記):新しい数学定理も新しい法則も主張しない──光行差、年周視差、ブラッドリーの 1728 年の観測、光行差定数の定義はいずれも標準的である。天体力学を作らない──使うのは二つの角度と、その位相差だけである。相対論的な扱いをしない──光行差の相対論的公式には立ち入らない。 v/c の一次までで足りる場面だけを見る。固有運動を扱わない──恒星自身の運動は周期的でないので、本稿の二つとは分けられる。触れるにとどめる。測定の歴史を裁定しない──誰が最初に何を見たかの帰属には立ち入らない。距離はしごを扱わない──視差より遠い段は論文297 の射程である。既刊との関係:論文297 は宇宙の距離が七段のはしごで、直接測られているのは一段目だけだと示した──その一段目が視差であり、本稿はその隣に立つもう一つの楕円を見る。論文325 は虹の角度に半径が入らないと示した──同じ型であり、ここでは光行差に距離が入らない。論文300 は同根か別根かは判定できると示した──本稿は「同じ形をしていても別根」の実例であり、判定に使ったのは値ではなく位相である。論文327 は二つの曲線が 0.083 パーセントしか違わないと示した──そこでは見た目が同じで別物、ここでは大きさが同じでも別物である。論文313 は体系が「同期」を複数の意味で使ってきたと示した──位相という語がここでも判定の道具になっている。加えたのは光行差定数を単純計算と文献値の両方で示し、その差を明示したこと、距離ごとの比を三桁にわたって出したこと、二つが同じ振幅になる距離を求めたこと、分離子を位置と速度の別に置いたことである。 第一に、光行差は 20.49552 秒角である(第2節)。 第二に、これが本稿の芯である。光行差は距離に依らず、視差は距離に反比例する(第3節)。 第三に、最も近い恒星でも 26.6442 倍ひらく。1 キロパーセクなら 20495 倍(第3節)。 第四に、振幅では分けられない場合がある。ある距離では二つが同じ大きさになる(第3節)。 第五に、位相が四分の一ずれている。ブラッドリーはそれで見分けた(第4節)。 第六に、分離子は「位置で決まるか、速度で決まるか」である(第5節)。 恒星は一年かけて空に小さな楕円を描き、その原因は二つありうる──地球の位置が変わるからの年周視差と、地球の速度が変わるからの光行差である。どちらも一年周期の楕円で、形では区別がつかない。光行差は tanalpha=v/c から出て 20.49552 秒角、満月の見かけの直径の約 1/88 である──(本稿の単純計算 20.492697 は文献値と 0.0138 パーセント違い、kappa は離心率を含む定義なので、本稿が使うのは文献値である)。そしてこの式には、恒星までの距離が入っていない──現れるのは観測者の速度と光速だけで、見ている相手の情報が一つも入らない。最も近いプロキシマですら視差の 26.6442 倍、1 キロパーセクでは 20495.5200 倍ひらく。二つが同じ大きさになる距離は 0.159135 光年で、そんな恒星は存在しない──振幅の大小では、常に光行差が勝つ。分けたのは振幅ではなく、位相である──円運動では速度は位置の四分の一周期先を向くので、二つの楕円はちょうど三ヶ月ずれる。ブラッドリーは 1728 年、視差を探していて楕円を見つけ、季節がずれていることで探し物ではないと知った。振幅が合わないことは証拠として弱い──距離を知らなければ視差の予想値が立たないからで、位相は距離を知らなくても予想できる。分けるものは一つ──その効果が観測者の位置で決まるか、速度で決まるか。それが決まれば距離依存も位相も自動的に決まり、独立に見えた三つの違いが一つの違いになる。論文297 は距離のはしごの一段目が視差だと書いた──本稿はその一段目のすぐ隣に、距離を一切含まない同じ形の楕円が乗っていることを言う。はしごの一段目は、単独では立っていない。最後に一つ──ブラッドリーは探していたものを見つけられず、探していなかったものを見つけた。そしてそれは光速の測定になった。20 秒角という角度から v/c が読めるからである。見つからなかったことが、別のものの物差しになった。 作成にあたって:本稿の着想と内容は、著者自身の考察に基づくものです。文章の構成整理や英訳、数式の確認には 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