Draft
Conversation
Collaborator
|
The docs specify that when n = p + q, where n is the number of bits in the float and p is the number of bitplanes, the relative error is bounded by 2^(q-23) or 2^(q-52). If that matches our implementation, then this would be a bug. Perhaps you can describe the problem to Peter in the original issue (I’m unfortunately a bit swamped at the moment)? |
Member
Author
|
Yep, that's what we're doing right now. Will go and raise it in the original issue. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Setting ZFP parameters according to llnl/zfp#272 (comment) .
Right now this still violates the error bounds so I am not quite sure why. Observed behavior:
I don't think our
compute_keepbitsfunction is wrong because it works for bit rounding. Additionally, even increasing themaxprecvalue did not seem to fix the issue. I thought that maybe ZFP implicitly assumed for some reason that the data is in double precision so I did a run with assuming 12 non-mantissa bits (instead of 9 for single precision) but that did not fix the issue either, although it reduced the percentage of pixels exceeding the error bound.