Repository navigation
feat(problems): IDTLZ1 and IDTLZ2 of Jain and Deb, as PlatEMO defines them, with reference fronts - #366
Merged
Conversation
… them, with reference fronts The inverted DTLZ1 and DTLZ2 (Jain and Deb, IEEE TEVC 18(4), 2014) are the usual test of how decomposition-based algorithms cope with an inverted front; VAMOS had neither (change request P3). They follow PlatEMO's IDTLZ1.m and IDTLZ2.m, registered as idtlz1 and idtlz2 in the DTLZ family, with n_obj configurable as for DTLZ: - IDTLZ1: f = (1 + g) / 2 - 0.5 (1 + g) s, with DTLZ1's g over the last k = n - M + 1 variables and its position shape s; n_var defaults to n_obj + 4, PlatEMO's D. - IDTLZ2: f = (1 + g) - (1 + g) s, with g = sum (x_i - 0.5)^2 and DTLZ2's shape; n_var defaults to n_obj + 9. The shape is PlatEMO's fliplr(cumprod([1, h])) .* [1, fliplr(t)], one helper for both. pymoo 0.6.2's InvertedDTLZ1 is the same function; pymoo has no inverted DTLZ2. The classes are not exported by vamos.problems. generate_reference_fronts.py writes idtlz1.2d, idtlz1.3d, idtlz2.2d and idtlz2.3d from PlatEMO's GetOptimum, (1 - w) / 2 and 1 - w / norm(w) for w on the unit simplex: 1000 points evenly spaced with two objectives (IDTLZ1's is DTLZ1's segment), and the 5050-point lattice of the DTLZ samples with three. Tests: the objectives equal PlatEMO's formulas, written out one objective at a time in the test, at fixed points with 2, 3 and 5 objectives, and (1 + g) / 2 - DTLZ1 and (1 + g) - DTLZ2; every point of the fronts is reached by a design with g = 0 and lies on its analytic front; registry dimensions, warnings, resolved fronts and an NSGA-II smoke run. 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-366-vamos-docs-preview.vamos-optimization.workers.dev Built from |
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Nov 19, 2026
Keeps both sides of #362 (DTLZ fronts with 4, 6 and 8 objectives) and of this branch (IDTLZ1 and IDTLZ2): the DTLZ rows of the problem table with their new fronts and the IDTLZ rows, both provenance rows, both generator functions and entries, and both sets of front residual checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Adds the inverted DTLZ problems IDTLZ1 and IDTLZ2 (
idtlz1,idtlz2) as PlatEMO defines them, with two- and three-objective reference fronts (change request P3). They are the usual test of how decomposition-based algorithms (NSGA-III, MOEA/D, RVEA) cope with an inverted front, and they were missing for the planned comparison of VAMOS with jMetal, jMetalPy, pymoo and PlatEMO.Source: H. Jain and K. Deb, "An Evolutionary Many-Objective Optimization Algorithm Using Reference-Point Based Nondominated Sorting Approach, Part II", IEEE TEVC 18(4):602–622, 2014, doi:10.1109/TEVC.2013.2281534, as implemented in PlatEMO's
Problems/Multi-objective optimization/DTLZ/IDTLZ1.mandIDTLZ2.m(BIMK/PlatEMO ate2d58cb, read from the repository; no code copied).src/vamos/foundation/problem/dtlz.py,IDTLZ1ProblemandIDTLZ2Problem, registered in the DTLZ family asidtlz1andidtlz2). Every objective is minimized, the variables lie in [0, 1], andn_objis configurable as for DTLZ.CalObjofIDTLZ1.m):f = (1 + g) / 2 - 0.5 (1 + g) s, with DTLZ1'sg = 100 (k + sum((x_i - 0.5)^2 - cos(20 pi (x_i - 0.5))))over the lastk = n - M + 1variables and DTLZ1's position shapes = fliplr(cumprod([1, x_1..x_{M-1}])) .* [1, 1 - x_{M-1}..1 - x_1]. PlatEMO'sD = M + 4, son_vardefaults ton_obj + 4(7 with three objectives).IDTLZ2.m):f = (1 + g) - (1 + g) s, withg = sum (x_i - 0.5)^2over the last variables and DTLZ2's shape (cos(x pi / 2)andsin(x pi / 2)).D = M + 9, son_vardefaults ton_obj + 9(12).kwarns andn_var < n_objraises.InvertedDTLZ1(0.5 (1 + g) - DTLZ1(x)) is the same function; pymoo has no inverted DTLZ2 and jMetal neither problem.vamos.problems; the problems are built by name (optimize("idtlz2", ...),make_problem_selection("idtlz1", n_obj=5)), as DTLZ5 and DTLZ6 are.idtlz1.2d.csv,idtlz1.3d.csv,idtlz2.2d.csvandidtlz2.3d.csv, written byexperiments/scripts/generate_reference_fronts.pyfrom PlatEMO'sGetOptimum:(1 - w) / 2(IDTLZ1) and1 - w / norm(w)(IDTLZ2) forwon the unit simplex. With two objectives, 1000 points spaced evenly along the front (IDTLZ1's is DTLZ1's segmentf1 + f2 = 0.5, and the file is the same asdtlz1.2d.csv); with three, the 5050-point lattice (H = 99) of the DTLZ1–DTLZ4 samples. The resolver finds them byn_obj(<key>.<M>d.csv, three objectives by default).docs/reference/problems.md: the registered count (260), the class list, two catalog rows, a paragraph on the definition and the shape of the fronts, the reference-front notes and a provenance row, and the source link, all marked Development after 1.4.0:.Not done: fronts with more objectives. They are as cheap and exact (the same formulas on a larger lattice), but the lattice convention for 4, 6 and 8 objectives arrives with the DTLZ fronts of #362; once both are merged,
idtlz1.<m>d/idtlz2.<m>dcan be generated with that lattice in a short follow-up, instead of a second copy of the same helper in this branch. IDTLZ3 and IDTLZ4 (also in PlatEMO) were not requested.Tests
tests/foundation/test_idtlz_problems.py:test_objectives_follow_platemos_formulas: IDTLZ1 and IDTLZ2 with 2, 3 and 5 objectives on fixed decision vectors (the bounds, the centre and five seeded points); the expected values are written out in the test from PlatEMO's formulas, one objective at a time withmath(f_iusesx_1 ... x_{M-i}and the complement ofx_{M-i+1}), not with the implementation's cumulative product;rtol = 1e-12.test_objectives_at_the_centre_of_the_box: hand-computed values,(0.375, 0.375, 0.25)for IDTLZ1 and(0.5, 0.5, 1 - sqrt(0.5))for IDTLZ2.test_idtlz_turns_dtlz_over: IDTLZ1 =(1 + g) / 2minus VAMOS's DTLZ1, and IDTLZ2 =(1 + g)minus DTLZ2, with 2, 3 and 6 objectives (pymoo's formulation).test_reference_front_points_are_reached_with_g_zero: every point of each packaged front is the image of a design with every distance variable at 0.5 (g = 0) within 1e-9; the points satisfysum(f) = (M - 1) / 2(IDTLZ1) or|1 - f| = 1(IDTLZ2) within 1e-12.n = M + 4,M + 9) with 3, 5 and 8 objectives, bounds, encoding, then_objoverride, the warning for a non-standardk, the error forn_var < n_obj, the resolved fronts (3D by default, 2D, none for 4), and an NSGA-II smoke run on both.tests/reference/test_reference_fronts.py: the four files lie on their analytic fronts within 1e-9 and have at least 1000 points, the mutual non-dominance test covers them, and the resolver test checks their names. The generic registry tests (test_problem_registry.py: default dimensions, the optimize contract) cover the two new keys.Compatibility
Additive: two new registered problems and four packaged files. No existing problem, front, default or public export changes.
Validation
Run from the worktree with
PYTHONPATHset to itssrc(vamos.__file__checked):python -m pytest -q -n 4 tests/foundation/test_idtlz_problems.py tests/reference/test_reference_fronts.py tests/foundation/test_problem_registry.py tests/foundation/test_problem_zoo.py tests/foundation/test_problem_evaluation_edge_cases.py tests/engine/test_algorithm_problem_matrix.py tests/foundation/test_problem_reference_values.py tests/ux/test_studio_catalog.py: 2016 passed, 18 skipped (existing skips).ruff checkandruff format --checkon the changed Python: clean.python -m compileall: clean.git diff --check: clean.python tools/typecheck.py --scope strictand--scope full: 0 diagnostics; ratchet new=0, increased=0.python tools/check_agent_docs.py: passed.python tools/check_repository_hygiene.pywith the new files staged: passed.python -m pytest -m "not slow" -n 4 -p no:cacheprovider -rfE: 10883 passed, 253 skipped, 9 xfailed, 1 failed,tests/experiment/test_cli_ablation.py::test_cli_ablation_runs_and_writes_variants, a known failure under xdist on Windows that also fails on untouchedmainand passes alone.python tools/health.py: all health checks passed.mkdocs build --strict: built.python experiments/scripts/generate_reference_fronts.py idtlz1.2d idtlz1.3d idtlz2.2d idtlz2.3d.Changelog entry
Added (under [Unreleased])
idtlz1andidtlz2with a configurable number of objectives (n_var = n_obj + 4andn_obj + 9by default), with reference fronts for two and three objectives (idtlz1.2d.csvtoidtlz2.3d.csv).Checklist
Architecture health
docs/dev/architecture_health.mdrelevant to this change.python tools/health.py.docs/dev/architecture_health.mdif I changed guardrails. (No guardrail changed.)Public API & dependencies
python tools/update_public_api_snapshot.pyif needed. (No public export changes: the problems are registered by name.)[project].dependencies.Behavior & tests
Changelog
CHANGELOG.mdis unchanged, and the changelog entry is under a "Changelog entry" heading in this description.Reports/retention
docs/dev/repository_hygiene.mdandpython tools/check_repository_hygiene.pypasses.🤖 Generated with Claude Code