Difference between revisions of "Documentation/4.0/Modules/EMSegment Command-line"
| Line 27: | Line 27: | ||
The primary function of the <B>EMSegmenter</B> module is to step the user through the process of calibrating, via algorithm parameters, the segmentation algorithm to a particular set of input data. However, once a successful collection of parameters is established, the user will commonly want to bypass this detailed calibration process when segmenting new images by using those parameters collected from the calibration process in <B>EMSegmenter</B> module. The <B>EMSegment Command-line module</B> which wraps the <B>EMSegmentCommandLine executable</B> provides this batch processing capability. The <B>EMSegment Command-line module</B> is automatic generated from the <B>EMSegmentCommandLine executable</B> using the --xml option. | The primary function of the <B>EMSegmenter</B> module is to step the user through the process of calibrating, via algorithm parameters, the segmentation algorithm to a particular set of input data. However, once a successful collection of parameters is established, the user will commonly want to bypass this detailed calibration process when segmenting new images by using those parameters collected from the calibration process in <B>EMSegmenter</B> module. The <B>EMSegment Command-line module</B> which wraps the <B>EMSegmentCommandLine executable</B> provides this batch processing capability. The <B>EMSegment Command-line module</B> is automatic generated from the <B>EMSegmentCommandLine executable</B> using the --xml option. | ||
| − | This module is especially appropriate for segmenting large quantity of data by scripted/batch processing. It requires predefined parameter set, and new target/atlas images can be specified on command line. | + | This module is especially appropriate for segmenting large quantity of data by scripted/batch processing. It requires predefined parameter set, and new target/atlas images can be specified on command line. A list of predefined task is given [ Modules:EMSegment-Command-Line3.6 here]. |
| − | + | <!-- ---------------------------- --> | |
| + | {{documentation/{{documentation/version}}/module-section|Tutorials}} | ||
| − | These slides and data describe the Slicer3 implementation of all three EMSegment modules and demonstrate their use | + | These slides and data describe the Slicer3 implementation of all three EMSegment modules and demonstrate their use. |
[[Media:EMSegTutorial-AHM2008.ppt | Slides]] - [[Media:EMSegTutorial-AHM2008.zip | Data]] | [[Media:EMSegTutorial-AHM2008.ppt | Slides]] - [[Media:EMSegTutorial-AHM2008.zip | Data]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<!-- ---------------------------- --> | <!-- ---------------------------- --> | ||
Revision as of 19:39, 11 December 2011
Home < Documentation < 4.0 < Modules < EMSegment Command-line
Introduction and Acknowledgements
|
This work was funded by the ARRA Supplement to the Neuroimage Analysis Center (NAC), funded by the National Institutes of Health. Information on NAC can be obtained from the NAC website. | |||||
|
Module Description
Use Cases
The primary function of the EMSegmenter module is to step the user through the process of calibrating, via algorithm parameters, the segmentation algorithm to a particular set of input data. However, once a successful collection of parameters is established, the user will commonly want to bypass this detailed calibration process when segmenting new images by using those parameters collected from the calibration process in EMSegmenter module. The EMSegment Command-line module which wraps the EMSegmentCommandLine executable provides this batch processing capability. The EMSegment Command-line module is automatic generated from the EMSegmentCommandLine executable using the --xml option.
This module is especially appropriate for segmenting large quantity of data by scripted/batch processing. It requires predefined parameter set, and new target/atlas images can be specified on command line. A list of predefined task is given [ Modules:EMSegment-Command-Line3.6 here].
Tutorials
These slides and data describe the Slicer3 implementation of all three EMSegment modules and demonstrate their use.
Panels and their use
A list of all the panels in the interface, their features, what they mean, and how to use them. For instance:
|
|
|
Similar Modules
- Point to other modules that have similar functionality
References
Publications related to this module go here. Links to pdfs would be useful. For extensions: link to the source code repository and additional documentation
Information for Developers
 |
Section under construction. |
The section above is generated using the following wiki code:
{{documentation/{{documentation/version}}/module-section|Information for Developers}}
{{documentation/{{documentation/version}}/module-developerinfo|ModuleTemplate|type=Interactive|category=Example}}
If you are documenting a CLI, the category should be extracted from the corresponding XML description. This could be done automatically using the following wiki template:
{{documentation/{{documentation/version}}/module-category|xmlurl=http://path/to/YOURMODULENAME.xml }}
If your module is available in Slicer repository, the following template could be useful to obtain the corresponding URL:
{{documentation/{{documentation/version}}/module-cli-xmlurl|{{documentation/modulename}}|SVNREVISION}}
Using this later template, the final syntax would be:
{{documentation/{{documentation/version}}/module-category|xmlurl={{documentation/{{documentation/version}}/module-cli-xmlurl|{{documentation/modulename}}|SVNREVISION}} }}
