- News & announcements
- ExoCTK updates.
- Updates on TSO WG tasks for FY2020.
- TSO activities on each instrument branch.
- Final definition of exoplanet consulting expert involvement on TSO WG tasks.
- Discussion/prioritization of TSO Jira tickets.
1. News & announcements
2. ExoCTK updates
|Task-015: Train new ExoCTK leads|
|Task-016: Address PandExo/ExoCTK liens|
|Task-017: Make PandExo and some of ExoCTK officially supported|
|25min||3. Updates on TSO WG tasks for Fiscal Year 2020|
|Pipeline readiness & preparation for TSO||Everyone|
|Instrument & cross-instrument TSO tasks||Everyone|
4. TSO activities per instrument team
|5min||NIRSpec activities/updates||Tony Keyes|
|5. Exoplanet consulting expert involvement on TSO WG tasks|
|TSO simulated data & noise limitations|
|JWST time stamps for TSO|
|JWST TSO QL tool|
|Synergies with between TSO and Coronographic WGs|
Had meeting with Julien Girard on this. Idea is to work on understanding how to use TSO + Coronography. He'll be sending simulated data on this.
6. Overview of DMS TSO-related tasks
|TSO DMSWG Dashboard|
Nestor Espinoza: The only unprioritized NIRISS-only ticket is JP-1177. This relates to the fact that an exposure with the F277w filter on NIRISS/SOSS can help disentangle contamination overlap between orders 1 and 2 at the red-end of order 1. This is already implemented in APT, and is in JDox, but not on the ETC.
Nikolay Nikolov and Brian Brooks: NIRCam didn't have any unprioritized tickets, but we did add JP-1478 to the list. We also commented on the list of critical and high priority tickets. See attachment: NIRCam_comments
Tony Keyes: There are no NIRSpec-specific tickets in the unprioritized TSO Dashboard list, but we have filed JP-1488 (BOTS Data need to be rectified) and consider it CRITICAL priority. We have reviewed the entire list of TSO Dashboard tickets (17613) and a separate NIRSpec DMS Dashboard (17609) and prepared a file with comments on NIRSpec-impact of all tickets. We did not present any of these additional comments at today's meeting, but expect to do so in the future.
|Closing remarks of the meeting|