View Issue Details

IDProjectCategoryView StatusLast Update
0003298Slicer4Module N4ITKBiasFieldCorrectionpublic2018-05-30 00:41
ReportergaddeAssigned Tofedorov 
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product VersionSlicer 4.2.2-1 
Target VersionbacklogFixed in Version 
Summary0003298: N4ITKBiasFieldCorrection shrinkfactor default of 4 may not be appropriate in some cases
Description

I was asked by Andriy Fedorov to report this here. In the case where data with a small number of slices is passed to N4ITKBiasFieldCorrection, the default shrinkfactor of 4 causes the algorithm to converge nearly immediately with no change in the image (and a bias field of all ones). Reducing the shrinkfactor allows it to proceed as normal. It's not clear whether the calculated field is actually worth anything with a partial brain, but as suggested by Andriy, it may be worth a warning when the chosen shrinkfactor is too large for the image size. (It also might be nice to allow it to subsample differently for each dimension)

TagsNo tags attached.

Activities

lassoan

lassoan

2018-05-30 00:41

developer   ~0015811

Retarget stale issues to backlog.

Issue History

Date Modified Username Field Change
2013-08-15 10:53 gadde New Issue
2013-08-15 10:53 gadde Status new => assigned
2013-08-15 10:53 gadde Assigned To => fedorov
2013-08-15 11:02 jcfr Target Version => Slicer 4.4.0
2014-07-29 12:16 jcfr Target Version Slicer 4.4.0 =>
2017-06-15 01:56 lassoan Summary shrinkfactor default of 4 may not be appropriate in some cases => N4ITKBiasFieldCorrection shrinkfactor default of 4 may not be appropriate in some cases
2018-05-30 00:41 lassoan Target Version => backlog
2018-05-30 00:41 lassoan Note Added: 0015811