SEARCH · Search NASA

Results for “Threshold crossing events (TCEs”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

12 records

All sources NASA NTRS DOE OSTI

NASA NTRS2019

Kepler Data Validation II–Transit Model Fitting and Multiple-Planet Search

This paper discusses the transit model-fitting and multiple-planet search algorithms and performance of the Kepler Science Data Processing Pipeline, developed by the Kepler Science Operations Center (SOC). Threshold crossing events (TCEs), which are transit candidate events, are generated by the Transiting Planet Search (TPS) component of the pipeline and subsequently processed in the data validation (DV) component. The transit model is used in DV to fit TCEs to characterize planetary candidates and to derive parameters that are used in various diagnostic tests to classify them. After the signature associated with the TCE is removed from the light curve of the target star, the residual light curve goes through TPS again to search for additional TCEs. The iterative process of transit model fitting and multiple-planet search continues until no TCE is generated from the residual light curve or an upper limit is reached. The transit model-fitting and multiple-planet search performance of the final release (9.3, 2016January) of the pipeline is demonstrated with the results of the processing of four years (17 quarters) of flight data from the primary Kepler Mission. The transit model-fitting results are accessible from the NASA Exoplanet Archive. The final version of the SOC codebase is available through GitHub.

Threshold crossing events (TCEs↗

NASA NTRS2017

Description of the TCERT Vetting Reports for Data Release 25

The Q1Q17 DR25 TCERT Vetting Reports are a collection of plots and diagnostics used by the Threshold Crossing Event Review Team (TCERT) to evaluate threshold crossing events (TCEs). While designation of Kepler Objects of Interest (KOIs) and classification of them as Planet Candidates (PCs) or False Positives (FPs) is completely automated via a robotic vetting procedure (the Robovetter) for the Q1Q17 DR25 planet catalog, as described in Thompson et al. (2017), these reports help to visualize the metrics used by the Robovetter and evaluate those robotic decisions for individual objects. For each Q1Q17 DR25 TCE, these reports include the following products: (a) the DV one-page summary, (b) selected pertinent diagnostics and plots from the full DV report, and (c) additional plots and diagnostics not included in the full DV report, including an alternate means of data detrending.

Kepler Objects of Interest↗

NASA NTRS2010

Data Validation in the Kepler Science Operations Center Pipeline

We present an overview of the Data Validation (DV) software component and its context within the Kepler Science Operations Center (SOC) pipeline and overall Kepler Science mission. The SOC pipeline performs a transiting planet search on the corrected light curves for over 150,000 targets across the focal plane array. We discuss the DV strategy for automated validation of Threshold Crossing Events (TCEs) generated in the transiting planet search. For each TCE, a transiting planet model is fitted to the target light curve. A multiple planet search is conducted by repeating the transiting planet search on the residual light curve after the model flux has been removed; if an additional detection occurs, a planet model is fitted to the new TCE. A suite of automated tests are performed after all planet candidates have been identified. We describe a centroid motion test to determine the significance of the motion of the target photocenter during transit and to estimate the coordinates of the transit source within the photometric aperture; a series of eclipsing binary discrimination tests on the parameters of the planet model fits to all transits and the sequences of odd and even transits; and a statistical bootstrap to assess the likelihood that the TCE would have been generated purely by chance given the target light curve with all transits removed. Keywords: photometry, data validation, Kepler, Earth-size planets

Wu, Hayley↗

NASA NTRS2016

Kepler Data Validation Time Series File: Description of File Format and Content

The Kepler space mission searches its time series data for periodic, transit-like signatures. The ephemerides of these events, called Threshold Crossing Events (TCEs), are reported in the TCE tables at the NASA Exoplanet Archive (NExScI). Those TCEs are then further evaluated to create planet candidates and populate the Kepler Objects of Interest (KOI) table, also hosted at the Exoplanet Archive. The search, evaluation and export of TCEs is performed by two pipeline modules, TPS (Transit Planet Search) and DV (Data Validation). TPS searches for the strongest, believable signal and then sends that information to DV to fit a transit model, compute various statistics, and remove the transit events so that the light curve can be searched for other TCEs. More on how this search is done and on the creation of the TCE table can be found in Tenenbaum et al. (2012), Seader et al. (2015), Jenkins (2002). For each star with at least one TCE, the pipeline exports a file that contains the light curves used by TPS and DV to find and evaluate the TCE(s). This document describes the content of these DV time series files, and this introduction provides a bit of context for how the data in these files are used by the pipeline.

DV Time Series↗

NASA NTRS2017

Kepler Planet Detection Metrics: Robovetter Completeness and Effectiveness for Data Release 25

In general, the Kepler pipeline identifies a list of Threshold Crossing Events (TCEs), which are periodic flux decrements meeting certain criteria (Jenkins, 2017). These TCEs are reviewed and those that appear consistent with astrophysically transiting or eclipsing systems are classified as Kepler Objects of Interest (KOIs). Further review is given to KOIs, which are then dispositioned as Planet Candidates (PCs) or False Positive (FPs). FPs are further denoted by four major flags that indicate if the signal is Not Transit-Like (NTL), due to a Stellar Eclipse (SS; previously referred to as Significant Secondary), and/or due to contamination from a source other than the target as evidenced by a Centroid Offset (CO) oran Ephemeris Match (EM) with another object. This entire TCE review process is known as dispositioning or vetting.In the first five Kepler mission planet candidate catalogs (Borucki et al., 2011a,b; Batalha et al., 2013; Burke et al., 2014; Rowe et al., 2015), TCEs were manually examined on an individual basis and dispositioned using various plots and quantitative diagnostic tests (see e.g., Coughlin, 2017). In the sixth catalog, Mullally et al. (2015a) employed partial automation via simple parameter cuts to automatically disposition a large fraction of TCEs as not transit-like. Mullally et al. (2015a) also used an automated technique known as the centroid Robovetter (Mullally, 2017) to automatically identify some FP KOIs due to centroid offsets - a telltale signature of light contamination from another target. The remaining targets were manually dispositioned. In the seventh catalog, Coughlin et al. (2016) automated theentire dispositioning process using what is collectively known simply as the Robovetter.In the eighth and final mission catalog, Thompson et al. (2017) use a revised Robovetter to automate the dispositioning of all TCEs with an emphasis on creating a catalog suitable for accurately determining planet occurrence rates. In order to calculate accurate occurrence rates, the completeness and effectiveness of the Robovetter must be characterized. We define these terms as applied to the Robovetter, following Thompson et al. (2017), as:1. Completeness: The fraction of transiting planets detected by the pipeline that are classified as planet candidates by the Robovetter.2. Effectiveness: The fraction of false positives detected by the pipeline that are classified as false positives by the Robovetter.The remainder of this document describes products that can be used to quantitatively assess Robovetter completeness and effectiveness for an arbitrary set of Kepler stars.

Robovetter↗

NASA NTRS2010

Data Validation in the Kepler Science Operations Center Pipeline

We present an overview of the Data Validation (DV) software component and its context within the Kepler ScienceOperations Center (SOC) pipeline and overall Kepler Science mission. The SOC pipeline performs a transiting planetsearch on the corrected light curves for over 150,000 targets across the focal plane array. We discuss the DV strategy forautomated validation of Threshold Crossing Events (TCEs) generated in the transiting planet search. For each TCE, atransiting planet model is fitted to the target light curve. A multiple planet search is conducted by repeating the transitingplanet search on the residual light curve after the model flux has been removed; if an additional detection occurs, aplanet model is fitted to the new TCE. A suite of automated tests are performed after all planet candidates have beenidentified. We describe a centroid motion test to determine the significance of the motion of the target photocenterduring transit and to estimate the coordinates of the transit source within the photometric aperture; a series of eclipsingbinary discrimination tests on the parameters of the planet model fits to all transits and the sequences of odd and eventransits; and a statistical bootstrap to assess the likelihood that the TCE would have been generated purely by chancegiven the target light curve with all transits removed.

photometry↗

NASA NTRS2019

TESS Data Release Notes: Sectors 1 – 13, Multi-Sector Search, DR20

These Data Release Notes provide information on the processing and export of data from the Transiting Exoplanet Survey Satellite (TESS). This data release is a combined, multi-sector transit search only. The underlying data products from individual observing sectors have been previously released. The data products included in this data release are the Data Validation (DV) reports, time series, and associated xml les for the threshold crossing events (TCEs) found by searching a combined data set including data from multiple observing sectors. These data products were generated by the TESS Science Processing Operations Center (SPOC, Jenkins et al., 2016) at NASA Ames Research Center from data collected by the TESS instrument, which is managed by the TESS Payload Operations Center (POC) at Massachusetts Institute of Technology (MIT). The format and content of these data products are documented in the Science Data Products Description Document (SDPDD)1. The SPOC science algorithms are based heavily on those of the Kepler Mission science pipeline, and are described in the Kepler Data Processing Handbook (Jenkins, 2017)2. The Data Validation algorithms are documented in Twicken et al. (2018) and Li et al. (2019). The TESS Instrument Handbook (Vanderspek et al., 2018)3 contains more information about the TESS instrument design, detector layout, data properties, and mission operations. The TESS Mission is funded by NASA's Science Mission Directorate.

Burke, Christopher J.↗

NASA NTRS2020

TESS Data Release Notes: Sectors 14 – 23, Multi-sector Search, DR34

TESS↗

NASA NTRSDate not supplied

Primary Mission Threshold Crossing Events in the TESS SPOC Transit Search

We present an overview of the single- and multiple-sector results of the Science Processing Operations Center (SPOC) transit search in the primary Transiting Exoplanet Survey Satellite (TESS) mission. TESS was designed to survey bright stars in the greater Solar neighborhood in search of transiting exoplanets. Data were acquired at a 2-minute cadence for 16,000-20,000 pre-selected target stars in each 28-day observation sector and processed in the SPOC pipeline at NASA Ames Research Center. The photometry pipeline produced a systematic error corrected light curve for each target star. Light curves were searched for transiting planet signatures by sector for all target stars, and separately for target stars observed in multiple sectors. Potential transit signals for which the transiting planet detection threshold was exceeded and a series of transit consistency tests were passed are referred to as Threshold Crossing Events (TCEs). We highlight the full TCE population and the population of SPOC TCEs that were later identified as TESS Objects of Interest (TOIs). Characteristics of the TCE populations implied by limb-darkened transiting planet model fits are also presented. SPOC pipeline data products are delivered to the Mikulski Archive for Space Telescopes (MAST)(http://archive.stsci.edu/missions-and-data/tess) for access by the community. Funding for the TESS Mission has been provided by the NASA Science Mission Directorate.

TESS↗

NASA NTRS2021

TESS Data Release Notes: Sectors 1 – 36, Multi-sector Search, DR53

These Data Release Notes provide information on the processing and export of data from the Transiting Exoplanet Survey Satellite (TESS). This data release is a combined, multi-sector transit search only. The underlying data products from individual observing sectors have been previously released. The data products included in this data release are the Data Validation (DV) reports, time series, and associated xml files for the threshold crossing events (TCEs) found by searching a combined data set including data from multiple observing sectors. These data products were generated by the TESS Science Processing Operations Center (SPOC, Jenkins et al., 2016) at NASA Ames Research Center from data collected by the TESS instrument, which is managed by the TESS Payload Operations Center (POC) at Massachusetts Institute of Technology (MIT). The format and content of these data products are documented in the Science Data Products Description Document (SDPDD)1. The SPOC science algorithms are based heavily on those of the Kepler Mission science pipeline, and are described in the Kepler Data Processing Handbook (Jenkins, 2020)2. The Data Validation algorithms are documented in Twicken et al. (2018) and Li et al. (2019). The TESS Instrument Handbook (Vanderspek et al., 2018) contains more information about the TESS instrument design, detector layout, data properties, and mission operations. The TESS Mission is funded by NASA's Science Mission Directorate.

TESS↗

NASA NTRS2022

TESS Data Release Notes:Sectors 42 – 46, Multi-sector Search, DR68

TESS↗

NASA NTRS2022

TESS Data Release Notes:Sectors 1 – 46, Multi-sector Search, DR69

TESS↗