Difference between revisions of "2008 Summer Project Week:ModuleChaining"
| Line 8: | Line 8: | ||
===Key Investigators=== | ===Key Investigators=== | ||
* UCSD: Marco Ruiz, Chris Churas, Jeff Grethe | * UCSD: Marco Ruiz, Chris Churas, Jeff Grethe | ||
| − | * Isomics: Steve Pieper | + | * Isomics: Steve Pieper, Daniel Blezek |
* GE: Jim Miller | * GE: Jim Miller | ||
| − | + | * Mario Negri Inst: Luca Antiga | |
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
Revision as of 20:07, 23 June 2008
Home < 2008 Summer Project Week:ModuleChaining Return to Project Week Main Page |
Key Investigators
- UCSD: Marco Ruiz, Chris Churas, Jeff Grethe
- Isomics: Steve Pieper, Daniel Blezek
- GE: Jim Miller
- Mario Negri Inst: Luca Antiga
Objective
To create a standard infrastructure for Slicer3 to support sequential module chaining functionality. This functionality includes features such as allowing the user to describe an ordered set of modules to execute one after another, which outputs to pipe as inputs of future module invocations and how to render the Slicer3 UI to gather the required parameters of the "chain". All of this done leveraging on the standard execution module to require minimal user input.
Approach, Plan
The first prototype has been developed as an independent engine system in Java. This will serve to provide a "proof of concept" type of grounds to evaluate and refine current and new ideas, in order to create a standard, full-feature version of this engine embedded into Slicer3.
Progress
Technical details of this effort are being documented at: Slicer3:Chain_CLMs
References
- Example Shell Script to chain two modules and expose the result as a CLI:
- Note, this shell script is not cross platform - the bundled tcl or python interp should be used instead of /bin/sh
