Plan for data acquisition for May 2024 run (run16)

Please make a plan with priority for the data acquisition in May 2024 run (run16). 

The calibration data taken regularly among the run:
https://sumire.pbworks.com/w/page/156874332/Calibration%20Data%20from%20Run%2016

• masterBiases
• masterDarkes
• Bootstrap?
  • Check detectorMap using IIS (see also PIPE2D-1426)
• Arc/Trace to make detectorMap

• • (What YM heard by Kiyoto is) Shortest exposure it enough for each lamp
    (longer exposure looked saturated), and 3 frames (instead of 5 frames) are enough.
  • i.e.,  w/ brn, 10s Ar, 45s Xe, 10s Ne, 70s Kr, 45s HgCd, 45s Trace
    w/ bmn, 10s Ar, 45s Xe, 10s Ne, 45s Kr, 45s Trace
• Trace to make fiberProfile
  • Take one ditheredFlat for mod4 group1, having mod16 trace.
    • Using mod16 trace, check if extraction is reasonable
    • Using ditheredFlat, make one profile and compare?
  • If extraction is not good, take the other three groups.
    --> it turns our that we should take new fiberProfiles (because of thermal cycle of the cameras)

Other data (to understand instrument)

• Quartz data to study InR dependency (PIPE2D-1283)
• Quartz data to monitor fiber-to-fiber throughput variation.
• Twilight 
  • At different rotator angle. Quartz data is needed at the same rotator angle.
• All-sky field
• All-F-star field
• Else?