× Sector 6 was reprocessed in May 2021, updating the background correction, manual exclude flags, timestamps, and input catalog. For more deatil please see the Reprocessing Information table below.

Sector 6 Information

For full data release notes see: DRN8, DRN42 (reprocessing). For a list of TIC IDs with noted issues, see this list

Sector Summary

Sector dates: December 12 2018 to January 6 2019

Pointing: Southern hemisphere

Days of Science Data Collection: 20.68

Days of Paused Data Collection: 1.09

Spacecraft Pointing (deg)

	RA	dec	roll
Spacecraft	92.01	-30.58	178.64
Camera 1	92.81	5.41	268.82
Camera 2	92.31	-18.59	268.76
Camera 3	91.62	-42.58	88.41
Camera 4	89.99	-66.56	87.05

Orbit Summary

Orbits	Dates (UTC) Start - End	Cadence # Start - End	Momentum dumps
19	2018-12-12 - 2018-12-24	171185 - 179687	Every 3.125 days
20	2018-12-25 - 2019-01-06	180468 - 189064	Every 3.125 days

Sector Notes

Noted Issue	Description
Data Collection	The first ∼3 days (start 2018-12-15 UTC) of orbit 19 were used to collect calibration data for measuring the pixel-response function of the cameras under the improved pointing system.
Scattered light	In Sector 6, the main stray light features are caused by the Earth rising above the sunshade at the end of orbit 19, which continues through the start of orbit 20.
TJD Calculation	The clock kernel used to calculate TJD in Sector 6 used ranging data collected only through late August, 2018; as a result, the extrapolation to Sector 6 times is slightly off. The error between true and calculated times grew linearly with time since August 2018, so that the calculated TJD values in all data products are offset from the correct values by ∼2.0 seconds at the end of orbit 20 (2019-01-06 UTC). See pg. 7 of the DRN for more information.

Reprocessing Information: DRN42

During TESS’s primary mission several updates were made to various instrument models, algorithms, and pipeline parameters. Below we list what was updated and applied when reprocessing sectors 1-13. Please see DRN42 for a more comprehensive explanation of each update.

Update	Description
Instrument models updated:	Electronics model Reference Flux, PRF, and Linearity
Calibration Pipeline Module updates:	The 1D bias estimate is now split into two components, a time-dependent scalar correction and a static row-dependent correction. The first two overclock rows were also removed. The propagation of the uncertainty from the 2D bias model was changed. It is a static term and no longer applied to pixel data.
Pre-Search Data Conditioning Pipeline Module updates:	The parameters to calibrate the PDC goodness metrics were finalized.
Transiting Planet Search Pipeline Module updates:	An initial run of TPS is now used to identify problematic epochs that are assigned “deemphasis weights” in a second and final run of TPS.
Compute Optimal Aperture Pipeline Module updates:	The photometric apertures for stars with Tmag less than 11 were slightly increased.
Photometric Analysis Pipeline Module updates:	The sky background estimate was modified. A scalar offset is now applied that forces the dimmest background-corrected pixels to values near zero, if those pixels were significantly negative.
TESS Input Catalog update:	Targets were reprocessed with version 8 of the TIC. The change affected the apertures assigned to individual targets and the calculations for crowding (CROWDSAP) and flux fraction (FLUXFRAC), and as such the physical properties of TCEs derived from stellar parameters.
Timestamps update:	Timestamps were updated to account for previous drift errors and electronic effects. All data from Sectors 1–36 are now registered to a consistent time system.
New data flags:	All flags are now consistent with those described in DRN30.
Threshold Crossing Event issues:	The planet search of the reprocessed light curves produced a different set of TCEs from the original processed data. There is a high degree of overlap, but not every TCE from previous data releases was recovered. To differentiate between the initial release and this reprocessed data a "pipeline instance number" is included in the filenames of the dv-timeseries, dv-reports, ad dv-result xml files. Larger pin numbers indicate later versions of the software were used to produce the data products. The DR number is also included as a keyword in the export product headers (DATA_REL).