× Sector 13 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.

× Warning for Sector 13: There is a star tracker anomaly that causes the spacecraft to fall out of fine pointing for approximately 1.25 hours from TJD 1665.2983 to 1665.350. During this time, the spacecraft exhibited increased pointing jitter.

Sector 13 Information

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

Sector Summary

Sector dates: June 19 to July 17 2019

Pointing: Southern hemisphere

Days of Science Data Collection: 27.51

Days of Paused Data Collection: 0.93

Spacecraft Pointing (deg)

	RA	dec	roll
Spacecraft	298.67	-76.33	198.94
Camera 1	284.05	-40.9	275.82
Camera 2	289.59	-64.68	280.33
Camera 3	357.94	-85.5	167.75
Camera 4	90.01	-66.56	258.88

Orbit Summary

Orbits	Dates (UTC) Start - End	Cadence # Start - End	Momentum dumps
33	2019-06-19 - 2019-07-03	307051 - 316969	Every 3.375 days
34	2019-07-04 - 2019-07-17	317638 - 327529	Every 3.375 days

Sector Notes

Noted Issue	Description
Star tracker anomaly	There was a single upset in the star trackers on the spacecraft bus. This resulted in a complicated interaction between the instrument quaternions and attitude control system. This interaction caused the spacecraft to fall out of fine pointing for approximately 1.25 hours from TJD 1665.2983 to 1665.350. During this time, the spacecraft exhibited increased pointing jitter - see page 3 of the DRN for more information.
Spacecraft pointing	Due to the proximity of the Moon to the boresight of Camera 1, guiding with Camera 1 was disabled and Camera 4 alone was used for guiding in all of orbit 33. In Orbit 34, both Camera 1 and Camera 4 were used for guiding for the entire duration of the orbit.
Scattered light	In Sector 13, the main stray light features are caused by the Moon and Earth in the first three quarters of each orbit.

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).