Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 4 of Ticket #1833


Ignore:
Timestamp:
08/01/13 15:40:57 (11 years ago)
Author:
abeham
Comment:

r9838: changed parameter collection for runs, so that the "checked" information is available.

There will be problems should an operator ever contain a value parameter called "Checked", that is to be collected and that operator is included in a checked multi operator. Currently, the string "Checked" doesn't appear in our solution anywhere.

Overall, I'm not that happy with how MultiOperators are collected. Keys such as "Crossover.0" are not helpful in the run analysis at all. Using the name of the operator (e.g. OrderCrossover2) instead of the parameter (e.g. 0) would make more sense, but unfortunately could lead to clashes when the same operator is added to a CheckedMultiOperator multiple times (e.g. in different parameterizations). Also the way the probabilities are collected (as array) is not suitable for analysis. What do you think?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1833

    • Property Owner changed from swagner to gkronber
    • Property Status changed from new to reviewing
    • Property Milestone changed from HeuristicLab 3.3.7 to HeuristicLab 3.3.9
  • Ticket #1833 – Description

    initial v4  
    1 The information which operator is checked in a `CheckedMultiOperator<T>` is lost in the run as the checked information is not collected.
     1The information which operator is checked in a `CheckedMultiOperator<T>` is lost in the run as the checked information is not collected. Related to #1695 that changed parameter collection.