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

From NAMIC Wiki
Jump to: navigation, search
Line 10: Line 10:
  
 
==Project Description==
 
==Project Description==
<div style="margin: 20px;">
+
{| class="wikitable"
<div style="width: 27%; float: left; padding-right: 3%;">
+
|- style="vertical-align:top;"
<h3>Objective</h3>
+
! style="text-align: left; width:27%" |      Objective
 
* 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
</div>
+
! style="text-align: left; width:27%" |      Approach, Plan
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Approach, Plan</h3>
 
 
* 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
</div>
+
! style="text-align: left; width:27%" |      Progress
<div style="width: 27%; float: left; padding-right: 3%;">
+
*
<h3>Progress</h3>
+
 
</div>
+
|}
</div>
 

Revision as of 22:28, 18 December 2015

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

Key Investigators

  • Hans Meine
  • Steve Pieper
  • Andriy Fedorov

Project Description

Objective
  • 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
Approach, Plan
  • 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
Progress