#15341 closed defect (fixed)

SEG read from file invisible in slice view

Reported by: Elaine Meng Owned by: Zach Pearson
Priority: high Milestone:
Component: DICOM Version:
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

I tried two different situations:

(1) session newseg.cxs attached with 4-24533 data (same as linked to DICOM in VR tutorial) + hand-drawn Segmentations blob in middle sagittal plane, which is the plane shown when you start the tool. Saved as newseg.cxs. Close data, restore session, start Segmentations, you do see the blob in the sagittal slice view, but if you move the sagittal plane slider it goes away and is never shown again even when you return to the same original plane. Is shown in 3D view but not in slice view.

(2) I had also saved that same segmentation from Segmentations as dcm file newseg.dcm attached. If I open 4-24533 data and then open newseg.dcm and then start Segmentations, the seg model is indeed listed in the Segmentations tool dialog, and if I click it, it is (initially) shown in the sagittal slice view midplane, but as before, as soon as I move the plane I can't get it back even when I go back to that same plane. Also it is not shown at all in the 3D view even though the Model Panel and Volume Viewer both say it is shown, and Volume Viewer says it is shown as surface.

Tested in daily build 1.9.dev202405230137 (2024-05-23) because I can't even start Segmentations in the current 1.8 rc build, so I didn't bother trying the current daily build.

Attachments (2)

newseg.cxs (2.0 MB ) - added by Elaine Meng 17 months ago.
newseg.dcm (7.5 MB ) - added by Elaine Meng 17 months ago.

Change History (3)

by Elaine Meng, 17 months ago

Attachment: newseg.cxs added

by Elaine Meng, 17 months ago

Attachment: newseg.dcm added

comment:1 by Elaine Meng, 17 months ago

Resolution: fixed
Status: assignedclosed

I did not have this problem in the UCSF ChimeraX version: 1.8rc202405312319 (2024-05-31). I made sure to choose the segmentation in the Segmentations tool when doing this test, but don't know if was necessary.

Note: See TracTickets for help on using tickets.