jdurbin/wekaMine — Issue #6: Add support to treat config files as a list of tasks. 
Author: jdurbin
Created: 2011-10-15 05:23:13+00:00
State: open

This requires issue #5 as a prerequisite.

Make the following, taken from the wiki, a reality (may need to be split into several issues/tasks):

There is also a fair chance that the params{} section will go away because I'd like the parameters to be per/experiment values too. However, to keep the experiment spec from growing into an even longer list of obligatory terms, I'll probably replace the experiment line with key-value map so that you can include just the things you use and
in any order. Something like:

```groovy
cvFolds = ['5','10']
experiments = [
classifier=$classifier
classAttr=$classAttr
discretization=$discretization
cvFolds=$cvFolds
]
```

Or, perhaps even better, I will replace it with a linear sequence of steps, denoted by type, like:

```groovy
experiments= [
filter: $normalization,
filter:$discretization,
attrEval: $attributeEval,
attrSearch: $attrSearch,
attrSearch.numAttributes: $numAttributes,
classifier: $classifier,
classifier.classAttribute: $classAttribute
]
```

A filter would be a generic unsupervised transformation, so one could have an arbitrary number of these. Or maybe a ufilter and a sfilter, where the latter would require a class attribute name. In any case, something of that sort, where a series of pipeline steps is specified flexibly rather than hard-coded is in the future for wekaMine.