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.

Sign up for GitHub

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

Jump to bottom

Allow sigma0 in EvolutionStrategyEmitter to be a vector #246

Closed
wants to merge 4 commits into from
Closed

Allow sigma0 in EvolutionStrategyEmitter to be a vector #246

wants to merge 4 commits into from

Conversation

itsdawei
Copy link
Collaborator

@itsdawei itsdawei commented Aug 10, 2022 •
edited by ld-ing

Description

Allow sigma0 in EvolutionStrategyEmitter to be a vector.

TODO

  • Figure out how to allow sigma to be a vector in CMA-ES.

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

@itsdawei itsdawei changed the title allow sigma0 to be a vector allow sigma0 in EvolutionStrategyEmitter to be a vector Aug 10, 2022
@itsdawei itsdawei changed the title allow sigma0 in EvolutionStrategyEmitter to be a vector Allow sigma0 in EvolutionStrategyEmitter to be a vector Aug 10, 2022
@itsdawei itsdawei requested a review from btjanaka August 10, 2022 23:16
@itsdawei itsdawei marked this pull request as ready for review August 10, 2022 23:16
@btjanaka
Copy link
Member

Closed as stale

@btjanaka btjanaka closed this May 31, 2024
@btjanaka btjanaka deleted the vector_sigma0_in_es_emitter branch May 31, 2024 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@btjanaka btjanaka Awaiting requested review from btjanaka

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@itsdawei @btjanaka