Difference between revisions of "Documentation/Labs/Units"

From Slicer Wiki
Jump to: navigation, search
m (Text replacement - "https?:\/\/(?:www|wiki)\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) " to "https://www.slicer.org/wiki/$1 ")
 
(2 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
This page summarize the on-going work related to the integration of units into Slicer.
 
This page summarize the on-going work related to the integration of units into Slicer.
  
−
* Wiki page: http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Units
+
There are two developments:
 +
 
 +
1. Application-level definition of units for controlling issues like display and precision for the GUI widgets displaying the values, see wiki page: https://www.slicer.org/wiki/Documentation/Nightly/Developers/Units 2. Volume node level definition of the quantity and units associated with an image volume. Discussion of this development started in this PR thread: https://github.com/Slicer/Slicer/pull/592
  
 
= Work-in-progress topic =
 
= Work-in-progress topic =
 +
 +
The idea is to add code triples (CodeValue, CodingSchemeDesignator, CodeMeaning) to describe QuantityValue and MeasurementUnits attributes defined for each volume.
 +
 +
Codes for units can/should be taken from [http://unitsofmeasure.org/trac UCUM]. Codes for quantities can be reused from DICOM (to be populated).
 +
 +
To define abbreviations for units, UCUM CodeValue is sufficient in most cases. When the code value is not acceptable (i.e., for Hounsfeld units), a mapping to a suitable abbreviation should be established in Slicer.
 +
 +
Examples: https://github.com/Slicer/Slicer/pull/592#issuecomment-252913866 and also this one https://github.com/QIICR/dcmqi/blob/master/doc/pm-example.json#L9-L12 show how it can be using DICOM concepts.
  
 
== Features ==
 
== Features ==

Latest revision as of 13:19, 27 November 2019

Home < Documentation < Labs < Units

Overview

This page summarize the on-going work related to the integration of units into Slicer.

There are two developments:

1. Application-level definition of units for controlling issues like display and precision for the GUI widgets displaying the values, see wiki page: https://www.slicer.org/wiki/Documentation/Nightly/Developers/Units 2. Volume node level definition of the quantity and units associated with an image volume. Discussion of this development started in this PR thread: https://github.com/Slicer/Slicer/pull/592

Work-in-progress topic

The idea is to add code triples (CodeValue, CodingSchemeDesignator, CodeMeaning) to describe QuantityValue and MeasurementUnits attributes defined for each volume.

Codes for units can/should be taken from UCUM. Codes for quantities can be reused from DICOM (to be populated).

To define abbreviations for units, UCUM CodeValue is sufficient in most cases. When the code value is not acceptable (i.e., for Hounsfeld units), a mapping to a suitable abbreviation should be established in Slicer.

Examples: https://github.com/Slicer/Slicer/pull/592#issuecomment-252913866 and also this one https://github.com/QIICR/dcmqi/blob/master/doc/pm-example.json#L9-L12 show how it can be using DICOM concepts.

Features

History

Retrieved from "https://www.slicer.org/w/index.php?title=Documentation/Labs/Units&oldid=62620"