Prior to v0.8.4, the parser would stop at the PixelData tag and return "success" regardless of what followed. For v0.8.4 and later, the parser skips to the end of the PixelData element and returns "fail" if there is a premature end-of-file or if there is garbage after the PixelData element.
The latter is preferable, but it changes the behavior of some of the tools in an undesirable way.
The vtkDICOMDirectory algorithm skips files with incomplete PixelData (due to the error condition), whereas it used to accept such files before. The dicomfind, dicomtocsv, dicompull, etc. tools used to accept files with incomplete PixelData, but now they ignore such files.
Files with incomplete PixelData are common enough that:
we want to be able to indicate this condition
we want to be able to read and use whatever portion of the data is present
Prior to v0.8.4, the parser would stop at the PixelData tag and return "success" regardless of what followed. For v0.8.4 and later, the parser skips to the end of the PixelData element and returns "fail" if there is a premature end-of-file or if there is garbage after the PixelData element.
The latter is preferable, but it changes the behavior of some of the tools in an undesirable way.
The vtkDICOMDirectory algorithm skips files with incomplete PixelData (due to the error condition), whereas it used to accept such files before. The dicomfind, dicomtocsv, dicompull, etc. tools used to accept files with incomplete PixelData, but now they ignore such files.
Files with incomplete PixelData are common enough that: