<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:387845123;
mso-list-type:hybrid;
mso-list-template-ids:660904248 -1827489760 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Hi Ziv,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks for elaborating on this.
Yes it is a xa projection (axial slices from what I can see).<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I followed your (and Louis and
other) suggestion (added xa image reader objects) and have created a new igstk
app in visual studio 9.0 on the lines of needle-biopsy app, and is now able<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>to load the image file and
display in the 4 quadrants, only if they are loaded from a folder with .dcm
image series. Had to split the large DICOM file into its frames as .dcm into <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>a folder to do this. It was not
loading if I tried with one single large file. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I am by no means a expert on
igstk, and might me missing many things here. Anyway, the goal is to load large
xa modality files and perform segmentation based on our custom<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>algorithms which intend to use
ITK for this. Registration and visualization will follow. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>First question is will igstk
allow us to access full potential of ITK for segmentation, or we have to rely
on what igstk provides. Also in cases like the hack you mentioned, how do we<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Integrate ITK pipe into igstk if
we have to fall back on ITK to load/process large DICOM files through igstk.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Also along the roadmap is to be
able to grab the DICOM fluoro directly from the c-arm, and superimpose 3d data
over 2d-fluoro, question is will igstk support this kind of approach.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Again I’m not an expert on
igstk (I’m .net architect), so are we on right track?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>satish<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> Ziv Yaniv
[mailto:zivy@isis.georgetown.edu] <br>
<b>Sent:</b> Tuesday, January 04, 2011 5:11 PM<br>
<b>To:</b> igstk-users@public.kitware.com; Satish<br>
<b>Subject:</b> Re: [IGSTK-Users] Multiframe DICOM<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Satish,<br>
<br>
Multi-frame DICOM is a bit too generic. Are you talking about a set of slices
comprising a volume that are contained in a single file instead of multiple
single slice files? Perhaps these are the XA projection images which you were
previously asking about? <br>
<br>
Also, if the DICOM tag for modality is not CT the igstkCTImageReader will
refuse to read it. For example a set of axial slices from cone-beam CT that
have an XA modality tag, even though they are equivalent to a CT. This is
intentional. <br>
If we expect a CT we don't want to allow the user to load an MR without the
developer knowing about this.<br>
<br>
I suggest that you first try to read the data using an igstk reader. If non of
them work then try reading using an ITK reader. Once you establish which pixel
type and other parameters work within ITK you can implement an igstk reader
which will only accept that type. This ensures that you only read the expected
data type (important if you want preset window and level values to work as
expected, etc.).<br>
<br>
If we are still talking about the XA projection images, then the following
"hack" in ITK may work for you; load the image set as a single 3D
image.<br>
<br>
This may not work if the movie is too long as ITK tries to load the whole
thing. <br>
<br>
If it does work you need to BE CAREFUL with your usage of this
"volume". The ITK concept of an image associates a pixel spacing with
each dimension, thus your 3D volume will most likely have a pixel dimension of
1 in each direction. In the image, x-y, plane this is fine, but your
"z" plane will be time which should not be treated in the same way as
space "x-y".<br>
When/if you apply ITK filters to this type of data you will most likely need to
apply them in a "slice by slice" manner. <br>
<br>
<br>
hope this helps<br>
Ziv<br>
<br>
<br>
On 1/4/2011 11:21 AM, Satish wrote: <o:p></o:p></p>
<p class=MsoNormal>Hi all,<o:p></o:p></p>
<p class=MsoNormal>Is it possible to read a multi-frame DICOM file (approx
250MB) with the igstkCTImageReader ?<o:p></o:p></p>
<p class=MsoNormal>Or do we have to split it into multiple .dcm files and
read…if so how do we split?<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Regards<o:p></o:p></p>
<p class=MsoNormal><b>Satish Kumar B.G</b><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Technical Architect<o:p></o:p></p>
<p class=MsoNormal><b><i>COMPUSOL</i></b><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>Powered by <a
href="http://www.kitware.com">www.kitware.com</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Visit other Kitware open-source projects at <a
href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Follow this link to subscribe/unsubscribe:<o:p></o:p></pre><pre><a
href="http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users">http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users</a><o:p></o:p></pre>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre><pre>Ziv Yaniv, PhD., Research Assistant Professor<o:p></o:p></pre><pre>Imaging Science and Information Systems (ISIS) Center<o:p></o:p></pre><pre>Department of Radiology<o:p></o:p></pre><pre>Georgetown University Medical Center<o:p></o:p></pre><pre>2115 Wisconsin Avenue, Suite 603<o:p></o:p></pre><pre>Washington, DC, 20007,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Phone: +1-202-6877286<o:p></o:p></pre><pre>Fax: +1-202-784-3479<o:p></o:p></pre><pre>email: <a
href="mailto:zivy@isis.georgetown.edu">zivy@isis.georgetown.edu</a><o:p></o:p></pre><pre>web: <a
href="http://isiswiki.georgetown.edu/zivy/">http://isiswiki.georgetown.edu/zivy/</a><o:p></o:p></pre></div>
</body>
</html>