Execute roadmap with ICS team for FDR2 deliverables that require input from each otherr

Roadmap for the data flow team input to the MICADO Template Manual document:

• Consolidate list of science and calibration and technical templates
  • 3 Imaging observing modes
  • Spectroscopic mode
  • PSFR calibrations
• Consolidate data flow input for observing Template Parameters:
  • Baseline is to deliver this to ICS the information via the Calibration Plan. Namely inform ICS team that they need to look at the rows "Observing Template" and then find the parameters in "Template parameters", "MICADO set up" and "Calibration Unit setup" in the tables with Calibration Tasks
  • In addition WP Imaging delivers the TSF files using the existing python code to generate them for imaging observing Templates. Question to HB: how does info in here overlap with that in aforementioned rows in Calibration Plan?
  • if confusion arises between ICS and data flow team: let ERIS Template Manual (and Calibration Plan) guide us.
  • This should make clear to data flow team what ends up in OBs and what in Templates. For example: dithering schemes.
• To be confirmed that we do not specify more about the OBs for which just the name is listed in the Calibration Plan for FDR2:
• clarify what is needed in terms of FITS keyword specification
  • see #133
  • if confusion arises: steal from ERIS DRLD

Handy links:

• Mutual deliverables listed here in ICD
• #55 (closed)
• https://gitlab.astro-wise.org/micado/micadowise/-/tree/master/src/micado/templates https://gitlab.astro-wise.org/micado/micadowise/-/blob/master/src/micado/test/functional/tsf_test.py

Gijs-to-self:

• no delivery of specification of ObservingBlocks defined in calibration plan. Data flow team plans to provide that manually tabulated (e.g., specification of the OBs dedicated to observations of photometric and astrometric standard fields, specification how HCI Templates alternate in HCI OBs.