Problem with loading RTPLAN in Slicer version 4.13.0-2021-11-05 r30381

[shahrokh2]

Hello Dear Developers and Users As mentioned in Support of 3D Slicer Community, entitled Problem with SlicerRT in Slicer version 4.11.20210226 r29738 / 7a593c8 (Nov 7), I have problem to load RTPLAN only in Slicer.

Steps to reproduce

1- I load CT images (CT), structures (RTSRUCT) and dose (RTDOSE) exported from ISOgray® (a Treatment Planning System for external radiotherapy) completely and without any problems. 2- I can not load beams (RTPLAN) to Slicer. When doing it in DICOM module, I get this message in the window entitled DICOM loading”: Could not load: 4: RTPLAN: Beamsetup1CTDB as a RT. 3- Also, I ticked Advanced, in DICOM database and then click on Examine key. I get this message in the table of Warnings: Reference image in series does not contain geometry information. Please use caution… 4- Anonymized data that I have trouble loading (including as RTDOSE, RTSTRUCT, CT (74 images) and RTPLAN) can be downloaded via the link below: https://www.dropbox.com/sh/e1d0yc24ghptslk/AADZyW550Q6geYbDuRn3hAMna?dl=0

At this anonymized data, as mentioned above I can load RTDOSE, RTSTRUCT, CT and can not load RTPLAN.

I have exactly same problem with other versions of 3DSlicer except 4.10.2 r28257. In other words, I must mentioned that I can load CT images, RTPLAN, RTSTRUCT and RTDOSE completely and without any problems in Slicer version: 4.10.2 r28257.

Expected behavior

I want to work with new options added to SlicerRT module in last version of Slicer (version 4.13.0-2021-11-05 r30381 / f46c474) after loading data exported from our TPS (ISOgray).

Environment

OS: Ubuntu 18.04.4 LTS OS Type: 64-bit Processor: Intel® Core™ i7-9700K CPU @ 3.60GHz × 8 Graphics: GeForce RTX 2070 SUPER/PCIe/SSE2 Slicer: 4.13.0-2021-11-05 r30381 / f46c474 SlicerRT Installed from Extension Manager

Please guide me to sole it. Best regards. Shahrokh.

[MichaelColonel]

PR #202 should fix your problem.

[cpinter]

Since there was no confirmation whether or not the fix helped, we can assume it did. Thanks @MichaelColonel !