Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Data Interface Control Dictionaries for METIS? #191

Open
hugobuddel opened this issue Sep 26, 2024 · 0 comments
Open

Add Data Interface Control Dictionaries for METIS? #191

hugobuddel opened this issue Sep 26, 2024 · 0 comments
Labels
instrument-specific Limited to a certain IRDB instrument package METIS

Comments

@hugobuddel
Copy link
Collaborator

Attached are the DICD (Data Interface Control Dictionaries) that I wrote for MICADO, micadodicd.zip. The conversion to yaml is included as well.

The DICD files are ASCII files named like ESO-ELT-DIC.MICADO_DET, with entries like

Parameter Name:    DET ANGLE
Class:             header
Context:           Detector
Type:              double
Value Format:      %.3f
Unit:              degree
Comment Format:    Angle of detector
Default:           0.0
Description:       Angle of detector

For MICADO I used those to define what all keywords mean. Where they were used was defined in the data model (that we don't have for METIS).

I propose we just use these DICD files for now, and put them in the IRDB. Maybe in the METIS/dicd directory? Then in the METIS/headers directory we put where these keywords are used.

I'm not sure about the future of these DICD files. To some extent they are being replaced by a new format that I do not have access to anymore. But much of the information was missing in this new format.

@hugobuddel hugobuddel added instrument-specific Limited to a certain IRDB instrument package METIS labels Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
instrument-specific Limited to a certain IRDB instrument package METIS
Projects
None yet
Development

No branches or pull requests

1 participant