Chrome Extension
WeChat Mini Program
Use on ChatGLM

A systematic validation of hot Neptunes in TESS data

Christian Magliano, Giovanni Covone, Richa Dobal, Luca Cacciapuoti, Luca Tonietti, Steven Giacalone, Jose Vines, Laura Inno, James S. Jenkins, Jack J. Lissauer, Allyson Bieryla, Fabrizio Oliva, Isabella Pagano, Veselin Kostov, Carl Ziegler, David R. Ciardi, Erica J. Gonzales, Courtney D. Dressing, Lars A. Buchhave, Steve B. Howell, Rachel A. Matson, Elisabeth Matthews, Alessandra Rotundi, Douglas Alves, Stefano Fiscale, Riccardo M. Ienco, Pablo Pena, Francesco Gallo, Maria T. Muscari Tomajoli

Monthly Notices of the Royal Astronomical Society(2022)

Cited 3|Views27
No score
Abstract
We statistically validated a sample of hot Neptune candidates applying a two-step vetting technique using DAVE and TRICERATOPS. We performed a systematic validation of 250 transit-like events in the Transiting Exoplanet Survey Satellite archive in the parameter region defined by P <= 4d and 3R(circle plus )<= R <= 5R(circle plus )?. Through our analysis, we identified 18 hot Neptune-sized candidates, with a false positive probability < 50 per cent < 50 per cent?. Nine of these planet candidates still need to be confirmed. For each of the nine targets, we retrieved the stellar parameters using ARIADNE and derived constraints on the planetary parameters by fitting the light curves with the juliet package. Within this sample of nine candidates, we statistically validated (i.e. with false positive probability < 0.3 per cent < 0.3 per cent?) two systems (TOI-277 b and TOI-1288 b) by re-processing the candidates with TRICERATOPS along with follow-up observations. These new validated exoplanets expand the known hot Neptunes population and are high-priority targets for future radial velocities follow-up.
More
Translated text
Key words
techniques: photometric,planets and satellites: detection,planets and satellites: general
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined