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

From NAMIC Wiki
Jump to: navigation, search
m (moved 2015 Summer Project Week:CLIModules Backgrounding in MeVisLab to 2016 Winter Project Week:CLIModules Backgrounding in MeVisLab: Postponed, will pick up again (had to cancel summer project week attendance))
 
(6 intermediate revisions by 2 users not shown)
Line 10: Line 10:
  
 
==Project Description==
 
==Project Description==
−
<div style="margin: 20px;">
+
{| class="wikitable"
−
<div style="width: 27%; float: left; padding-right: 3%;">
+
! style="text-align: left; width:27%" |  Objective
−
<h3>Objective</h3>
+
! style="text-align: left; width:27%" |  Approach and Plan
 +
! style="text-align: left; width:27%" |  Progress and Next Steps
 +
|- style="vertical-align:top;"
 +
|
 +
<!-- 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
−
</div>
+
|
−
<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>
+
|
−
<div style="width: 27%; float: left; padding-right: 3%;">
+
* Got CLI running in background
−
<h3>Progress</h3>
+
* For now, stay with synchroneous API, but don't let GUI freeze
−
</div>
+
* [https://github.com/commontk/CTK/issues/624 Issue filed] about XML attribute for "supports progress output"
−
</div>
+
* (improved CLIImporter's usability w.r.t. many paths)
 +
|}

Latest revision as of 23:18, 6 January 2016

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
  • Got CLI running in background
  • For now, stay with synchroneous API, but don't let GUI freeze
  • Issue filed about XML attribute for "supports progress output"
  • (improved CLIImporter's usability w.r.t. many paths)
Retrieved from "https://www.na-mic.org/w/index.php?title=2016_Winter_Project_Week/Projects/CLIModules_Backgrounding_in_MeVisLab&oldid=91787"