From: jpr <jpr>
Date: Wed, 15 Feb 2006 13:39:09 +0000 (+0000)
Subject: Replace image with more significant name
X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?p=gdcmData.git;a=commitdiff_plain;h=96e6b49071524c866e9e0f2db4a9b7aafddbdc46

Replace image with more significant name
---

diff --git a/MR_Philips_Intera_PrivateSequenceExplicitVR_in_SQ_2001_e05f_item_wrong_lgt_use_NOSHADOWSEQ.README.txt b/MR_Philips_Intera_PrivateSequenceExplicitVR_in_SQ_2001_e05f_item_wrong_lgt_use_NOSHADOWSEQ.README.txt
new file mode 100755
index 0000000..ffacfeb
--- /dev/null
+++ b/MR_Philips_Intera_PrivateSequenceExplicitVR_in_SQ_2001_e05f_item_wrong_lgt_use_NOSHADOWSEQ.README.txt
@@ -0,0 +1,14 @@
+As usual for ViewForum burnt CDROMs, the Endianness switches from Little Endian
+to Big Endian, and then back to Little Endian within an 'Explicit VR' 
+private DICOM Sequence (the length of which is *not* 0xffffffff).
+The heuristics to guess the endianness looking at the 'delimitors'
+(whether they start with 0xfffe or 0xfeff) works for a while, and then breaks.
+in SQ 2001|e05f, the first Item starter (at offset 0x1102) tells us 
+the endianess swaps to BigEndian (we find FFFE  E000) ;
+The entry of the first SQItem (2001|0010) is BigEndian, but its length (1600 on
+disk is LittleEndian)  
+It seems to be a serious bug !
+
+The only way to read the image is to ask the reader (if you can) to skip the
+'private sequences'.
+-> use gdcm::File::SetLoadMode( NO_SHADOWSEQ );
diff --git a/MR_Philips_Intera_PrivateSequenceExplicitVR_in_SQ_2001_e05f_item_wrong_lgt_use_NOSHADOWSEQ.dcm b/MR_Philips_Intera_PrivateSequenceExplicitVR_in_SQ_2001_e05f_item_wrong_lgt_use_NOSHADOWSEQ.dcm
new file mode 100755
index 0000000..ff75c5a
Binary files /dev/null and b/MR_Philips_Intera_PrivateSequenceExplicitVR_in_SQ_2001_e05f_item_wrong_lgt_use_NOSHADOWSEQ.dcm differ