Repository navigation
Read FITS 16-bit integers as signed and expose BZERO/BSCALE in im.info #10312
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
karandhaodiyal28-hash
wants to merge
5
commits into
python-pillow:main
Choose a base branch
from
karandhaodiyal28-hash:fix-fits-16bit-signedness
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.
+126
−7
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
eae5c49
Read FITS 16-bit integers as signed and expose BZERO/BSCALE in im.info
karandhaodiyal28-hash 34c6620
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 2c2333b
Use format specifiers in FITS test helper
karandhaodiyal28-hash 8ed26bb
Handle consecutive-sample payloads in FitsGzipDecoder
karandhaodiyal28-hash ce9d598
Use explicit little-endian rawmodes in FitsGzipDecoder
karandhaodiyal28-hash 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
Binary file not shown.
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
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.
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.
Could we preserve integer precision when parsing
BZEROandBSCALE?Right now, every value goes through
float()before being converted back to an integer. For example,BZERO = 9007199254740993would end up stored as9007199254740992because the original integer isn't exactly representable as a float.Since the PR leaves image scaling to the caller, losing precision in the metadata could lead to incorrect pixel values when that scaling is applied.
Maybe we could try parsing integer literals with
int()first, then fall back tofloat()for decimal or exponent notation. A regression test with an integer larger than2**53would help.