Difference between revisions of "Projects:Iowa Longitudinal PETCT Analysis using 3DSlicer"
From NAMIC Wiki
| Line 10: | Line 10: | ||
==Slicer-related infrastructure discussion issues== | ==Slicer-related infrastructure discussion issues== | ||
| + | * should there be an infrastructure for extension/module-specific parameter settings, and an interface to keep them in Slicer settings file? Should these settings be accessibel from Slicer Settings dialog, or from a panel in the extension? | ||
| + | * It is important for reproducibility purposes to be able to keep track of the parameters and initialization (e.g., fuducials) used for certain processing operation. Should we consider how to do this on the Slicer infrastructure level, or resolve on a per-case basis? | ||
| + | * PET SUV CLI module improvements: output SUV volume, and use another module for statistics calculations? | ||
=References= | =References= | ||
Revision as of 21:43, 7 November 2012
Home < Projects:Iowa Longitudinal PETCT Analysis using 3DSlicerContents
Summary
Participants
Technical details
Use-case workflow
Items under development
- should there be an infrastructure for extension/module-specific parameter settings, and an interface to keep them in Slicer settings file? Should these settings be accessibel from Slicer Settings dialog, or from a panel in the extension?
- It is important for reproducibility purposes to be able to keep track of the parameters and initialization (e.g., fuducials) used for certain processing operation. Should we consider how to do this on the Slicer infrastructure level, or resolve on a per-case basis?
- PET SUV CLI module improvements: output SUV volume, and use another module for statistics calculations?
