Difference between revisions of "2014 Summer Project Week:Subject hierarchy integration"
From NAMIC Wiki
(Page created) |
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/") |
||
| (7 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<gallery> | <gallery> | ||
| − | Image:PW-SLC2014.png|[[ | + | Image:PW-SLC2014.png|[[2014_Summer_Project_Week|Projects List]] |
| + | Image:SlicerRT_0.13_SubjectHierarchy_ProstateEclipseLoaded.png|Module UI | ||
</gallery> | </gallery> | ||
==Key Investigators== | ==Key Investigators== | ||
| + | * Csaba Pinter, Queen's | ||
| + | * Jean-Christophe Fillion-Robin, Kitware | ||
| + | * Steve Pieper, Isomics | ||
| + | * Andras Lasso, Queen's | ||
==Project Description== | ==Project Description== | ||
| − | + | The new Subject hierarchy module and mechanism has been integrated into Slicer core recently, but has some issues and requests that need to be fixed.<br><br> | |
| + | Resources:<br> | ||
| + | *[https://www.slicer.org/wiki/Documentation/Labs/SubjectHierarchy Labs wiki page] | ||
| + | *[http://screencast.com/t/7fZ0eybAl Introduction video] | ||
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
| − | * | + | * Finalize the Subject hierarchy module and mechanism, fix outstanding issues and bugs |
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * | + | * Collect feedback; Please come and find me (Csaba) if you have |
| + | ** used it and have any comments | ||
| + | ** a special data type which needs a role plugin to be implemented | ||
| + | ** a feature that would need to have a simplified workflow and can be supported by a function plugin | ||
| + | * Go through the non-trivial items on the list with the core group and make decisions | ||
| + | * Implement fixes and changes, do testing | ||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * Subject hierarchy plugins in python - discussion with Jc and Steve: use adaptor class and signals/slots or create a scripted wrapper class with setPythonSource |
| + | * Subject hierarchy UI bugs (collapse, disappear, reorder) - discussion with Julien and Jc: write unit test with simple tree view, populate and reproduce without the bulky subclassed widgets | ||
| + | * Use cases | ||
| + | ** Andriy | ||
| + | *** Seg.Obj support is added in Reporting | ||
| + | *** Reporting workflows to be supported | ||
| + | *** Add Longitudinal PET-CT SH support | ||
| + | ** Hans & crew (Dave, Jessica) | ||
| + | *** Huntington's QA procedure, needed plugins TBD | ||
| + | ** Sonia | ||
| + | *** Laurent: new node added automatically under selected SH node? | ||
| + | *** Plugins to add | ||
| + | **** SceneView - Load scene view | ||
| + | **** Segmentation - Go to Editor module for volumes | ||
</div> | </div> | ||
</div> | </div> | ||
Latest revision as of 17:39, 10 July 2017
Home < 2014 Summer Project Week:Subject hierarchy integration
Module UI
Key Investigators
- Csaba Pinter, Queen's
- Jean-Christophe Fillion-Robin, Kitware
- Steve Pieper, Isomics
- Andras Lasso, Queen's
Project Description
The new Subject hierarchy module and mechanism has been integrated into Slicer core recently, but has some issues and requests that need to be fixed.
Resources:
Objective
- Finalize the Subject hierarchy module and mechanism, fix outstanding issues and bugs
Approach, Plan
- Collect feedback; Please come and find me (Csaba) if you have
- used it and have any comments
- a special data type which needs a role plugin to be implemented
- a feature that would need to have a simplified workflow and can be supported by a function plugin
- Go through the non-trivial items on the list with the core group and make decisions
- Implement fixes and changes, do testing
Progress
- Subject hierarchy plugins in python - discussion with Jc and Steve: use adaptor class and signals/slots or create a scripted wrapper class with setPythonSource
- Subject hierarchy UI bugs (collapse, disappear, reorder) - discussion with Julien and Jc: write unit test with simple tree view, populate and reproduce without the bulky subclassed widgets
- Use cases
- Andriy
- Seg.Obj support is added in Reporting
- Reporting workflows to be supported
- Add Longitudinal PET-CT SH support
- Hans & crew (Dave, Jessica)
- Huntington's QA procedure, needed plugins TBD
- Sonia
- Laurent: new node added automatically under selected SH node?
- Plugins to add
- SceneView - Load scene view
- Segmentation - Go to Editor module for volumes
- Andriy
