Agree the CDF metadata with the SDC and with Tim

[alastairtree]

From Maxine:

Here are the YAML files which describe the CDF file attributes. This file format is how we describe the attributes in our code.

Since the variables are the same for level 1, it’s just one file that describes the variable attributes, but if you’d like to see changes to the attributes for L1A/L1B/L1C just let me know. Feel free to directly edit that file and send it back, compile a list of changes, or even open a PR in imap_processing with updates (if you really want to get fancy). These attributes should have the changes requested by Ed a few months back, but have not been validated by SPDF. The main focus for your team is probably CATDESC, FIELDNAM, VALIDMIN, VALIDMAX, and UNITS, with the most important attribute being CATDESC.

Any variables that end in _attrs are used as dimensions (we are coming up with a different standard for this, but that’s how it is now.) The actual dimension name does NOT have _attrs, it’s solely used in this file.

In addition to the global variables in mag_global_full.yaml, there are mission-wide global variables that are also included in every file. There are also some mission-wide variables included in each CDF file – such as ground_software_version.

If these YAML files are unclear, I’m happy to transfer them into a spreadsheet instead. These attributes are also still a work in progress, although we are a lot closer to the “final” values than my initial attempt.

mag_global_full.yaml.txt
mag_vars_full.yaml.txt

[alastairtree]

We are being asked to provide SPASE metadata in addition to the ISTP stuff in the CDF fields.
More details in https://lasp.colorado.edu/galaxy/pages/viewpage.action?pageId=228084198&preview=%2F228084198%2F228084199%2FParameter_SPASE_info_v03.pdf
e.g. for us stuff that looks like this:
DICT_KEY = “SPASE>Field>FieldQuantity:Magnetic,Qualifier:Magnitude”
DICT_KEY = “SPASE>Field>FieldQuantity:Magnetic,Qualifier:Vector,CoordinateSystemName:GSM,CoordinateRepresentation:Cartes
These are just extra key/value pairs that go into CDV metadata.
The CDF metatdata is all configured at https://github.com/IMAP-Science-Operations-Center/imap_processing/tree/dev/imap_processing/cdf/config
So we can just deliver updates to the MAG config files or talk to Maxine and iterate on CDF files.
Similarly they want "global attributes" - docs are at https://lasp.colorado.edu/galaxy/pages/viewpage.action?pageId=228084198&preview=%2F228084198%2F228084201%2FGlobal_SPASE_info_IMAP_example_v03.pdf
For this we are expected to deliver a simple ASCII file