Parcels is slow with v1.4.2 of netCDF4 on python3 #513
Comments
|
Related: Unidata/netcdf4-python#809 |
|
Does one has to limit the netcdf version of the environment ? like a downgrade via conda-forge? or is this a parcels intern issue - if the case how can I downgrade the netcdf version there? Thanks in advance! |
|
I now downgraded the netcdf version via conda install -n env_name -c conda-forge netcdf4=1.4.1 works fine :D |
erikvansebille
added a commit
to conda-forge/parcels-feedstock
that referenced
this issue
Mar 5, 2019
updating version, sha256 and build number for v2.0.0beta2 Also limiting netcdf4 to v1.4.1, because of issues with v1.4.2 (see OceanParcels/parcels#513)
erikvansebille
added a commit
to erikvansebille/parcels-feedstock
that referenced
this issue
Mar 5, 2019
updating version, sha256 and build number for v2.0.0beta2 Also limiting netcdf4 to v1.4.1, because of issues with v1.4.2 (see OceanParcels/parcels#513)
Merged
|
This has now been fixed in #597 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've recently seen that Parcels can sometimes be very slow on python3. After some digging around, we think that this is related to a recent upgrade of the
netCDF4package. We therefore suggest to avoid using v1.4.2 of the netCDF4 package, especially if you're using python3.The plan now is to wait for a future update of
netCDF4, and see if that fixes the slowness.The text was updated successfully, but these errors were encountered: