Meta Bug for segmentation of tubular structures
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | None | T2494 META: Create usable end-user application / demo (3M3) | ||
Restricted Maniphest Task | ||||
Resolved | None | T2710 Segmentation of tubular structures | ||
Restricted Maniphest Task | ||||
Restricted Maniphest Task | ||||
Resolved | None | T2913 Could not use the "Confirm segmentation" button in Vesseltree segmentation (3m3) | ||
Restricted Maniphest Task | ||||
Resolved | None | T2680 Segmentation of tubular structures documentation | ||
Restricted Maniphest Task | ||||
Restricted Maniphest Task | ||||
Restricted Maniphest Task | ||||
Restricted Maniphest Task | ||||
Resolved | None | T2917 Perspective-Button "Tubular Structures" | ||
Restricted Maniphest Task | ||||
Restricted Maniphest Task |
Event Timeline
[SVN revision 19606]
ADD (#2710): adding first files for 3M3 vessel segmentation view
AdaptiveRegionGrowingView has to be modified, currently it is only a copy of navibroncho-->vesselTreeSegmentationView.
Still missing:
- hierarchical oder of object in the datatree
- gui has no upper/lower threshold field
- ...
Multiple selection for VesselTrees about to be commited.
Need a place to build it into!
;)
[SVN revision 19648]
CHG (#2710): added a combobox for selection of structure type and two spin boxes for lower and upper threshold
[SVN revision 19725]
FIX (#2710): adaptiveRG works now in both directions (lower or upper threshold fixed)
Adaptive Region Growing should work now for both directions with volume rendering preview.
Boost sub view is still work in progress.
[SVN revision 19730]
ADD (#2710): Added manual correction cost image calculation filter and GUI
[SVN revision 19745]
FIX (#2710): Preliminary version for boosting only selected branches
ToDo:
- rename nodes according to selected organ type
- re-boosting buggy (endless loop)
-...
there is a bug in AdaptiveRegionGrowingView: If the image only gets loaded and not selected, the InputImage is not set. I will add a safety check if the member m_InputImageNode is NULL.
This should squash (solve) the bug but for convenience the variable m_InputImageNode should be set after an image was loaded.
[SVN revision 19750]
FIX (#2710): checking if member variable m_InputImageNode is not NULL to catch exception when the image was not selected in DataManager
ok, I have a small change that switches interaction of setting the one seedpoint from left mouse button + shift to only left mouse button. But since the statemachine.xml is in the core, I have to wait for a core modification flag.
->tomorrow...
[SVN revision 19758]
ADD (#2710): QmitkVesselTreeSegmentationCleanerView added and integrated into VesselTreeSegmentation bundle
Still missing for VesselTreeSegmentationCleaner:
- endless loop if trying to remove the root of the vesseltree
[SVN revision 19776]
ADD (#2710): added two filters for multiscalehessianbasedmeasureimagefilter. The filters in itk review directory contain bugs.
[SVN revision 19777]
CHG (#2710): able to use the option GetScalesOutput(), GetHessianOutput()
[SVN revision 19784]
CHG (#2710): one can insert some seed points for the manual segmentation; changes in ui
[SVN revision 19847]
ENH (#2710): The cost calculation is now done only on the volume of interest as defined by the user-set seed points
[SVN revision 19890]
FIX (#2710): changing to QToolBox with bold headlines. For this, the qgroupboxes of subviews had to be removed.
As Marco proposed, the bug is divided now into 4 further bugs one for each sub view.
If someone has open (buggy) issues please document them in T2850 if related to adaptive region growing (sub view)
#2789 if related to boost segmentation (sub view)
#2851 if related to crop vessels (sub view)
#2852 if related to manual segmentation (sub view)
Currently selecting one interactor button does not deselect the others. So pressing the adaptive region growing seed point button, switching to the manual segmentation and clicking the point placing button there results in changing the Adaptive RG Seed point on left click and placing additional manual segmentation pointson shift+LMB. This behaviour is not desirable in my opinion, comments?
(In reply to comment #33)
Yes and difficult to implement... suggestions?
Is it possible (and doable with a reasonable amount of work) to have the vesseltreesegmentationview manage all the active (and "relevant") interactors? The sub views having to call a "requestinteractor()" function or something similar?
not practible... but we could think of a mechanism that the main view sends a signal if a different widget was activated. Then the one view could toggle the button and deactivate the interactors.
[SVN revision 20003]
FIX (#2710): adding property "showVolume" to segmentation node to show volume
[SVN revision 20376]
FIX (#2710): adding try catch to prevent total crash of the app (hopefully...)
[SVN revision 20380]
ADD (#2710): Added view icon and a couple of itk::ExceptionObject catches
[SVN revision 20426]
ADD (#2710): reduced button icon size slightly to not exceed the inner button area
[SVN revision 20622]
CHG (#2710): Silenced more of the default command line output, flag ADVANCED_DEBUG_MESSAGES allows for more communication
[SVN revision 20623]
CHG (#2710): Silenced more of the default command line output, flag ADVANCED_DEBUG_MESSAGES allows for more communication