-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
@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: |
@fedorov , |
@fedorov I just checked that issue and noticed that one of the slices is corrupted: dciodvfy output
How should we handle such situations?
|
This seems to be a fatal situation, and the action is very straightforward - if the input series does not have |
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. |
It’s one corrupt file in case 592 intraop images. File names and extension also differs from the usual intraop protocol... |
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. |
No description provided.
The text was updated successfully, but these errors were encountered: