[vtkusers] vtkDICOMDirectory and vtkDICOMReader issue with files in the stack.

[David Gobbi]

I'm not aware of any standard DICOM tags that identify locator images.
That's why I check the ImageOrientationPatient, and if it doesn't match the
rest of the series, I sort the image into a different stack. My co-worker
enhanced our dicom browser so that, when the user clicks on a series, a
thumbnail image is displayed for each stack so that the user can choose.

Choosing the stack with the largest number of images is reasonable.

 - David

On Fri, Jul 22, 2016 at 8:48 AM, zarko.milosevic <zarko at kg.ac.rs> wrote:

> Mostly i work with CT images and, in most cases, i had that situation where
> there is one locator image and because of that i had two stacks.
> In those circumstances i just load the stack with largest number of
> dedicated files.
> Is there some other, more elegant, solution to identify the purposes of
> stacks ? Via some DICOM tag for example.
>
> So for those cases i have some temporary solution.
>
> I have problem with some cases where loaded image have one slice and where
> series have one stack and no time slots.
>
> How should i identify those proposed situations ? To go throught files
> using
> fileindex array and compare if those values (ImageOrientationPatient,
> ImagePositionPatient vs. InstanceNumber) is changing in files?
>
> If so what would be solution ?
>
> Zarko
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20160722/5c846186/attachment.html>