<div dir="ltr">Dear Mathieu,<br><br>Thank you for your mail.<br><br>As you suggested, I will send you the diff files of GDCM layer once I am done with that.<br><br>Thank you.<br><br>Warm Regards,<br>Subrahmanyam Gorthi.<br>
<br><br><br><div class="gmail_quote">On Tue, Sep 16, 2008 at 9:24 AM, Mathieu Malaterre <span dir="ltr"><<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.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;">
Subrahmanyam,<br>
<div class="Ih2E3d"><br>
On Mon, Sep 15, 2008 at 5:41 PM, Subrahmanyam Gorthi<br>
<<a href="mailto:subrahmanyam.gorthi@gmail.com">subrahmanyam.gorthi@gmail.com</a>> wrote:<br>
> Dear Mathieu,<br>
><br>
> I am very happy to inform that I am now able to export the segmentation<br>
> results to RTSTRUCT using ITK.<br>
<br>
</div>Kudos !<br>
<div><div></div><div class="Wj3C7c"><br>
> Thanks a lot for your valuable guidance on the pipeline, handling DICOM<br>
> sequences and converting 3-D mask to contour.<br>
><br>
> The inputs to the current Exporter are:<br>
><br>
> 1. A DICOM slice of the CT image:<br>
> For extracting patient related and other common information.<br>
><br>
> 2. 3-D Masks of the segmentation regions:<br>
> These are converted to contours using the<br>
> itkContourExtractor2DImageFilter & itkExtractImageFilter and is given as<br>
> input input to the RTSTRUCT writer.<br>
><br>
> 3. Few other parameters:<br>
> Parameters like names to be assigned to the ROIs, Number of ROIs to be<br>
> exported, type of contours etc...<br>
><br>
> The output of the Exporter: RTSTRUCT DICOM file.<br>
><br>
> I verified the results by viewing the output file in a DICOM dumper, and<br>
> also by superposing the RTSTRUCT contours over the DICOM CT image, using<br>
> some third party tools. The code seems to work fine :-)<br>
><br>
> Now RTSTRUCT Writer part is done. but RTSTRUCT Reader is yet to be written<br>
> :-(<br>
> Since the above application does not need RTSTRUCT Reader, I first started<br>
> with the RTSTRUCT Writer.<br>
> Still many modifications and cleanup are to be done for RTSTRUCT writer<br>
> itself for using it for other general applications.<br>
><br>
> My doubt is: for contributing this part to ITK (Insight Journal?), how<br>
> should I manage the modified/added files?<br>
><br>
> In my code, I added the following files to the ITK\Code\IO direcory:<br>
> 1. itkRTSTRUCTIO.h<br>
> 2. itkRTSTRUCTIO.cxx<br>
> 3. itkRTSTRUCTIOFactory.h<br>
> 4. itkRTSTRUCTIOFactory.cxx<br>
<br>
</div></div>This is exactly the minimum required.<br>
<div class="Ih2E3d"><br>
> I modified the following files in ITK\Utilities\gdcm\src directory by adding<br>
> few additional functions:<br>
> 1. gdcmFile.cxx<br>
> 2. gdcmFileHelper.h<br>
> 3. gdcmFileHelper.cxx<br>
<br>
</div>Those will be slightly more difficult to handle, since the IJ<br>
mechanism does not handle patch (AFAIK), but only external project to<br>
ITK. If you can send me the diff of those files, so that I can<br>
integrate them in ITK/gdcm before IJ submission. Therefore the day you<br>
do your IJ submission the API in gdcm will already be augmented with<br>
your patch.<br>
<div class="Ih2E3d"><br>
> There are two other files: mask2contour.cxx & Export2RTSTRUCT.cxx.<br>
<br>
</div>Great !<br>
<div class="Ih2E3d"><br>
> Can I simply put all the above files in a single folder and submit to the<br>
> Insight journal along with the paper?<br>
> (I still need to do significant cleanup and write the IJ-Paper :D)<br>
<br>
</div>If we except the gdcm patch, then everything else nicely fit in the process.<br>
<div class="Ih2E3d"><br>
> The DICOM files that I am using for testing are bit large (around 60 MB).<br>
> Is there any size limit for IJ submission?<br>
<br>
</div>Not that I know of. The only restriction is that you are responsible<br>
for anonymizing the RTSTRUCT object before submission.<br>
<div class="Ih2E3d"><br>
> Once again many thanks for your help.<br>
<br>
</div>np :)<br>
<br>
good luck,<br>
--<br>
<font color="#888888">Mathieu<br>
</font></blockquote></div><br></div>