Mission Overview
TESS Light Curves From Full Frame Images ("TESS-SPOC")
Primary Investigator: Douglas A. Caldwell
HLSP Authors: Douglas A. Caldwell, Jon M. Jenkins, Eric B. Ting, Peter Tenenbaum, Joseph D. Twicken, Jeffrey C. Smith, Christina Hedges, Michael M. Fausnaugh, Christopher J. Burke, Bill Wohler
Released: 2020-11-12
Updated: 2024-10-24
Primary Reference(s): Caldwell et al. 2020
Citations: See ADS Statistics
Overview
Since the start of the TESS Mission, the TESS Science Processing Operations Center (SPOC) pipeline has been used to calibrate full-frame images (FFI) and to assign world-coordinate system information to the FFI data delivered to the MAST. The SPOC pipeline has generated target pixel files, light curves, and associated products from two-minute cadence target data, but not from FFIs (Jenkins, et al. 2016). Data provided with this release extend the SPOC pipeline processing to include targets selected from the FFIs to create target pixel and light curve files for up to 160,000 targets per sector.
Targets are selected from the FFIs using the TESS Input Catalog (TIC; Stassun et al. 2019) with a maximum of 10,000 targets per Sector on each of the sixteen TESS CCDs. Selection criteria include all two-minute cadence targets, targets bright in the near-infrared (H magnitude <=10), targets within 100 parsecs, and targets with TESS magnitude <=13.5. Details of the target selection are given in (Caldwell et al. 2020). The data products for the TESS-SPOC FFI targets are the same as for the two-minute cadence targets: calibrated target pixel files, simple aperture photometry flux time series, presearch data conditioning corrected flux time series, and cotrending basis vectors (CBV) sampled at the FFI cadence. The initial release includes TESS-SPOC FFI data products for the TESS northern hemisphere Sectors 14-26.
Data Validation Products Introduced With Sector 36 Release
Beginning May 2021, the TESS-SPOC pipeline processing was extended to run planet search on TESS-SPOC FFI targets to identify Threshold Crossing Events (TCEs). Starting with Sector 36, in addition to the light curve and target pixel files for all targets, there are TESS-SPOC FFI Data Validation (DV) products similar to those generated for two-minute cadence target data for those targets with a detected TCE. Due to longer data collection time for FFIs, the minimum transit pulse duration used in the search is 2 hours, versus 0.5 hours for two-minute cadence data. The maximum pulse duration is 15 hours for both two-minute and FFI data. TESS-SPOC FFI transit searches are only performed on a single sector at a time.
DV products are generated for TESS-SPOC FFI targets with Threshold Crossing Events (TCEs) and are summarized in the TESS Archive Manual section 2.0 Data Products Overview: Planet Search Products. For each target, there is a DV Results XML file, a DV Time Series FITS file, a human-readable full DV Report PDF, and a human-readable mini DV report PDF. For each TCE detected on the target, there is a corresponding TCE summary report PDF. The detailed content of each of these products is the same as that for two-minute cadence data and is described in the TESS Science Data Products Description Document, Sections 10-15. Only those targets that have detected TCEs have DV products generated, thus, not all TESS-SPOC light curves will have associated DV files.
Data Products
The light curve and target pixel files have the following file naming convention:
hlsp_tess-spoc_tess_phot_<tid>-<sector>_tess_v1_<type>.fits
where:
- <tid> = The full, 16-digit, zero-padded TIC ID.
- <sector> = The Sector represented as a 4-digit, zero-padded string, preceded by an 's', e.g., 's0026' for Sector 26.
- <type> = 'lc' for the light curve and 'tp' for the target pixel files.
The co-trending basis vector (CBV) files have the following file naming convention:
hlsp_tess-spoc_tess_phot_<cam>-<ccd>-<sector>_tess_v1_cbv.fits
where:
- <cam> = The Camera number, one of {1, 2, 3, 4}.
- <ccd> = The CCD number, one of {1, 2, 3, 4}.
- <sector> = The Sector represented as a 4-digit, zero-padded string, preceded by an 's', e.g., 's0026' for Sector 26.
The CBV bundles have the following file naming convention:
hlsp_tess-spoc_tess_ffi_<sector>_tess_v01_<type>-bulk-dl.<exten>
where:
- <sector> = The Sector represented as a 4-digit, zero-padded string, preceded by an 's', e.g., 's0026' for Sector 26.
- <type> = "cbv" for the CBV bundles.
- <exten> = The file type, either "tar.gz" or "sha256".
The data validation files have the following naming convention:
hlsp_tess-spoc_tess_phot_<tid>-<sector_start>-<sector_end>_tess_v1_<dvtype>.<exten>
where:
- <tid> = The full, 16-digit, zero-padded TIC ID.
- <sector_start> = The Sector used as the starting Sector for the planet search, represented as a 4-digit, zero-padded string, preceded by an 's', e.g., 's0036' for Sector 36.
- <sector_end> = The Sector used as the ending Sector for the planet search, represented as a 4-digit, zero-padded string, preceded by an 's', e.g., 's0036' for Sector 36.
- <dvtype> = The type of data validation file, one of {"dvm", "dvr", "dvs-<tce>", "dvt"}. NOTE: <tce> represents the TCE number as a zero-padded, two-digit integer.
- <exten> = The file type, one of "pdf", "xml", or "fits"
Data file types:
| _lc.fits | Light curve file. |
| _tp.fits |
Target pixel file. |
| _cbv.fits | Co-trending Basis Vector file. |
| _bulk-dl.tar.gz | All TESS-SPOC CBV files for a given Sector. |
| _bulk-dl.sha256 | SHA256 checksum to verify successful download of the tar.gz file. |
| _dvm.pdf | The "mini" DV report. |
| _dvr.pdf | The full DV report. |
| _dvs-<tce>.pdf | The TCE summary report for TCE number <tce> for this target. |
| _dvr.xml | The DV result XML. |
| _dvt.fits | The DV time series. |
Data Access
-
A web-based interface for cross-mission searches of data at MAST or the Virtual Observatory. Download TESS-SPOC light curves for a few targets.
-
Search for, and retrieve, TESS-SPOC data products programmatically based on a list of coordinates or target names.
Tips On Using Portal and astroquery.mast With TESS-SPOC Data
How Do I Do A Search For Only Mission-Produced Light Curves, Only TESS-SPOC Light Curves, Or Both?
I Have One Or More Targets With Known TIC IDs, How Do I Retrieve The Light Curves For Them Efficiently?
Sector Availability
Bulk download shell scripts that use curl are provided to download every light curve (LC), target pixel (TP), or set of data validation files (DV, starting with Sector 36) for a given Sector, for those who need to download many files per Sector. When fully downloaded, the total data volume on disk (target pixel + light curve + data validation) for a single Sector is large (~650 GB for Sectors 1-26, and ~1.8 TB for the Extended Mission Sectors, beginning with Sector 27). These data are also available in the MAST Portal and through MAST APIs like astroquery.mast.
Each Sector also has a tar bundle (and an associated checksum file) available for download that contains the CBV files for that Sector; the CBV bundles are not very large.
Target List files are provided that contain the TIC ID, RA (J2000, deg), and Dec (J2000, deg) for targets that have TESS-SPOC target pixel files created. Most, but not all, also have light curve files created for them. For users with very large target lists, it is recommended you download these .csv files first to cross-match with your list of targets BEFORE you query MAST to search for and download TESS-SPOC data products.
| Year 1 (Sectors 1-13) | Year 2 (Sectors 14-26) |
|---|---|