fix: inconsistences in individual comparison #386
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently there are few places in the code that try to achieve contradictory optimization targets: some operators treat "lesser" individuals as better, some treat "greater" ones as better.
This PR aims to clean things up and target only minimization ("lesser" individuals are "better").
Maximization can be achieved by implementing custom individual type with custom
Ordtrait implementation.TODO: Implement MinIndividual & MaxIndividual types in the ecrs library, so both types of optimalization are available for user out of the box.
Linked issues
Important implementation details