TSO Documentation Tracker --- Cycle 6

Under section “Saturation in the context of JWST” 

Adjust Cycle 5 proposals link to Cycle 6 proposals. Or remove reference to save future effort.  

Under section “TSOs of very bright targets” 

Add description that NIRSpec will have Multistripe.

Slow axis direction of readout is incorrect, and MULTISTRIPE readout direction is also incorrect. Also means right reference pixels are the ones read out, not left. 

Expand section on minimizing contamination to also include description of offset strategy to place close binaries off of the POM

Consider any changes to multistripe warning:

"Science observing with the new SOSS multistripe subarrays will begin after successful commissioning, nominally at the start of Cycle 5. ETC signal-to-noise predictions will be refined, once on orbit data are available."

Add mention of multistripe subarrays

Additional description for reducing contaminating sources 

Additional description of number of exposures per dither in the APT section. 

See Jira ticket

Describe superstripe subarrays for Imaging Time Series.

NIRCam Short Wavelength Grism Time Series 

NIRCam Short Wavelength Grism Time Series Observing Strategies

Populate with relevant info and update/add figures with flight data after comm activities. 

NIRCam Short Wavelength Grism Time Series Observing Strategies

Review informational text and edit if needed:

"The use of the Dispersed .....  balancing integration time and data volume."

NIRCam Short Wavelength Grism Time Series

Review warning text note and edit if needed:

"Due to the complexities of new detector ......   the accuracy of the ETC and the pipeline during and after Cycle-3."

 Tracked under JDOXCM-750

Introduce new versions of Imaging and LRS subarrays

• Add the 4 new Prism multistripe subarrays to Table 2 
• "Exposure Specification" - explicitly mention that multistripe can only be used with NRSRAPID
• "Gain, sensitivity, and bright limiting magnitudes" - add new multistripe bright limits to Table 3 
• "What do BOTS mode data look like?" - add multistripe cartoon from cal forum presentation (or simulated multistripe spectrum) to this section + brief write-up on how we expect the time-series to look 

• Add the 4 new Prism multistripe subarrays to Table 2 
• Specify that 4 reference pixels are interleaved for multistripe and ref pix correction can be used for Prism multistripe observations 

•  Add section on multistripe readout

• "Exposures" - add a note that offsets can be seen at the exposure breaks, and suggest users to increase exp/dither as a workaround 

•  add section on Prism Multistripe readout (including details on interleaving reference pixels, size of the science pixels in the subarray, and timestamps on the time-series) 

•  Add Prism multistripe subarrays to Table 1 (since the smaller subarrays have do not coverage the full Prism wavelength range) 
• add wavelength coverage of multistripe subarrays to Fig 1?

•  Add new bright limits with the 4 Prism multistripe subarrays
• Add plot showing SNR vs bright limit 

•  Include multistripe as a consideration for obtaining broad wavelength coverage of bright targets (J < 11) 

•  Add Multistripe info to Table 1

•  Add page or section on "Considering bright limits and S/N for Prism multistripe subarrays"
  

•  Mention that parallel capabilities are being investigated during Cycle 5?

• Remove/reframe mention that integrations are treated as individual observations. 

• Add PandExo figure of the throughputs of the different modes as a function of wavelength  

• Add NIRSpec multistripe subarrays to Table 2

• under "TSOs roadmap - spectroscopy" Step 5, either add that multistripe modes are OR are not available in PandExo

• Add figure for example HGA move 
• Add description of what HGA move looks like in the time-series 

• Add mention of HGA header keyword that can be used to know if one happened during observation. (HGA_move = 'T' or 'F')

• Add figure for example tilt event (Alderson 2022 or Ahrer 2025). Maybe link to Marshall's TR for tilt events. 
• Figure 5 here is also a great example of what I happening in the LC, the FWHM changes, and physically what is going on with the mirror segments during a tilt event 

• Add comment that FGS timestamps don't necessarily line up with science time stamps 

• Intrapixel gain variations. Restructure slightly to make it immediately clear that these aren't expected to be a big issue.

• Reorder the noise sources in order of their relative impact, highest to lowest – e.g., 1/f first, pixel-to-pixel variations last 

• link to 1/f articles (e.g., NIRSpec 1/f removal article) or TR (e.g., SOSS TR) 

• "after which signals cannot be linearized" just links to the current page – need to re-word 

• "TSOs of very bright targets" - reframe mention of NIRISS multistripe subarrays to also include NIRSpec
• "Is it possible to use multistripe subarrays?" as a bullet point 
  • remove "It is important to note that NIRISS SOSS serves as a special case, as new multistripe subarrays have been designed for implementation in Cycle 5 that are capable of observing any transit host without saturation."

placeholder: noise sources for multistripe observations (if we find one)