Skip to content

CCMO configuration

Configure ccmo through vamos.algorithms.CCMOConfig. This page is the parameter reference, not a tutorial about the algorithm; see CCMO for the algorithm, its variations and its budget rule.

New in VAMOS 1.2.0. The 1.0 compatibility baseline does not cover CCMO and CCMOConfig yet.

from vamos.algorithms import CCMOConfig

Configuration overview · Algorithm contracts · Optimization

CCMOConfig dataclass

Bases: _SerializableConfig

Configuration of CCMO (Tian et al., 2021).

pop_size is the size of each of the two populations, at least 2. The crossover selects the variation: ("de", {"cr": ..., "f": ...}) the DE variation (real variables only), any two-parent crossover the GA variation, which keeps one child per pair of parents.

default(pop_size=None, n_var=None, encoding=None) classmethod

Create the default CCMO configuration: that of the paper and of jMetal's port.

pop_size=None means 100. Real variables use the GA variation with SBX (probability 1.0, distribution index 20) and polynomial mutation (probability 1/n, distribution index 20). Discrete and mixed encoding values take their crossover and mutation from the shared encoding table.

Builder methods

Use CCMOConfig.builder() to obtain the fluent builder; do not import the private builder class directly. The methods below are generated from that returned object, so their signatures are not maintained as a second manual parameter table.

Bases: _ConfigBuilderState, _PopSizeBuilder, _CrossoverBuilder, _MutationBuilder, _RepairBuilder, _InitializerBuilder, _ConstraintModeBuilder, _ResultArchiveBuilder

Fluent builder for CCMO configs.

Examples: cfg = CCMOConfig.default(n_var=15) cfg = CCMOConfig.builder().pop_size(100).crossover("de", cr=1.0, f=0.5).mutation("pm", prob="1/n", eta=20.0).build()