Papers › A search for transit timing variations within the exomoon corridor using Kepler data
A search for transit timing variations within the exomoon corridor using Kepler data
David Kipping, Daniel A. Yahalomi
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
An exomoon will produce transit timing variations (TTVs) upon the parent planet and their undersampled nature causes half of such TTVs to manifest within a frequency range of 2 to 4 cycles, irrespective of exomoon demographics. Here, we search through published Kepler TTV data for such signals, applying a battery of significance and robustness checks, plus independent light curve analyses for candidate signals. Using the original transit times, we identify 11 (ostensibly) single-planets with a robust, significant and fast (P_(TTV)<4 cycles) TTV signal. However, of these, only 5 are recovered in an independent analysis of the original photometry, underscoring the importance of such checks. The surviving signals are subjected to an additional trifecta of statistical tests to ensure signal significance, predictive capability and consistency with an exomoon. KOI-3678.01, previously validated as Kepler-1513b, is the only case that passes every test, exhibiting a highly significant (>20 sigma) TTV signal with a periodicity, amplitude and shape consistent with that caused by an exomoon. Our analysis finds that this planet is 8.2_(-0.5)^(+0.7) R_⊕ orbiting at 0.53_(-0.03)^(+0.04) AU around a late G-type dwarf. After forecasting the planetary mass, we expect it to be capable of maintaining at least a 0.3 M_⊕ exomoon for 5 Gyr, and the TTV signal corresponds to a moon mass as low as 0.75 Lunar masses. We thus encourage follow-up observations and dynamical analysis of this unique signal, but caution skepticism until such data can be obtained.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections