You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Please contact Kevin Stevenson or Sarah Kendrew to add issues to this page.


Instrument / GroupDescription of the Issue (include JIRA/PR links if possible)PriorityLead(s)Status
DMS / Calibration

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

MediumNeed to present plan to calibration WG for approval
DMS / Calibration

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.
Medium
DMS / Calibration

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

HighMeeting planned for Friday, May 11 at 3pm





MIRI TSO

Target acquisition needs to be implemented in APT

MediumComplete?
MIRI TSO

Enable TSO mode for MIRI imaging

MediumComplete?
MIRI TSO

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

  • Do we need tests during commissioning?
Low
MIRI TSO

Enable MRS TSO mode

  • Caution: data volumes could be too high
Medium





NIRCam TSO

Enable SW DHS spectroscopic mode

High
NIRCam TSO

Enable narrow-band filter option for target acquisition

High
NIRCam TSO

Enable TA on saturated targets

Medium





NIRSpec BOTS

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

Low

NIRSpec BOTS

Enable WATA on saturated targets

High

NIRSpec BOTS

Enable WATA with NGROUPS=1 or 2

Medium

NIRSpec BOTSEnable 100% duty cycle modeHigh





NIRISS SOSS

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

Low
NIRISS SOSSEnable 100% duty cycle modeHigh





JDox

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

Medium

NIRCam recommendation: ~35k ADU

No values from other teams

JDoxAdd decision tree describing how to plan TSOsMedium





ETC

Needs brightest pixel listed in output

Low






APTAPT asks for transit ephemeris in HJD, not BJDLow

APT

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?
LowEverett submitted a ticket (INC0051035) with the JWST Help Desk
  • No labels