Hi Stefan,
yes, I load a series of DICOM images and then save the project as an MITK file.
The slice duplication seems to occur after several save / load iterations. Note
that when I export the segmentations into NRRD files, they have the right size.
Kind regards,
Peter Salz
Here is the output of the detail section:
Image (0x12d280c70)
Dimension: 3
Dimensions: 512 512 127
Channel: Unnamed [scalar]
PixelType: scalar
BitsPerElement: 2
ComponentType: short
NumberOfComponents: 1
BitsPerComponent: 16
TimeSlicedGeometry: TimeSlicedGeometry (0x12d284740)
EvenlyTimed: 1
TimeSteps: 1
GetGeometry3D(0): SlicedGeometry3D (0x12d2832a0)
IndexToWorldTransform:
Matrix:
0.683594 0 0
0 0.683594 0
0 0 3
Offset: [-202, -193, -428]
Center: [0, 0, 0]
Translation: [-202, -193, -428]
Inverse:
1.46286 0 0
0 1.46286 0
0 0 0.333333
Scale : 1 1 1
BoundingBox: ( 0,512 0,512 0,127 )
Origin: [-202, -193, -428]
ImageGeometry: 1
Spacing: [0.683594, 0.683594, 3]
TimeBounds: [-3.40282e+38, 3.40282e+38]
EvenlySpaced: 1
DirectionVector: [0, 0, 1]
Slices: 127
GetGeometry2D(0): PlaneGeometry (0x12d27be70)
IndexToWorldTransform:
Matrix:
0.683594 0 0
0 0.683594 0
0 0 3
Offset: [-202, -193, -428]
Center: [0, 0, 0]
Translation: [-202, -193, -428]
Inverse:
1.46286 0 0
0 1.46286 0
0 0 0.333333
Scale : 1 1 1
BoundingBox: ( 0,512 0,512 0,1 )
Origin: [-202, -193, -428]
ImageGeometry: 1
Spacing: [0.683594, 0.683594, 3]
TimeBounds: [-3.40282e+38, 3.40282e+38]
ScaleFactorMMPerUnitX: 0.683594
ScaleFactorMMPerUnitY: 0.683594
Normal: [0, 0, 3]
Am 02.10.2013 um 11:38 schrieb "Kislinskiy, Stefan"
<[email protected]>:
> Hi Peter,
>
> did I understand you correctly that you open an unconverted DICOM image, i.e.
> not a .nrrd file? Can we have a look at the details of your DICOM-image
> (right-click on your image in the data manager and select “Details…”)?
>
> Best regards,
> Stefan
>
> Von: Peter Salz [mailto:[email protected]]
> Gesendet: Dienstag, 1. Oktober 2013 14:22
> An: [email protected]
> Betreff: [mitk-users] MITK duplicates CT slices on its own
>
> Hi,
>
> I am segmenting several CT datasets with multiple materials. It happened
> several times that MITK duplicated slices of the dataset: For example, my
> current dataset has 142 slices, but MITK shows 709, there are 3 or 4
> identical slices before the slider moves to the next slice.
> The most annoying part is, the segmentations are then corrupted, since they
> are still in the 142 slices range. What happens is that everytime I modify
> the segmentation, a vector::_M_range_check error occurs (see screenshot).
>
> This happens with the precompiled MITK 20013.06 version for Mac OS X 10.8.5 I
> downloaded from the MITK website.
>
> I look forward to hear solutions or tips on how to work around this bug since
> I really need to continue with my project (my other project is already on
> hold because of another bug I reported concerning loading and saving DICOM
> images). Also, many hours of segmentation seem to be wasted, which is really
> frustrating.
>
>
> Kind regards,
>
> Peter Salz
>
> <image002.jpg>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
