-
Notifications
You must be signed in to change notification settings - Fork 2
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
year 0 exists #38
Comments
@doutriaux1 thanks for raising this, I believe I have hit the same problem before.. |
Marking issue as stale, since there has been no activity in 30 days. Unless the issue is updated or the 'stale' tag is removed, this issue will be closed in 7 days. |
@jasonb5 this is similar in some ways to #46, and I know that @pochedls has suggested a work around for the issue (so rather than a traceback as above, it works) in CDAT/cdms#334 |
I need to look at the code to get an idea of what changes are required. I see two viable options going forward:
|
Marking issue as stale, since there has been no activity in 30 days. Unless the issue is updated or the 'stale' tag is removed, this issue will be closed in 7 days. |
Marking issue as stale, since there has been no activity in 30 days. Unless the issue is updated or the 'stale' tag is removed, this issue will be closed in 7 days. |
0-12-31 0:0:0.0
BUT
Traceback (most recent call last):
File "", line 1, in
File "/1Tb/miniconda3/envs/jupyter-vcdat/lib/python3.6/site-packages/cdtime/compreltime.py", line 254, in reltime
return _cdtime.reltime(value, units)
ValueError: Invalid relative time units
The text was updated successfully, but these errors were encountered: