# TESS timing citation register

Status: citation register for method and context.

This register supports method and context only. It does not support a result
claim. Its scope is TESS mission, timing, transit-model, and archive context.
It is not a complete bibliography of `docs/TESS-PAPER.md`: the software and
analytic-model references used by that paper (Astropy Collaboration 2022,
Harris et al. 2020, Jenkins et al. 2016, Mandel and Agol 2002, and Virtanen
et al. 2020) are listed in the paper's own reference section and are not
duplicated here. It is not evidence that the repository's TESS timing work is novel, peer
reviewed, or a discovery. The entries here justify choices of data source,
software, and analysis method; they do not validate any measured mid-transit
time, ephemeris, or timing residual.

The register was compiled on 2026-10-22 from the references already checked in
`docs/PROBLEMS-DEEP.md` (D1 to D15). Every entry has a DOI, an arXiv identifier,
or a publisher or archive URL. Identifier syntax is checked offline by
`research/tess-timing/scripts/check_tess_refs.py`. Network resolution is opt-in
with `--fetch`, which checks DOIs through the Crossref API, arXiv identifiers
through the arXiv abstract page, and other URLs with an HTTP request.

No entry is a placeholder, and no entry is marked `UNVERIFIED`. An identifier
that cannot be resolved is not added to this register.

## Register

| Key | Citation | Identifier | Accessed | Supports |
| --- | --- | --- | --- | --- |
| TESS-01 | Ricker et al., "Transiting Exoplanet Survey Satellite", Journal of Astronomical Telescopes, Instruments, and Systems 1, 014003 (2015) | https://doi.org/10.1117/1.JATIS.1.1.014003 | 2026-10-22 | Mission context: instrument, orbit, cadence, and the public data model. It does not support a timing measurement. |
| TESS-02 | Guerrero et al., "The TESS Objects of Interest Catalog from the TESS Prime Mission", ApJS 254, 39 (2021) | https://doi.org/10.3847/1538-4365/abefe1 | 2026-10-22 | Context for confirmed and candidate transiting planets and for the scale of the TESS candidate sample. |
| TESS-03 | Ivshina and Winn, "TESS Transit Timing of Hundreds of Hot Jupiters", ApJS 259, 62 (2022) | https://doi.org/10.3847/1538-4365/ac545b | 2026-10-22 | Method context for mid-transit timing, ephemeris updates, and catalog-scale timing work. It is not a validation target for this repository. |
| TESS-04 | Wang et al., "Long-term Variations in the Orbital Period of Hot Jupiters from Transit-timing Analysis Using TESS Survey Data", ApJS 270, 14 (2024) | https://doi.org/10.3847/1538-4365/ad0847 | 2026-10-22 | Method context for long-baseline transit timing and period-change searches. |
| TESS-05 | Nabbie et al., "Transit-timing Variations in TESS: A Catalog from the First 5 yr", ApJS 285, 31 (2026) | https://doi.org/10.3847/1538-4365/ae7a34 | 2026-10-22 | Context for existing transit-timing coverage through TESS Sector 69 and for checking whether a sector is already covered. |
| TESS-06 | Naponiello, "A homogeneous transit-timing-variation investigation of all TESS systems with a confirmed single-transiting planet", A&A 705, A5 (2026) | https://doi.org/10.1051/0004-6361/202557512 | 2026-10-22 | Method context for homogeneous timing analysis of single-transiting systems. |
| TESS-07 | Agol and Fabrycky, "Transit Timing and Duration Variations for the Discovery and Characterization of Exoplanets in the TESS era", arXiv:1706.09849 (review, v4 2025) | https://arxiv.org/abs/1706.09849 | 2026-10-22 | Theory and precision-scaling context for transit timing and duration variations. |
| TESS-08 | Kreidberg, "batman: BAsic Transit Model cAlculatioN in Python", PASP 127, 1161 (2015) | https://doi.org/10.1086/683602 | 2026-10-22 | Transit model context: limb-darkened transit shapes and model parameter definitions. |
| TESS-09 | Lightkurve Collaboration, "Lightkurve: Kepler and TESS time series analysis in Python", ASCL 1812.013 (2018) | https://ascl.net/1812.013 | 2026-10-22 | Context for reading and handling TESS time-series products. |
| TESS-10 | Stassun et al., "The Revised TESS Input Catalog and Candidate Target List", AJ 158, 138 (2019) | https://doi.org/10.3847/1538-3881/ab3467 | 2026-10-22 | Context for stellar parameters, contamination checks, and target selection. |
| TESS-11 | Foreman-Mackey et al., "emcee: The MCMC Hammer", PASP 125, 306 (2013) | https://doi.org/10.1086/670067 | 2026-10-22 | Sampling method context for posterior inference. |
| TESS-12 | Foreman-Mackey et al., "exoplanet: Gradient-based probabilistic inference for exoplanet data and other astronomical time series", JOSS 6, 3285 (2021) | https://doi.org/10.21105/joss.03285 | 2026-10-22 | Inference method context for gradient-based transit fitting. |
| TESS-13 | NASA Goddard, "TESS Data Products Information" | https://heasarc.gsfc.nasa.gov/docs/tess/data-products.html | 2026-10-22 | Context for TESS target pixel files, light curves, cadence, quality flags, and product definitions. |
| TESS-14 | Mikulski Archive for Space Telescopes (MAST) | https://mast.stsci.edu/ | 2026-10-22 | Archive context for locating and retrieving public TESS products. |
| TESS-15 | NASA Exoplanet Archive | https://exoplanetarchive.ipac.caltech.edu/ | 2026-10-22 | Context for published ephemerides and planetary parameters used as priors or comparison values. |

## Counts

- Entries: 15.
- Distinct citations: 15.
- Entries covering the TESS mission: TESS-01, TESS-02, TESS-10.
- Entries covering transit timing: TESS-03, TESS-04, TESS-05, TESS-06, TESS-07.
- Entries covering transit modeling or inference: TESS-07, TESS-08, TESS-11, TESS-12.
- Entries covering the archive or MAST data products: TESS-13, TESS-14, TESS-15.

## Check

Run from the repository root:

```bash
python research/tess-timing/scripts/check_tess_refs.py
python research/tess-timing/scripts/check_tess_refs.py --fetch
```

The first command is offline and checks the table structure, unique and
non-empty keys, identifier syntax, access dates, and the absence of placeholder
markers. The second command resolves each identifier over the network and
prints the result. A failed resolution is a failure, not a warning to ignore.
