Difference between revisions of "EngineeringRetreat2010/Isomics"
From NAMIC Wiki
(Created page with 'Isomics Overall Goals for namic years 7-10: * Support DBPs and collaborations * "Finish" slicer4 [http://www.slicer.org/slicerWiki/index.php/Documentation-3.6#Core Core] ** Fas…') |
|||
| Line 10: | Line 10: | ||
** Flexible data I/O and solid MRML representation | ** Flexible data I/O and solid MRML representation | ||
** Customized visualization and annotation for medical imaging | ** Customized visualization and annotation for medical imaging | ||
| + | *** longitudinal, cross-subject, multi-modal, interactive... | ||
| + | *** clean interfaces | ||
* Coding goals | * Coding goals | ||
** Move everything non-core to extensions | ** Move everything non-core to extensions | ||
| + | ** Everything script accessible for extension and debugging | ||
** Put much of the general purpose code in [http://commontk.org CTK] | ** Put much of the general purpose code in [http://commontk.org CTK] | ||
** Develop topic branches to fix toolkits rather than workarounds in slicer code | ** Develop topic branches to fix toolkits rather than workarounds in slicer code | ||
** Improve communication among distributed developer team (how?) | ** Improve communication among distributed developer team (how?) | ||
| + | |||
* Strong DICOM support | * Strong DICOM support | ||
Revision as of 12:45, 17 November 2010
Home < EngineeringRetreat2010 < IsomicsIsomics Overall Goals for namic years 7-10:
- Support DBPs and collaborations
- "Finish" slicer4 Core
- Fast, usable, base for extension development
- Easily extended (C++, Python, WebKit/JavaScript)
- Logical extension workflow interfaces
- Bundles of extensions to support topic areas
- Flexible data I/O and solid MRML representation
- Customized visualization and annotation for medical imaging
- longitudinal, cross-subject, multi-modal, interactive...
- clean interfaces
- Coding goals
- Move everything non-core to extensions
- Everything script accessible for extension and debugging
- Put much of the general purpose code in CTK
- Develop topic branches to fix toolkits rather than workarounds in slicer code
- Improve communication among distributed developer team (how?)
- Strong DICOM support
- dcmtk networking (track ITKv4)
- local storage that represents image acquisition (Not an abstract image type that throws away all the metadata - rather a rich representation that is perhaps only partly specified for non-dicom types.).
- ctkDICOM GUI
- DICOM RT I/O
