Difference between revisions of "2011 Summer Project Week DICOM RT"
(One intermediate revision by the same user not shown) | |||
Line 4: | Line 4: | ||
</gallery> | </gallery> | ||
− | [[Image:sshot.png| | + | [[Image:sshot.png|300px|Synthetic noise]] |
Synthetic DICOM-RT sample data [http://forge.abcd.harvard.edu/gf/download/frsrelease/85/1865/random.zip] | Synthetic DICOM-RT sample data [http://forge.abcd.harvard.edu/gf/download/frsrelease/85/1865/random.zip] |
Latest revision as of 14:02, 24 June 2011
Home < 2011 Summer Project Week DICOM RTSynthetic DICOM-RT sample data [1]
Key Investigators
- MGH: Nadya Shusharina, Greg Sharp
- Kitware: Luis Ibanez
- Isomics: Steve Pieper
- Cosmo software: Drew Wassem
- A*STAR: Alexandre GOUAILLARD (in spirit)
Synthetic images, vector fields, RT structures and RT doses in Slicer and ITK
Figure out the best representation in ITK and Slicer4 for various RT and related datastructures.
Objective
We are designing synthetic DICOM-RT dataset which includes CT image, structure set and dose distribution. The following guidelines are used. We measured the noise power spectrum of a real CT image and constructed synthetic image with exactly the same spectrum. Then we included "skin" and one internal spherical structure. Synthetic contours were generated and recorded in labelmap format. Synthetic dose distribution was generated in mha format.
Approach, Plan
Currently synthetic DICOM-RT is loaded into Slicer 3.6.3 from file through Plastimatch extension DICOM/DICOM-RT Import. We plan to build Plastimatch command line module that will allow us to create synthetic image, structures and dose distribution interactively according to user's needs.
Progress
- Discussed the use of Slicer4 hierarchies to group structure sets
- Reviewed DICOM networking interface with respect to RT workflows
- Worked around resampling performance issues with itk vector images
References
Delivery Mechanism
This work will be delivered to the NAMIC Kit as a
- NITRIC distribution
- Slicer Module
- Built-in: perhaps RT support can become part of MRML
- Extension -- commandline: Maybe, if needed
- Extension -- loadable: yes, for a custom interface