# Errors reading Dicom files from CIRRUS HD-OCT

**URL:** <https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890>\
**Category:** Support\
**Tags:** dicom, oct\
**Created:** [August 24, 2018, 6:26pm UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890 "2018-08-24T18:26:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ekisolid](https://avatars.discourse-cdn.com/v4/letter/e/58956e/32.png) [@Ekisolid](https://discourse.slicer.org/u/Ekisolid)\
**Post date:** [August 24, 2018, 6:26pm UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/1 "2018-08-24T18:26:59Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [August 24, 2018, 9:32pm UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/2 "2018-08-24T21:32:28Z")

</div>

[https://www.slicer.org/wiki/Documentation/Nightly/FAQ/DICOM](https://www.slicer.org/wiki/Documentation/Nightly/FAQ/DICOM)

---

<div class="post-metadata">

**Author:** ![Ekisolid](https://avatars.discourse-cdn.com/v4/letter/e/58956e/32.png) [@Ekisolid](https://discourse.slicer.org/u/Ekisolid)\
**Post date:** [August 27, 2018, 10:30am UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/3 "2018-08-27T10:30:17Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 27, 2018, 11:53am UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/4 "2018-08-27T11:53:03Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Mihail\_Isakov](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@Mihail\_Isakov](https://discourse.slicer.org/u/Mihail_Isakov)\
**Post date:** [August 28, 2018, 7:21am UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/5 "2018-08-28T07:21:15Z")

</div>

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](http://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_6.2.html)  
Table 6.2-1. DICOM Value Representations

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 28, 2018, 1:35pm UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/6 "2018-08-28T13:35:46Z")

</div>

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](http://dicomlookup.com/lookup.asp?sw=Tnumber&q=(0018,0088)). I also had a look at a couple of [DICOM conformance statements of CIRRUS HD OCTs](https://www.zeiss.com/meditec/int/products/conformance-interoperability/dicom-conformance.html?catalog=dicom-cirrus-hd-oct) and this field was not listed. Have you added this field manually or modified (anonymized, converted, etc.) these files in any way?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 28, 2018, 10:12pm UTC](https://discourse.slicer.org/t/errors-reading-dicom-files-from-cirrus-hd-oct/3890/8 "2018-08-28T22:12:50Z")

</div>

@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.