Skip to content
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

get cartesian view invalid pixels to be nan. #1767

Merged
merged 3 commits into from
Dec 19, 2024
Merged

Conversation

saransh13
Copy link
Member

@saransh13 saransh13 commented Dec 16, 2024

As above. The other change is that the distance is always in the direction of the x-ray propagation direction. negative distances should not be specified for the image anymore.

Previous view vs current view comparison below:

Screenshot 2024-12-16 at 3 15 13 PM

Screenshot 2024-12-16 at 3 12 42 PM

@saransh13 saransh13 requested a review from psavery December 16, 2024 23:15
@pep8speaks
Copy link

pep8speaks commented Dec 16, 2024

Hello @saransh13! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 25:1: E302 expected 2 blank lines, found 1

Comment last updated at 2024-12-18 21:34:51 UTC

saransh13 and others added 3 commits December 18, 2024 15:34
It is expected to always be positive now, so enforce this in the GUI,
and handle old settings where it may have been negative.

Signed-off-by: Patrick Avery <[email protected]>
This sets pixels to nan that are either:

1. Part of a detector's panel buffer
2. Not located on any detector

This is important for making FIDDLE images appear nice.

Signed-off-by: Patrick Avery <[email protected]>
@saransh13 saransh13 merged commit 95e7586 into master Dec 19, 2024
9 checks passed
@saransh13 saransh13 deleted the cartesian-fix branch December 19, 2024 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants