返回资讯中心
外部精选
软件工程
#开发者实时流

I may have discovered a new exoplanet using Claude

Using AI to (probably) discover an exoplanet.

Hacker News 最新specbug2026/10/18 · 2026/10/1830 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Using AI to (probably) discover an exoplanet.

Contents

The Watcher

Light Reading

Clocking Laps

Stellar Characterization

Is It a Bird? Is It a Plane?

The Art of Divination

Acknowledgements

DisclaimerI'm no astronomer and would appreciate a professional pair of eyes. If you can help, please drop a note at rishitv@protonmail.com.

There is a star in the southern constellation Triangulum Australe, 218 light-years away. It dims by 0.21% for five hours, every 36.34 days. As far as I can tell, this dip has gone unreported throughout human history, and if my analysis holds true, reveals a planet 3.75x the size of Earth.

I'm not an astronomer. Quite typically, I started out as an aspiring astronaut, which morphed into astronomy, astrophysics, fundamental physics, and finally settled into computer science & programming, and as this post is my witness, into AI cajoling. Last week, I may have come full circle when I employed such AI prowess to (probably) discover an exoplanet, in a system far far away!

It is still a candidate, which is to say a guess, and as Feynman said:

It doesn't make a difference how beautiful your guess is. It doesn't make a difference how smart you are, who made the guess, or what his name is. If it disagrees with the experiment, it's wrong.

So I have published predictions of the next transits, along with the pre-registered tests that will strengthen or disprove my hypothesis. The relevant dataset, code, ephemeris and predictions are attached at the end.

This blogpost is an attempt to distill my findings, primarily for self-directed learning. It also contains background on how I used Claude to look centuries into the past at something I may never see.

Our candidate planet orbits the star TIC 402710280. TESS is NASA's exoplanet survey satellite, and its TESS Input Catalog (TIC) records over 1.7B objects. The star number, as far as I can tell, is a surrogate primary key assigned during batch processing.

TESS has been stargazing since 2018. Each of its four cameras can capture a 16.8 MP snapshot of an average constellation, covering a 24° x 96° total field of view, or an Observation Sector. TESS tiles the celestial sky into several sectors (over 100 so far) and stares at each sector for about 27 days. For roughly 20,000 selected stars it records brightness every two minutes; for everything else in the field it saves full-frame images (FFIs) at a slower cadence. Our star never made the two-minute list, so this analysis relies almost entirely on FFIs.

TESS "sees" a planet by the shadow it casts upon us, much like you would see a moth flitting across a distant streetlamp. Such transits appear as small dips in the star's total brightness. The depth of the dip is roughly the fraction of the star's disc the planet covers, the ratio of their areas:

Earth crossing the Sun would dim it by 84 parts per million; Jupiter about 1%. Our candidate blocks 0.21% of its star's flux.

We can plot a star's light curve (the graph of its brightness over time) to look for such transits. A single dip may be a fluke (a cosmic ray, a wobble of the spacecraft, sunlight scattered off the Earth), so you want dips that repeat at a fixed period before inferring anything in orbit. Even then, it could result from the star's dark spot rotating into view or eclipsing binaries. The 27-day sector rotation also makes it harder to find planets with a longer orbital period, since TESS only revisits the patch once every year or two.

TESS sends images back home, not light curves. But that's alright, we can turn an image into a brightness measurement by the way of photometry, and there are several techniques to do it. A typical technique is to sum up the pixels around a star (within some aperture) and subtract the background sky noise, to get a star's brightness. Run this for each of the ~12k images in a sector, sort the values by time, and you have the star's light curve.

Keep iterating for every star, in every image, over eight years, and you get a search space of over pixel measurements. Pipelines like QLP orchestrate this photometry at scale and publish light curves for millions of stars, with one light curve per star per sector. We evaluated over 10 million of these public light curves.

Once you have a light curve, you still need to detect a transit programmatically. One approach is to use a window of width (say, 5 hours) and slide it across the light curve. At each step, average the points inside the window and subtract that from the average just outside it, on either side. If the inside is darker than the outside by some threshold, flag it as a potential transit.

The window width is a hyperparameter – too short and you get false positives; too long and the average dilutes to missed signals. We looped through ten widths, from 45 mins to 18 hrs, and flagged anything above 6σ.

Six sigma sounds strict, but ten million light curves across ten window widths and a thousand positions per light curve result in measurements. Even pure gaussian noise could lead to hundreds of false positives at that rate. Real data is obviously more messy, but we can estimate the FPR by running the calculation twice: once on the light curves, and once on the same light curves flipped upside down. Noise makes fake troughs and fake peaks ~equally often, but a flipped light curve can't contain a real transit.

We can employ more tactics to weed out further impostors:

All of this, and more, left us with 2,263 stars with at least one clean dip.

The TESS magnitude () is the measure of a star's brightness in the red-to-near-infrared band, as estimated from other surveys (e.g., Gaia). We restrict our samples to stars with (lower is brighter), since fainter stars yield lower flux and higher noise. This reduced our search space to 142 stellar candidates (we converged upon such a threshold as to keep the final count manageable).

