The Graphcut plugin was excluded due to Patent-Issues
(ITK also included a graphcut function, but excluded it again as well due to patents).

not working on that atm. but maybe sometimes in the future

I just made an easy fix ,that allows seedsImages to be saved like and image.

error message

Another solution: Establish a novel file ending "msi" for mitk seeds image. Its actually saved as PIC, but when it is loaded, its put into a mitk::seedsimage

reverted blueberry changes.
Now waiting for the repository to go green for comitting

[SVN revision 28600]
FIX (#5732): Reverted changes to blueberry framework.

Now, all Tests and all changes have been done!

[SVN revision 28692]
COMP (#5557): Updated SlicedGeometry3D Test. mitk::Geometry3D::GetCornerPoint should apparently return the same value, wether it is an imageGeometry or not.

[SVN revision 28812]
COMP (#5557): Updated TimeSlicedGeometry Test.

All geometry changes have been committed and tested successfully.

[SVN revision 28816]
FIX (#5557): Corrected signed/unsigned comparison

[SVN revision 28634]
FIX (#5557): Adjusted Geometry Tests

[SVN revision 28636]
COMP (#5557): The function "FitGeometry" was adding 0.5 offset, if it is an imagegeometry! No manual 0.5 offset correction allowed anymore!!! See geometry doc!

[SVN revision 28691]
FIX (#5557): Undid bad changes in mitk::Geometry3D::GetCornerPoint and mitk::BoundingObject::FixGeometry

Newest Patch for Geometries and Segmentation Tools

[SVN revision 28633]
FIX (#5557): Small Bugfix: The function "GetCornerPoint" was adding 0.5 offset manually, if it was an imagegeometry. This has been removed.

Basically all the changes were:

• give a warning, when trying to add a non-image-geometry onto an image using setGeometry
• for each kind of geomety a function called "ChangeImageGeometryConsideringOriginOffset" has been implemented to add/remove the offset for center-based behavior
• Comments for several functions improved

[SVN revision 28568]
FIX (#5557): Adjust Geometries to center-based behaviour if they are image-geometries

Ivo and me agreed on a final solution. You can see it in the newest patch, attached to this bug. We would like to commit it like this.

A newer patch with all the changes to fix this bug

Patch for Geometries and Segmentation Tools

The attached Patch corrects geometries behaviour and fixes the behaviour of the segmentation tools.

A newer patch with all the changes to fix this bug

Newest Patch for Geometries and Segmentation Tools

We found the problem.

We had to make some more changes .. a new (better) patch is coming soon

Killed the bug locally by changing mitk::image::setGeometry and creating the function
mitk::Geometry3D::ChangeImageGeometryConsideringOriginOffset(bool isAnImageGeometry)

Patch for Geometries and Segmentation Tools

Still could not fix it, postponed to 3M4 release.
Would be happy if someone else could have a look at it.

Bug is still there. We were not able to fix it yet.
Maybe postpone it.

Bug still appears in 3M3 v 1.0 installer version

Bug is quite critical. Makes the organ-segmentation via shape models in 3M3 v1.0 quite unusable.

4d binary image

reopened, thomas wants it!
a 4D MITK Surfaces for testing can easily created by opening the attached binary 4D image and click "Create Polygon Model" from the context menu (Segmentation bundle needs to be enabled).

It is probably not possible to store 4D models in STL format. Are there other 3D model formats that we (or ITK/VTK) support to store 4D models?

4d binary image

Some changes have been made in the segmentation bundle in context of another bug (do not know the ID). Anyway, the segmentation bundle supports segmentation of binary images now.

MITK won't freeze anymore, when saving a 3D/4D image in inproper format (bmp). Instead we just get error messages

[SVN revision 25557]
FIX (#5129): corrected Signal/Slot connection, so the sliders of "bilateral filter" are working properly now

All geometry changes have been committed and tested successfully.

[SVN revision 25833]
FIX (#4948): Corrected some offset issues, see bugtracker for more details

problem occurs in all the tools of the manual segmentation bundle. Reverted some of the changes made in rev 19782 to compensate offset.

mitkContourUtils.cpp -- Checked
mitkCorrectorAlgorithm.cpp -- need to be checked
mitkContourTool.cpp -- Checked
mitkPaintbrushTool.cpp -- need to be checked
mitkRegionGrowingTool.cpp -- Checked (but maybe another bug detected. Starting Region sometimes quite far away from starting pixel)
mitkSegTool2D.cpp -- Checked
mitkSetRegionTool.cpp -- need to be checked (fill/erase)

changed Signal/Slot behaviour. Cropping object is now a helper object.

[SVN revision 24952]
FIX (#4736): changed Signal/Slot behaviour. Cropping object is now a helper object

[SVN revision 26151]
FIX (#4692): Added if-check for imagegeometries to the function mitkGeometry3D::IsIndexInside, so it can produce correct output

Little graphic to make the coherence of coordinates more comprehensible

All geometry changes have been committed and tested successfully.

coordinates

I had a look at it. It is possible to convert 4D mitk images to itk images, apply itk filters on them and get back the result in a 4D mitk image. You have to use the correct macros. Do not use "AccessByItk" but "AccessFixedDimensioByItk" !!

@Xin : What's the statuss?

4D Pointsets are not still not fully supported!

T8092 needs to be finished first

Could not reproduce the bug, propably fixed with geometry changes

Quite a lot changes happened at Geometry3D.
Need to check if this bug is still contemporary..

We have a look

Please checkout the branch
bug-3199-StringVectorPropertyForPointSet

I need to stop working on this bug due to more important bug (this here is only a feature request). For anyone who want to continue here:

Currently trying to manually insert the patch locally.
Still need to adjust Mapper2D and Mapper3D

Current Status:

Results of discussion in the MITK meeting:

Bug is not very specific. My images load in accetpable speed. Can we maybe close this, Markus?