[vtkusers] distinguish between real CT scans(beam ON) and non-realCT scans(beam OFF)

[Ashish Singh]

Thanks Scott, I checked the section you mentioned in dicom standard. Yes, I
can always check for these strings in the dicom tags, but what if these tags
have incorrect information due to maybe machine or human error (I don't know
if a tech. can add or modify these.) . How do we go about it in that case?
Is there another check that we can do?

Thanks,
Ashish

On Fri, Feb 19, 2010 at 1:36 PM, Scott Johnson <Scott.Johnson at neuwave.com>wrote:

>  Hello Ashish,
>
>
>
> You’re looking at the right attribute.  If Image Type (0008,0008) contains
> DERIVED is has been computed from one or more other images.  Look in Part 3
> section C.7.6.1.1.2.  The attribute will probably also contain SECONDARY,
> but I can’t guarantee that.
>
>
>
> You might also look at Derivation Description (0008,2111) section
> C.7.6.1.1.3.  But that attribute is type 3 (optional).
>
>
>
> Good luck.
>
>
>
>                                 -- Scott
>
>
>
> *From:* vtkusers-bounces at vtk.org [mailto:vtkusers-bounces at vtk.org] *On
> Behalf Of *Ashish Singh
> *Sent:* Friday, February 19, 2010 10:31 AM
> *To:* vtkusers at vtk.org; gdcm-developers at lists.sourceforge.net
> *Subject:* [vtkusers] distinguish between real CT scans(beam ON) and
> non-realCT scans(beam OFF)
>
>
>
> Hi,
>
> I am trying to recursively read all dicom images from a CT study with
> several series. How do I figure out which images are real/primary
> scans(where the x-ray beam was ON) and which ones are not( such as recons,
> etc.)? I have been looking at the Image Type Tag(0008,0008) and series
> description tag (0008,103E), but is there a more systematic and foolproof
> way of figuring this out?
>
> This may not exactly be a VTK/GDCM question, but since there are many dicom
> experts in the community, if anyone can guide me, I would really appreciate
> it.
>
> Thanks,
> Ashish
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20100223/17db8312/attachment.htm>