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.

Sign up for GitHub

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

Jump to bottom

Split handling of standard conforming DICOM from non-standard DICOM #4496

Open

thewtex opened this issue Mar 7, 2024 · 0 comments

Labels

Member

thewtex commented Mar 7, 2024

As suggested by @pieper in #4134 (comment)

My general preference would be to have the core reader code only handle completely standard dicom so that it is readable and maintainable. Any special code to handle malformed or vendor specific data should be detected and handled in dedicated classes, ideally with diagnostic info available so users know they have odd data and can report the issues to whoever created it.

thewtex added the type:Design label

thewtex mentioned this issue

BUG: itkDCMTKFileReader Spacing Issue #4134

Merged

7 tasks

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