Difference between revisions of "Projects:ARRA:SlicerEM:AtlasCreator"
| Line 26: | Line 26: | ||
==== Proposal: Running Atlas Creator in a Grid Environment ==== | ==== Proposal: Running Atlas Creator in a Grid Environment ==== | ||
| + | |||
| + | The Atlas Creator concept supports parallelized computation. An existing grid environment can be leveraged during the Registration phase as shown in the diagram above. | ||
| + | |||
| + | Only the Registration can be performed parallelized since it is the most time-consuming task in the Atlas Creator pipeline. | ||
| + | |||
| + | The Atlas Creator module runs on one node in the cluster (most likely the head node) and then generates bash scripts which start the registration using the 3D Slicer launch mechanism. These scripts can be run using an existing scheduler or a similar mechanism. An existing DISPLAY environment is not necessary for using the 3D Slicer launch mechanism. | ||
| + | |||
| + | The module immediately recognizes if the parallelized registration jobs are complete and then continues the pipeline on the node where the it was first started. | ||
| + | |||
| + | ===== Input for Parallelized Computation ===== | ||
| + | * Optional: Command for scheduling the generated bash scripts. This command will be run with the generated bash scripts as individual arguments. | ||
| + | * Optional: Path to 3D Slicer (must be a network installation reachable by each node) | ||
| + | * Optional: The temporary directory to be used by the 3D Slicer launch mechanism | ||
| + | * Optional: The config file directory to be used by the 3D Slicer launch mechanism | ||
| + | * The number of different computation nodes. The Atlas Creator will use this number to distribute the parallelized registration among the input images. | ||
==== Proposal: Invoking Atlas Creator via Python ==== | ==== Proposal: Invoking Atlas Creator via Python ==== | ||
Revision as of 20:43, 2 February 2011
Home < Projects:ARRA:SlicerEM:AtlasCreatorContents
Atlas Creator
The Atlas Creator combines existing segmentations to an anatomical atlas based on robust statistics.
GUI
The following screenshot shows the graphical user interface of the Atlas Creator module in 3D Slicer Version 3.
Priority List
- Implement dynamic registration
- Watch out for overflows
- Re-structure Atlas Creator code according to the Design specified below
- Implement support for parallel Computation
- Add Help and Online Documentation
- Include Shape Atlas functionality
Design
The following State Machine diagram shows the flow of the Atlas Creator logic.
Proposal: Running Atlas Creator in a Grid Environment
The Atlas Creator concept supports parallelized computation. An existing grid environment can be leveraged during the Registration phase as shown in the diagram above.
Only the Registration can be performed parallelized since it is the most time-consuming task in the Atlas Creator pipeline.
The Atlas Creator module runs on one node in the cluster (most likely the head node) and then generates bash scripts which start the registration using the 3D Slicer launch mechanism. These scripts can be run using an existing scheduler or a similar mechanism. An existing DISPLAY environment is not necessary for using the 3D Slicer launch mechanism.
The module immediately recognizes if the parallelized registration jobs are complete and then continues the pipeline on the node where the it was first started.
Input for Parallelized Computation
- Optional: Command for scheduling the generated bash scripts. This command will be run with the generated bash scripts as individual arguments.
- Optional: Path to 3D Slicer (must be a network installation reachable by each node)
- Optional: The temporary directory to be used by the 3D Slicer launch mechanism
- Optional: The config file directory to be used by the 3D Slicer launch mechanism
- The number of different computation nodes. The Atlas Creator will use this number to distribute the parallelized registration among the input images.
