Constarium
← Search

Table · dataset · 2024

Validation of 69 exoplanets using ExoMiner V1.2

Listed in IVOA Registry (Virtual Observatory)

Most existing exoplanets are discovered using validation techniques rather than being confirmed by complementary observations.

Description

These techniques generate a score that is typically the probability of the transit signal being an exoplanet (y(x)=exoplanet) given some information related to that signal (represented by x). Except for the validation technique in Rowe et al. (2014), which uses multiplicity information to generate these probability scores, the existing validation techniques ignore the multiplicity boost information.

In this work, we introduce a framework with the following premise: given an existing transit-signal vetter (classifier), improve its performance using multiplicity information. We apply this framework to several existing classifiers, which include vespa, Robovetter, AstroNet, ExoNet, GPC and RFC, and ExoMiner, to support our claim that this framework is able to improve the performance of a given classifier. We then use the proposed multiplicity boost framework for ExoMiner V1.2, which addresses some of the shortcomings of the original ExoMiner classifier, and validate 69 new exoplanets for systems with multiple Kepler Objects of Interests from the Kepler catalog.

Links

Where it is published

Documentation and papers

Catalogue records · 2

Topics

Provenance · 1 source records, 7 field assertions
SourceKeyLast seenRaw
IVOA Registry (Virtual Observatory)ivo://cds.vizier/j/aj/166/288 d agoJSON v1
FieldAssertionExtractorEvidence
access_levelsource · IVOA Registryconnector:ivoa_registry@1.0.0
concepts[field].local:field:astronomymapping · IVOA Registryconnector:ivoa_registry@1.0.0
descriptionsource · IVOA Registryconnector:ivoa_registry@1.0.0rr.resource.res_description
license_textsource · IVOA Registryconnector:ivoa_registry@1.0.0
publication_datesource · IVOA Registryconnector:ivoa_registry@1.0.0
titlesource · IVOA Registryconnector:ivoa_registry@1.0.0rr.resource.res_title
updated_datesource · IVOA Registryconnector:ivoa_registry@1.0.0