- User Since
- Aug 1 2016, 12:10 PM (225 w, 5 d)
Wed, Nov 25
Tue, Nov 24
apparently a vtkLoopUpTable is set automatically so the property as such cannot be used to handle custom vtkLookUpTables
Oct 22 2020
In T26382 the recent developments are summarized.
Oct 6 2020
Oct 5 2020
-ADD: A segmentation is drawn on timestep 0, if I change the timestep, the segmentation remains and I can add a new segmentation on timestep !=0, both segmentations are visible since I only have one timestep --> As axpected
-SUBSTRACT: The drawn segmentation can be removed independent from the timestep 0 and timestep !=0 --> As expected
-CORRECTION: The drawn segmentation is removed independent from the timestep 0 and timestep !=0 --> As expected
-PAINT: Painted segmentation occurs on timestep 0. When changing the timestep, the painted segmentation is added to the static segmentation --> As expected
-WIPE: Segmentation is wiped on timestep 0 and wiped on timestep !=0 --> As expected
-RegionGrowing2D: Region Growing is applied on timestep 0 (fits to the image). When changing the timestep, the region growing result fits to the timestep. No crash. Quite slow updates. --> As expected
-FILL: Different timesteps can be filled. When changing the timestep, the segmentation remains --> As expected
-ERASE: Different timesteps can be erased. --> As expected
-2D FastMarching: T27721
It really suprises me that FastMarching2D crashes now since I explictly played with timesteps in T26975. But maybe I truly overlooked something, then I am sorry.
Sep 25 2020
Request discussion result:
Sep 18 2020
I think the things you changed are all reasonable, the things I would add (I can not do it atm because I don't have access to the document)
Sep 16 2020
I agree :)
just started to have a look.
Sep 4 2020
Sep 3 2020
@kislinsk @kalali I have in mind that you recently had a look at the ClippingPlane. Since the clipping plane does not show the expected behavior, does it make sense to rewrite the documentation for it? I have in mind you even considered to declare it deprecated.
Sep 2 2020
should work now
I just received an E-Mail that the problem could be related to the data source (some server or network drive) so maybe no MITK issue after all :)
I would suggest that at least the plugin feedback in the GoogleDocs and the toplevel-> main page /MITKUserManual should be corrected before the Release. The rest should be corrected soon after.
@kislinsk: should we further investigate this or have a known issue section in the documentation?
Sep 1 2020
The log information in the console which Jonas reported doesn't turn up. So the console doesn't show any new information after the reader is selected.
I will ask about the HDD / IO.
I am not sure if that is related but today one of my cooperation partners reported that she couldn't open an 4D image in MITK (Latest develop installer).
On my laptop it just works fine. On her laptop, however, she doesn't even get to the logging point. It doesn't show anything, it just stops (She closed the workbench after 10 Minutes).
I asked her whether it was an ancient laptop, but no ;)
Aug 31 2020
- To my knowledge it should generate a mask out of a Surface and in MITKData there should be some...I will have a look
- That is rather a bug, because in Phenotyping there is a reference that shouldn't be there, maybe we can remove that.
Aug 28 2020
Region growing task can be found here T27684
Aug 27 2020
Aug 21 2020
Crash fixed by D380 :)
Aug 14 2020
Proposed a fix in D388, maybe there is a more elegant way but it works now
@kalali this looks like a bug introduced by the selection concept?
Aug 13 2020
Aug 10 2020
Aug 7 2020
Oh I didn’t look into the Differential yet, only tried it with the current develop. The crash I observed in with FastMarching3D
So I have a fix for the contour problem but what is missing is that the pointset is still drawn on timestep 0 instead of the current timestep and I have to figure out why.
I also experience a crash in the tool:
File is FastMarchingTool.cpp
I can partly confirm it.
Aug 6 2020
2D Segmentation tools:
Aug 4 2020
Aug 3 2020
Test image: 3D+t Heart
duplicate to T27641
You totally right and the reason why I oversaw this is when I double checked:
Aug 2 2020
All issues have been adressed in respective subtasks.
Jul 31 2020
Jul 30 2020
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
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)
Eventually related to changes in D360