Skip to content
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

Dicom tag not recognized #327

Open
leochan2009 opened this issue Oct 18, 2017 · 8 comments
Open

Dicom tag not recognized #327

leochan2009 opened this issue Oct 18, 2017 · 8 comments
Assignees

Comments

@leochan2009
Copy link
Contributor

leochan2009 commented Oct 18, 2017

No description provided.

@leochan2009
Copy link
Contributor Author

leochan2009 commented Oct 18, 2017

screen shot 2017-10-18 at 11 57 01 am

@fedorov
Copy link
Member

fedorov commented Oct 18, 2017

@leochan2009 you should update Slicer. I don't know the root of this issue, but a related problem in Slicer DICOM module was fixed recently.

Related issues:

@leochan2009
Copy link
Contributor Author

@fedorov ,
thanks, Andriy, i will take a look.

@che85
Copy link
Member

che85 commented Jan 19, 2018

@fedorov I just checked that issue and noticed that one of the slices is corrupted:

image

dciodvfy output

(0x0051,0x100b) SH Acquisition Matrix Text  - Warning - Explicit value representation doesn't match data dictionary; Explicit <LO> Dictionary <SH>
Error - Seek failed - while reading unencapsulated Pixel Data
Error - Dicom dataset read failed
Warning - Unrecognized defined term <CCG_CSTemp> for value 1 of attribute <Coding Scheme Designator>
Error - Missing attribute Type 2C Conditional Element=<Laterality> Module=<GeneralSeries>
Warning - Unrecognized defined term <CCG_CSTemp> for value 1 of attribute <Coding Scheme Designator>
Error - Missing attribute Type 1C Conditional Element=<PixelData> Module=<ImagePixelMacro>
Warning - Unrecognized defined term <M> for value 3 of attribute <Image Type>
Warning - Unrecognized defined term <SAT1> for value 1 of attribute <Scan Options>
Warning - Attribute is not present in standard DICOM IOD - (0x0010,0x21c0) US Pregnancy Status 
Warning - Attribute is not present in standard DICOM IOD - (0x0032,0x1032) PN Requesting Physician 
Warning - Attribute is not present in standard DICOM IOD - (0x0032,0x1033) LO Requesting Service 
Warning - Attribute is not present in standard DICOM IOD - (0x0032,0x1060) LO Requested Procedure Description 
Warning - Attribute is not present in standard DICOM IOD - (0x0008,0x0100) SH Code Value 
Warning - Attribute is not present in standard DICOM IOD - (0x0008,0x0102) SH Coding Scheme Designator 
Warning - Attribute is not present in standard DICOM IOD - (0x0008,0x0104) LO Code Meaning 
Warning - Attribute is not present in standard DICOM IOD - (0x0032,0x1064) SQ Requested Procedure Code Sequence 
Warning - Dicom dataset contains attributes not present in standard DICOM IOD - this is a Standard Extended SOP Class

How should we handle such situations?

  def createLoadableFileListForSeries(self, series):
    seriesNumber = RegistrationResult.getSeriesNumberFromString(series)
    loadableList = []
    for dcm in self.getFileList(self.intraopDICOMDirectory):
      currentFile = os.path.join(self.intraopDICOMDirectory, dcm)
      # at the following line it crashes
      currentSeriesNumber = int(self.getDICOMValue(currentFile, DICOMTAGS.SERIES_NUMBER))
      if currentSeriesNumber and currentSeriesNumber == seriesNumber:
        loadableList.append(currentFile)
    return loadableList

@che85 che85 self-assigned this Jan 19, 2018
@fedorov
Copy link
Member

fedorov commented Jan 19, 2018

Error - Missing attribute Type 1C Conditional Element=<PixelData>

This seems to be a fatal situation, and the action is very straightforward - if the input series does not have PixelData, there is really nothing we can do with it.

@fedorov
Copy link
Member

fedorov commented Jan 19, 2018

The real question is how could this kind of data could be produced by the scanner if the standard acquisition protocol was followed. Something must be different about that case.

@che85
Copy link
Member

che85 commented Jan 19, 2018

It’s one corrupt file in case 592 intraop images. File names and extension also differs from the usual intraop protocol...

@fedorov
Copy link
Member

fedorov commented Jan 19, 2018

It must have a different Series/StudyInstanceUID from any other instances, right?

If that is the case, it means we also need to add another check to ignore any of the instances that have inconsistent StudyInstanceUID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants