If I remember it correctly, the bug was almost resolved.
However, in the last session I was working on it I observed that there was still a problem for rendering labels on layers >1, but I had no chance to dig deeper here. It probably has something to do with the new data structure that was used in the mapper.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 10 2017
May 5 2017
Jan 19 2017
Oct 14 2016
Pushed new branch bug-19522-IntegrationLatestMasterWithMultiLabelPlugin.
Oct 11 2016
Pushed new branch bug-19822-FixDefaultParameterDefinition.
Aug 2 2016
The exception occurs if I try to close the application.
Just for documentation:
Hongzhi Lan, hongzhi@standford.edu, reported a related issue on the MITK Mailing List on 6th April 2016:
[f78cfa]: Merge branch 'bug-19577-vtk-debug-leak'
Merged commits:
2016-02-24 18:25:19 Sandy Engelhardt [aab040]
COMP: quick fix: disable VTK_DEBUG_LEAKS for this test
[f56e84]: Merge branch 'bug-19543-SplineVtkMapper3D-Fix-NewTest'
Merged commits:
2016-02-24 16:10:19 Sandy Engelhardt [a0a9a9]
new SplineVtkMapper3DTest in MITKMapperExt with new MITKData hash tag
[049b4a]: Merge branch 'bug-19543-SplineVtkMapper3D-Fix-NewTest'
Merged commits:
2016-02-24 16:51:15 Sandy Engelhardt [e15df5]
COMP: Set Multisample should fix windows problem
[8f0845]: Merge branch 'bug-19543-SplineVtkMapper3D-Fix-NewTest'
Merged commits:
2016-02-25 11:41:35 Sandy Engelhardt [b101ec]
Adjust data type and test type description in cmake to be both in singular should enable missing test on dashboard
[258fcc]: Merge branch 'bug-19543-SplineVtkMapper3D-Fix-NewTest'
Merged commits:
2016-02-24 17:34:23 Sandy Engelhardt [4d6543]
COMP: Rendering of translucent objects fail on dashboard see new T19575
The issue is almost fixed now (see branch bug-19522-CreateNewMultilabelMapper3D).
A new mapper for multilabel images is required to fix this issue.
Summary of problem description
I changed the bug title, since the segmented region is not shown in the 3D view at all, independent of which segmentation tool used.
[180e8b]: Merge branch 'bug-19515-crash-when-accept-all-slices-for-2D-interpolat
Merged commits:
2016-02-12 02:45:38 Andreas Fetzer [fcae24]
Fixed PixelType when accepting interpolation for all slices
I can confirm this bug.
When drawing a contour during segmentation, the region will be immediately filled (it should be rendered as outline binary).
[732bf6]: Merge branch 'bug-19065-NavigationToolCalibrationView'
Merged commits:
2015-05-26 19:23:10 Sandy Engelhardt [20bfe5]
Append IGTTool file type to filename when saving a NavigationTool
Christoph, are there other further concerns?
Hi Tobi,
This bug looks resolved. Could you close it or are there any other open issues?
[463592]: Merge branch 'bug-18961-Adjust-Image-Cropper'
Merged commits:
2015-04-15 14:10:06 Sandy Engelhardt [cd8836]
adjust help text
What is the status of this bug? Is it an issue for all OS or only for linux?
Hi Tobi,
could you merge this into master or are there any other open issues?
Dear Florian,
Just found the same bug....
I agree to Thomas. My impression is that it never worked before 2014.10.
This bug is related to that the tool is not able to be used on specific pixel types. T17862
I think this is a general issue which depends on your keyboard/language settings.
[e42965]: Merge branch 'bug-18388-ScreenshotMakerFix'
Merged commits:
2014-11-05 16:29:48 Sandy Engelhardt [5f58c3]
Added missing render window update and fixed colors of crosshair
I think the "crazy-going" of the renderwindow is part of the procedure and not actually a bug.
Indeed, an update of the render window is missing after clicking button "High-res Single Screenshot".
When saving the 2D multiplanar renderwindows, the crosshair is rendered in white. I fixed it as well.
Also, there is an update missing when placing the seed point in the region growing 3D tool. The point becomes only visible after additional interaction with the render window.
The bug has been solved within the scope of T19065.
This is related to bug-11476
Rightclick on the level window slider > Images > ... enables to select the image (not only the topmost image) where the new grey level range should be applied to.
[eaf8ad]: Merge branch 'bug-18189-PointSet-Filename-Proposal'
Merged commits:
2014-11-05 16:38:49 Sandy Engelhardt [acbd46]
replace fix file name with data node name
[722112]: Merge branch 'bug-18084-IntegrationBranchBeforeNewRelease'
Merged commits:
2015-05-20 17:00:04 Sandy Engelhardt [dad2a1]
Add test condition to test
ImageTimeSelector seems to use a direct reference on the relevant ImageDataItem (volume or slice) instead of using an additional ImageDataItem.
I removed the MITK_INFO output to console from the core classes that we introduce before committing the code.
A new ultrasound image example has been added to MITK-Data (.../MITK-Data/UltrasoundImages/4D_TEE_Data_MitralValve.dcm and the MITK-Data-Hashtag has been updated.
Some rendering tests still fail on Christoph's nightly due to MITK's event handling (which is not used in VTK).
[97efe3]: Merge branch 'bug-17978-FilePaths'
Merged commits:
2014-08-06 16:22:19 Sandy Engelhardt [49580a]
Update file path and names of used input files
I changed the descriptions accordingly in Step 0 to Step 8 .
I could not reproduce this bug.
Tobi, what is the status of this bug?
Is it fixed since there was already a merge?
We decided that this is unlikely and too hard to reproduce. Feel free to re-open if you can reproduce the bug.
The replacement of the old mapper in tutorial step 3 has been done in bug-17800-Remove-VolumeMapper3D along with the general deletion.
The bug depends on bug-18373.
Did the crash turned up on the current master or on the bugbranch-17800 ?
The VolumeDataVtkMapper3D has the possibility to use Clipping Planes. This functionality in currently integrated into the GPUVolumeMapper3D by Jasmin.
Could not reproduce this bug on the current master. Everythings works fine.
Rendering component handover.
Rendering component handover.
Nico, could you export the scene with the tube renderings where the bug occured as STL-file and add it as attachment here?
We could reproduce this bug on Windows on the current master.
Rendering component handover.
Rendering component handover.
The steps using the QmitkSliceWidget should be redesigned pretty soon since we have plans to add more tutorial steps to the documentation.
I think we all agree that its not advantageous to show outdated/deprecated code in the tutorial. Thus, I set the importance to "medium".
The QmitkSliceWidget has been moved to QtWidgetsExt (which is not deprecated). There are no plans to remove the QmitkSliceWidget from MITK, so I will mark this bug as invalid.
Rendering component handover.
[3165e8]: Merge branch 'bug-16941-Reactivated-Viewport-Rendering-Test-For-Mac'
Merged commits:
2014-10-15 15:17:18 Sandy Engelhardt [9fb4a9]
reactivate rendering test
We would like to reactivate the test in order to check whether it works now regarding the latest changes.
Rendering component handover.