Skip to content

BUG: Fix range shifter placement and 3D centering on ion plan import - #344

Open
xskere wants to merge 1 commit into
SlicerRt:masterfrom
xskere:330-fix-range-shifter-placement
Open

BUG: Fix range shifter placement and 3D centering on ion plan import#344
xskere wants to merge 1 commit into
SlicerRt:masterfrom
xskere:330-fix-range-shifter-placement

Conversation

@xskere

@xskere xskere commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Two problems left imported proton plans with their range shifters in the wrong place and the 3D view unable to center on the patient:

First, the dynamic beam sequence import applied the isocenter translation twice: once while updating the beam transform and again explicitly afterward. This placed every imported beam and its range shifter at twice the isocenter offset, more than a metre from the patient. The redundant second translation has been removed so imported beams and range shifters sit at their correct location.

Second, a retracted range shifter was drawn shifted sideways off the beam axis, which pushed it outside the field of view and further skewed the automatic centering. The range shifter model now always stays on the beam axis, and whether it is retracted or inserted is conveyed through its transparency rather than it being moved out of position.

Re #330

Two problems left imported proton plans with their range shifters in the wrong place and the 3D view unable to center on the patient:

First, the dynamic beam sequence import applied the isocenter translation twice: once while updating the beam transform and again explicitly afterward. This placed every imported beam and its range shifter at twice the isocenter offset, more than a metre from the patient. The redundant second translation has been removed so imported beams and range shifters sit at their correct location.

Second, a retracted range shifter was drawn shifted sideways off the beam axis, which pushed it outside the field of view and further skewed the automatic centering. The range shifter model now always stays on the beam axis, and whether it is retracted or inserted is conveyed through its transparency rather than it being moved out of position.

Re SlicerRt#330
@cpinter

cpinter commented Aug 3, 2026

Copy link
Copy Markdown
Member

If @ferdymercury agrees then we can integrate. Thank you!

@ferdymercury ferdymercury left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks a lot!

Not sure if the RangeShifter Opacity settings could be configured via two GUI buttons ? Or is hard-coded 0.05 vs 0.3 good enough ?

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