Repository navigation
feat(resources): DTLZ1-4 and DTLZ7 reference fronts with 4, 6 and 8 objectives - #362
Merged
Merged
Conversation
…bjectives
resolve_reference_front_path("dtlz2", None, n_obj=m) gave None for every
m other than 2 and 3, so IGD, IGD+, epsilon and the Hausdorff distance
had no automatic reference on many-objective DTLZ runs (VAMOS-Studio
request R4). VAMOS now packages its own samples with 4, 6 and 8
objectives, written by generate_reference_fronts.py:
- dtlz1.<m>d and dtlz2.<m>d: the largest Das-Dennis lattice with at most
10 000 points (H = 37, 13 and 8: 9880, 8568 and 6435 points), scaled
to sum(f) = 0.5 or projected onto the unit sphere. It is the lattice of
PlatEMO's reference fronts (UniformPoint(10000, M)), and jMetal's
DTLZ2-DTLZ4 files with those numbers of objectives hold the same
points in the same order.
- dtlz7.<m>d: the last objective is 2 (M - sum psi(f_i)) with
psi(t) = t (1 + sin(3 pi t)), which separates, so the front is the
product of the values of each f_i that no smaller value beats in psi;
a grid of such values, thinned to 5050 points.
DTLZ3 and DTLZ4 share DTLZ2's front, so their sample is DTLZ2's: the
resolver falls back from a problem without a file of its own to the
files of the problem whose front it shares, in either source, as it
already did for jMetal's files. Their two- and three-objective files
keep their names. Files with more than three objectives are written
with the shortest repr of each value, which reads back exactly. The
jmetal source keeps two and three objectives: jMetal's DTLZ1 and DTLZ7
files with 4, 6 and 8 objectives are sparse (183 to 370 points).
Tests: every point lies on the analytic front within 1e-9 and is the
image of a Pareto-optimal design as VAMOS evaluates it, and the resolver
returns dtlz<k>.<m>d.csv (DTLZ3 and DTLZ4: dtlz2.<m>d.csv) for 4, 6
and 8 objectives and nothing for DTLZ5, DTLZ6 or other numbers.
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-362-vamos-docs-preview.vamos-optimization.workers.dev Built from |
10 tasks done
NicolasRodriguezUribe
added a commit
that referenced
this pull request
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
Packages reference fronts of DTLZ1–DTLZ4 and DTLZ7 with 4, 6 and 8 objectives and makes the resolver find them by
n_obj(VAMOS-Studio change request R4). Until nowresolve_reference_front_path("dtlz2", None, n_obj=m)returnedNonefor everymother than 2 and 3, so IGD, IGD+, epsilon and the Hausdorff distance had no automatic reference on many-objective DTLZ runs. VAMOS-Studio ships its own copies of jMetal's files for these cases and can drop them.src/vamos/resources/reference_fronts/, the defaultvamossource), written byexperiments/scripts/generate_reference_fronts.py(dtlz1.4d…dtlz7.8d):dtlz1.{4,6,8}d.csvanddtlz2.{4,6,8}d.csv: the largest Das-Dennis simplex lattice with at most 10 000 points (H = 37, 13 and 8: 9880, 8568 and 6435 points), scaled tosum(f) = 0.5(DTLZ1) or projected onto the unit sphere (DTLZ2). This is the lattice of PlatEMO's reference fronts (PROBLEM.optimum = GetOptimum(10000)withUniformPoint's NBI method, which is single-layer for these M and also raises zeros to 1e-6). jMetal'sDTLZ2.{4,6,8}D.csv(its DTLZ3 and DTLZ4 files are the same bytes) hold exactly the same points in the same order (checked: maximum difference 0.0), so the default source gives the IGD-like values of jMetal and Evolver for DTLZ2–DTLZ4.dtlz7.{4,6,8}d.csv: on the front, the last objective is2 (M - sum psi(f_i))withpsi(t) = t (1 + sin(3 pi t)). It separates, so a point is Pareto-optimal exactly when eachf_iis a value that no smaller value beats inpsi; the front is the product of those values (taken from a grid of 200 001 points of [0, 1]). About 10^5 such combinations are thinned to 5050 points by farthest-point selection, as for the three-objective file.reprof each value (exact round trip), about half the size ofnp.savetxt's default format: 4.98 MB in all, the largest file 808 kB._SHARED_FRONTS). The existing two- and three-objective files keep their names and are still the ones resolved (dtlz3.csv,dtlz4.2d.csv,jmetal-dtlz2.3d.csv, ...).DTLZ1.4D.csvis 0.02486). Thejmetalsource therefore keeps two and three objectives, and it never falls back to VAMOS's files.docs/reference/problems.md: the DTLZ rows of the catalog table, the reference-front notes, a provenance row and a note on PlatEMO's and jMetal's files, all marked Development after 1.4.0:.Sources: jMetal
resources/referenceFronts/DTLZ{1,2,3,4,7}.{4,6,8}D.csv(local clone; identical at commit1e4b83cae6, the commit VAMOS already cites), compared but not copied; PlatEMOProblems/Multi-objective optimization/DTLZ/DTLZ1.m,DTLZ2.m,Algorithms/Utility functions/UniformPoint.mandProblems/PROBLEM.m(BIMK/PlatEMO ate2d58cb), read for the lattice convention only.Tests
tests/reference/test_reference_fronts.py:sum(f) = 0.5, the unit sphere, DTLZ7's last objective) and each file has at least 1000 points; the existing mutual non-dominance test covers the new files;test_many_objective_dtlz_fronts_are_reached_by_pareto_optimal_designs: for DTLZ1, DTLZ2, DTLZ3, DTLZ4 and DTLZ7 with 4, 6 and 8 objectives, a design rebuilt from each point of the resolved file, with the distance variables at their optimum, evaluates to that point within 1e-9 (DTLZ4 with itsalpha = 100);test_many_objective_dtlz_fronts_are_chosen_by_number_of_objectives:dtlz<k>.<m>d.csvfor DTLZ1, DTLZ2 and DTLZ7,dtlz2.<m>d.csvfor DTLZ3 and DTLZ4 (also for a key such asdtlz3.4d),Nonefor DTLZ5, DTLZ6 andm + 1objectives, no DTLZ3 or DTLZ4 many-objective files packaged, and the old names unchanged;tests/reference/test_jmetal_reference_fronts.py: thejmetalsource still givesNonefor DTLZ2 and DTLZ3 with more than three objectives, although VAMOS now has a front there.Compatibility
Additive. New packaged files: a lookup that returned
None(DTLZ1–DTLZ4 and DTLZ7 with 4, 6 or 8 objectives) now returns a front, so benchmarks, studies and Studio compute reference-front indicators for those runs where they skipped them before. Every lookup that returned a file returns the same file. No public API, schema or default changes.Validation
Run from the worktree with
PYTHONPATHset to itssrc(vamos.__file__checked):python -m pytest -q -n 4 tests/reference/test_reference_fronts.py tests/reference/test_jmetal_reference_fronts.py tests/foundation/test_packaging_data.py tests/ux/test_studio_catalog.py: 972 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: 10876 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 dtlz1.4d dtlz1.6d dtlz1.8d dtlz2.4d dtlz2.6d dtlz2.8d dtlz7.4d dtlz7.6d dtlz7.8d(about two minutes).Changelog entry
Added (under [Unreleased])
dtlz1.<m>d.csv,dtlz2.<m>d.csvanddtlz7.<m>d.csv), whichresolve_reference_front_pathfinds byn_obj; DTLZ3 and DTLZ4 resolve to DTLZ2's file. DTLZ1–DTLZ4 use the Das-Dennis lattice of PlatEMO's reference fronts, the points of jMetal's DTLZ2–DTLZ4 files with those numbers of objectives.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.)[project].dependencies.Behavior & tests
Nonenow return a front.)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