Papers › Orbital Stability of Circumstellar Planets in Binary Systems
Orbital Stability of Circumstellar Planets in Binary Systems
Billy Quarles, Gongjie Li, Veselin Kostov, Nader Haghighipour
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.
Planets that orbit only one of the stars in stellar binary systems (i.e., circumstellar) are dynamically constrained to a limited range of orbital parameters and thus understanding conditions on their stability is of great importance in exoplanet searches. We perform ∼700 million N-body simulations to identify how stability regions depend on properties of the binary, as well as, the starting planetary inclination and mean longitude relative to the binary orbit. Moreover, we provide grid interpolation maps and lookup tables for the community to use our results. Through Monte-Carlo methods we determine that planets with a semimajor axis aₚ ≲8% of the binary semimajor axis a_(bin) will likely be stable given the known distribution of binary star parameters. This estimate varies in the Lidov-Kozai regime or for retrograde orbits to 4% or 10% of a_(bin), respectively. Our method to quickly determine the circumstellar stability limit is important for interpreting observations of binaries using direct imaging with JWST, photometry with TESS, or even astrometry with Gaia.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1912.11019")
Code
Syntology Ran 0 of 15 code samples harvested from 1 repository linked to this paper; 15 have no recorded run.
By repository: official repository: 15 samples from 1 repository, 0 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
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
15 samples harvested; 0 ran; 0 honoured the contract we drafted; 15 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.
Licence: 0 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from saturnaxis/ThreeBody_Stability. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
b40550b168724b33 · report
1746065b601bb547 · report
bff506809520a700 · report
41bdd146089cc571 · report
83bff15f1d155792 · report
d7e7323e7d1c25d7 · report
3362fadd5effb216 · report
7dbdcbccd773f557 · report
a4865c749c397ded · report
0a9c60755c336725 · report
06fe9559c634000c · report
64df6276c7d18b00 · report
2815c2092b6692cd · report
406b57901b2af776 · report
7bd73f60b4320d4f · report
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