Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set novelty to the threshold when ProximityArchive is empty #479

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

btjanaka
Copy link
Member

@btjanaka btjanaka commented Jul 2, 2024

Description

Previously, we returned inf novelty when the ProximityArchive was empty. However, this can cause issues in code that expects ranking values to be finite values, such as in CMAEvolutionStrategy.check_stop. Functionally, this value works just as well as inf because it shows that the solutions had enough novelty to be added to the archive. Strictly speaking, since the archive is empty in this case, the novelty is undefined, so there are many values that would work.

Status

  • I have read the guidelines in
    CONTRIBUTING.md
  • I have formatted my code using yapf
  • I have tested my code by running pytest
  • I have linted my code with pylint
  • I have added a one-line description of my change to the changelog in
    HISTORY.md
  • This PR is ready to go

@btjanaka btjanaka merged commit eb5471e into master Jul 2, 2024
17 checks passed
@btjanaka btjanaka deleted the empty-novelty branch July 2, 2024 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant