← Latest papers
🔭 astrophysics

Finding Circumbinary Planets: A Semi-Automated Transit Search of TESS Eclipsing Binaries

This paper introduces a semi-automated framework called monocbp{\tt mono-cbp} for detecting circumbinary planets in TESS eclipsing binary light curves, which successfully recovers over 50% of known transiting circumbinary planets and identifies one new candidate while demonstrating strong performance in simulated tests.

Original authors: Benjamin D. R. Davies, David J. A. Brown, Samuel Gill, Jenni R. French

Published 2026-04-13
📖 5 min read🧠 Deep dive

Original authors: Benjamin D. R. Davies, David J. A. Brown, Samuel Gill, Jenni R. French

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to find a tiny, dark moth flying past a pair of massive, flashing spotlights. That is essentially what astronomers are doing when they hunt for circumbinary planets—planets that orbit two stars at once.

This paper introduces a new, semi-automated "moth-hunting" tool called mono-cbp, designed to scan data from NASA's TESS space telescope to find these elusive worlds. Here is a breakdown of how they did it, using simple analogies.

The Challenge: Finding a Needle in a Haystack of Flashlights

Most planets orbit a single star. But some orbit two stars (like Tatooine in Star Wars). These are called circumbinary planets.

  • The Problem: The two stars are constantly eclipsing each other (one blocking the other), creating huge, bright dips in the light curve. A planet passing in front of them is like a tiny moth fluttering past a lighthouse; its shadow is incredibly faint compared to the stars' own "flashing."
  • The Complication: Unlike planets around single stars, these planets don't have a strict schedule. Because the two stars are dancing around each other, the planet's transit times shift wildly (like a train that is always late or early). This makes standard search algorithms, which look for perfect patterns, useless.

The Solution: The "Mono-CBP" Framework

The authors built a software pipeline to find these planets by looking for single, isolated events rather than a repeating pattern. Think of it like looking for a single drop of rain in a storm rather than waiting for a specific pattern of raindrops.

Here is how their "Mono-CBP" tool works, step-by-step:

1. The Noise-Canceling Headphones (Masking & Detrending)

First, the software has to ignore the massive "flashing" of the two stars.

  • Masking: They use a known schedule of the stars' eclipses to digitally "black out" those parts of the data. It's like putting a piece of tape over the bright parts of a photo so you can see the tiny details in the shadows.
  • Detrending: Stars aren't perfectly steady; they twinkle, spot, and pulse. The software uses a "cosine" and "biweight" filter (think of it as a sophisticated noise-canceling headphone) to smooth out the background wiggles so the tiny planet signal doesn't get lost.

2. The "One-Two Punch" Detector (The Search)

The software scans the cleaned-up light curve for any sudden dip in brightness.

  • It doesn't care if the dip happens once or twice. It just looks for a "threshold crossing event" (TCE)—a moment where the light drops significantly.
  • It can even spot a "one-two punch," where a planet passes in front of both stars in the same orbit, creating two dips close together.

3. The Bouncer at the Club (Vetting)

The search is very sensitive, so it catches a lot of "false alarms" (like a glitch in the camera or a star spot). The software acts as a bouncer with a checklist:

  • Is it a glitch? If the dip happens at the exact same time for thousands of other stars, it's a camera error, not a planet.
  • Is it a trend? If the dip looks like a slow slope rather than a sharp box, it's probably just the star breathing, not a planet.
  • The Model Match: The software tries to fit the dip into different shapes: a planet transit, a sine wave, or a sudden jump. If the "planet shape" fits best, it gets a "Candidate" badge.

The Results: One New Hope

The team applied this tool to 512 binary star systems from the TESS catalog.

  • The Catch: They found one promising candidate (TIC 319011894).
  • The Mystery: This system has two stars eclipsing every 8.3 days. There is a tiny, extra dip in the light that might be a planet. However, it could also be a trick of the light or a second, very faint eclipse. It needs more observation to confirm.
  • The Good News: They tested their tool on 14 known circumbinary planets (discovered by the Kepler mission). Even though TESS data is "noisier" than Kepler's, their tool successfully found more than 50% of the transits for every planet, and 75% for most of them. This proves the tool works!

Why This Matters

Finding these planets is hard because:

  1. They are rare: We only know of about 15 of them so far.
  2. They are unpredictable: Their orbits wobble, making them hard to track.
  3. They are faint: The planet's shadow is tiny compared to the stars.

This new framework is like a high-tech metal detector that can scan a beach for a specific type of coin, even if the waves are crashing and the sand is shifting. It allows astronomers to scan massive amounts of data quickly without needing a supercomputer for every single star.

The Bottom Line

The authors have built a reliable, semi-automated way to hunt for planets in binary star systems. While they only found one new candidate so far, the method is proven to work. As TESS continues to collect data and future telescopes (like PLATO) come online, this tool will help us build a bigger picture of how planets form in these chaotic, double-star neighborhoods.

In short: They built a smart filter to ignore the noise of dancing stars so we can finally hear the whisper of a planet passing by.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →