Difference between revisions of "2013 Summer Project Week Breakout Session:RT"
From NAMIC Wiki
Line 14: | Line 14: | ||
*** Suggested tasks according to loaded data, even set toolbar icons | *** Suggested tasks according to loaded data, even set toolbar icons | ||
** CLI improvements ([http://www.na-mic.org/Wiki/index.php/2013_Summer_Project_Week:CLI_Improvements project page]) | ** CLI improvements ([http://www.na-mic.org/Wiki/index.php/2013_Summer_Project_Week:CLI_Improvements project page]) | ||
+ | *** Support other module types: qMRMLNodeComboBox level, add to hierarchy when creating new node | ||
=== Handling deformable transforms === | === Handling deformable transforms === |
Revision as of 19:43, 20 June 2013
Home < 2013 Summer Project Week Breakout Session:RTBack to Summer project week Agenda
Agenda
Patient Hierarchy
- Briefly present already implemented features and internals (Csaba)
- Discuss integration into Slicer core
- Name of the module and the common classes (SubjectHierarchy?)
- Propose SubjectHierarchy name to Ron
- What and how to generalize from SlicerRT's Patient Hierarchy
- Explore other use cases for SubjectHierarchy (Reporting/SR, Longitudinal (such as Andrey's PET/CT))
- Make sure there are no conflicts with other hierarchies (Time, etc.)
- Minimize the duplication between DICOM DB tags and PatientHierarchy attributes
- Exceptions: Modality, ?
- Suggested tasks according to loaded data, even set toolbar icons
- CLI improvements (project page)
- Support other module types: qMRMLNodeComboBox level, add to hierarchy when creating new node
- Name of the module and the common classes (SubjectHierarchy?)
Handling deformable transforms
- Meeting minutes of the Monday meeting about this
- Create a roadmap so that work can start on this
- Dicom Spatial Registration Objects (SRO), Greg needs both rigid & deformable
New DICOM browser
- Plan for integrating it into CTK trunk, Screenshots
- Roadmap for accommodating those changes Slicer core