[Dcmlib] exExtractCSA

[Mathieu Malaterre]

Hi Christina ,

  As you may or may not know SIEMENS is not -AFAIK- publishing any
information on the encoding of there CSA header. So indeed the code
may not be as clean as we wanted in the first place. Anyway new devpt
is taking place in GDCM 2.x, we now have nicely encapsulated this
feature in classes:

http://gdcm.sourceforge.net/html/classgdcm_1_1CSAHeader.html
http://gdcm.sourceforge.net/html/classgdcm_1_1CSAElement.html

  I invite you to switch to GDCM 2.x :

http://gdcm.sourceforge.net/wiki/index.php/GDCM_Release_2.0

Thanks
-Mathieu

On Fri, Jul 18, 2008 at 9:37 AM, Christina Rossmanith
<ChrRossmanith at gmx.de> wrote:
> Hi,
>
> the gdcm example showing how to extract Siemens CSA data from DICOM files (exExtractCSA.cxx) writes the element data to a temporary file and reads this file subsequently. Why isn't the data processed in memory? I've modified the example a little to get the B_Value and the DiffusionGradientDirection for a large number of files. I think writing to and reading from disk slows down processing the files, doesn't it? Did the code just grow and it was nice to have the element data isolated on disk? And now it is up to the user to optimize the code  ;-)
>
> Christina Rossmanith
> --
> Christina Rossmanith
>
> GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
> http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196
> _______________________________________________
> Dcmlib mailing list
> Dcmlib at creatis.insa-lyon.fr
> http://www.creatis.insa-lyon.fr/mailman/listinfo/dcmlib
>



-- 
Mathieu