When loading a single rotated MRI dataset, performing a global reinit shows the correct (rotated) perspective. Performing a normal reinit on that dataset completely changes the view: the transversal window does not show transversal slices anymore etc.
This behaviour seems like a bug. If only one dataset is loaded, I would expect global reinit and reinit to do the same. If not, maybe these menu entries should be renamed? In any case, displaying coronal slices in a window that says "transversal" is wrong.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Duplicate | None | T8350 Reinit behaviour for rotated datasets | ||
| Resolved | kislinsk | T8909 Clarify meaning of Global Reinit vs Reinit |
Event Timeline
Comment Actions
I think this behavior is on purpose but could need more explanation:
- "global reinit" makes the first/red render-window display transversal slices, also if the image is not aligned along the MITK world coordinate system. I.e. the global variant calculates a smallest bounding box in world coordinates and makes this bounding box the render-window-world
- "reinit" takes the coordinate system of the selected mitk::Image as the render-window-world
The render windows use their "world" and display 1. xy plane 2. the yz plane 3. the xz plane.
I like the "reinit" version because it displays the actual acquired slices. However, the integration into ExtApp is only technically motivated and could be reworded. Perhaps:
"MPR: Reset to transversal" instead of "global reinit".
"MPR: Display these slices" instead of "reinit"
If somebody arguments against "slices" because polygonal data or point sets don't have slices, I'd argue that nobody who uses the application would care and developers could get used to it.
Other suggestions?
Comment Actions
Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.