I am currently removing the last remains of ipPic from MITK (not yet as a dependency of ipFunc, though), and will also remove or convert the last .pic and .pic.gz files from MITK-Data
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 10 2021
Nov 2 2021
Oct 14 2021
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Oct 8 2021
I close this meta task. The last open task seems to be T18866, but as the priority indicates it has low priority.
Oct 7 2021
@kislinsk How to proceed here?
Aug 6 2021
Jul 15 2021
Due to the refactoring of the (MultiLabel) Segmentation modules / plugin views we postponed this again. We need the functionality to explicitly address specific labels of a label set image so that we can compute the center of mass of a specific label.
Also, in the long run we don't want to rely on the data manager / context menu to select the current segmentation / jump to the current segmentation but rather provide additional possibilities (e.g. inside other plugin views) to focus the camera view to a segmentation mask.
Jul 14 2021
Jun 22 2021
Jun 4 2021
Apr 9 2021
Apr 7 2021
Mar 10 2021
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Feb 3 2021
We discussed this and decided to open a new task to cleanly define the problem. We thought that this task mixes many different things without stating the minimal steps to reproduce a single problem, so please continue here: T28270
I don't mind, I'm not planing to fix this before the release, so if you have time. I'm testing this with the develop branch and comparing it with the MITK 2018 installer.
Beware of a few things. T28211: [Image Rendering] Color change/ Opacity strange behaviour (only in Windows installers) also fixed rendering of image slices in 3-d, so I suggest to use the latest release branch to test anything related instead of the snapshot installers.
Feb 2 2021
In T19522#68902, @goch wrote:Specifically it is not visible on the 2D planes in the 3D render window, this error is unrelated to volume rendering.
Jan 19 2021
- The new selection concept automatically removes non-matching segmentation nodes if the reference image was changed. A warning is shown Select or create a segmentation (Tools disabled)
- The new selection concept does not allow to select a non-matching segmentation node
- Selecting a matching segmentation node that is invisible results in the warning: The selected segmentation is currently not visible! (Tools disabled)
- Showing the invisible segmentation node results in the warning: Please perform a reinit on the segmentation image! (Tools disabled)
- Performing a reinit on the matching segmentation node enables the tools (no warning shown)
We are now using a different approach but this should be verified with the new widgets.
Jan 2 2021
Nov 11 2020
The original issue of this task was fixed a long time ago.
Hi there! 🙂
Hi there! 🙂
Oct 26 2020
I just stumbled upon this while testing the utilities with 4D data. Depending on the number of timesteps and the complexity of the operation the selected operation might take a while (you ca actually see the progress in the console output).
This should be discussed as I do not see any
whole new segmentation functionality this year
Oct 23 2020
This tasks came up again in the discussion of the clipping plane plugin, which allows for volume annotations for segmentations. Since we decided to remove the clipping plane plugin from the MITK release, this task was tagged with "Next Milestone" in order to restore the useful feature of volume annotations also outside the clipping plane plugin.
Sep 30 2020
mitkToolInteractionTestSuite in mitkToolInteractionTest.cpp does not contain any tests (all disabled)
Sep 25 2020
Sep 22 2020
Hi there! 🙂
Sep 10 2020
Meanwhile another cmdline app for extracting time steps was written.
Deleted branch T19828-dynamic-analysis-improvements-snapshot.
Deleted branch T10304-NavigationDataPlayerAsTrackingDevice_2017_01.
Deleted branch T19831-CommonMiniApps.
Deleted branch T19830-fixing-rendering-of-arbitraryTimeGeometries-snapshot.
Deleted branch T19830-fix-rendering-of-arbitrary-TimeGeometries-master.
Deleted branch T19814-4d-planarfigures-master.
Deleted branch T19473-consider-triggertime-in-DICOM-loading-rebased.
Deleted branch T19814-4d-planarfigures-master2.
Deleted branch T19814-4d-planarfigures-master-rebased.
Deleted branch T19473-consider-triggertime-in-DICOM-loading.
Deleted branch T19724-usBasedFeatureProcessing.
Deleted branch T19784-AddQtAAEnableHighDpiScaling.
Deleted branch T19168-CleanPluginIntegration.
Deleted branch T19736-NavigationModuleDocumentation_2016_09.
Deleted branch T18881-FixIGTTimeStampAndReaderWriter.
Deleted branch T19609-integration-branch.
Deleted branch T10304-NavigationDataPlayerAsTrackingDevice.
Deleted branch T18520-ConstCorrectForGeometries.
Deleted branch T19786-ImplementOverlayLayouterAsServiceStyleRebase.
Deleted branch T19786-ImplementOverlayLayouterAsServiceRebaseNov.
Deleted branch T19786-DICOMAnnotationDemo.
Deleted branch T19786-ImplementOverlayLayouterAsOverlayManagerReplacement.
Deleted branch T18922-OpenGLBackendRebase2.
Deleted branch T18922-OpenGLBackendRebase.
Deleted branch T19360-legacy-scene-surface-line-width-incompatible.
Deleted branch T19801-planar-figure-interactor-crash.
Sep 1 2020
Hi there! 🙂
Aug 26 2020
Is this still a topic?
Aug 21 2020
Crash fixed by D380 :)
Aug 7 2020
In T18436#208159, @thomass wrote:Oh I didn’t look into the Differential yet, only tried it with the current develop. The crash I observed in with FastMarching3D
Oh I didn’t look into the Differential yet, only tried it with the current develop. The crash I observed in with FastMarching3D
Did you experience the error based on the Differential? Did you open FastMarching for 2D or 3D?
I also experience a crash in the tool: