RIC PWb : FITS header propagation unclear for AO telemetry

[astronomyk]

https://jira.eso.org/browse/MET-2162

The cases described in the bullet points are simple and clear (and automatically propagated by CPL), but the case of meteorological / atmospheric parameters and AO telemetry is less clear. It might be useful to have the full set of such parameters available in a combined output exposure, representing e.g. the full range of airmasses. The AO telemetry mentioned here might actually be too big to be a few FITS keywords (at VLT UT4 it is saved as two binary tables per exposure).

My answer on Jira

The AO telemetry will indeed be a huge dataset, on the same order as the raw data output from METIS. It will be stored in binary files on the ESO servers, and the pipeline will add references to these data products in the headers of each of the processed FITS files.

I have taken note of your suggestion to include the extra information on all atmospheric/meteorological parameters for the individual frames used in combined exposures. I agree that this may indeed be useful information, as the references to the AO telemetry for each raw frame should indeed remain with the final data product.

This leaves us with the action to incorporate the AO-telemetry references for the individual data frames in any combined frame

[astronomyk]

• Define structure for incorporating summaries of the variable information in raw frames for a SoF into the combined exposure files (e.g. AO telemetry references)