The successful offspring analyzer should be made more user friendly

[mkommend]

The usability of the successful offspring analyzer should be improved:

• By default the manipulators and crossovers should be collected
• The selected operator parameter should be named automatically

[svonolfe]

improved usability of successful offspring analysis in r10346

[mkommend]

It would be better if the result names were also configurable to display for example crossovers instead of selected crossover operator. A possible solution would be to use ScopeTreeLookupParameters, which would also improve the code quality.

[svonolfe]

adapted remaining VRP operators to successful offspring analysis in r10348

[svonolfe]

I aggree that the manual scope tree traversal should be removed from the SuccessfulOffspringAnalyzer and replaced with ScopeTreeLookupParameters. This would improve the overall design and also fix the problem of naming the analysis results correctly.

However, first the ScopeTreeLookupParameter must be changed to return null values instead of throwing an exception if a certain variable is not available in a scope. For instance, not all individuals have been manipulated and thus this variable ("SelectedManipulationOperator") is not available in some scopes.

[mkommend]

The ScopeTreeLookupParameter does not throw an exception if the variable is not found and can therefore be used in the SuccessfulOffspringAnalyzer without any modifications.

[mkommend]

r10917: Merged r10346, r10348 into stable.