If more than one image is loaded to datamanager the spacing of the worldGeometry has to be recomputed. The new spacing must be the greatest common divisor(gcd) of all spacings in one direction to cover the pixels of all images.
However this is not implemented that way, as the minimum spacing of each spacings is picked.
( The corresponding lines might be #326 to #325 in mitkDataStorage.cpp )
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Duplicate | None | T8910 META BUG Geometry Cleanup | ||
| Wontfix | None | T16159 Depends on #11948: Crosshair position is wrong in axial view after reinit on other image | ||
| Wontfix | None | T11948 ComputeBoundingGeometry3D grid wrong (world geometry calculation) | ||
| Resolved | kislinsk | T11113 MITK doesn't visualize normalized and thus very small meshes in the expected way. | ||
| Wontfix | None | T10785 Spacing of a worldGeometry of several images is not the greatest common divisor of all spacings | ||
| Wontfix | None | T24071 Revisit 2-d image rendering | ||
| Wontfix | None | T17812 SlicedGeometry3D initialisation fix for non-image geometries | ||
| Resolved | kislinsk | T20204 Provide public getter for reference geometry of sliced geometries | ||
| Resolved | kislinsk | T20217 Equality checks when setting data storage for renderers | ||
| Resolved | kislinsk | T20218 DataStorage::ComputeBoundingBox3D creates geometry with incorrect origin and bounding box | ||
| Wontfix | kislinsk | T24080 Write visual debugging utilitiy for inspecting geometries |
Does this imply any loss of function in its current implementation? Otherwise please adjust the severity to feature request.
Currently we have a shift in MITK, when several images are visible at the same time.
A world geometry is calculated, that includes the geometries of all visible objects. This geometry is used to render the objects onto planes. The used spacing for the rendering is NOT THE original spacing of the objects! the objects are resampled with the spacing of the world geometry. The Spacing of the world geometry is however not the smallest common divisor!
e.g.: Two Images are loaded:
Image1: Spacing (1.00, 1.00, 1.00)
World Geometry Spacing: (0.50, 0.75, 1.00)
The World Geometry Spacing is set as the minimum occuring spacing for each dimension. Due to this, images might be displayed wrong!
To prevent information loss, we could define it as the smallest common divisor. But then, we can easily get extremly small spacings, which will result in extreme memory consumption.
Markus F. should be consulted for solutions.
This bug could not be fixed within the 2013-06 release and has medium severity. Setting target milestone to unspecified.
This bug could not be fixed within the release 2013-06. Setting its target milestone to unspecified
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs