Slicer3:Execution Model - Revision history

Marianna at 19:37, 19 May 2008

2008-05-19T19:37:47Z

Marianna at 19:30, 19 May 2008

2008-05-19T19:30:30Z

Marianna at 19:29, 19 May 2008

2008-05-19T19:29:13Z

Marianna: /* Documentation */

2008-05-19T19:27:47Z

Documentation

Marianna: /* Documentation */

2008-05-19T19:26:32Z

Documentation

Marianna: /* Status */

2008-05-19T19:25:50Z

Status

Marianna: /* Status */

2008-05-19T19:25:26Z

Status

Marianna: 1 revision

2008-05-15T18:00:48Z

1 revision

Lantiga: /* Status */

2007-01-13T07:45:33Z

Status

New page

=== Abstract ===

The purpose of the Slicer3 Execution Model is to facilitate a "run-everywhere" philosophy for algorithm writers. NAMIC has adopted a standard for algorithm "self-description" that is followed when command line executables are written. Slicer, the grid, clusters, etc... will be able to use the executables directly in their environment.

=== Status ===

The Slicer3 execution model contains three components:

# Module Description Parser - This is a C++ library that parses an xml description of a module and creates C++ classes that can be accessed in applications.
# Command Line Processing - This is a C++ program that uses the Module Description Parser to generate C++ code that parses the command line arguments specified in the xml module description. This code can be included in the command line module to access the command line arguments at run-time.
# Slicer3 GUI - This GUI and related MRML and Logic classes uses the Module Description Parser to create GUI, MRML and Logic classes for each module "discovered" at run-time.

Currently, an initial implementation of all three components is complete.

[[Execution_Model_Reference_Systems | Here]] is a discussion page on how to deal with reference systems in the Execution Model.

=== Documentation ===

Look at the [[Slicer3:Execution_Model_Documentation|Slicer3:Execution Model Documentation]] for details.

=== Background ===

The initial implementation of the Slicer3 Execution Model followed a Wiki discusion of requirements and implementation options. Refer to the [[Slicer3:Execution_Model_Discussion|Slicer3:Execution_Model_Discussion]] for background and motivation.

← Older revision		Revision as of 19:30, 19 May 2008
Line 1:		Line 1:
−	~~=== Abstract ===~~	+	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model here]</font></big>a
−
−	The purpose of the Slicer3 Execution Model is to facilitate a "run-everywhere" philosophy for algorithm writers. NAMIC has adopted a standard for algorithm "self-description" that is followed when command line executables are ~~written. Slicer, the grid, clusters, etc... will be able~~ to ~~use~~ the ~~executables directly in their environment~~.
−
−	==~~= Status ===~~
−
−	~~The Slicer3 execution model contains three components:~~
−
−	~~# Module Description Parser - This is a C++ library that parses an xml description of a module and creates C++ classes that can be accessed in applications.~~
−	# Command Line Processing - This is a C++ program that uses the Module Description Parser to generate C++ code that parses the command line arguments specified in the xml module description. This code can be included in the command line module to access the command line arguments at run-time.
−	~~# Slicer3 GUI - This GUI and related MRML and Logic classes uses the Module Description Parser to create GUI, MRML and Logic classes for each module~~ "~~discovered~~" ~~at run-time.~~
−
−	~~Currently, an initial implementation of all three components~~ is ~~complete.~~
−
−	[http://www.~~na-mic~~.org/~~Wiki~~/index.php/~~Execution_Model_Reference_Systems Here] is a discussion page on how to deal with reference systems in the Execution Model.~~
−
−	~~=== Documentation ===~~
−
−	~~Look at the [[~~Slicer3:~~Execution_Model_Documentation\|Execution Model Documentation~~]~~] for details.~~
−
−	~~=== Background ===~~
−
−	~~The initial implementation of the Slicer3 Execution Model followed~~ a ~~Wiki discussion of requirements and implementation options. Refer to the [[Slicer3:Execution_Model_Discussion\|Execution Model Discussion]] page for background and motivation.~~

@@ Line 13: / Line 13: @@
 Currently, an initial implementation of all three components is complete.
-[http://www.na-mic.org/Wiki/index.php/Execution_Model_Reference_Systems | Here] is a discussion page on how to deal with reference systems in the Execution Model.
+[http://www.na-mic.org/Wiki/index.php/Execution_Model_Reference_Systems Here] is a discussion page on how to deal with reference systems in the Execution Model.
 === Documentation ===
@@ Line 21: / Line 21: @@
 === Background ===
-The initial implementation of the Slicer3 Execution Model followed a Wiki discusion of requirements and implementation options. Refer to the [[Slicer3:Execution_Model_Discussion|Slicer3:Execution_Model_Discussion]] for background and motivation.
+The initial implementation of the Slicer3 Execution Model followed a Wiki discussion of requirements and implementation options. Refer to the [[Slicer3:Execution_Model_Discussion|Execution Model Discussion]] page for background and motivation.

@@ Line 13: / Line 13: @@
 Currently, an initial implementation of all three components is complete.
-[[http://www.na-mic.org/Wiki/index.php/Execution_Model_Reference_Systems | Here]] is a discussion page on how to deal with reference systems in the Execution Model.
+[http://www.na-mic.org/Wiki/index.php/Execution_Model_Reference_Systems | Here] is a discussion page on how to deal with reference systems in the Execution Model.
 === Documentation ===

← Older revision		Revision as of 19:37, 19 May 2008
Line 1:		Line 1:
−	~~<big>'''Note~~:~~''' We are migrating this content~~ to the ~~slicer~~.~~org domain~~ - ~~<font color=~~"~~orange~~"~~>The newer page~~ is [http://www.~~slicer~~.org/~~slicerWiki~~/index.php/Slicer3:~~Execution_Model here~~]~~</font></big>~~a	+	=== Abstract ===
		+
		+	The purpose of the Slicer3 Execution Model is to facilitate a "run-everywhere" philosophy for algorithm writers. NAMIC has adopted a standard for algorithm "self-description" that is followed when command line executables are written. Slicer, the grid, clusters, etc... will be able to use the executables directly in their environment.
		+
		+	=== Status ===
		+
		+	The Slicer3 execution model contains three components:
		+
		+	# Module Description Parser - This is a C++ library that parses an xml description of a module and creates C++ classes that can be accessed in applications.
		+	# Command Line Processing - This is a C++ program that uses the Module Description Parser to generate C++ code that parses the command line arguments specified in the xml module description. This code can be included in the command line module to access the command line arguments at run-time.
		+	# Slicer3 GUI - This GUI and related MRML and Logic classes uses the Module Description Parser to create GUI, MRML and Logic classes for each module "discovered" at run-time.
		+
		+	Currently, an initial implementation of all three components is complete.
		+
		+	[http://www.na-mic.org/Wiki/index.php/Execution_Model_Reference_Systems Here] is a discussion page on how to deal with reference systems in the Execution Model.
		+
		+	=== Documentation ===
		+
		+	Look at the [[Slicer3:Execution_Model_Documentation\|Execution Model Documentation]] for details.
		+
		+	=== Background ===
		+
		+	The initial implementation of the Slicer3 Execution Model followed a Wiki discusion of requirements and implementation options. Refer to the [[Slicer3:Execution_Model_Discussion\|Execution Model Discussion]] for background and motivation.

← Older revision	Revision as of 18:00, 15 May 2008
(No difference)