- Sarah Kendrew
- Brian Brooks
- Nikolay Nikolov
- Everett Schlawin
- Nestor Espinoza
- Knicole Colon
- Michael Regan
- Eddie Bergeron
- Loic Albert
- Elena Manjavacas
- News & Announcements (all)
- Roundtable Cycle 2 calibration plan updates (all)
- Handling LRS SLITLESSPRISM 390 Hz noise (Regan)
- TSO WG work (TSO monitors, non-linearity, 1/f, etc.; all)
- Roundtable check-in
1. News & announcements
Nestor Espinoza : some cycle 2 stats. huge increase in exoplanet proposals compared to cycle 1 (not all TSOs)
the TSO modes are heavily requested as well: esp NIRSpec BOTS
TSOs are ~20-30% of JWST usage for cycle 2 proposals (yay and yikes)
2. Cycle 2 calibration plan check-in
Cycle 2 calibration plan is not yet fixed - mission office will review the programs before assigning PIDs.
|3. 390 Hz noise for MIRI|
Slides from Eddie & Mike.
Noise is actually present in all array configurations, but in most array configs the noise is in phase (which occurs when npixels in subarray is a multiple of 256) . Very visible in SLITLESSPRISM.
Initial fix from Ressler is to move the subarray, increasing frame read time by 8%
Eddie created a library of solutions with various compromises. Some even shorten the frame time.
Quite an impactful change, need to start the transition asap - we need consensus and buy in from stakeholders asap. We should not accept having this additional noise in the data for the lifetime of the mission - we would not have picked this for flight had we known about it.
SK: like the smallest size where we gain 6.6% read time
NE: what is the cost?
NE: how well can we correct it in data?
We need to quantify with some numbers for the trade-off for this work to assess whether it's worthwhile doing.
LA: should we optimize the subarray size to maximize the background coverage if that is proving problematic?
ES: can we make a new subarray to avoid the shadowed region?
|4. TSO Work||Nestor Espinoza|
TSO monitor Nikolay Nikolov :
Bad pixels/NaNa Nestor Espinoza :
with newest version of the pipeline bad pixels are converted to NaNs. newest processed data shows a LOT of NaNs, more than expected. Probably related to new bad pixel map.
|5. Roundtable check-in|
|2 mins||4. Closing Remarks|