Difference between revisions of "2017 Winter Project Week/dcmqi"

Latest revision as of 15:58, 13 January 2017

Objective	Approach and Plan	Progress and Next Steps
Introduce dcmqi to the community improve documentation discuss next steps and specific open issues	Present, meet collaborators... discuss pros and cons of integration as an external project into Slicer, and agree on the plan discuss the process of integration of new segmentation contexts by the user passing DICOM instances to the converters support of units/quantities in Slicer (also see labs page)	Discussions with the groups interested in exploring the use of DICOM for quantitative imaging research Identified an alternative (improved, hopefully) approach for communicating measurements to the SR converter using CSV: CSV table for the measurement quantities + CSV or JSON for describing the column names Discussed harmonization of the existing Units support in Slicer, and support of quantities/units for scalar volumes (only, for now); agreed that for now it makes sense to communicate per-volume quantity/units as MRML node attributes

@@ Line 37: / Line 37: @@
 |
 <!-- Progress and Next steps bullet points (fill out at the end of project week -->
-*
+* Discussions with the groups interested in exploring the use of DICOM for quantitative imaging research
+* Identified an alternative (improved, hopefully) approach for communicating measurements to the SR converter using CSV: CSV table for the measurement quantities + CSV or JSON for describing the column names
+* Discussed harmonization of the existing Units support in Slicer, and support of quantities/units for scalar volumes (only, for now); agreed that for now it makes sense to communicate per-volume quantity/units as MRML node attributes
 |}
@@ Line 44: / Line 46: @@
 * dcmqi Slicer extension: https://www.slicer.org/wiki/Documentation/Nightly/Extensions/DCMQI
 * DICOM4QI at RSNA2016: https://fedorov.gitbooks.io/rsna2016-qirr-dicom4qi/content/
+* https://peerj.com/articles/2057/