Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 1 of Ticket #2792, comment 1


Ignore:
Timestamp:
05/31/17 16:45:12 (7 years ago)
Author:
abeham
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2792, comment 1

    initial v1  
    1 The cleanest solution in my opinion would be to change the parameter type from `OptionalConstrainedValueParameter<IManipulator>` to `ConstrainedValueParameter<IManipulator>`. We do have the mutation probability parameter which, if set to 0%, can produce the same configuration compared to selecting no mutation operator. Of course this would break API backwards compatibility.
     1The cleanest solution in my opinion would be to change the parameter type from `OptionalConstrainedValueParameter<IManipulator>` to `ConstrainedValueParameter<IManipulator>`. We do have the mutation probability parameter which, if set to 0%, can produce the same configuration compared to selecting no mutation operator. ~~Of course this would break API backwards compatibility.~~ (actually, the parameter was never exposed as an optional constrained value parameter, but as interface type)
    22
    33Another option would be to check in OnProblemChanged if the user loads a problem for the first time and then select a mutation operator by default. This is a bit more tricky, because the user could deliberately change mutation to "-" in which case we must not overrule with a default choice.