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

From NAMIC Wiki
Jump to: navigation, search
 
Line 28: Line 28:
 
* For now, stay with synchroneous API, but don't let GUI freeze
 
* For now, stay with synchroneous API, but don't let GUI freeze
 
* [https://github.com/commontk/CTK/issues/624 Issue filed] about XML attribute for "supports progress output"
 
* [https://github.com/commontk/CTK/issues/624 Issue filed] about XML attribute for "supports progress output"
 +
* (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)