DICOM, Volumetric, 3 dimensional structured

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

DICOM, Volumetric, 3 dimensional structured

Richard Frank

The dicom image data (without much meta data) can be stored / read in .mha format using VTK MetaImageIO writer, if that helps you.
It's a block of bits, and reads fast.

I've written medical products that read DICOM files using DCMTK, which is like you say, a lot of work. (that's the polite version)

If you don't need to read them yourself, just read them with VolView and save them out as .mha from within VolView.

HTH

Rick



>------------------------------
>
>Message: 2
>Date: Wed, 17 Jan 2018 12:24:03 -0700 (MST)
>From: Sneaky Polar Bear <[hidden email]>
>To: [hidden email]
>Subject: Re: [PCL-users] DICOM, Volumetric, 3 dimensional structured
> clouds
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>No, I can store segmented bits as point clouds or stl's.  This is purely for
>convenience at the moment, basically just everything about handling DICOM
>(loading, moving around, etc) is laborious.  So I was hoping to just convert
>DICOM to a more usable format right after receiving it.
>
>I am creating a point cloud by reading dicom layers directly into a point cloud.
>
>Prolly better to respond to the original post than continue this thread tho, to
>keep everything together.
>
>
>
>--
>Sent from: http://www.pcl-users.org/
>
>
>------------------------------
>
>Message: 3
>Date: Wed, 17 Jan 2018 12:49:38 -0700 (MST)
>From: Sneaky Polar Bear <[hidden email]>
>To: [hidden email]
>Subject: Re: [PCL-users] DICOM, Volumetric, 3 dimensional structured
> clouds
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>The reason for wanting to keep it structured is to facilitate highly efficient
>searching and processing.
>
>
>
>--
>Sent from: http://www.pcl-users.org/
>
>
>------------------------------
>
>Message: 4
>Date: Thu, 18 Jan 2018 06:57:28 -0700 (MST)
>From: JamesRayen <[hidden email]>
>To: [hidden email]
>Subject: [PCL-users] What's the meaning of depth_mask_ in
> octree_base.h?
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=us-ascii
>
>Hello,
>I'm reading the source code of octree in pcl, but I have some problem. I don't
>know how to understand the  procedure of building an octree, is there any thesis
>introducing the procedure of building an octree in pcl?And what's the purpose of
>using depth_mask_?
>
>
>
>--
>Sent from: http://www.pcl-users.org/
>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>[hidden email] / http://pointclouds.org
>http://pointclouds.org/mailman/listinfo/pcl-users
>
>
>------------------------------
>
>End of PCL-users Digest, Vol 89, Issue 25
>*****************************************
_______________________________________________
[hidden email] / http://pointclouds.org
http://pointclouds.org/mailman/listinfo/pcl-users