NA-MIC/Projects/NA-MIC Kit/Execution Model - Revision history

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

2017-07-10T17:09:13Z

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

Melonakos at 21:33, 5 November 2008

2008-11-05T21:33:07Z

Melonakos at 21:31, 5 November 2008

2008-11-05T21:31:07Z

Melonakos at 21:26, 5 November 2008

2008-11-05T21:26:29Z

Melonakos at 18:43, 28 November 2007

2007-11-28T18:43:36Z

Millerjv at 21:44, 19 April 2007

2007-04-19T21:44:28Z

Millerjv at 21:42, 19 April 2007

2007-04-19T21:42:08Z

Millerjv at 21:37, 19 April 2007

2007-04-19T21:37:19Z

Millerjv at 21:37, 19 April 2007

2007-04-19T21:37:07Z

Millerjv at 21:29, 19 April 2007

2007-04-19T21:29:51Z

@@ Line 18: / Line 18: @@
 = Links =
-* [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model Slicer3 Execution Model]
+* [https://www.slicer.org/wiki/Slicer3:Execution_Model Slicer3 Execution Model]
-* [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation Slicer3 Execution Model Documentation]
+* [https://www.slicer.org/wiki/Slicer3:Execution_Model_Documentation Slicer3 Execution Model Documentation]
-* [http://www.slicer.org/slicerWiki/index.php/Slicer3:VisualBlog Slicer3 Visual Blog]
+* [https://www.slicer.org/wiki/Slicer3:VisualBlog Slicer3 Visual Blog]

@@ Line 20: / Line 20: @@
 * [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model Slicer3 Execution Model]
 * [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation Slicer3 Execution Model Documentation]
-* [[Slicer3:VisualBlog | Slicer3 Visual Blog]]
+* [http://www.slicer.org/slicerWiki/index.php/Slicer3:VisualBlog Slicer3 Visual Blog]

@@ Line 18: / Line 18: @@
 = Links =
-* [[Slicer3:Execution_Model|Slicer3 Execution Model]]
+* [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model Slicer3 Execution Model]
 * [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation Slicer3 Execution Model Documentation]
 * [[Slicer3:VisualBlog | Slicer3 Visual Blog]]

@@ Line 19: / Line 19: @@
 * [[Slicer3:Execution_Model|Slicer3 Execution Model]]
-* [[Slicer3:Execution Model Documentation | Slicer3 Execution Model Documentation]]
+* [http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation Slicer3 Execution Model Documentation]
 * [[Slicer3:VisualBlog | Slicer3 Visual Blog]]

@@ Line 1: / Line 1: @@
   Back to [[NA-MIC_Collaborations|NA-MIC_Collaborations]]
-'''Objective:''' The Slicer3 Execution Model realizes the "Extensible Algorithmic Framework" goal by providing an interactive point-and-click interface to ITK-based command line executables as well as a batch processing interface to execute large scale experiments on clusters and grids. This objective is reached without requiring extensive re-engineering by the algorithm developer. The Execution Model uses an XML syntax to describe algorithm options and user interface controls. Slicer3 constructs the appropriate user interfaces from this description and manages the data transfer to and from the algorithm module. Modules are discovered at runtime and delivered to clinicians as plugins to Slicer3.
+= Name of Template Project goes here =
-'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3.  The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations.  Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.
+The Slicer3 Execution Model realizes the "Extensible Algorithmic Framework" goal by providing an interactive point-and-click interface to ITK-based command line executables as well as a batch processing interface to execute large scale experiments on clusters and grids. This objective is reached without requiring extensive re-engineering by the algorithm developer. The Execution Model uses an XML syntax to describe algorithm options and user interface controls. Slicer3 constructs the appropriate user interfaces from this description and manages the data transfer to and from the algorithm module. Modules are discovered at runtime and delivered to clinicians as plugins to Slicer3.
 [[Image:AnisotropicDiffusionFilterGUI.png|thumb|400px|Slicer3 user interface for a command line module. This user interface was constructed automatically from the XML description of the module parameters.]]
-'''Key Investigators'''<nowiki>: </nowiki>
+= Key Investigators =
-* Dan Blezek, Jim Miller and Bill Lorensen (GE)
+*GE: Dan Blezek,Jim Miller and Bill Lorensen
-Links:
+= Links =
 * [[Slicer3:Execution_Model|Slicer3 Execution Model]]
 * [[Slicer3:Execution Model Documentation | Slicer3 Execution Model Documentation]]
 * [[Slicer3:VisualBlog | Slicer3 Visual Blog]]

← Older revision		Revision as of 21:44, 19 April 2007
Line 5:		Line 5:
	'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations. Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.		'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations. Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.

−	[[Image:AnisotropicDiffusionFilterGUI.png\|thumb\|400px\|Slicer3 user interface for a command line module.]]	+	[[Image:AnisotropicDiffusionFilterGUI.png\|thumb\|400px\|Slicer3 user interface for a command line module. This user interface was constructed automatically from the XML description of the module parameters.]]

← Older revision		Revision as of 21:42, 19 April 2007
Line 5:		Line 5:
	'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations. Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.		'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations. Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.

−	[[Image:AnisotropicDiffusionFilterGUI.png]]	+	[[Image:AnisotropicDiffusionFilterGUI.png\|thumb\|400px\|Slicer3 user interface for a command line module.]]

← Older revision		Revision as of 21:37, 19 April 2007
Line 5:		Line 5:
	'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations. Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.		'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. Modules can provide their own help information, acknowledgments, and logos. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, geometry, points, booleans, integers, floating point numbers, strings, files, directories, lists, and enumerations. Additional parameter datatypes such as MRML scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.

−	[Image:AnisotropicDiffusionFilterGUI.png]	+	[[Image:AnisotropicDiffusionFilterGUI.png]]

← Older revision		Revision as of 21:29, 19 April 2007
Line 3:		Line 3:
	'''Objective:''' The Slicer3 Execution Model realizes the "Extensible Algorithmic Framework" goal by providing an interactive point-and-click interface to ITK-based command line executables as well as a batch processing interface to execute large scale experiments on clusters and grids. This objective is reached without requiring extensive re-engineering by the algorithm developer. The Execution Model uses an XML syntax to describe algorithm options and user interface controls. Slicer3 constructs the appropriate user interfaces from this description and manages the data transfer to and from the algorithm module. Modules are discovered at runtime and delivered to clinicians as plugins to Slicer3.		'''Objective:''' The Slicer3 Execution Model realizes the "Extensible Algorithmic Framework" goal by providing an interactive point-and-click interface to ITK-based command line executables as well as a batch processing interface to execute large scale experiments on clusters and grids. This objective is reached without requiring extensive re-engineering by the algorithm developer. The Execution Model uses an XML syntax to describe algorithm options and user interface controls. Slicer3 constructs the appropriate user interfaces from this description and manages the data transfer to and from the algorithm module. Modules are discovered at runtime and delivered to clinicians as plugins to Slicer3.

−	'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. A rich set of parameter types can be provided to a module including: scalar images, vector ~~image~~, diffusion weighted images, diffusion tensor images, models, fiducials, booleans, integers, floating point numbers, strings, lists, and enumerations. Additional parameter datatypes such as scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.	+	'''Progress:''' A base implementation of module discovery, user interface construction, and module execution is integrated into Slicer3. The implementation supports modules packaged as command line executables as well as modules loaded as dynamic libraries. A rich set of parameter types can be provided to a module including: scalar images, vector images, diffusion weighted images, diffusion tensor images, models, fiducials, booleans, integers, floating point numbers, strings, lists, and enumerations. Additional parameter datatypes such as scenes, comma separated value files, and transforms are under development. Parameter sets can be archived as part of a MRML scene in Slicer3. Parameters are realized in the Slicer3 user interface using a rich set of widgets that include: node selectors, sliders, text entries, spin boxes, check boxes, radio buttons, and directory browsers. Modules can report multistage progress and modules can be terminated from Slicer3. Modules are run in a separate thread of execution and are queued so that only one module will execute at a time. Modules report information to the standard Slicer3 logging facility. Extensive documentation on the execution model is available describing the XML module description, the parameter types, command line parameter parsing tools, the automatic user interface construction, process control tools, and CMake configurations for new modules.