Issue Tracker

Optimal background subtraction needs to be decided upon and implemented in CALTSO3

• Optimal TSO Spectral Background Subtraction
  

Continuous Integration / Unit testing

• We need to develop a standard set of tests that automatically run on the calibration pipeline whenever there is an update.

ISIM clock is not precise enough for TSO, need to use FPE clock for relative time and S/C clock for reference point

Target acquisition needs to be implemented in APT

For LRS slitless: complete.

(Note: small snafu in APT 26.1beta, will be addressed with PR 90948 hopefully for the 26.1 release version)

For Imaging: work approved but not yet scheduled for implementation (as of 07/2018); expected to be available for cycle 1.

For MRS: complete.

Enable TSO mode for MIRI imaging

Tests show long persistence ramp in TSO data, no easy means to pre-flash detector

• Do we need tests during commissioning?

Enable MRS TSO mode

• Caution: data volumes could be too high

Telescope roll may be an issue with MRS

• FGS holds position, but not roll angle
• Large distance of MRS from rotation axis could cause deviations of several pixels over the course of an observation

Enable SW DHS spectroscopic mode

Enable narrow-band filter option for target acquisition

Enable TA on saturated targets

How do we ensure the target falls in the 1.6” aperture before TA?

• Enable 4-point mosaic to increase field of view

Enable WATA on saturated targets

Enable WATA with NGROUPS=1 or 2

Enable mode to use F277W filter to remove spectral overlap as a calibration

Need bias and 1% saturation levels to make target fluence recommendation to observers

NIRCam recommendation: ~35k ADU

No values from other teams

List brightest pixel fluence in output

APT only asks for transit ephemeris in HJD

• Want to enable option for BJD

APT may be slow to run Visit Planner for short period planets

• Visit planner in APT 25.4.4 gets stuck (or is slow) for some short-period planets
• Karla Peterson and Everett worked out a solution where he multiplied the planet period by 5 and then it works pretty smoothly and since the period is so short there are still plenty of starting windows.
• If this problem persists in APT, perhaps we should have a note somewhere in JDox (and/or APT) that explains this workaround (multiply the period by a small integer) to users for short period ephemerides?

For very long exposures, the APT visit planner fails to satisfy the phase constraint.

• See JWST program 1201 (NEAT), observation 11 (phase curve observation of WASP-121b)
• The phase constraint is correctly set, but the calculated visibility periods do not satisfy it.
  
• The problem appears whenever t_exp > P - w -1048, where t_exp is the total exposure time, P is the planet period, and w is the time width of the of the observing start window specified in the phase constraint, all in seconds.
  

PR 90539

Resolution: We are *not* planning to change JWST's VSS/JCL to change the way it deals with Phase constrained observations. We *are* planning to have APT alert the user with a warning when the Phase constraint is lost due to the overlapping windows problem. We believe a handful of observations a year will face this issue and we can refer the user to documentation of workarounds in the APT warning.

Proposed workarounds:

1. The user doubles the period and recalculates the phase start and end to apply to only one of the two transits in that doubled period. (Downside: loss of half of the scheduling opportunities, but that shouldn't be a big deal since there are so many.)
2. The user could double the period and create two observations - one with the start and end time of the first transit and one with the start and end time of the second transit. The second observation could be put "on hold" in case it is needed for increased scheduling flexibility.
3. Create a short observation that can be correctly constrained and SEQ NON-INT it to the desired long TSO observation. This is a more elegant solution, but has more overheads associated with it.
4. Use a single tight Between to nail down the observation to a single transit. This would be helpful when coordinating the observation with another observatory.

David submitted a ticket (INC0058021)

Resolved