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.

Sign up for GitHub

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

Jump to bottom

read_restart: use time_bnds instead of time_bounds for CF compatibility #3303

Open
infotroph opened this issue Jun 4, 2024 · 0 comments
Open

read_restart: use time_bnds instead of time_bounds for CF compatibility #3303

infotroph opened this issue Jun 4, 2024 · 0 comments

Comments

@infotroph
Copy link
Member

infotroph commented Jun 4, 2024 •
edited
Loading

This seems like a reasonable fix for this PR. Long term it might be worth being consistent about calling this time_bnds throughout, which I think is better aligned with the CF standard: ORNL DAAC lists time_bnds as required, and time_bnds appears* in the conventions themseves whereas time_bounds does not. Can we consider a followup patch to make read_restart use time_bnds?

*Though admittedly time_bnds only appears in an non-normative example. The CF conventions are messy!

Originally posted by @infotroph in #3249 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@infotroph