Skip to content

Should CMA_cmean become a versatile option? #351

@nikohansen

Description

@nikohansen

After

import cma
es = cma.CMAEvolutionStrategy(...)

the value of the CMA_cmean option is available via es.opts['CMA_cmean'] or es.sp.cmean. Do we have a use case where we would want to change the value dynamically via the cma_signals.in file?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions