- News & announcements.
- Plan for build 7.5 pipeline testing throughout the summer (all).
- TSO activities on each instrument branch (all).
- Discussion/prioritization of TSO Jira tickets.
1. News & announcements
2. Plan for build 7.5 pipeline testing throughout the summer
Nestor Espinoza introduces the fact that we have to provide feedback to the CalWebb WG on the JWST Calibration Pipeline Build 7.5 (mainly through opening of Jira tickets). The hope is that this also serves as input to the community to know what works, what doesn't — and of course, for us. He notes that we should not only provide feedback on the final TSO3 Stage, but also on Stage 1 and Stage 2 (both for imaging and spectroscopy), following the TSO steps that are taken in those stages. Sarah Kendrew notices the importance of doing this for imaging, where they found a bug in the MIRI imaging mode (see below); Nikolay Nikolov also mentions this is valuable based on his experience (see below); Nestor Espinoza has been having a similar experience with NIRISS/SOSS testing on his side. The team agrees that this is the way to go.
The proposal Nestor Espinoza gives to the TSO WG is to do this in a (2-week) sprint: basically, work together in the problem in order to have quick feedback about possible steps that might fail (which might be useful to test if this is due to problems in the simulations or an actual bug on the pipeline). Sarah Kendrew likes this idea as well. Nikolay Nikolov and Tony Keyes would prefer to do the testing on their own, at their own pace. On the one hand, Nikolay doesn't think he can commit to a 2-week effort, whereas Tony has to consult with the experts testing the pipeline in NIRSpec (James M. and Maria P.). The team thus agreed for Nestor Espinoza and Sarah Kendrew to do a testing sprint, report that to the team, and then for Nikolay Nikolov and Tony Keyes to perform their own testing and report back to the team.
To organize the work, Nestor Espinoza will create a spreadsheet where we will leave our feedback to each of the steps of the pipeline. Sarah Kendrew mentions to be careful between validation and verification. We want to provide feedback to the CalWebb WG via Jira tickets by testing that the algorithms do what they are expected to do. If we want to provide enhancements, however, that most likely involves a direct e-mail or document sent to the WG. Both are extremely useful, but use very different channels to reach the CalWebb WG. Tony Keyes also mentions to be aware of the Jira tickets in the TSOWG DMS Dashboard, and Sarah Kendrew notes that useful information is also available on the dashboards of each of the instruments (MIRI DMS Dashboard, NIRCam DMS Dashboard, NIRISS DMS Dashboard, NIRSpec DMS Dashboard). If you encounter a bug/problem with a step, make sure you check those before opening a new one — use those also as general information; a quick read through them before starting testing is very, very useful.
|3. TSO activities on each instrument branch
|4. Closing remarks of the meeting