Segmentation not displayed in Weasis v4.6.0

103 views
Skip to first unread message

Stefania Paperini

unread,
Apr 30, 2025, 9:39:52 AMApr 30
to dcm4che
Hi!

I have a couple of problems with the display of the segmentation object (Segmentation Storage (1.2.840.10008.5.1.4.1.1.66.4) in Weasis.

The first problem is about updating from v4.5.1 to v4.6.0: in v4.6.0 the Segmentation example that you can lunch from the web page: https://weasis.org/en/tutorials/dicom-segmentation/ doesn't work anymore (at least for me).
Also the segmentation object that I created and that I could display together with the corresponding ultrasound volume cannot be displayed anymore. 
In this case, that worked fine with v4.5.1, each frame of my ultrasound volume was saved in different Dicom files and I referenced the SOP instances in the tag:  (0008, 1155) (Referenced SOP Instance UID) in the "Per Frame Functional Group Sequence" (5200, 9230) of the Segmentation object.

The second problem is that if I save the ultrasound volume as Enhanced Ultrasound Volume, in only one multiframe Dicom file, the Segmentation object cannot be displayed, not even with Weasis v.4.5.1.
In this case I have only one volume file to reference and I try to put the tag:  (0008, 1155)  both in the "Per Frame Functional Group Sequence" (5200, 9230) (here having the same "Referenced SOP Instance UID" value for each frame) and in the Shared Functional Groups Sequence (5200, 9229) (so only one value for the "Referenced SOP Instance UID") but without any luck.

Can you suggest a way to display the Segmentation object as overlay of a multiframe volume in Weasis? 

Thank you a lot!

All the best,

Stefania




Nicolas Roduit

unread,
May 5, 2025, 2:20:18 AMMay 5
to dcm4che
Thank you for reporting these issues.
In version 4.6.0, files containing more than 400 segmentation frames have been deactivated due to performance concerns (with some cases it freezes the application). This is a temporary measure while we work on resolving display issues related to segmentation objects. As a result, some files may not be displayed as expected.
For the second issue, could you provide a sample and open an issue.

Stefania Paperini

unread,
May 7, 2025, 8:19:06 AMMay 7
to dcm...@googlegroups.com
Hi Nicolas,
thank you for your answer. I created the issue in github: Segmentation object not correctly displayed with Enhanced US Volume #666 
In github there was not the possibility to add the dicom files, so I will attach them here.
I checked them for conformity with the dciodvfy.exe tool of David Clunie. If I need to make some adjustments in order to display the segmentation in Weasis, just let me know.
I will also attach the log files, in case they help.

Thank you for investigating the problem!

 Stefania


--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dcm4che/881d3974-25bb-4b46-9a4a-a8a3cf847ab0n%40googlegroups.com.
boot.log
default.log

Nicolas Roduit

unread,
May 9, 2025, 4:27:10 AMMay 9
to dcm4che
See my response at #666

Stefania Paperini

unread,
May 21, 2025, 11:27:47 AMMay 21
to dcm...@googlegroups.com
Hi Nicolas,

Thanks a lot!
I opened an additional issue (https://github.com/nroduit/Weasis/issues/673) that could be also related to #667 (not sure about the correlation, though). I attach the input Dicom files here.
All the best,

Stefania



Reply all
Reply to author
Forward
0 new messages