Difference between revisions of "Slicer3:Batchmake Integration"
From NAMIC Wiki
Line 2: | Line 2: | ||
* Goal: Run Slicer execution modules on multiple datasets and/or explore the parameter space of those modules using local computer resources or local GRID resources | * Goal: Run Slicer execution modules on multiple datasets and/or explore the parameter space of those modules using local computer resources or local GRID resources | ||
− | * Summary: BatchMake | + | * Summary: BatchMake integration with Slicer3 is complete. Real-world applications (EMSegmenter) are using BatchMake from within Slicer. Examples are given on how to use BatchMake with your Slicer3 Execution Modules (GaussianBlur example). |
== Background == | == Background == | ||
Line 36: | Line 36: | ||
* Consider general (no programming required) solution to using BatchMake with other Slicer modules | * Consider general (no programming required) solution to using BatchMake with other Slicer modules | ||
** User browses to execution modules and specifies where wildcards should be substituted into command line | ** User browses to execution modules and specifies where wildcards should be substituted into command line | ||
+ | * Provide batch registration module | ||
+ | ** Requires completion of Registration Modules (non-batch versions) | ||
+ | *** See: http://www.na-mic.org/Wiki/index.php/NAC_Grid_Enabled_ITK | ||
+ | *** See: http://www.na-mic.org/Wiki/index.php/ITK_Registration_Optimization |
Revision as of 15:05, 3 October 2007
Home < Slicer3:Batchmake IntegrationIntroduction
- Goal: Run Slicer execution modules on multiple datasets and/or explore the parameter space of those modules using local computer resources or local GRID resources
- Summary: BatchMake integration with Slicer3 is complete. Real-world applications (EMSegmenter) are using BatchMake from within Slicer. Examples are given on how to use BatchMake with your Slicer3 Execution Modules (GaussianBlur example).
Background
- BatchMake provides an open-source toolkit for launching a controlled sequence of applications on the local computer or a GRID.
- Condor is used as the open-source toolkit that provides access to GRID resource. It also provides an easy-to-install and easy-to-configure GRID implementation/network. We highly recommend it for your GRID needs.
- BatchMake and Condor work together to sequence tasks and to allocate and monitor resources and job progress.
Status
Completed
- BatchMake Library
- Distributed via Slicer3's getbuildtest2.tcl script
- Slicer3 code location: Slicer3-lib/BatchMake
- Default distribution does not include Condor
- Can be installed by users
- Changing two BatchMake variables will configure BatchMake to use Condor
- Distributed via Slicer3's getbuildtest2.tcl script
- EMSegmenter BatchMake module
- Distributed via Slicer3's getbuildtest2.tcl script
- Slicer3 GUI Access: Filters/BatchProcessing/EMSegmenter BatchMake Module
- Slicer3 code location: Slicer3/Applications/CLI/BatchMake
- Applies EMSegmenter algorithm to a collection of data using local computer or GRID
- Distributed via Slicer3's getbuildtest2.tcl script
- GaussianBlur BatchMake module
- Distributed via Slicer3's getbuildtest2.tcl script
- Slicer3 GUI Access: Filters/BatchProcessing/GaussianBlur BatchMake Module
- Provides a simple example of how to batchmake-ify your Slicer3 modules
- Distributed via Slicer3's getbuildtest2.tcl script
To do
- Provide documentation
- Provide tutorial at AHM in January 2008
- Determine how to deliver BatchMake's GRID monitoring tool with Slicer3
- Requires FLTK - will not be re-written into KWWidgets
- Consider general (no programming required) solution to using BatchMake with other Slicer modules
- User browses to execution modules and specifies where wildcards should be substituted into command line
- Provide batch registration module
- Requires completion of Registration Modules (non-batch versions)