General updates: NIRSpec pipeline validation, non-linearity, 1/f noise.
Meeting slides can be found here (available on innerspace; external folks, please contact Nestor Espinoza if interested).
1. News & announcements
Nestor Espinoza received email from Scott Friedman that our HAT-P-14b observations will not be approved as the timeline is basically frozen. But we have the opportunity to bring the observation forward at the JWST Daily Briefing (JDB), where it is likely to be approved. Sounds like this will be relatively "easy". SHould bring this forward a few weeks ahead of the time of execution. Suggested that we could write a 1-page summary for the different instruments giving the arguments for these observations, which we can share. Has there been any progress on that?
No progress so far but we can make a start on it. Everett will discuss with Tom.
SK: concerns about the JDB
Knicole: Scott & Randy expressed concerns about the planning constraints given the transit periods. Might be good to add in backup targets to mitigate that difficulty.
Loic Albert good progress on extract1d for NIRISS SOSS. pushing working version of extract1d to STScI next week, which would get it ready in time for commissioning. datamodel changes that were needed for the output product all done on the STScI side. hope goes smoothly once the code is delivered to SCSB.
Had a request from CalWG re. pipeline development priorities. Was on the agenda for last CalWG meeting (Notes).
Reviewing JIRA tickets or open TSO items
which of all tickets needs to be prioritised for work?
what are we missing?
Please review the tickets and address these questions!
We have to circle back to the CalWG by January to provide feedback. Will try to have a discussion in our group in early Dec (TBD) to discuss. Nestor will create a table of his suggested issues and reach out for further discussion to instrument experts.
4. General updates (NIRSpec pipeline validation, non-linearity, 1/f noise, JDox)
have a dedicated (restricted) page for the meeting notes on these progress meetings, for those who can't attend
have gone all the way through non-linearity step
working on the dark step; bit more complicated than expected. dark file has both negative and positive values, puzzling.
SB: darks averaged at frame level. will change how we produce the darks in commissioning; instead of averaging over all frames, will compute average dark current and apply that to good pixels. this method will get rid of the near-zero values
ES: do we want to subtract this, does it just add noise?
SB: not really as the subtracted value is always the same. in new method will have a time-constant value to the good pixels. those with time variable dark current will usually be masked.
LA: similar for SOSS; NIRSpec's strategy shoudl probably also be applied to NIRISS
ES: NIRCam not using this but sounds like a good idea
SK: suspect similar for MIRI, have heard that darks strategy has evolved
next: jump step. open questions on how to validate this step.
SK: a MIRI GTO science team has found some odd behaviour in the jump step - this was not TSOs but MRS high-z simulations so very different data, but quite odd behaviour so may will need further work
Non-linearity work: reports in progress.
1/f noise (Nestor)
Nestor is very proud of his 1/f fits to darks
currently simulating 1/f frames with those models and exploring how slope estimates and errors behave in different subarrays