Open bnlawrence opened 3 years ago
Hi Bryan, Could you let me know what the LBTIM header value is? The code is beholden to that - I'm most interested in the "units" part of the number (https://github.com/NCAS-CMS/cf-python/blob/master/cf/read_write/um/umread.py#L550-L558)
Thanks.
Hi Bryan - I think I may have worked this out - the default calendar behaviour of cftime
changed at cftime 1.3.0
. Assuming thaet this is the case, you either go back to cftime 1.2.0
, or wait until we release cf-python 3.8.0 later this week. The new cf-python requires cftime>=1.3.0
and is adjusted accordinginly.
You're too quick for me ... does this mean I don't need to find the LBTIM header? If so, I can wait for cf-python 3.8.0. Ta.
Yes - no need to go digging in the header, I think. It would be nice to test this theory out, though ... do you have a test file handy? Thanks.
I am attempting to aggregate as set of UM pp files in a directory. These include a file which appears to have a 30th of February. I had expected cf-python to warn me and change to a
360_day
calendar (or allow me to specify it in the read statement).Error message
Environment: sci6.jasmin.ac.uk, private conda install: