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?<br>
<br>Thanks,<br>Ashish<br><br><div class="gmail_quote">On Fri, Feb 19, 2010 at 1:36 PM, Scott Johnson <span dir="ltr"><<a href="mailto:Scott.Johnson@neuwave.com">Scott.Johnson@neuwave.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Hello Ashish,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">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.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">You might also look at Derivation Description (0008,2111)
section C.7.6.1.1.3. But that attribute is type 3 (optional).</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Good luck.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> --
Scott</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;">
<a href="mailto:vtkusers-bounces@vtk.org" target="_blank">vtkusers-bounces@vtk.org</a> [mailto:<a href="mailto:vtkusers-bounces@vtk.org" target="_blank">vtkusers-bounces@vtk.org</a>] <b>On Behalf Of </b>Ashish
Singh<br>
<b>Sent:</b> Friday, February 19, 2010 10:31 AM<br>
<b>To:</b> <a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a>; <a href="mailto:gdcm-developers@lists.sourceforge.net" target="_blank">gdcm-developers@lists.sourceforge.net</a><br>
<b>Subject:</b> [vtkusers] distinguish between real CT scans(beam ON) and
non-realCT scans(beam OFF)</span></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hi,<br>
<br>
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?<br>
<br>
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.<br>
<br>
Thanks,<br>
Ashish</p>
</div></div></div>
</div>
</blockquote></div><br>