Hand-over DPS-ICS interface to Ric and Michael and Werner

To hand over to Ric (WP DPS lead), Michael (ICS lead) and Werner (ICD custodian): the agreement on who is responsible for what in

ToDo

• plan this for this DPS-ICS meeting
• MICADO – FITS Header (e.g., list of mandatory FITS header keywords required by imaging and spectroscopy pipeline.
• content of observing Template manual (e.g., detailing observing Template parameters)
• DPS-ICS libraries and ICD

See DPS-ICS minutes

References:

• Detector software manual
• Technical Note on FITS header keywords

Handy links

• emailthread on joint DPS-ICS meeting

Related to #134 (closed)

---

As an experiment, we decided to formulate this issue as an email to the ICS team. This has three benefits:

• It will give us a clear way to determine whether the issue can be closed: once the email is sent.
• Actually drafting the email makes it clear precisely what needs to be done to achieve that.
• Finally, formulating it as an email allows us to focus on actions that collaboration with others, in this case the ICS team.

Dear Jörg and Michael, CC Kieran,

Appendix C.1 of the MICADO DRLD [1] now contains a list of FITS keywords that are required for the data processing. Can you take a look to see whether this makes sense too you?

We have updated our naming scheme to match the ones you proposed in MICADO_ICS_fits_headers.20210325.pdf

We agreed that we prefer to have all raw data to have the same FITS headers, even those that are normally not relevant to the data item. For example, there will always be a header item to indicate whether the flat lamp is on or off, even if it should be possible to infer that from the type of raw data. The main benefit is that this would make it possible to detect incorrect configurations, and it can also be considered simpler. See https://drive.google.com/file/d/1r5qx4gD00N-hQoab1jWVZy2_1TDmDaTQ/view?usp=sharing .

This is a very limited list on purpose, entirely from the perspective of the data processing software. In particular, it is every keyword that is listed in the Data Reduction Library Specification or associated prototype. We will later communicate a list of keywords that we would like to have for the data flow subsystem, but are not essential for the data processing. E.g. this will include parameters used for the simulator, such as temperatures.

Kieran is CC'ed because this would be the minimal set of keywords that should be simulated in order to process the simulated data.

Cheers, Hugo

[1] https://gitlab.astro-wise.org/api/v4/projects/micado%2Fdatareductionlibrarydesigndrs/jobs/artifacts/master/raw/ELT-SPE-MCD-56305-0019_DataReductionLibraryDesignDRS.pdf?job=latex_pdf

Actions to take:

• Create a table with all these header items.
• Ensure the names of MICADO_ICS_fits_headers.20210325.pdf are used.
• Add keywords from #133 (comment 24922)
• Perhaps include information to indicate which subset of headers relevant for which raw data type.
• Ensure that MicadoWISE can deal with headers that are not necessary for a particular datatype. Perhaps not as part of this issue.
• Perhaps include a reference to the new background template, see #151 (closed)