Add calculated values to algorithm runs for further analysis.

[epitzer]

Sometimes it might be necessary to add additional values to algorithm runs that can be calculated from existing results such as a normalized value by dividing through e.g. problem size.

[epitzer]

Create RunCollectionModificationEvaluator that evaluates IRunCollectionModifiers (r6662)

[epitzer]

Add concrete run collection modifiers to add calculated values and discretized values (r6663)

[epitzer]

Include RunCollection modification into RunCollection View (r6664)

[epitzer]

Add RunCollectionValueRemover modifier and disallow name change in RunCollectionFuzzifier (r6665)

[epitzer]

Modify run collection to force update of cached values (r6667)

[epitzer]

Enable grouping before fuzzification (r6668)

[epitzer]

Add missing plugin dependency (r6669)

[epitzer]

Also register events in cloning constructor (r6670)

[epitzer]

Remove unnecessary suffix parameter and correctly include grouping clause in generated item name (r6671)

[epitzer]

Enable modifications of order and number of runs in RunCollectionModificationEvaluator and implement RunCollectionSorter (r6677)

[abeham]

This is a welcomed feature, that I myself would have needed a couple of times already. However can you elaborate this feature a little more? I wonder about the specific needs, because I'm a bit skeptical on the way this is implemented.

The one thing I ask myself about this feature: Why don't we just make this user interface only? All I assume you would need is to add/remove and probably modify results in several runs of a RunCollection. There can be a simple dialog that allows you to do this.

I would imagine this to work like this: I have my run collection. I open the dialog where I can filter the runs (e.g. in a simple checkbox list or via a more or less fancy search string). To all filtered runs I can then add/remove or modify results.

I don't understand the necessity to build a "RunCollection Modification Evaluator".

[epitzer]

Replying to abeham:

Why don't we just make this user interface only? All I assume you would need is to add/remove and probably modify results in several runs of a RunCollection. There can be a simple dialog that allows you to do this.

In my opinion the RunCollection Modification Evaluator is your simple user interface with the added benefit that you can save the modifications both for re-use with new runs and for documenting your changes to the embedded RunCollection.

I don't understand the necessity to build a "RunCollection Modification Evaluator" as a creatable item.

I think it is a good idea to remove it since it has now been embedded into the view selector of the RunCollection in r6664 and is not really needed anymore.

[abeham]

From a UI perspective that's not a dialog at all. It's a wrapper around a collection with a special view. However, I don't see the necessity to have both a RunCollection Modification Evaluator and a RunCollection. My question is this: Why can't the RunCollectionView do the modification? Why do we need a wrapper item with another view for that?

[epitzer]

Actually it has already been discussed with swagner and mkommend and is planned for integration into the RunCollection itself albeit not as a view-only mechanism but similar to the existing implementation.

[abeham]

Okay, the ticket is in reviewing state, I thought this would be released that way.

[epitzer]

Add RunCollectionGroupCreater for re-grouping a RunCollection (r6686)

[epitzer]

Extend calculator to support other data types, literals, stack manipulations and conditionals (r6687)

[epitzer]

Rename RunCollectionFuzzifier to RunCollectionDiscretizer (r6690)

This commit contains both version and a modified cloning method in the old fuzzifier to enable upgrading by cloning a fuzzifier in the GUI which will then become a discretizer.

[epitzer]

Remove obsolete RunCollectionFuzzifier (r6691)

[epitzer]

Integrate functionality of RunCollectionModificationEvaluator directly into RunCollection and its view. (r6693)

This update includes a modified RunCollectionModificationEvaluator that automatic migrates all modifies into the RunCollection.

[epitzer]

Remove obsolete RunCollectionModificationEvaluator (r6694)

[epitzer]

Fix spacing of modifiers list (r6695)

[epitzer]

Remove unnecessary reference to HeuristicLab.Parameters (r6697)

[abeham]

r6902

• fixed cloning when object has not been initialized properly

[epitzer]

r6903 Enable discretization by empirical distribution's quantiles.

[epitzer]

r6908 Fix quote handling and simplify tokenizer in Calculator and provide better error message.

[mkommend]

The implementation looks ok, but I am quite skeptical about the usefulness of several modifiers (e.g., RunCollectionSorter or the RunCollectionRunRemover).

Additionally it would be nice if all the source files are grouped into a folder.

[epitzer]

I agree about grouping the modifiers into a folder.

Here are some examples for the application of the questionable modifiers:

• When handling very large run collections it can become cumbersome to manually delete a lot of runs especially when handling complex criteria. For this purpose, the RunCollectionRemover can be combined with the filtering capabilities to remove only the required selection of runs.
• The RunCollectionSorter can, for example, be used to produce a certain order of e.g. mutation operators or problem names along an axis in a bubble chart.

[epitzer]

r7228: Move run collection modifiers into a separate folder