Repository navigation
feat(agemoea): AGE-MOEA-II as AGE-MOEA's variant, checked against jMetal - #359
Merged
Merged
Conversation
AGEMOEAConfig gains variant ("agemoea", the default, or "agemoea_ii"), with
its builder method. AGE-MOEA-II (Panichella, GECCO 2022) changes two steps of
the first-front score, the two that jMetal's AGEMOEA2EnvironmentalSelection
overrides: the exponent p, found by Newton-Raphson from the non-extreme point
nearest to the ideal point, and the diversity, measured with geodesic
distances through the projected midpoints. Everything else is AGE-MOEA's.
tools/agemoea2_reference_values.py and tools/jmetal_values/AgeMoea2Values.java
record jMetal's exponents, distances and survival scores (main at 46fb0a61f7)
in tests/engine/data/agemoea2_jmetal_values.json; the exponents and distances
agree on every case, and the scores wherever AGE-MOEA's shared steps agree
with jMetal's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…acement Every AGE-MOEA space (real, constrained, binary, integer, permutation and mixed) offers replacement, Evolver's choice between AGE-MOEA's survival (agemoea, the default) and AGE-MOEA-II's (agemoea_ii, Evolver's agemoeaII). The bridge sets AGEMOEAConfig.variant, and the name table exchanges the parameter and its values with Evolver. The default still builds the configuration of VAMOS 1.4.0. agemoea_constrained now has more than 100 000 discrete combinations, so its exhaustive build moves to the slow tier and the fast tier samples it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
VAMOS documentation previewhttps://pr-359-vamos-docs-preview.vamos-optimization.workers.dev Built from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
VAMOS runs AGE-MOEA-II (Panichella, GECCO 2022, doi:10.1145/3512290.3528732) as a variant of AGE-MOEA, as Evolver does:
AGEMOEAConfig.builder().variant("agemoea_ii"), andreplacement: agemoea_iiin the tuning spaces (Evolver'sreplacement: agemoeaII). The default,"agemoea", is unchanged, so every existing configuration and seeded run gives the same result.The reason is practical: the reference fronts of the CRE and RCM suites are being regenerated with VAMOS, and their algorithm portfolio, until now run with Evolver, includes AGE-MOEA-II with CDP and with the epsilon-constrained method.
Changes
Survival (
agemoea/geometry.py). AGE-MOEA-II changes two steps of the first-front score. They are the two that jMetal'sAGEMOEA2EnvironmentalSelection, written by the author, overrides:p: Newton-Raphson fromp = 1(precision 0.001, at most 100 steps) onlog(sum |a_i|^p), from the non-extreme point nearest to the ideal point (AGE-MOEA takes the point nearest to the diagonal and a closed form);L_pmanifold. Both points and their midpoint are projected on it, and the distance is the length of the path through the projected midpoint.Everything else is AGE-MOEA's, with that
p: the extreme points, the normalization, the later fronts, the tournament, the constraint handling (feasibility and the six techniques) and the numba greedy kernel.Configuration.
AGEMOEAConfig.variantis a field added after 1.0, so it goes last, and the builder gainsvariant(...). An unknown name raisesValueError.AGEMOEAVariant,AGEMOEA_VARIANTSandresolve_agemoea_variantlive inconfig/types.py.Tuning (second commit):
replacement(agemoea, the default, oragemoea_ii);variant;parameter_names.pyexchanges the parameter and the valueagemoeaIIwith Evolver;tools/update_parameter_spaces.py.agemoea_constrainednow passes 100 000 discrete combinations, so it joins_LARGE_SPACES: the exhaustive build runs in the slow tier (it passes) and the fast tier samples it.Docs: the AGE-MOEA page (setting and reference), an "AGE-MOEA-II" section in the algorithm reference, and the tuning guide (the AGE-MOEA spaces and the name table). All carry the "Development after 1.4.0" marker.
Checked against jMetal
tools/agemoea2_reference_values.pyandtools/jmetal_values/AgeMoea2Values.javafollow the pattern of the MOEA/D criteria (#258). They writetests/engine/data/agemoea2_jmetal_values.jsonfrom jMetal'smainat46fb0a61f7, the commit pinned for the MOEA/D fixture, with the AGE-MOEA selection classes compiled from that commit and placed first on the classpath. There are 119 cases:L_qspheres withqfrom 0.4 to 6, and include zero coordinates and coordinates above 1.Declared departures (also in the docs):
pis capped at 20, as in AGE-MOEA and in pymoo's AGE-MOEA-II; jMetal does not cap it.0.95 < p < 1.05; VAMOS, like jMetal, always goes through the midpoint. Both coincide atp = 1.A behavioural check, not part of the tests. Hypervolume over 10 seeds, population 100, NumPy engine, reference point 1.1, against pymoo 0.6.1.6's
AGEMOEA2with the same operators:agemoeaagemoea_iiAGEMOEA2VAMOS's AGE-MOEA-II is within seed variation of pymoo's. On DTLZ2 both show the same lower mean and larger spread than AGE-MOEA.
Validation
Run on Windows 11 with Python 3.12, following
AGENTS.md:python tools/typecheck.py --scope strictand--scope fullpass, with 0 diagnostics and ratchet new=0, in a.[dev]-only environment withconstraints/ci.txt.python tools/health.py: all health checks passed;mkdocs build --strict: passes;python tools/check_agent_docs.py: passes;python tools/update_parameter_spaces.py --check: the grammars are valid and the snapshot is current.ruff check src/vamos tests,ruff format --checkon the changed files,compileallon the changed files andgit diff --checkall pass.pytest -m "not slow" -n 6: 10 839 passed, 2 failed. Both are fixed in this branch:replacement;tests/experiment/test_cli_ablation.py::test_cli_ablation_runs_and_writes_variantsis pre-existing. It fails the same way (SystemExit: 2) on an untouchedorigin/mainunder-n 6, and passes alone. It is a MOEA/D ablation, which this branch does not touch.pytest -m slow, without the exhaustive combination builds: 70 passed and 1 failure, the_LARGE_SPACESthreshold above, now fixed.tests/engine/test_agemoea_ii.py: 88 tests.Changelog entry
[Unreleased] — Added
AGEMOEAConfig.builder().variant("agemoea_ii"), andreplacement: agemoea_iiin every AGE-MOEA tuning space (Evolver'sreplacement: agemoeaII);AGEMOEA2EnvironmentalSelection;"agemoea", is unchanged.🤖 Generated with Claude Code