-
-
Notifications
You must be signed in to change notification settings - Fork 2
Avoid using h5netcdf? #23
Comments
It's possible that we can just remove |
Getting a lot of these errors atm:
Reopening this issue, didn't seem to resolve it. |
Reverted this via #30 to fix deployment. |
Eak, sorry about this, I really need to write some more tests so we can catch simple failures like this before pushing to master. Sorry, my bad! I'll look into this next week |
No worries! Yes, we should probably add some tests haha |
I've recreated this issue locally. I've tried changing the engine to all the options (other than |
I've recreated this issue locally. I've tried changing the engine to all the options (other than But I think I've got it working without @fwirtz no rush, but please could you try this new code on AWS? |
@JackKelly Will do! Thanks. |
That worked! |
MetOfficeMessage.load_netcdf()
ends with the line:return xr.open_dataset(netcdf_bytes_io, engine='h5netcdf')
This means we must include
h5netcdf
inenvironment.yml
. But, includingh5netcdf
forces conda to downgradecartopy
from v0.18 to v0.17, which breaksnwp_plot.py
:One solution may be to see if we can use an xarray engine which isn't
h5netcdf
.The text was updated successfully, but these errors were encountered: