stackImagePositionSynchronizer should only synchronize images on approximately the same plane
See original GitHub issueI’ve had a number of users report to me directly that the stackImagePositionSynchronizer
exhibits unexpected behavior. For example:
- Two axial stacks
- Two coronal stack
When scrolling one of the axial stack’s, I would expect the other to update it’s image to the closest slice. I would expect both coronal stack’s, because their for a different orientation, to remain on their current image.
Unfortunately, in some instances, we stacks in other orientations “jump” to a new image. Often the first or last one in their stack.
We can accomplish this by updating the synchronizer to discount images that aren’t in the same orientation. I think the math here is making sure the row dot product and column dot product are ~1 for the two images being compared (the source image, and each target image in the stack)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:10
Top GitHub Comments
Hi @ranasrule. Yesterday we had some problems with our Gitlab server, now it’s back online. Please try again, sorry for the inconveniences.
Hi @ranasrule,
I’m very sorry for the response delay. The commit mentioned above, is our implementation of the solution to the scroll synchronization error between viewports. In brief, we added a sync botton to the toolbar when two or more viewports are active and that component has the needed logic to sync the viewports in a correct way.
The error that you described earlier is because we use a custom field in the ohif settings that indicates the study instance UID that you want to visualize, here are an example of this settings:
Best regards.