2023-06-28 TSO WG Meeting notes

Nikolay Nikolov  reminds people that IS Review training for TSO is happening throughout the 

Nikolay Nikolov showed a summary and discussed the TSO observations for the past 14 days. As usual, most used mode is NIRSpec. Two observtions with issues. First, PID 2594 had a target star TA didn't work because defined location pointed to no star. This had some errors on the NIRISS APT — used full frame, used a different TA than the target. Even if it went through, it would have failed (saturated). PID 1981 exposure started, but something happened and the exposure was aborted. WOPR. 

Sarah Kendrew reminds us that something like what happened with PID 1981 happened also last year with MIRI. Nikolay Nikolov : does the FGS use several guide stars? Loic Albert notes there is a set of stars that can be used. In any case, an investigation should ensue. Sarah Kendrew: FGS team is very helpful on figuring out these analyses. They are constantly working on updating algorithms. She also shares the fact that some users would like to have more information on the FGS results. Nestor Espinoza highlights that this might be important to document — the fact users can in theory read OSS messages through MAST and  that they can download and analyze FGS data. Nestor Espinoza has a student working on this during the summer — will update folks.

Observation 4 on visit 1 of 1331 was skipped as well WOPR 88815

Nikolay Nikolov  

Nikolay Nikolov introduced a plan for FY 2024. Deadline for turning this on is July 14th. This includes:

• Pipeline Validation for TSOs: need to constantly validate pipeline updates or to identify issues with the pipeline. Idea is that after each pipeline version is released, we can use a "standard dataset" to pass the pipeline through. This tool will then produce plots/statistics/figures that can be examined and checked for issues. We could have datasets for low and high number of groups, and compare differences to previous versions of the pipeline as well. Narrow down problems to different steps. Nestor Espinoza
  
  
• Implement CR detection for TSOs: there are improvements that can be done on the CR detection for TSOs. Current FY2023 plan is on identifying the idea, solidifying the methods — FY2024 is to implement that in the pipeline (write the code, interact with the CalWG, etc.).
  
  
• Background monitoring for TSOs: backgrounds can dilute transit depths. Need to monitor in particular zodiacal backgrounds. There is now monitoring going on for all instruments through the year. This is more of a TSO-instrument-branch-focused project. Idea is for representatives to update on the TSO WG on this ongoing work on their branches.
  
  
• Non-linearity corrections: idea would be to where the non-linearity plays a more important role — and what is the best data analysis approach for correcting for this. Loic Albert suggests this is not only a non-linearity but also a charge migration issue. Nestor Espinoza shares that work he has been doing with Leonardo Ubeda in NIRSpec actually showcases this to be the case. This task is basically a continuation of this on the next FY.
   
• 1/f noise algorithm: incorporate an algorithm into the JWST pipeline. Nikolay Nikolov working with a summer student on testing four algorithms for imaging data — not yet tested on TSO data. Nestor Espinoza has a TSO algorithm that he presented on the CalWG team. ROEBA. Idea would be to do more testing on different algorithms and propose one to implement on TSOs.
  
  
• Instrumental systematics: visit-long slopes observed on different instrument. Identifying the root cause can help identify a solution to correct solution on data collection. Everett has done a good deal of analyses on anti-correlation on NIRCam data. Idea is to look at mnemonics from FOS dataset and identify physical properties that correlate with visit-long slopes.
  
  
• MIRI: Sarah Kendrew has been showing a set of systematic effects on MIRI TSOs, which requires some investigation. Probably a thorough look might be necessary to identify all issues. Probably most of the most prominent. Sarah Kendrew also adds some operational changes too happening, whose priority is unknown (e.g., MIRI TA).
  
  
• Timestamp calibration: we currently don't have a way to constantly measure precision of time-stamps on individual instruments. We need to monitor and document timestamp generation and caveats. Sarah Kendrew notes this is important especially for people that do coordinated information. In particular documentation on this end.