- User Since
- Aug 1 2016, 12:10 PM (181 w, 3 d)
Aug 2 2016
For some reason it appears that the spacing gets changed for 3D image data during the measurement process. While the original scene file has a spacing of 0.3/0.3/1 the scene file WITH measurement has a spacing of 0/0/1.
[a02c31]: Merge branch 'bug-16086-LiveWireBoxImprovement'
2013-09-23 10:28:19 Arthur Teimourian [22a074]
Fixed LiveWire Box
New remote branch pushed: bug-16086-LiveWireBoxFix
New remote branch pushed: bug-16086-LiveWireBoxImprovement
[f77b23]: Merge branch 'bug-15805-ReduceContoureSetFilterCrashFix'
2013-09-19 13:28:07 Arthur Teimourian [2ea003]
New remote branch pushed: bug-15805-ReduceContoureSetFilterCrashFix
It was a file package from Jan, which he distributed for the last MITK-Diffusion testing.
Crash occurs when using IVIM data.
sorry caspar my bug
New remote branch pushed: bug-15062-faulty-image-in-documentation
My code tries to avoid that the DICOMSeriesReader sets the spacing to 0.
No I am not. I had requested a core changed request a few month ago, which got rejected.
MITK still crashes while loading fluoroscopy DICOM images. Added attachment to bug.
Fluoroscopy Arthur's hand (Test Image)