View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004693 | Slicer4 | Core: Segmentation | public | 2019-05-21 22:59 | 2019-05-21 23:15 |
Reporter | lassoan | Assigned To | lassoan | ||
Priority | normal | Severity | minor | Reproducibility | sometimes |
Status | assigned | Resolution | open | ||
Product Version | Slicer 4.11.0 | ||||
Target Version | Slicer 4.11.0 | Fixed in Version | |||
Summary | 0004693: Segmentation closed surface representation sometimes rendered incorrectly in slice views | ||||
Description | Display of some complex segmentations in slice views are not correct if "Closed surface" representation is chosen to be displayed in slice views. It is only a display issue and does not affect the segmentation or segment statistics. Workaround until the display issue is fixed:
| ||||
Tags | No tags attached. | ||||
The current method of creating closed polygons by cutting closed surfaces only works for simple cases (e.g., not too many line segments, polygons not containing each other). vtkContourTriangulator implements a more sophisticated method (although significantly slower than the current, fragile implementation). It seem to provide reasonable output for reasonable input. There are still issues in case of extreme cases, such as cutting a surface generated by thresholding. Unfortunately, sometimes the filter hangs indefinitely in If the hang is fixed then then we can switch to the vtkContourTriangulator filter by merging this branch: https://github.com/lassoan/Slicer/tree/segmentation-closed-surface-in-slice-view |
|