Corrupted instance drop
Identify and discard unreadable or corrupted instances from a study.
Problem
You’re loading a folder of DICOM files, and some are corrupted: truncated files, zero-byte placeholders, non-DICOM text files accidentally mixed in, or files with bad DICOM headers. You don’t want the entire load to fail because of one bad file. The app should skip corrupted files, load everything valid, and report which files were skipped.
Steps
Partial Failure
-
Open a mixed set of files (⌘O), e.g.
test.dcm(valid) +corrupted.dcm(bad header). -
The valid file loads successfully. The metadata sidebar is visible, the Files tree shows only the valid study, and a notice names
corrupted.dcmas skipped.
Complete Failure (All Files Corrupted)
-
Open only corrupted files. E.g.
corrupted.dcmalone. -
The metadata sidebar does not appear. An error message is displayed: “Load failed” / “Invalid DICOM file, expected header is missing”.
Skip Non-DICOM Files
-
Load valid DICOMs + non-DICOM files. E.g.
test.dcm,sr-test.dcm, andnotes.txt(plain text) orempty.dcm(zero bytes). -
Both valid files load. The Files tree shows two study headers. A notice reports that the invalid files could not be read and were skipped, and names each one.
Result
On a mixed load, valid files open and corrupted or non-DICOM files are skipped, so the study tree shows only good entries; if everything is corrupt you get a “Load failed” message. Each skipped file (zero-byte, non-DICOM, or bad header) is named in the notice.