Difference between revisions of "2016 Winter Project Week/Projects/Workflows"

From NAMIC Wiki
Jump to: navigation, search
 
(2 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
==Key Investigators==
 
==Key Investigators==
 
* Raúl San José
 
* Raúl San José
−
* Jorge Onieva  
+
* Jorge Onieva
 +
* Hans Meine (interested observer)
  
 
==Project Description==
 
==Project Description==
 
{| class="wikitable"
 
{| class="wikitable"
 +
! style="text-align: left; width:27%" |  Objective
 +
! style="text-align: left; width:27%" |  Approach and Plan
 +
! style="text-align: left; width:27%" |  Progress and Next Steps
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
−
! style="text-align: left; width:27%" |       Objective
+
|
−
<!-- Add a bulleted list of key points -->
+
<!-- Objective bullet points -->
 
* Implement a reusable mechanism to work with workflows in Slicer that navigate between different modules
 
* Implement a reusable mechanism to work with workflows in Slicer that navigate between different modules
 
* Implement an easily extensible and customizable GUI  
 
* Implement an easily extensible and customizable GUI  
−
 
+
|
−
! style="text-align: left; width:27%" |       Approach, Plan
 
 
<!-- Add a bulleted list of key points -->
 
<!-- Add a bulleted list of key points -->
 
* Discuss what would be the best approach from a GUI point of view
 
* Discuss what would be the best approach from a GUI point of view
 
* Implement an abstract module class that other modules could instantiate to implement a custom workflow
 
* Implement an abstract module class that other modules could instantiate to implement a custom workflow
 
* Discuss what would be the best way of persisting the state of the workflow (see [[2016_Winter_Project_Week/Projects/Data_Persisting|Data Persisting]] project)
 
* Discuss what would be the best way of persisting the state of the workflow (see [[2016_Winter_Project_Week/Projects/Data_Persisting|Data Persisting]] project)
−
 
+
|
−
! style="text-align: left; width:27%" |     Progress
 
 
<!-- Fill this out at the end of Project Week; describe what you did this week and what you plan to do next -->
 
<!-- Fill this out at the end of Project Week; describe what you did this week and what you plan to do next -->
−
*
+
*Slicelets and total customization of the Slicer UI seem to be a good approach to implement workflows (from a GUI point of view). It looks too hard to generalize a GUI for every workflow ("CLI style")
 +
* One of the best options for Python modules seems to be extending the ScriptedLoadableModule classes, adding input/output parameters and a "run" method, following a similar architecture than CLIs
  
 
|}
 
|}

Latest revision as of 14:57, 8 January 2016

Home < 2016 Winter Project Week < Projects < Workflows

Key Investigators

  • Raúl San José
  • Jorge Onieva
  • Hans Meine (interested observer)

Project Description

Objective Approach and Plan Progress and Next Steps
  • Implement a reusable mechanism to work with workflows in Slicer that navigate between different modules
  • Implement an easily extensible and customizable GUI
  • Discuss what would be the best approach from a GUI point of view
  • Implement an abstract module class that other modules could instantiate to implement a custom workflow
  • Discuss what would be the best way of persisting the state of the workflow (see Data Persisting project)
  • Slicelets and total customization of the Slicer UI seem to be a good approach to implement workflows (from a GUI point of view). It looks too hard to generalize a GUI for every workflow ("CLI style")
  • One of the best options for Python modules seems to be extending the ScriptedLoadableModule classes, adding input/output parameters and a "run" method, following a similar architecture than CLIs

Background and References

This project can be closely coupled with Data Persisting project

Retrieved from "https://www.na-mic.org/w/index.php?title=2016_Winter_Project_Week/Projects/Workflows&oldid=92020"