Allowing Offset Special Requirements in NIRCam Grism TSO obs

[stscijgbot-jp]

Issue JP-3842 was created on JIRA by Bryan Hilbert:

Currently, APT allows you to add an Offset SR to a NIRCam Grism Time Series observation. Not long ago, the pipeline was updated to be able to calculate where the trace will land within the aperture for a given Offset. However, only the offset in the x direction was used. Any provided y offset is ignored, and the pipeline assumes that the trace is in the standard location, at row 34. (See JP-3595 for the discussion about this.)

I think we need to fix the inconsistency between APT and the pipeline on this. Either update the pipeline to also pay attention to the supplied y offset, or update APT to only allow an x offset. My initial thought is that the former sounds a lot easier.

From the perspective of the TSO community, does it make sense to allow a y offset? I searched through all of the NIRCam Grism TS data, and found only 1 or 2 observations that included an Offset SR. Both of those were in Tom Greene/Everett Schlawin's program 1185. So it seems like there isn't a big demand to support offsets. 

[stscijgbot-jp]

Comment by Bryan Hilbert on JIRA:

The TSO CT has this issue on the agenda for their next meeting.