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
But as you mentioned, the issue with this solution is that "filters" are saved in the zarr files (.zattrs and .zmetadata) which makes it necessary for users to have this filter installed on their machine when opening the dataset. However, this particular filter can be seen as a one way filter and does not need a decoder for reading.
Applying bitrounding directly to the Dataset circumvents the writing of the filters information, but still keeps the information about the number of keepbits in the _QuantizeBitRoundNumberOfSignificantDigits attribute.
Explain the different approaches how BitRounding and Zarr can be used and explain why we have chosen not the alternative approach below:
But as you mentioned, the issue with this solution is that "filters" are saved in the zarr files (
.zattrs
and.zmetadata
) which makes it necessary for users to have this filter installed on their machine when opening the dataset. However, this particular filter can be seen as a one way filter and does not need a decoder for reading.Applying bitrounding directly to the Dataset circumvents the writing of the
filters
information, but still keeps the information about the number of keepbits in the_QuantizeBitRoundNumberOfSignificantDigits
attribute.Originally posted by @observingClouds in #71 (comment)
The text was updated successfully, but these errors were encountered: