Meeting agenda:

  1. News & Announcements.
  2. Status on TSO commissioning papers.
  3. Status on TSO Helpdesk & Jira tickets.
  4. Instrument roundtable check-in
  5. Closing remarks

Discussion items

5 mins

1. News & announcements

10min2. Status on TSO commissioning papers

  • Short-wavelength paper draft going around already; target submission is next few weeks. Would be nice to coordinate with everyone else on an exact submission data for public display (e.g., arXiv).
  • Nestor Espinoza suggests to start an e-mail chain to define this. Also wonders that given everyone seems to be converging to PASP, that we might want to give a heads-up to the journal on this. Need to know status of SOSS paper, however, to make this happen. Need also to give the ERS team a heads-up about this.

  • Nestor Espinoza has no updates on how the SOSS paper is going. Been too busy with ERS and GO SOSS data analysis. 


  • No one from the MIRI team present (Sarah on leave), but paper seems very advanced too. 
5min2. Status on TSO Helpdesk & Jira tickets

General updates
  • Nestor Espinoza discusses that the inflow of Helpdesk ticket question definitely increased since data was released (as expected). 

  • One of the "subgroups" that is somewhat behind fixing user tickets is ExoCTK. Two reasons for this: (1) members that had to leave pre-commissioning or during commisisoning and (2) ExoCTK currently at very low priority level (data analysis and helping, e.g., the ERS teams and general community is much higher in the priorities — this includes documenting commissioning results, new findings on JDox, working on internal reports, etc.).

  • Knicole Colon asked if anything can be done resource-wise to help ExoCTK.
  • Nestor Espinoza clarifies that all will be OK — it's just that at this particular point in time (and space), there is no much extra resources to dedicate to ExoCTK. But that will change when prep for Cycle 2 begins (which will be soon). Most of the updating should be relatively straightforward depending how everything goes, e.g., on the Pandeia side. Brian Brooks confirms things are moving on this, releases will happen, but not yet.
10min3. Instrument roundtable check-in

  • Reports on some micro-tilt events seen on SW ERS data. They seem to not have too much impact on the actual photometry, however, despite flux variations which are seen if one takes aperture photometry around mirror segments.

  • Memory issues — each segment is 6 GM, total usage at Stage 1 is 30 GB. Maybe splitting size might be smaller for NIRCam? Nestor Espinoza asks if there is a particular step that produces the problem? Everett Schlawin clarifies that if you are saving every step, then memory explodes. Also, if you run every step in the way, you can't clear the memory of the step before it.

  • Nestor Espinoza thinks this might be good to bring up at the CalWebb WG meetings.
  • Everett Schlawin also wanted to share a better wavelength solution with the public for NIRCam, but doesn't know of a quick way to "oficially" do that. Nestor Espinoza mentions he has encountered the same problem — believes there might be a mid-way solution? He'll bring this up at the WIT meeting.

  • Nestor Espinoza reports on some calibration programs happening to track the wavelength solution/trace changes due to PWCPOS changes. These still don't happen, but they will and will sample different pupil wheel positions to hopefully characterize this (maybe once and for all).
  • Another interesting development on calibration programs is one that is following a standard star. He's performing analyses on this as we speak, will report on the TSO WG meeting.

  • Nestor Espinoza reports on a big tilt event seen on the ERS data for NIRSpec G395H. Easy-ish-ly to handle, so no big problem — but pops up clearly on the FWHM.

  • No updates on MIRI.
2 mins4. Closing Remarks