2024-11-13 TSO CT Meeting notes

Nestor Espinoza  on behalf of Munazza Alam 

• Same targets as before.
  
  
• There should be a JDox article about coordinating JWST observations with other observatories in. Nestor Espinoza will contact JDox leads to figure out where this should go.
  
  
• What about locking planned windows? Hannah Diamond-Lowe asks whether once this is in the PDF this is good enough. Nestor Espinoza suggests this might be priority-dependant of course — being in the PDF is necessary but not sufficient to guarantee you a window.
  
  
• Aarynn Carter asks whether there is any way in which the window can be guaranteed in general (or "better than best-effort"). Nestor Espinoza mentions this falls on the question about how priorities are defined in terms of being time-critical (e.g., supernovaes might have priority given they are one-time events). Hannah Diamond-Lowe asks whether knowing better how priorities get done we could help clarify how to put users' proposals up in the priority list (e.g., in JDox).

Aarynn Carter 

• Aarynn Carter introduces TSO task list for NIRISS/SOSS:
  
  
  • Among the tasks, there was some discussion on 1-group ramps for SOSS. Michael Regan does note the pipeline doesn't like 1-group integrations — 2 groups with the second saturated is fine. Aarynn Carter notes that this might imply adding some code in the JWST pipeline to create "fake" second group data that have DO NOT USE in them.
    
    
  • Aarynn Carter mentions work currently in progress:
    
    • He has coded up Tim Brandt's ramp-fitting, and is comparing it against the pipeline ramp-fitting — as well as a comparison of jump detection. Tim's code improves things, but is unclear if it is the jump or ramp-fitting parts of his codes. Aarynn Carter belives is the latter, but is checking this as we speak.
      
      
    • There's work right now on figuring out the NIRISS/SOSS background. There's work on creating background templates, and validating those against actual observations. Everett Schlawin asks whether the background Nestor Espinoza took for his science program makes things better. Nestor Espinoza shares it's not a huge improvement for that particular target (WASP-63), but it might for other objects.

Achrene Dyrek 

• Achrene Dyrek shares NIRCam DHS tasks — in particular, the following points were discussed/raised:
  
  
  • Everett Schlawin suggests to add a task that handles contamination overlap for observers. Nestor Espinoza suggests this could be worked together with ExoCTK, who implemented the contamination overlap tool for SOSS. He suggests to simply start a task in the Kanban board, and then discuss how to jointly work on this with ExoCTK.
    
    
  • Michael Regan asks what ground testing is needed for the number of reference pixels to include on each substripe task. Achrene Dyrek explains this is a question about optimizing the reading with the constraint of not losing too much time reading for reference pixels. Michael Regan suggests in theory this could be worked out at first-order to figure out what 1/f correction you want to remove. John Stansberry suggests to set up a dedicated session to discuss this.
  • Achrene Dyrek led a discussion on the identification of calibration sources:
    
    
    • Given the constraints, Michael Regan suggests the LW would survive a detector "blast".
    • For the wavelength calibrator, Nestor Espinoza notes that SOSS used an A-star. He'll look the technical report up and will send it to Achrene + John.
    • RE: TSO calibrator — Everett Schlawin asks about HAT-P-14b given there's plenty of spectra for cross-instrument checks? Object is grazing, but spectra was able to be extracted. Nestor Espinoza is a bit scared of the target given some wiggles were observed in SOSS, and also because the contaminant might be actually a bit worse in SOSS. Food for thought!