We then scoured reliable data sources to compile available information:

Candidates with known correlates (candidates, planets, eclipsing binaries) were ruled out. Which left 27 candidates with a dip or two, that yet remain elusive to the human archive.

We ignored 13 of the 27 candidates, since they marked only a single dip in our data. Of the rest, we couldn't derive consistent orbital motion for 12 of them: either they fit several periods equally well, or fit no period consistent with the transit length. So we excluded those 25 as well. And then there were two, each with a single, clean period.

So far, we've treated a transit as a spherical cow, but astronomers also care about the transit chord, i.e., the points at which an object cuts through the star. The impact parameter, is defined by the proximity of the transit path to the centre. when the object passes through the centre, while a path that nicks the rim has . Grazing transits are ambiguous, because the same dip fits multiple explanations (could be another star clipping the edge or a planet wholly transiting). TIC 447447071 has a periodic dip every 33.7 days. However, its transit nicks the edge with , and with Gaia suggesting a variable star velocity (possibly due to a companion star), it was dropped from consideration.

And thus we arrive at our champion candidate, TIC 402710280.

These are the four transits of TIC 402710280:

The data from Sectors 100 and 102 were captured in early 2026 and had no public light curves yet, so we produced our own (using the photometry technique you surely recall, dear reader). Sector 66 would have added a fifth transit and tightened the period estimates, but alas, it fell prey to sheer randomness; sunlight scattered off the Earth and Moon flooded the cameras around the transit, and MIT's QLP pipeline flags that stretch of data as unreliable.

To extract the orbital period from the transits, we first estimate the number of orbits between the different transit observations. A planet on a fixed orbit transits at

The time gaps between consecutive transit observations:

Suppose the shortest gap is exactly one orbit, and count the orbits across observations:

Whole number orbits lend strength to our assumed orbital period . However, they would hold equally true for half or third of it ( or ). Each of these shorter periods predict extra transits, and we can evaluate the light curve on those dates (fortunately, TESS was paying attention on some of those dates). We find no statistically significant transit for any of them, so our shortest gap spans exactly one orbit.

The gap is only an approximation. To pin it down, we plot each transit's mid-time against its epoch. The slope is the period. The best-fitting line is the one that minimizes

where is each transit's timing uncertainty.

Thus we established the orbital period of the object transiting TIC 402710280:

While this linear model forms a good baseline, it assumes a perfectly constant orbital period. To test that, astronomers compare the observed transit time against the model's prediction:

Each transit is boxed to 2 or 3 mins, so these offsets are ~10x larger than expected. We can think of two explanations to these residual transit time variations:

Either way, while the transits stand; we're uncertain about their timing. The next few (predicted) transits shall explain this better.

To learn about a planet, it is useful (and quite poetic) to start with its star.

ESA's Gaia satellite measures the apparent displacement of nearby stars due to a change in the Earth's point of view (revolution). This shift (parallax) is inversely proportional to the star's distance:

For TIC 402710280, Gaia cataloges , which puts the star 66.8 parsecs, or 218 light-years away. The star's distance and its apparent brightness reveal its luminosity. The flux we receive is , which gives a luminosity of (solar luminosity). TIC lists the star's surface temperature at K (the Sun is 5770 K). Luminosity, temperature and size are tightly coupled, since every patch of the star's surface radiates according to its temperature:

Solving for the radius gives : a smaller, cooler K dwarf, about 0.88 times the mass of our Sun.

We went through this effort to create a reference baseline to size our object. The dip depth is measured in the ratio of their radii:

So the object is 3.75 times Earth's radius (Neptune is 3.88), just the right size for a planet.

Using Kepler's third law (measured in AU), we can estimate the distance of the planet from its star:

That's about half as far as Mercury is from the Sun. To cover that orbit every five weeks (five-week years!) it must move at twice Earth's orbital velocity (62 km/s).

ten times Earth's sunlight, which would lead it to an equilibrium temperature of a balmy 227 °C.

A planet this large would also trap a thick atmosphere (and heat), so is probably warmer. Even the smallest stars are three times larger, so this safely rules out a companion star (so long as the dip originates from TIC 402710280).

Going by typical size-to-mass relations, it would weigh about 14 Earths, although there are, of course, no recorded measurements as yet. While there are sub-Neptunes aplenty, our solar system hosts none and so we don't quite know enough about the composition of such planets. The planet is heavy enough to tug its star by about 2.8 m/s as it orbits, which should be detectable by ESPRESSO. Knowing the mass and radius would give us its density, which could unearth clues about its true composition.

Source: https://tess.mit.edu/tess-planet-count/

About 70% of settled TOI turn up false positives. So we must strive to make a best effort at falsifying this incredible observation.

The usual impostor is a blended eclipsing binary: a gravitationally bound pair of stars undergoing mutual eclipses, nearly collinear with our star along the line of sight. Each TESS pixel represents

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →