Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes
5 mins

1. News & announcements

Everyone
  • There's been an email discussion about the Calspec2 Photom() step, whether it should be in the default exection of the pipeline stage. As this calibration step corrects for throughput, blaze functions etc, there is a concern it will introduce systematics. Most scientists and analysts are skipping the step as the analysis looks at differential (spectro-)photometry so doesn't require physical units. The step can be toggled in the calwebb_tso-spec2.cfg file (or the asdf file that will replace it). 
    • Regan & Keyes question how you can get correct line ratio measurements if you don't correct for throughputs?
    • more analysis is needed

  • APT2021.1 will include a warning & workaround for a known issue with visit planning for long TSOs. When the scheduled visit time is bigger than the period then APT is not able to respect the input phase constraints. See ticket  
    Jira
    serverSTScI JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdaac911eb-9c55-3f14-8368-77b436fb6dc2
    keyAPT-90539
    . The workaround implemented raises a warning and tells the user to double the period provided to AT, and adjust the phase range to match. This will reduce the number of available scheduling opportunities (by half)
    • on discussion the WG agrees this is not idea as it will require documentation and will confuse users. The impact on the schedulability of the various programs is also not fully known. 
    • we feel the option to have this properly corrected by APT should remain on the table as the workaround is not optimal
    • (update: Nestor Espinozahas emailed Jeff Valenti to provide this feedback after the meeting)
  • Brian Brookstalked about the release of ETC 1.6, which contained TSO-specific updates. Some changes for MIRI are still being worked as they required an update to the timing document. This work is in progress, led by Bryan Holler. Some JDocs updates will be required. A description of changes can be found in this article.






30min2. High efficiency modes


  • See meeting slides for updates
  • Loic Albert brings up importance of providing technical information to science community (or "study group") so they can then determine impact on science. 
  • Michael Regan says a report on the 100% duty cycle mode for the NIR detectors is ready (by Eddie B)
  • Michael Regan & Eddie B have also looked into different read modes in the NIR that avoid 1/f noise. Have for example spoken to Karl M at UAZ regarding an IRS2 read mode for NIRCam. There are many possibilities but need to gather evidence and numbers on the need and the trade-offs. 
  • Case for keeping (or bringing back) the 0 frame resets mode for MIRI is also compelling for TSOs, as the problems solved by the frame resets did not significantly impact TSO science, whereas these observations will suffer from the loss of efficiency particularly for v bright targets
  • Team feels this is an important activity that we should take action on soon. We need the science justification for these capabilities, so the project (Goddard) has both the view of the technical and scientific impact & can assess - but will take time.
  • Nestor EspinozaSarah Kendrewwill set up an additional small-group meeting in the next 2 wks to discuss a plan for this activity. All from TSO WG are welcome + some additional stakeholders. 
  • Loic Albert asks if changing the readout speeds of our detectors is possible to increase the saturation limits? 
    • this is theoretically possible but introduces additional noise, and not sure if  JWST SI readout electronics can acommodate much faster speeds.




5min3. Outlier detection update


  • Nikolay will present at the May Cal WG meeting and we should have an internal discussion beforehand. Propose that we do this in next meeting, or set up a small separate meeting for this topic.
  • Michael Regan reports there is a pull request for the jump step, to work properly on 3 and 4 group integrations. Next step is to identify jumps across multiple integrations.
5 mins4. 1/f noise



Nestor Espinoza
  • Work in progress on the PSD modelling - will return to this in next meeting




5 mins5. Final comments or updates



Sarah Kendrew
  • Let's meet again in 2 weeks!

...