Difference between revisions of "2016 Winter Project Week/Projects/CLIModules Backgrounding in MeVisLab"

From NAMIC Wiki
Jump to: navigation, search
Line 11: Line 11:
 
==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
+
|
 +
<!-- Objective bullet points -->
 
* Make it possible to run CLI modules asynchronously in MeVisLab, i.e. without freezing the UI during (potentially long) runtime
 
* Make it possible to run CLI modules asynchronously in MeVisLab, i.e. without freezing the UI during (potentially long) runtime
 
* Possibly enable progress reporting (as in CTK/Slicer) for CLIs that support this
 
* Possibly enable progress reporting (as in CTK/Slicer) for CLIs that support this
! style="text-align: left; width:27%" |       Approach, Plan
+
|
 
* Start CLIs in the background (already refactored to this avail)
 
* Start CLIs in the background (already refactored to this avail)
 
* Add status fields, modeled after typical background task modules
 
* Add status fields, modeled after typical background task modules
 
* Parse output every xx milliseconds
 
* Parse output every xx milliseconds
 
* Try to immediately detect finished process
 
* Try to immediately detect finished process
! style="text-align: left; width:27%" |     Progress
+
|
 
*
 
*
 
|}
 
|}

Revision as of 14:07, 24 December 2015

Home < 2016 Winter Project Week < Projects < CLIModules Backgrounding in MeVisLab

Key Investigators

  • Hans Meine
  • Steve Pieper
  • Andriy Fedorov

Project Description

Objective Approach and Plan Progress and Next Steps
  • Make it possible to run CLI modules asynchronously in MeVisLab, i.e. without freezing the UI during (potentially long) runtime
  • Possibly enable progress reporting (as in CTK/Slicer) for CLIs that support this
  • Start CLIs in the background (already refactored to this avail)
  • Add status fields, modeled after typical background task modules
  • Parse output every xx milliseconds
  • Try to immediately detect finished process