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

time_bnds units differ from time units #110

Closed
klindsay28 opened this issue Apr 29, 2022 · 1 comment · Fixed by #118
Closed

time_bnds units differ from time units #110

klindsay28 opened this issue Apr 29, 2022 · 1 comment · Fixed by #118

Comments

@klindsay28
Copy link
Collaborator

In out current MOM6 output, units for the variables time and time_bnds are

time:units = "days since 0001-01-01 00:00:00"
time_bnds:units = "days"

This difference is not compliant with CF conventions, sec 7.1, paragraph 2.

It caused problems for a post-processing script that I use. I alluded to this in this week's section meeting, but it took awhile to figure out the source of the problem for my script.

I dug into FMS and found that if we add

&mpp_io_nml
    cf_compliance = .true.
/

to input.nml, then time_bnds:units is the same as time:units.

Can we modify input_nml.yaml so that the above is added to input.nml?

The also makes the value of time:calendar lowercase and changes the attribute name cartesian_axis in MOM output to axis. I do not expect these changes to cause problems for tools.

The latter change might actually make MOM output more amenable to the cf-xarray library that @dcherian and others have developed.

@klindsay28
Copy link
Collaborator Author

@alperaltuntas , can we talk about how to get cf_compliance = .true. in mpp_io_nml added to input.nml into MOM_interface?
This unit difference is a headache for my analysis scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant