View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000116 | Slicer3 | EMSegmenter | public | 2007-11-15 14:21 | 2007-11-20 06:44 |
Reporter | davisb | Assigned To | davisb | ||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0000116: When normalization is turned on, after segmentation, normalized and input images are confused | ||||
Description | As part of the EMSegmenter process, the input images can be intensity normalized. These new, normalized images are added to the MRML scene. Their names are the same as the input image names, causing confusion in the GUI interfaces and possibly also confusing the inputs that go into the segmentation algorithm. Needs further study... | ||||
Tags | No tags attached. | ||||
It appears that there is a problem with cloning the target node. This may be due to changes of Copy to CopyWithScene? Need to investigate further. Need to debug vtkEMSegmentMRMLManager::CloneTargetVolume. |
|
The confusion was due to a gui bug that displayed both the input images and the normalized input images in the target image dialog. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2007-11-15 14:21 | davisb | New Issue | |
2007-11-15 14:21 | davisb | Status | new => assigned |
2007-11-15 14:21 | davisb | Assigned To | => davisb |
2007-11-15 17:09 | davisb | Note Added: 0000140 | |
2007-11-20 06:44 | davisb | Status | assigned => closed |
2007-11-20 06:44 | davisb | Note Added: 0000146 | |
2007-11-20 06:44 | davisb | Resolution | open => fixed |