Difference between revisions of "2011 Summer Project Week Dicom2Nrrd"
| Line 17: | Line 17: | ||
<!-- What you plan to achieve during project week goes here --> | <!-- What you plan to achieve during project week goes here --> | ||
| − | + | Refactoring the DWI DicomToNrrdConverter using GDCM 2.x. Clean up current code and better documentation. By separating the big (and only) .cxx file into multiple small classes that handle one type of data each, the maintainability of the entire code will be greatly improved. And the program can easily be extended into new vendor's format and new data types (for example, time series). | |
</div> | </div> | ||
| Line 26: | Line 26: | ||
<!-- What specific things you will be doing during the week: writing code? trying code on specific datasets? talking with other attendees? All of the above? --> | <!-- What specific things you will be doing during the week: writing code? trying code on specific datasets? talking with other attendees? All of the above? --> | ||
| − | + | Separate code for supporting different DICOM format from various vendors into individual classes. As a project week activity, we will code up the base class and implementation for one vendor format. The interface visible to the users (the driver program) will be keep unchanged. | |
</div> | </div> | ||
Revision as of 18:54, 16 June 2011
Home < 2011 Summer Project Week Dicom2Nrrd- DicomToNrrdUIPanel.jpg
Dicom To NRRD Converter
Key Investigators
- GE Research: Xiaodong Tao
- UIowa: Mark Scully
Objective
Refactoring the DWI DicomToNrrdConverter using GDCM 2.x. Clean up current code and better documentation. By separating the big (and only) .cxx file into multiple small classes that handle one type of data each, the maintainability of the entire code will be greatly improved. And the program can easily be extended into new vendor's format and new data types (for example, time series).
Approach, Plan
Separate code for supporting different DICOM format from various vendors into individual classes. As a project week activity, we will code up the base class and implementation for one vendor format. The interface visible to the users (the driver program) will be keep unchanged.
Progress
References
Delivery Mechanism
This work will be delivered to the NAMIC Kit as a command line module.
