RIQ FCa : AO telemetry for HCI

[astronomyk]

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

I understand that which exact parameters from the AO telemetry will be recorded, at which frequency and under which format is not yet completely defined and therefore not tackled at the moment.
However, is it considered to include in the header of the images the average basic atmospheric conditions (mean seeing, wind speed, tau_0 etc.) and AO parameters (e.g. frequency, gain, modes, Strehl ratio, Magnitude of the star for the WFS etc.) ? (along with the definition on how those parameters are estimated in the pipeline documentation).
What is the current status of AO telemetry recording at VLT-UT4 when using the ASM ?

Action Item: https://jira.eso.org/browse/MET-2240

Suggested major action:

1. Determine and add AO related header keywords to E-LIS-KUL-MET-1002 (METIS Data Interface Definition) document.
2. Coordinate that these header values are populated.
3. Define how header keywords are propagated from raw to processed data products.

[hugobuddel]

I wrote a very little bit about what is included in the raw (and therefore processed) data about the atmosphere. But we aren't very explicit, simply because I didn't know what we would like to store.

Perhaps we should just expand and be explicit in section 3.1.1; can you make some suggestions @gotten ?

[gotten]

I understand that which exact parameters from the AO telemetry will be recorded, at which frequency and under which format is not yet completely defined and therefore not tackled at the moment.

Indeed not completely defined. The full stream will be a substantial amount of data (wavefront maps / slopes at some sampling frequency?).

However, is it considered to include in the header of the images the average basic atmospheric conditions (mean seeing, wind speed, tau_0 etc.) and AO parameters (e.g. frequency, gain, modes, Strehl ratio, Magnitude of the star for the WFS etc.) ? (along with the definition on how those parameters are estimated in the pipeline documentation).

I assume the SCAO module will have this info and hands this to the ICS where it will end up in the file headers. We will forward this information to the science data products. Would need to check the SCAO / ICS documents to see which keywords are defined and if the definitions for the parameters are stated there.

What is the current status of AO telemetry recording at VLT-UT4 when using the ASM ?

The METIS SCAO and HCI leads would probably be the best points of contact within our team to know this. It also seems like a valuable source of know-how. However the status of the UT4 project would seem out of our scope.

[gotten]

Answered in JIRA with a few small text edits to the text above

[hugobuddel]

Thanks @gotten!

I've discussed FITS header keywords with Faustine Cantalloube before (when learning about HCI in the context of MICADO) and I expect that Faustine would hope that we take a more proactive approach in what header keywords we want for the sake of science and that we take the lead in ensuring these are actually there.

As in, what I learned from that conference is that there is often data missing simply because no-one realized it might have been useful. But I don't know what would actually be useful.. Nevertheless, these HCI headers is not set in stone and not the most urgent thing to get perfect.

[hugobuddel]

How do we proceed with the AO telemetry for HCI?

Our Action Item (https://jira.eso.org/browse/MET-2240) is:

Suggested major action:

1. Determine and add AO related header keywords to E-LIS-KUL-MET-1002 (METIS Data Interface Definition) document.
2. Coordinate that these header values are populated.
3. Define how header keywords are propagated from raw to processed data products.

So far we did not get anything useful from the SCAO team or the scientists. So what do we do? Apparently no-one cares.

@gilles a suggestion?

[gotten]

Not sure if we have directly asked the scientists. From talks with SCAO and ICS it seems just the definition of the AO keywords is the bottleneck. There are are a crazy amount of things that you can define and store but if there is a list of AO keywords that people agree on they will implement them. If we work with science team and HCI we can probably get some headers defined.

…

On Tue, 9 Apr 2024 at 17:18, Hugo Buddelmeijer ***@***.***> wrote: How do we proceed with the AO telemetry for HCI? Our Action Item (https://jira.eso.org/browse/MET-2240) is: Suggested major action: 1. Determine and add AO related header keywords to E-LIS-KUL-MET-1002 <https://jira.eso.org/browse/MET-1002> (METIS Data Interface Definition) document. 2. Coordinate that these header values are populated. 3. Define how header keywords are propagated from raw to processed data products. So far we did not get anything useful from the SCAO team or the scientists. So what do we do? Apparently no-one cares. @gilles <https://github.com/gilles> a suggestion? — Reply to this email directly, view it on GitHub <#262 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYTWTW5H6PBBBZKVDQYYFLY4OW63AVCNFSM6AAAAAA6NQVB32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGUZTCOBYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>