-
Notifications
You must be signed in to change notification settings - Fork 18
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
CF compliance work #7
base: master
Are you sure you want to change the base?
Conversation
Created /main/branches/dev/leifdenby/vn0.8_cf-compliance from /main/trunk@3628. git-svn-id: https://code.metoffice.gov.uk/svn/monc/main/branches/dev/leifdenby/vn0.8_cf-compliance@3995 0f676ef4-b20c-4647-9485-21614760d15f
Just need to do propagation of units through fields which are derived through mpi reductions now
Much more work to do...
Many more to do, but this is a good start
Conflicts: .gitignore
@sjboeing I've been thinking about this work and I would like to get it into our fork. I was thinking that I could make the functionality opt-in rather than default. That way it wouldn't change default behaviour, but if someone asks for units, longname attributes etc they could enable this. Specifically when enabled it would require that for all scalar fields it is defined: 1) what grid the variable exists on (staggered or non-staggered in each dimension), 2) what the units of the field are and 3) what the "longname" of the field is (and optionally the "standard_name" can be provided too. Thoughts? |
Implementing https://github.com/leifdenby/monc/issues/6