View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004475Slicer4Extension: VMTKpublic2017-11-18 17:502017-12-23 09:55
ReporterMuddyLancer Assigned Topieper  
PriorityurgentSeveritycrashReproducibilityalways
Status closedResolutionreopened 
Product VersionSlicer 4.6.2 
Target VersionFixed in Version 
Summary0004475: Slicer Segmentation Crashes with One Fiducial
Description

Hi all! I'm currently using VMTK in Slicer 4.6.2 to analyze confocal z-stacks. The Vessel Filtering works great. However, when I attempt to use the segmentation with one fiducial, the application freezes and then crashes. The program works flawlessly if I identify two fiducials. I tried following the tutorial online, but it is linked to a corrupted shockwave file.

Steps To Reproduce

Have tried installing and re-installing the software. Happens with multiple files. Tried installing on different computer with different OS (Windows 10 vs Windows 7) and crash still occurs.

TagsNo tags attached.

Activities

pinter

pinter

2017-11-20 09:44

developer   ~0015412

Hi! I see you're using 4.6.2. As it's more than a year old and a lot of things happened since then, please try your workflow with 4.8.0. If the problem is still present, and nobody claims this ticket (I'm not sure who's responsible for VMTK), please write on discourse.slicer.org
pieper

pieper

2017-11-20 10:22

administrator   ~0015413

Please re-open this if you confirm after following Csaba advice.
MuddyLancer

MuddyLancer

2017-11-22 13:30

reporter   ~0015436

Thank you for your rapid responses! I downloaded Slicer 4.8.0 (Win 64-bit) and tried my workflow again. This time, the software doesn't crash; however, if I only place one fiducial and don't specify a stopper, it doesn't return any segmentation. If I place two fiducials, then the marching algorithm attempts to connect the two fiducials and halts once it does. From previous published papers, it appears that the algorithm can explore all interconnected vessels before stopping; my segmentation is clearly not doing this.

pieper

pieper

2017-11-24 12:10

administrator   ~0015443

Hmm, I'm not sure if the behavior changed in VMTK and we don't have anyone actively supporting this right now. Did you check the resources at VMTK.org? Typically if features aren't exposed (or working) in the interface we suggest people try using VMTK tools directly.
pieper

pieper

2017-12-23 09:55

administrator   ~0015466

Not clear that anything needs to be changed. Let us know if there's a specific bug.

Issue History

Date Modified Username Field Change
2017-11-18 17:50 MuddyLancer New Issue
2017-11-18 17:50 MuddyLancer Status new => assigned
2017-11-18 17:50 MuddyLancer Assigned To => pinter
2017-11-18 19:57 pinter Assigned To pinter =>
2017-11-18 19:57 pinter Category Core: Segmentation => Extension: VMTK
2017-11-20 09:44 pinter Note Added: 0015412
2017-11-20 10:22 pieper Assigned To => pieper
2017-11-20 10:22 pieper Status assigned => closed
2017-11-20 10:22 pieper Resolution open => no change required
2017-11-20 10:22 pieper Note Added: 0015413
2017-11-22 13:30 MuddyLancer Status closed => feedback
2017-11-22 13:30 MuddyLancer Resolution no change required => reopened
2017-11-22 13:30 MuddyLancer Note Added: 0015436
2017-11-24 12:10 pieper Note Added: 0015443
2017-12-23 09:55 pieper Status feedback => closed
2017-12-23 09:55 pieper Note Added: 0015466