2008 Summer Project Week:ModuleChaining - Revision history

Mruiz at 03:23, 26 June 2008

2008-06-26T03:23:37Z

Mruiz at 14:08, 25 June 2008

2008-06-25T14:08:38Z

Mruiz at 20:07, 23 June 2008

2008-06-23T20:07:25Z

Pieper: /* References */

2008-06-23T12:02:26Z

References

Pieper: /* Key Investigators */

2008-06-23T12:02:06Z

Key Investigators

Mruiz at 20:12, 17 June 2008

2008-06-17T20:12:42Z

Mruiz: New page: {| |Project Week Main Page ]] |} NOTOC ===Key Investigators=== * UCSD: Marco Ruiz, Chris Churas, Jeff...

2008-06-17T20:07:06Z

New page: {| |thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page ]] |} __NOTOC__ ===Key Investigators=== * UCSD: Marco Ruiz, Chris Churas, Jeff...

New page

{|
|[[Image:ProjectWeek-2008.png|thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page]] ]]
|}

__NOTOC__

===Key Investigators===
* UCSD: Marco Ruiz, Chris Churas, Jeff Grethe
* Isomics: Steve Pieper
* GE: Jim Miller

<div style="margin: 20px;">

<div style="width: 27%; float: left; padding-right: 3%;">

<h1>Objective</h1>
To create a standard infrastructure for Slicer3 to support creation, parameter gathering and execution of "chains" of modules.

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h1>Approach, Plan</h1>

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.

</div>

<div style="width: 40%; float: left;">

<h1>Progress</h1>

Technical details of this effort are being documented at:
[[Slicer3:Chain_CLMs]]

</div>

<br style="clear: both;" />

</div>

@@ Line 10: / Line 10: @@
 * Isomics: Steve Pieper, Daniel Blezek
 * GE: Jim Miller
 * Mario Negri Inst: Luca Antiga
@@ Line 33: / Line 35: @@
 <h1>Progress</h1>
-Technical details of this effort are being documented at:
+We successfully integrated the chain module engine into Slicer3 and test run it with 2 custom chain descriptors (created according to specifications). These descriptors were successfully used by the integrated engine to behave as a true Slicer3 module (tested within the UI):  auto-generating the desired "Standard Execution Model" descriptor when invoked with the "--xml" reactor and, when invoked without it, executing in sequence the referred modules, with the appropriate argument chaining, as expected. All details of this effort are being documented at: [[Slicer3:JavaBasedChainCLMsEngine]]
 </div>
@@ Line 41: / Line 41: @@
 </div>

@@ Line 47: / Line 47: @@
 * Example Shell Script to chain two modules and expose the result as a CLI:
 http://www.na-mic.org/ViewVC/index.cgi/trunk/Modules/CommandLineModule/Testing/CLI-shell.sh?annotate=6987
-** Note, this shell script is not cross platform - the bundled tcl or python interp should be used instead of /bin/sh
+* Note, this shell script is not cross platform - the bundled tcl or python interp should be used instead of /bin/sh

← Older revision		Revision as of 12:02, 23 June 2008
Line 41:		Line 41:

	</div>		</div>
		+
		+
		+	===References===
		+
		+	* Example Shell Script to chain two modules and expose the result as a CLI:
		+	http://www.na-mic.org/ViewVC/index.cgi/trunk/Modules/CommandLineModule/Testing/CLI-shell.sh?annotate=6987
		+	** Note, this shell script is not cross platform - the bundled tcl or python interp should be used instead of /bin/sh

@@ Line 7: / Line 7: @@
 ===Key Investigators===
-* UCSD: Marco Ruiz, Chris Churas, Jeff Grethe
+* UCSD: Marco Ruiz, Jeff Grethe
 * Isomics: Steve Pieper, Daniel Blezek
 * GE: Jim Miller
@@ Line 34: / Line 34: @@
 Technical details of this effort are being documented at:
-[[Slicer3:Chain_CLMs]]
+[[Slicer3:JavaBasedChainCLMsEngine]]
 </div>

@@ Line 17: / Line 17: @@
 <h1>Objective</h1>
-To create a standard infrastructure for Slicer3 to support creation, parameter gathering and execution of "chains" of modules.
+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.
 </div>