• Discuss simulated TSO data, file sizes, BG subtraction

Discussion items

15 minNIRSpec TSO CV3 Presentation



  • Had to divide by white light curve to remove brightness variations
  • Two main sources of systematic noise
    • 1/f noise from detector electronics
    • Flux variations from drift/jitter
  • NIRSpec should reach 200 ppm noise floor in <5 min of integration
5 minNIRSpecStephan 
  •  Real CV3 data available (see presentation)
  • Typical file size ~ 4 GB
  • Max file size ~ 20 GB
  • Median of "out-of-trace" pixels per column removes detector 1/f noise
5 minNIRCamTom
  • Jarron is simulating TSO data
  • Spectral BG subtraction should be "column-by-column" (cross-dispersion direction), but cannot cross strip boundaries
  • Image BG subtraction likely an annulus
  • Typical file size ~ 13 GB
  • Max file size ~ 173 GB
  • Jonathan Fraine will be PoC
10 minNIRISSJason
  • Have simulations for 6 different exoplanet systems
    • Source code
    • working on documentation, adding 1/f noise, etc
  • Typical file size ~ 2 GB
  • Max file size ~ 24 GB
  • Recommend “column-by-column” (in the cross-dispersion direction)
  • See slide below for 1/f subtraction
5 minMIRISarah
  • Slitless LRS integrated into MIRI Simulator, currently testing
  • Typical file size ~ 10.4 GB
  • Max file size ~ 45 GB
  • Ongoing discussion about BG subtraction
    • no subtraction may work
    • off-source BG exposure seems prudent
    • Not sure if "column-by-column" (in the cross-dispersion direction) will work

Additional discussionAll
  • What data products would be needed for simulated data? What level?
  • What's the schedule for providing simulated data?
  • Does the simulated data need to have proper headers? If so, what are the constraints?
  • Suggested that 1/f noise subtraction should be separate from the BG subtraction
  • Integrating BG subtraction into 1D spectral extraction should be fine



Action items