Difference between revisions of "2016 Summer Project Week/DICOM Parametric Maps"

From NAMIC Wiki
Jump to: navigation, search
 
(6 intermediate revisions by 2 users not shown)
Line 28: Line 28:
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Progress</h3>
+
<h3>Progress and Next Steps</h3>
 
* There is already a first version of a code generator that creates code for DICOM modules, functional groups and partly IODs
 
* There is already a first version of a code generator that creates code for DICOM modules, functional groups and partly IODs
 +
* converter WIP in dcmqi: https://github.com/QIICR/dcmqi/issues/20
 
</div>
 
</div>
 
</div>
 
</div>
 +
<br style="clear:left;">
 +
 +
== References ==
 +
* RWVM sample dataset: [[File:QIN-HEADNECK-rwvm.dcm.zip]]
 +
* RWVM generation code: https://github.com/QIICR/Slicer-PETDICOMExtension/blob/master/SUVFactorCalculatorCLI/SUVFactorCalculator.cxx#L856-L965

Latest revision as of 19:12, 28 June 2016

Home < 2016 Summer Project Week < DICOM Parametric Maps

Key Investigators

  • Michael Onken
  • Jan Schlamelcher
  • Andrey Fedorov
  • Christian Herz

Project Description

This software project is part of the QIICR project.

Objective

  • Add API to DCMTK (library called dcmpmap) which allows easy creation and reading of DICOM Parametric Map objects
  • Parametric Map objects have been introduced in DICOM with Supplement 172 in 2014.
  • From the Supplement: DICOM Parametric Maps include quantitative derived images computed from acquired images, where each pixel value has a "meaning" in the real world, and the name "parametric" alludes to the meaning being the parameter of something, such as a pharmacokinetic model. In general, the term "parametric map" is loosely used to refer to any derived image whose pixel values have a quantitative meaning, as opposed to acquired images, whose pixel values may or may not have meaning
  • This week we will work to discuss and finalize the API of the the library and prepare it for checkin to DCMTK

Approach, Plan

  • Discuss existing API and refine it
  • Finalize it (documentation, cleanup) for checkin into DCMTK

Progress and Next Steps


References