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

[FEATURE REQUEST] Implement Active CMA-ES #85

Open
tehqin opened this issue Feb 9, 2021 · 2 comments
Open

[FEATURE REQUEST] Implement Active CMA-ES #85

tehqin opened this issue Feb 9, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@tehqin
Copy link
Collaborator

tehqin commented Feb 9, 2021

Description

Currently, the CMA-ES implementation doesn't support negative weights. Implement this feature.

Note: some thought is required for filter-based selection.

Reference on active CMA-ES: https://hal.archives-ouvertes.fr/hal-00503250/document

@tehqin tehqin added the enhancement New feature or request label Feb 9, 2021
@btjanaka btjanaka added this to the v0.4.0 milestone Feb 9, 2021
@btjanaka btjanaka removed this from the v0.4.0 milestone Mar 10, 2021
@twoletters
Copy link

Does this relate to parameter "weight_rule" (either "truncation" or "active") in the CMA-ES-based emitters? I am trying to determine the implications of setting it to "active", but could not understand the limited documentation or make sense of the code. It looks like these emitters can generate negative values even with "weight_rule" set to "truncation", so what is the purpose of it?

@btjanaka
Copy link
Member

btjanaka commented Mar 6, 2022

@twoletters Correct, this relates to setting weight_rule="active". This would correspond to leveraging active CMA-ES https://hal.archives-ouvertes.fr/hal-00503250/document such that we update the covariance matrix based both on solutions that were inserted into the archive and solutions that were not inserted into the archive. Currently, weight_rule="active" is actually not implemented (I think you will eventually get an error if you use this option) -- hence why we raised this issue.

@btjanaka btjanaka self-assigned this Mar 7, 2022
@btjanaka btjanaka modified the milestone: v0.6.0 Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants