Difference between revisions of "2008 Engineering review at Utah:Summary"

From NAMIC Wiki
Jump to: navigation, search
Line 9: Line 9:
 
** '''Dicom to nrrd conversion''', in particular with DWI data with different coordinate systems, gradient direction schemes, variable b-values and more. Agreed to run a "hard test" by taking new Siemens mosaic-format, multiple b-value DICOM data (Core-3 UNC autism project) and testing the existing conversion tool.
 
** '''Dicom to nrrd conversion''', in particular with DWI data with different coordinate systems, gradient direction schemes, variable b-values and more. Agreed to run a "hard test" by taking new Siemens mosaic-format, multiple b-value DICOM data (Core-3 UNC autism project) and testing the existing conversion tool.
 
** '''Quality control / Validation:''' Discussion of need to QC the nrrd DTI data (conversion correct?, tensors in correct orientation?, outlier detection?, artifact detection?). Group defined a need to work on QC methodology for data quality checking, to be run within Slicer-3 but maybe also as a stand-alone command-line as part of the data conversion and correction pipelines.
 
** '''Quality control / Validation:''' Discussion of need to QC the nrrd DTI data (conversion correct?, tensors in correct orientation?, outlier detection?, artifact detection?). Group defined a need to work on QC methodology for data quality checking, to be run within Slicer-3 but maybe also as a stand-alone command-line as part of the data conversion and correction pipelines.
−
** '''Workflow:''' Concepts of a workflow environment was discussed, using the example of DTI preprocessing and population-based analysis of DTI data. Need for two concepts, one for ''chaining'' of NAMIC modules, and one for running such chains/pipelines in a batch mode. Discussion of Batchmake versus capabilities of Grid computing.  
+
** '''Workflow:''' Concepts of a workflow environment was discussed, using the example of DTI preprocessing and population-based analysis of DTI data. Need for two concepts, one for '''''chaining''''' of NAMIC modules, and one for running such chains/pipelines in a batch mode. Discussion of Batchmake versus capabilities of Grid computing.  
  
 
*Wednesday 26
 
*Wednesday 26

Revision as of 16:38, 28 March 2008

Home < 2008 Engineering review at Utah:Summary
  • Monday 24
  • Kick-off presentations and definition of open issues to be discussed. Main theme: a) Putting modules into workflow pipelines, running such pipelines on a large number of datasets using a batch processing and eventually grid capabilities. b) New methods from the Utah groups to be integrated into Slicer-3. Presentations by different groups on:
    • Slicer-3 architecture
    • Segmentation
    • DTI analysis
    • Shape analysis
  • Tuesday 25: Topics discussed in details:
    • Dicom to nrrd conversion, in particular with DWI data with different coordinate systems, gradient direction schemes, variable b-values and more. Agreed to run a "hard test" by taking new Siemens mosaic-format, multiple b-value DICOM data (Core-3 UNC autism project) and testing the existing conversion tool.
    • Quality control / Validation: Discussion of need to QC the nrrd DTI data (conversion correct?, tensors in correct orientation?, outlier detection?, artifact detection?). Group defined a need to work on QC methodology for data quality checking, to be run within Slicer-3 but maybe also as a stand-alone command-line as part of the data conversion and correction pipelines.
    • Workflow: Concepts of a workflow environment was discussed, using the example of DTI preprocessing and population-based analysis of DTI data. Need for two concepts, one for chaining of NAMIC modules, and one for running such chains/pipelines in a batch mode. Discussion of Batchmake versus capabilities of Grid computing.
  • back to agenda [1]
Retrieved from "https://www.na-mic.org/w/index.php?title=2008_Engineering_review_at_Utah:Summary&oldid=23406"