Errors reading Dicom files from CIRRUS HD-OCT

Support
,
1

Operating system: Windows 10
Slicer version:4.8.1
Expected behavior:loading Dicom files from CIRRUS HD-OCT
Actual behavior: errors in loading process.

2

https://www.slicer.org/wiki/Documentation/Nightly/FAQ/DICOM

3

Hi,

I’ve patched my DICOM folder with the DICOM patcher and there are some issues in the proces:

DICOM patching started…

Examining .\ZDBDIR2.ibk…

Not DICOM file. Skipped.

Examining .\ZDBDIR2.ib…

Not DICOM file. Skipped.

Examining .\Export2.xml…

Not DICOM file. Skipped.

Examining .\Data64To32Convertor.cmd…

Not DICOM file. Skipped.

Examining DataFiles\E773\5MT7JPM9KQ72AUMGN5LV92BV9NL92IDFS27IOLS4X2ZU.EX.DCM…

Patching…

Writing DICOM…

Unexpected error: Invalid tag (0018, 0088): invalid literal for float(): 0.04724409

Any suggestion?

4

Maybe there are space characters before or after the number. That would violate the DICOM standard.

5

Hi,
BTW, leading or trailing space characters for VR DS don’t violate DICOM standard, it is DICOM standard. And DS is VR of 0018,0088.

http://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_6.2.html
Table 6.2-1. DICOM Value Representations

1 Like
6

Yes, you are right, leading and trailing spaces are allowed. Can you check what exactly do you have in those fields? Probably there are some other non-printing characters that violate the standard - newline, 0x00, …?

It is somewhat odd that these field is found in an OCT image, as this field is only referenced in MR IODs. I also had a look at a couple of DICOM conformance statements of CIRRUS HD OCTs and this field was not listed. Have you added this field manually or modified (anonymized, converted, etc.) these files in any way?

8

@Ekisolid We would either need a dump of all fields (you can use dcmdump command-line tool or “Metadata” feature of Slicer’s DICOM browser) or a sample data set for further investigation.

1 Like