Difference between revisions of "Slicer3:Large scale experiment control brainstorming"

From NAMIC Wiki
Jump to: navigation, search
 
Line 7: Line 7:
 
# Slicer3 is used interactively to select a set of parameters for an algorithm or workflow on a single dataset.  Then, these parameters are applied to N datasets non-interactively.
 
# Slicer3 is used interactively to select a set of parameters for an algorithm or workflow on a single dataset.  Then, these parameters are applied to N datasets non-interactively.
 
# Slicer3 is used interactively to select a subset of parameters for an algorithm or workflow on a single dataset.  Then, the remaining parameter space is searched non-interactively. Various parameter space evaluation techniques could be employed, the simplest of which is to sample the space of (param1, param2, param3).
 
# Slicer3 is used interactively to select a subset of parameters for an algorithm or workflow on a single dataset.  Then, the remaining parameter space is searched non-interactively. Various parameter space evaluation techniques could be employed, the simplest of which is to sample the space of (param1, param2, param3).
 +
 +
Note, that with the above two use cases, we are only trying to address large scale experiment control from the standpoint of what it means to Slicer3.  We are '''not''' trying to solve the general case.
 +
 +
== Assumptions and restrictions ==
 +
 +
== Components ==
 +
 +
(Steve, fill this section in from the whiteboard.)
 +
 +
== Thought experiements ==
 +
 +
Below are a few thought experiments to address the above. These will be used to see how the above needs can be addressed.
 +
 +
=== Makefiles + the loopy launcher ===
 +
 +
=== BatchMake ===

Revision as of 15:43, 2 April 2007

Home < Slicer3:Large scale experiment control brainstorming

Goal

To provide Slicer3 with a mechanism for submitting, monitoring, and summarizing large scale experiments that utilize Slicer3 modules, particularly the Command Line Modules. This page summarizes our thoughts, requirements, and experiments to date.

There are two introductory use cases that we wish to support:

  1. Slicer3 is used interactively to select a set of parameters for an algorithm or workflow on a single dataset. Then, these parameters are applied to N datasets non-interactively.
  2. Slicer3 is used interactively to select a subset of parameters for an algorithm or workflow on a single dataset. Then, the remaining parameter space is searched non-interactively. Various parameter space evaluation techniques could be employed, the simplest of which is to sample the space of (param1, param2, param3).

Note, that with the above two use cases, we are only trying to address large scale experiment control from the standpoint of what it means to Slicer3. We are not trying to solve the general case.

Assumptions and restrictions

Components

(Steve, fill this section in from the whiteboard.)

Thought experiements

Below are a few thought experiments to address the above. These will be used to see how the above needs can be addressed.

Makefiles + the loopy launcher

BatchMake