Slicer3:Execution Model Documentation - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T17:32:37Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Marianna: Protected "Slicer3:Execution Model Documentation" [edit=sysop:move=sysop]

2008-05-22T16:27:29Z

Protected "Slicer3:Execution Model Documentation" [edit=sysop:move=sysop]

Marianna: Unprotected "Slicer3:Execution Model Documentation"

2008-05-19T19:41:18Z

Unprotected "Slicer3:Execution Model Documentation"

Marianna: Replacing page with ''''Note:''' We are migrating this content to the slicer.org domain - The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_M...'

2008-05-19T19:41:00Z

Replacing page with '<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_M...'

Show changes

Marianna at 21:12, 11 April 2008

2008-04-11T21:12:00Z

Pieper: /* Introduction */

2008-03-03T13:28:45Z

Introduction

Gregsharp: /* User-defined Modules Built Outside of Slicer3 */

2008-02-14T19:30:23Z

User-defined Modules Built Outside of Slicer3

Millerjv: /* XML Schema */

2007-12-14T01:05:36Z

XML Schema

Pieper: /* FAQ */

2007-10-31T14:50:37Z

FAQ

Lorensen: /* Building the Slicer3 Command Line Programs Outside of Slicer3 */

2007-10-17T12:55:09Z

Building the Slicer3 Command Line Programs Outside of Slicer3

← Older revision		Revision as of 17:32, 10 July 2017
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_Documentation here]</font></big>a	+	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:Execution_Model_Documentation here]</font></big>a

← Older revision		Revision as of 21:12, 11 April 2008
Line 1:		Line 1:
		+	<big><font color="#e72300">Please make changes to this page [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation here]</font></big>
	== Introduction ==		== Introduction ==

← Older revision		Revision as of 13:28, 3 March 2008
Line 65:		Line 65:

	Python scripts are found using the discovery mechanisms for the other plugins. Since Python plugins are fundamentally different from the shared and executable plugins, they are documented on their own [[Slicer3:Execution Model Documentation:Python \| page]].		Python scripts are found using the discovery mechanisms for the other plugins. Since Python plugins are fundamentally different from the shared and executable plugins, they are documented on their own [[Slicer3:Execution Model Documentation:Python \| page]].
		+
		+	=== Calling Command Line Modules from Other Code ===
		+
		+	In addition to the automated GUI that shows up in the Slicer3 user interface, the Execution Model can be used to encapsulate functionality that is invoked by other parts of the program. For instance, the Editor Module can invoke the Model Maker Module to build models. By invoking a command line module in this way, you get the advantage of background processing with progress reporting. See [[Slicer3:Execution Model Documentation:Programmatic Invocation \| this page]] for more details.

	=== Architecture ===		=== Architecture ===

@@ Line 918: / Line 918: @@
+#
 FIND_PACKAGE(GenerateCLP REQUIRED)
-INCLUDE(${GenerateCLP_SOURCE_DIR}/UseGenerateCLP.cmake)
+INCLUDE(${GenerateCLP_USE_FILE})
+#

@@ Line 163: / Line 163: @@
 ;;; </description>
-;;; <integer> | <float> | <double> | <boolean> | <string> | <integer-vector> | <float-vector> | <double-vector> | <string-vector> | <integer-enumeration> | <float-enumeration> | <double-enumeration> | <string-enumeration> | <file> | <directory> | <image> | <geometry> [type="fiberbundle|''model''"] | <point>[multiple="true|''false''"] [coordinateSystem="lps|ras|''ijk''"] | <region>[multiple="true|''false''"] [coordinateSystem="lps|ras|''ijk''"]
+;;; <integer> | <float> | <double> | <boolean> | <string> | <integer-vector> | <float-vector> | <double-vector> | <string-vector> | <integer-enumeration> | <float-enumeration> | <double-enumeration> | <string-enumeration> | <file> | <directory> | <image>[type="''scalar''|''label''|''tensor''|''diffusion-weighted''|''vector''|''model''"] | <geometry> [type="''fiberbundle''|''model''"] | <point>[multiple="''true''|''false''"] [coordinateSystem="''lps''|''ras''|''ijk''"] | <region>[multiple="''true''|''false''"] [coordinateSystem="''lps''|''ras''|''ijk''"]
-::: The type of the parameter. The scalar types ('''integer''', '''float''', etc.) correspond to the usual programming language types. The '''-vector''' types are represented by comma separated values of the scalar type. The '''-enumeration''' types use the '''<element>''' tag to enumerate choices of the scalar type. '''<image>''' is a special type that indicates that the parameter is a file name that specifies images. If the attribute multiple is "true", multiple arguments are allowed for '''scalar''', '''file''', '''directory''', '''image''', '''geometry''', '''point''' and '''region''' parameters. The attribute coordinateSystem is allowed for the parameters '''point''' and '''region'''. The attribute ''fileExtensions'' is allowed for '''file''', '''image''' and '''geometry'''. fileExtensions can contain a list of comma separated file extensions for optional use by the GUI. If the parameter has a ''flag'' or ''longflag'', then the flag may be specified multiple times on the command line. The resulting C++ variable will be a std::vector of the scalar type. If the multiple parameter does not have a flag, then multiple arguments can appear on the command line. However, a multiple parameter with no flags must be the last parameter specified.
+::: The type of the parameter. The scalar types ('''integer''', '''float''', etc.) correspond to the usual programming language types. The '''-vector''' types are represented by comma separated values of the scalar type. The '''-enumeration''' types use the '''<element>''' tag to enumerate choices of the scalar type. '''<image>''' is a special type that indicates that the parameter is a file name that specifies images. If the attribute ''multiple'' is "true", multiple arguments are allowed for '''scalar''', '''file''', '''directory''', '''image''', '''geometry''', '''point''' and '''region''' parameters. The attribute ''coordinateSystem'' is allowed for the parameters '''point''' and '''region'''. The attribute ''fileExtensions'' is allowed for '''file''', '''image''' and '''geometry'''. fileExtensions can contain a list of comma separated file extensions for optional use by the GUI. If the parameter has a ''flag'' or ''longflag'', then the flag may be specified multiple times on the command line. The resulting C++ variable will be a std::vector of the scalar type. If the multiple parameter does not have a flag, then multiple arguments can appear on the command line. However, a multiple parameter with no flags must be the last parameter specified.
 ;;;; <name> (required if longflag is not specified)

← Older revision	Revision as of 16:27, 22 May 2008
(No difference)

← Older revision	Revision as of 19:41, 19 May 2008
(No difference)

← Older revision		Revision as of 14:50, 31 October 2007
Line 1,362:		Line 1,362:
	*Matlab		*Matlab

		+	== How do I debug my command line module? ==
		+
		+	See [[Slicer3:Execution_Model_Documentation:Debugging]]

	Back to [http://www.na-mic.org/Wiki/index.php/Slicer3:Documentation Slicer3 Documentation]		Back to [http://www.na-mic.org/Wiki/index.php/Slicer3:Documentation Slicer3 Documentation]

@@ Line 1,004: / Line 1,004: @@
 # Checkout the Slicer3 command line programs
 ## svn co http://www.na-mic.org/svn/Slicer3/trunk/Applications/CLI
-# Some of the programs in CLI rely on vtkITK. If you will e using these command line programs, then checkout vtkITK.
+# Some of the programs in CLI rely on vtkITK. If you will be using these command line programs, then checkout vtkITK.
 ## svn co http://www.na-mic.org/svn/Slicer3/trunk/Libs/vtkITK
 ## Run cmake on vtkITK.