-
Notifications
You must be signed in to change notification settings - Fork 65
Correctly handle HDF5 fillvalue for string dtype arrays. #988
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
Open
sharkinsspatial
wants to merge
8
commits into
main
Choose a base branch
from
fix/problem_fillvalues
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+106
−4
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
9ed7c07
Correctly handle HDF5 fillvalue for string dtype arrays.
sharkinsspatial ecc6c02
fix: handle H5Dataset missing fillvalue attribute with dtype-based fa…
abarciauskas-bgse 22c67b0
Merge branch 'main' into fix/problem_fillvalues
maxrjones 7d41afb
Update virtualizarr/parsers/hdf/hdf.py
maxrjones a5138ab
Update changelog entry
maxrjones dab4cf7
Merge branch 'main' into fix/problem_fillvalues
TomNicholas 2e91a26
Apply suggestion from @maxrjones
sharkinsspatial b38e56c
Merge branch 'main' into fix/problem_fillvalues
sharkinsspatial File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
I'm wondering if this could be introducing a different type of bug where now we are introducing a value for the zarr metadata
fill_valuethat could differ from what is in the dataset's original metadata. I realized today that for GPM IMERG HH precipitation theattrsfrom the h5py Dataset include both_FillValueandCodeMissingValuewhich both are-9999.0:Whereas this fallback returns
1e+20:I recognize that
CodeMissingValueis not a standard attribute (as far as I can tell), but should the zarrfill_valueattribute fall back to the_FillValueattribute picked up by h5py?Looking at NASA-IMPACT/veda-odd#371 would this be handled by the more general purpose phase 3 "
fill_value_defined()distinction: stop propagating h5py-default fills to zarr storage."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.
@maxrjones curious what you think
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.
@abarciauskas-bgse For clarification,
fill_valueand_FillValueare distinct semantic concepts https://virtualizarr.readthedocs.io/en/stable/custom_parsers.html#fill-values.fill_valueis always set byHDF5but as you noted above, not all types offill_valuethatHDF5can produce are supported by Zarr v3.Uh oh!
There was an error while loading. Please reload this page.
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.
Right ok, thanks for reminding me about that distinction -- I recalled there were 2 semantic concepts but forgot about the details and that excellent documentation. In that case, since this function is for the first fill value concept --
Value for uninitialized chunks - (e.g., Zarr fill_value)-- then probably this fallback is reasonable?And I recognize that the
h5ds['/Grid/precipitation'].attrs['_FillValue']is for the 2nd conceptSentinel value - (e.g., CF _FillValue ))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.
The
CodeMissingValueis a different issue, but this is a good flag since Zarr's default fill values could differ from numpy or support dtypes not defined innp.ma.default_fill_value@sharkinsspatial why did you chose to use numpy's default fill values here?
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.
That was a change I made, to be clear, and in discussion with @maxrjones it sounds like there may be a Zarr native fallback to use to look into