Open 03shek opened 3 months ago
In MPR mode, SR localization jumps to wrong instances (since it can become an inverted image stack) sometimes. Eg., default 1x1 viewport instance 1 is legs. Once in MPR mode, instance 1 is head in WB CT.
Phantom study that exhibits the bug without anatomy (pwd: "secrecy"): https://fileshare.uhn.ca/download/39c5d602-6f95-4882-8cff-e3c2fe7e38bf
CT with default 1x1 viewport instance 1 is legs. Once in MPR mode, instance 1 is head in WB CT.
Default viewport see legs on i=1.
Make 2 measurements corresponding to i=1 (legs) and i=end (head).
Load MPR mode.
Axial MPR mode i=1 shows head.
SR localization becomes inverted/wrong
Localize to measurement for legs, but viewport jumps to head. Measurement at this location stays yellow (ie, not current).
Localize to measurement for head, but viewport jumps to legs. Measurement at this location stays yellow (ie, not current).
Exiting MPR mode to Common Hanging protocol 1x1 does not fix this, only dragging series into 1x1 viewport does.
Windows 10
000000
Chrome 126.0.0
I think i know what is happening
Describe the Bug
In MPR mode, SR localization jumps to wrong instances (since it can become an inverted image stack) sometimes. Eg., default 1x1 viewport instance 1 is legs. Once in MPR mode, instance 1 is head in WB CT.
Phantom study that exhibits the bug without anatomy (pwd: "secrecy"): https://fileshare.uhn.ca/download/39c5d602-6f95-4882-8cff-e3c2fe7e38bf
Steps to Reproduce
CT with default 1x1 viewport instance 1 is legs. Once in MPR mode, instance 1 is head in WB CT.
Default viewport see legs on i=1.
Make 2 measurements corresponding to i=1 (legs) and i=end (head).
Load MPR mode.
Axial MPR mode i=1 shows head.
SR localization becomes inverted/wrong
The current behavior
Localize to measurement for legs, but viewport jumps to head. Measurement at this location stays yellow (ie, not current).
Localize to measurement for head, but viewport jumps to legs. Measurement at this location stays yellow (ie, not current).
Exiting MPR mode to Common Hanging protocol 1x1 does not fix this, only dragging series into 1x1 viewport does.
The expected behavior
OS
Windows 10
Node version
000000
Browser
Chrome 126.0.0