Papers › The Transiting Exoplanet Survey Satellite: Simulations of planet detections and...
The Transiting Exoplanet Survey Satellite: Simulations of planet detections and astrophysical false positives
Peter W. Sullivan, Joshua N. Winn, Zachory K. Berta-Thompson, David Charbonneau, Drake Deming, Courtney D. Dressing, David W. Latham, Alan M. Levine, Peter R. McCullough, Timothy Morton, George R. Ricker, Roland Vanderspek, Deborah Woods
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.
The Transiting Exoplanet Survey Satellite (TESS) is a NASA-sponsored Explorer mission that will perform a wide-field survey for planets that transit bright host stars. Here, we predict the properties of the transiting planets that TESS will detect along with the eclipsing binary stars that produce false-positive photometric signals. The predictions are based on Monte Carlo simulations of the nearby population of stars, occurrence rates of planets derived from Kepler, and models for the photometric performance and sky coverage of the TESS cameras. We expect that TESS will find approximately 1700 transiting planets from 200,000 pre-selected target stars. This includes 556 planets smaller than twice the size of Earth, of which 419 are hosted by M dwarf stars and 137 are hosted by FGK dwarfs. Approximately 130 of the R < 2 R_⊕ planets will have host stars brighter than K = 9. Approximately 48 of the planets with R < 2 R_⊕ lie within or near the habitable zone (0.2 < S/S_⊕ < 2), and between 2-7 such planets have host stars brighter than K = 9. We also expect approximately 1100 detections of planets with radii 2-4 R_Earth, and 67 planets larger than 4 R_⊕. Additional planets larger than 2 R_⊕ can be detected around stars that are not among the pre-selected target stars, because TESS will also deliver full-frame images at a 30-minute cadence. The planet detections are accompanied by over one thousand astrophysical false positives. We discuss how TESS data and ground-based observations can be used to distinguish the false positives from genuine planets. We also discuss the prospects for follow-up observations to measure the masses and atmospheres of the TESS planets.
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="1506.03845")
Code
Syntology Ran 0 of 1 code samples harvested from 1 repository linked to this paper; 1 has no recorded run.
By repository: community (archive-listed): 1 sample 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
1 sample harvested; 0 ran; 0 honoured the contract we drafted; 1 has 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 1 sample 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 lgbouma/tessmaps. “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.
2dddac1a39e5434a · 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