-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Element (0029,0010) "Item length exceeds the bytes remaining in file" #223
Comments
Update: |
Thanks for the report. There's nothing special about "(0029,0010) LO [SIEMENS CSA HEADER]", it just starts an important Siemens private group in the file. The part of the error that worries me is "in Sequence (0000,0000)", since no valid tag ever has the value (0000,0000). Can you do a gdcmdump of the original file and send me the dump? I want to see where the group length elements and sequence elements are. Also, of course, be sure to XX out any sensitive information in the dump. |
Thanks for the feedback! |
I found the problem in vtkDICOMParser.cxx and pushed a commit that should fix it (6a81888). Please try updating from the master branch and let me know if it works for you. There was a bug with parsing files with an explicit VR transfer syntax that contained a sequence of defined length that had VR=UN. Here, the difficulty was the "ApplicationHeaderSequence". The bug caused an error to be thrown at the first element of the sequence, not because there was anything wrong with that element, but only because it was the first element in a sequence that was incorrectly parsed.
I'm re-attaching the DICOM file after XX-ing a few attributes and zeroing the image: INST1.zip |
Dear David, |
I wrote some code using VTK-Dicom to read CT scan data. I actually have two sources: one from a GE scanner and one from a Siemens scanner.
The GE data is read just fine.
When I use the same code to read the data from the Siemens scanner, I get the following errors below.
gdcmdump reads the file in question without errors and the problem seems to be related to the element labelled "(0029,0010) LO [SIEMENS CSA HEADER]".
Is there a known problem with this field? If so, is there any recommended workaround to read such data?
Thanks!
PS: I built the most recent commit b69e7ac of vtk-dicom
The text was updated successfully, but these errors were encountered: