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

BUG: Do not display volume rendering if volume is under non-linear transform #7065

Merged
merged 1 commit into from Jul 4, 2023

Conversation

lassoan
Copy link
Contributor

@lassoan lassoan commented Jul 4, 2023

This commit just hides the volume and logs a message if a non-linearly transformed volume is attempted to be displayed using volume rendering.

This is a partial fix, as it would be better if the user was warned on the GUI in advance that the volume will not be displayed; and it would be even better to allow correct display of the volume regardless of what transform it is under. Still, this fix is useful as it prevents a volume from appearing in incorrect position.

see #6648

…ansform

This commit just hides the volume and logs a message if a non-linearly transformed volume is attempted to be displayed using volume rendering.

This is a partial fix, as it would be better if the user was warned on the GUI in advance that the volume will not be displayed; and it would be even better to allow correct display of the volume regardless of what transform it is under. Still, this fix is useful as it prevents a volume from appearing in incorrect position.

see Slicer#6648
@lassoan lassoan added this to the Slicer 5.3 milestone Jul 4, 2023
@lassoan lassoan requested a review from pieper July 4, 2023 17:14
@lassoan lassoan self-assigned this Jul 4, 2023
Copy link
Member

@pieper pieper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems logical to me. I was thinking we could just harden the transform internally so that it renders as expected even if it's slow, but we can always add that in the future.

@pieper pieper enabled auto-merge (squash) July 4, 2023 18:36
@pieper pieper merged commit f541fb5 into Slicer:main Jul 4, 2023
5 checks passed
@lassoan lassoan deleted the hide-warped-volume-rendering branch July 4, 2023 21:50
@lassoan
Copy link
Contributor Author

lassoan commented Jul 4, 2023

Thanks for the review. Implementing hardening internally would be better, but it would be a bit more work (we would need to expose the hardening API in a way that it could be used without modifying the existing node or creating a new node; we would also need to ensure that the resampling is done automatically when the volume or transform is changed, and not recomputed unnecessarily).

@pieper
Copy link
Member

pieper commented Jul 5, 2023

I was also wondering if we can make a workaround recipe for this using the CLI autoexecute feature with one of the resampling CLIs.

@lassoan
Copy link
Contributor Author

lassoan commented Jul 6, 2023

Good idea. We could work on it next time somebody asks for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants