View Issue Details

IDProjectCategoryView StatusLast Update
0001939Slicer4Module EMSegmentpublic2014-03-06 06:09
Reporterthomasjwhitford Assigned Topohl  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Product VersionSlicer 4.1.0 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0001939: EM segmenter fails to finish
Description

running Slicer 4.1 stable on win64 windows7, 16GB of memory
run em segment with atlas, brain segmentation task on the brain mri sample data
following error log:
TCLAuto: Minimum: 0.0
TCLAuto: Check for Class WM
TCLAuto: Atlas : atlas_whitematter(Aligned)
TCLAuto: Scans : MR-head_pos(Aligned)_N4corrected
TCLAuto: LogGauss : 1
TCLAuto: CutOffProb : 80 (Absolut) -- 95.20 % (Percent)
TCLAuto: MaxProbVal : 82
TCLAuto: Samples : 60566
TCLAuto: GreyExtrima: (14, 97)
TCLAuto: Mean : 4.409
TCLAuto: Covariance : 0.006

::::LOGMEAN Float:4.40915

EMSegmentPy 04/25/2012 15:56:11: Pre-processing completed successfully

onEntryInternal - entering input from 7. Specify Intensity Distributions
processingAfterOnEntry
goForward - posting ValidationTransition
attemptToGoToNextStep - Attempting to go to the next step
validateInternal - validating input from 7. Specify Intensity Distributions
goToNextStepAfterSuccessfulValidation - Calidation succeeded
goToNextStepAfterSuccessfulValidation - Posting TransitionToNextStep
performTransitionBetweenSteps - Performing transition between steps
onExitInternal - exiting 7. Specify Intensity Distributions
onEntryInternal - entering input from 8. Edit Node-based Parameters
processingAfterOnEntry
goForward - posting ValidationTransition
attemptToGoToNextStep - Attempting to go to the next step
validateInternal - validating input from 8. Edit Node-based Parameters
goToNextStepAfterSuccessfulValidation - Calidation succeeded
goToNextStepAfterSuccessfulValidation - Posting TransitionToNextStep
performTransitionBetweenSteps - Performing transition between steps
onExitInternal - exiting 8. Edit Node-based Parameters
onEntryInternal - entering input from 9. Define Miscellaneous Parameters
processingAfterOnEntry
goForward - posting ValidationTransition
Traceback (most recent call last):
File "C:\Slicer 4.1.0 32bit\Slicer 4.1.0\lib\Slicer-4.1\qt-loadable-modules\Python\EMSegmentWizard\EMSegmentDefineMiscParametersStep.py", line 153, in onEntry
self.loadFromMRML()
File "C:\Slicer 4.1.0 32bit\Slicer 4.1.0\lib\Slicer-4.1\qt-loadable-modules\Python\EMSegmentWizard\EMSegmentDefineMiscParametersStep.py", line 221, in loadFromMRML
if self.__roiWidget:
AttributeError: ctkWorkflowWidgetStep has no attribute named '_EMSegmentDefineMiscParametersStep__roiWidget'
attemptToGoToNextStep - Attempting to go to the next step
validateInternal - validating input from 9. Define Miscellaneous Parameters
goToNextStepAfterSuccessfulValidation - Calidation succeeded
goToNextStepAfterSuccessfulValidation - Posting TransitionToNextStep
performTransitionBetweenSteps - Performing transition between steps
onExitInternal - exiting 9. Define Miscellaneous Parameters
onEntryInternal - entering input from Segmentation finished
processingAfterOnEntry
goForward - posting ValidationTransition
attemptToGoToNextStep - Attempting to go to the next step
validateInternal - validating input from Segmentation finished
goToNextStepAfterSuccessfulValidation - Calidation succeeded
goToNextStepAfterSuccessfulValidation - Posting TransitionToNextStep
performTransitionBetweenSteps - Performing transition between steps
onExitInternal - exiting Segmentation finished
onEntryInternal - entering input from 10. Segment
processingAfterOnEntry
goToStepSucceeded
EMSEG: Copying data to algorithm class...atlas data...target data...Setting number of target images: 1
AddingTargetImage...
Spacing: 1 1 1
Origin: 0 0 0
Extent: 0 255 0 255 0 129
Spacing: 1 1 1
Origin: 0 0 0
Extent: 0 255 0 255 0 129
global data...tree data...

Warning: the segmentation ROI was bogus, setting ROI to entire image
Axis 0 - Image Min: 1 <= RoiMin(1) <= ROIMax(-1) <= Image Max:256
Axis 1 - Image Min: 1 <= RoiMin(1) <= ROIMax(-1) <= Image Max:256
Axis 2 - Image Min: 1 <= RoiMin(1) <= ROIMax(-1) <= Image Max:130
NOTE: The above warning about ROI should not lead to poor segmentation results; the entire image should be segmented. It only indicates an error if you intended to segment a subregion of the image.
Define Boundary as: 1, 256, 1, 256, 1, 130,

DONE
[Start] Segmentation algorithm...
Local Version
Reserve memory for InputVector...Done
Multi Threading is working (8 cpus)
Print intermediate result to NULL
Registration Interpolation Type: Linear
Start vtkImageEMLocalSegmenter::HierarchicalSegmentation
====================================== Segmenting Level 1 ==========================================
Registration Type: Disabled
GenerateBackgroundProbability: Off
Standard exception: bad allocation
Failed to allocate 170393600 bytes.
ERROR: In ............\EMSegment\vtkEMSegmentLogic.cxx, line 2162
vtkEMSegmentLogic (057AFB38): Exception thrown during segmentation: bad allocation

TagsNo tags attached.

Activities

pohl

pohl

2012-04-25 16:28

developer   ~0004078

you seem to run out of memory

GenerateBackgroundProbability: Off
Standard exception: bad allocation
Failed to allocate 170393600 bytes.
ERROR: In ............\EMSegment\vtkEMSegmentLogic.cxx, line 2162
vtkEMSegmentLogic (057AFB38): Exception thrown during segmentation: bad allocation

pohl

pohl

2012-05-07 13:29

developer   ~0004186

Thomas, are you running Slicer on a 32 bit Windows OS ? If so we do not support 32 bit versions anymore.

thomasjwhitford

thomasjwhitford

2012-05-07 16:06

reporter   ~0004190

Hi there, no I am running a 64-bin Windows operating system with 16GB of RAM and 3.3GHz processor speed...

But it seems to work in the nightly version of Slicer, so maybe it's already been fixed?

pohl

pohl

2012-05-07 16:26

developer   ~0004191

I have not fixed anything. Can you reproduce the error ?

thomasjwhitford

thomasjwhitford

2012-05-07 16:39

reporter   ~0004192

Hi there, it seems to be working fine now! Curious... maybe my computer was just having a bad day :-)

Thanks for your help!

pohl

pohl

2012-05-08 06:22

developer   ~0004195

bug is not reproducible

jcfr

jcfr

2012-07-27 15:40

administrator   ~0005366

Dear issue reporter,

Good news :) Slicer developers SOLVED the problem you reported - YOU now need to VERIFY and CLOSE this issue.

thomasjwhitford

thomasjwhitford

2012-07-29 17:56

reporter   ~0005439

Great, thanks!

Issue History

Date Modified Username Field Change
2012-04-24 22:03 thomasjwhitford New Issue
2012-04-24 22:03 thomasjwhitford Status new => assigned
2012-04-24 22:03 thomasjwhitford Assigned To => pohl
2012-04-25 16:28 pohl Note Added: 0004078
2012-05-07 13:29 pohl Note Added: 0004186
2012-05-07 13:29 pohl Status assigned => feedback
2012-05-07 16:06 thomasjwhitford Note Added: 0004190
2012-05-07 16:26 pohl Note Added: 0004191
2012-05-07 16:39 thomasjwhitford Note Added: 0004192
2012-05-08 06:22 pohl Note Added: 0004195
2012-05-08 06:22 pohl Status feedback => resolved
2012-05-08 06:22 pohl Resolution open => fixed
2012-05-08 15:13 jcfr Target Version => Slicer 4.x AHM Summer 2012
2012-07-27 15:40 jcfr Note Added: 0005366
2012-07-29 17:56 thomasjwhitford Note Added: 0005439
2012-07-29 17:56 thomasjwhitford Status resolved => closed
2014-03-06 06:09 jcfr Fixed in Version => Slicer 4.2.0