-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Harmonize encoding from h5netcdf with netcdf4 #11067
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
base: main
Are you sure you want to change the base?
Conversation
56c6396 to
71aa924
Compare
| "zlib", | ||
| "szip", | ||
| "bzip2", | ||
| "blosc", | ||
| "zstd", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo: learn why this is a different bug?
pixi.toml
Outdated
| distributed = "2024.6.*" | ||
| flox = "0.9.*" | ||
| h5netcdf = "1.3.*" | ||
| h5netcdf = "1.4.*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
undo if #11068 doesn't get accepted
bea7ba4 to
255d849
Compare
|
closing since being more aggressive seems to be ok |
c0d66e3 to
2006346
Compare
We were trying to figure why certain compression features were not included in our h5netcdf backend. This PR to h5netcdf should provide the filters variable, but I understand that it is too bleeding edge for you all to pin to h5netcdf/h5netcdf#307
0526993 to
25b1b0d
Compare
kmuehlbauer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hmaarrfk typo? It's h5netcdf 1.8.0
yes thanks, i kinda just played off memory. |
We were trying to figure why certain compression features were not included in our h5netcdf backend.
This PR to h5netcdf should provide the filters variable, but I understand that it is too bleeding edge for you all to pin to h5netcdf/h5netcdf#307
xref: #10657
Ultimately, I don't think you can change the backend without ensuring it is "drop in replacement" at least in what concerns metadata.
Critically, if you compress certain data with zstd, and you try to resave it, it would be saved as 'raw' ruining any gains you had from the compression.
whats-new.rstapi.rst