-
Notifications
You must be signed in to change notification settings - Fork 33
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
order in required_global_attributes
matters
#737
Comments
larsbuntemeyer
changed the title
order in "required_global_attrbitues" matters
order in Apr 12, 2024
required_global_attrbitues
matters
Sorry, I'll try to provide a minmal example, but, e.g., see here... |
larsbuntemeyer
changed the title
order in
order in May 7, 2024
required_global_attrbitues
mattersrequired_global_attributes
matters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just wanted to dump this here, since we now have fixed our required global attributes for CORDEX. I'm not sure if it's by intention, but it seems like the order of variables in the
required_global_attributes
tables seems to matter when they are evaluated during cmorization. This is probably related to #628. For example, if if have...... and my input dataset file contains
domain_id: "EUR-50"
, cmor will correctly and automatically add the global attributesdomain: "Europe"
to the file. However, this wil not work if thedomain
attribute comes before thedomain_id
attribute in the list ofrequired_global_attributes
, e.g., this will not work...This is somehow confusing and it's not the case for attributes like, e.g.,
source_id
andsource
....The text was updated successfully, but these errors were encountered: