-
Notifications
You must be signed in to change notification settings - Fork 241
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
Missing reference times in CF output #1347
Comments
An issue to be aware of while fixing this: If adding or subtracting large numbers of seconds to calculate reference time with something like |
@jsimkins2 I think this is mostly in your functions. Can you take a look? |
I think this is fixed for CRUNCEP in #1357. Could code from that PR be reused, or generalized and applied to all of the met2CF functions? |
@dlebauer Yes, that can be reused and applied to other data.atmosphere functions. The only difference is the reference date. This varies per source, download.MACA references 1900-01-01, while download.GFDL references 1861-01-01 |
This issue is stale because it has been open 365 days with no activity. |
Unstaling: Still needs to be done. Shouldn't be too hard, just need to make sure we fix all instances. |
This issue is stale because it has been open 365 days with no activity. |
Several functions in
data.atmosphere
produce invalid CF output because they give time in units of "sec", with no internal indication what time the file started.Description
Context
The CF format conventions require that time variables always include a reference time in their units attribute, and the PEcAn documentation at least implies that times should be days since 1700-01-01 00:00:00 UTC. Enforcing this at the CF conversion stage would simplify the logic of all the met2model.MODEL functions, and would be more reliable than assuming filenames contain start dates.
Possible Implementation
The text was updated successfully, but these errors were encountered: