hm, strange. Ad hoc I cannot give a hint. Good you found a workarround. For further investigation, may be mitk::Image has special wrapping instruction, that interferes with your approach.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 30 2020
To finish this task, one should check/verify that all release relevant plugins follow the discussion result.
I'm setting up a clang 10 dart client right now. If that is submitting successfully I would close the task
I can reproduce the behavior for the US4DCyl but not for the heart 3D+t. But it looks exactly like the error for static segmentation and t=2 (that I showed during the telco).
Jul 29 2020
Is this task resolved with the landing of {D360}?
Deleted branch bugfix/T27085-2DRegionGrowing.
Seems like I figured it out. What I had to do was to change SWIG_TypeQuery("_p_mitk__Image") to SWIG_TypeQuery("_p_itk__SmartPointerT_mitk__Image_t") and change the type of image to mitk::Image::Pointer *image. When passing Pic3D now and printing the number of dimensions, 3 is printed as one would expect. I will further investigate how to interact with other libraries like SimpleITK.
I tried an approach like @floca suggested with the SWIG wrapping that is already available in MITK. Here is my code to transfer a MITK image from C++ to Python:
@thomass I checked Fast Marching 3D and re-opened T18436: [Segmentation] Fast Marching 3D Tool only supported for first time step in 4D images for the static mask cases.
Could you re-check the dynamic case? I tested it and with t = 0 I got a dynamic mask (4D) with a segmentation only on the first (0) timestep but with t != 0 I have the same problem as described in the mentioned task (green contour nowhere near the seed point).
So Region Growing 3D seems to work and could probably be used for reference for other algorithms.
duplicate of T27621
Resolved with D369
that was misleading since the statistics view is in the measurement toolkit view (actually it is quite confusing, maybe we can change that in general)
Pushed new branch T27618-UpdateReadme.
Eventually related to changes in D360
Jul 28 2020
If you use Python 3.7/3.8, you need to install SWIG version 4.0.2. This solves the problem. Currently, SWIG version 3.0.2. is installed in the Superbuild.