You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The addition of zarr as an output format (#1165) is a great step forward, as it significantly improves the storage efficiency of my large particle files! It is also important to note that the initialisation of a ParticleSet from a .zarr particle file is also possible. So I suggest to update the parcels documentation for ParticleSet.from_particlefile() so that other users know that this functionality is also possible with zarr.
Cláudio
The text was updated successfully, but these errors were encountered:
Hi @claudiofgcardoso, thanks for the comment. Yes, it would be a good addition to also support zarr in ParticleSet.from_particlefile(). But I'll do that as part of the larger refactoring project this summer, where I'm implementing dumping directly to zarr during a pset.execute() (instead of dumping to temporary npy files).
There are at least three advantages of using zarr directly:
Hi @erikvansebille, glad to read that Parcels is migrating to zarr and I'm looking forward for this merge! There's no need to keep this issue open so I'll close it :)
Hello all,
The addition of zarr as an output format (#1165) is a great step forward, as it significantly improves the storage efficiency of my large particle files! It is also important to note that the initialisation of a ParticleSet from a .zarr particle file is also possible. So I suggest to update the parcels documentation for
ParticleSet.from_particlefile()
so that other users know that this functionality is also possible with zarr.Cláudio
The text was updated successfully, but these errors were encountered: