Skip to content

Developers ​

How the collection is built, tested and documented. The procedures live next to the code they describe, in READMEs, so that they change with it; this page says where to find them.

The principle ​

What can be computed is generated or checked, never maintained by hand. The availability of a problem in a modeling is the presence of its file; the features are computed from the model; the reference objectives from the results of the crons; the documentation pages from the files of each problem. A test checks that no list of problems is written by hand.

Where to read ​

I want toRead
add a problem, or a modelingext/README.md
run the tests, or add onetest/README.md
know what the crons do, and handle the issues they open.github/workflows/README.md
compute the reference objectives againtools/references/README.md
know the NLP of each JuMP schemeJuMP schemes
follow the conventions of the ecosystemct-conventions and AGENTS.md

Three kinds of tests ​

KindWhenFails on
Does not breakevery pull request, small grid, a few iterationsan exception or a non-finite objective
Same NLPevery pull request, no solvetwo modelings that give different NLPs
Convergencethe weekly crons, or on demand (label test convergence)nothing: the solver status and the gap to the reference are reported

The convergence results feed the reference objectives and the problem pages, and the Status page shows the latest reports.

The documentation ​

The problem pages, the Status page and the API Reference are generated at each build; docs/modelings.jl holds what the pages need to know about each modeling. The build solves nothing for the problem pages: their results come from the crons. To build it locally:

bash
julia --project=docs docs/make.jl
npx serve docs/build/1 --listen 5173

make.jl clears docs/build/ before it builds, so a server on it shows nothing until the build ends. To keep the previous site browsable meanwhile, serve the preview once and rebuild through it; the preview is replaced only when a build succeeds:

bash
docs/preview.sh serve          # http://localhost:5175, in its own terminal
docs/preview.sh build          # after each change; prints "preview updated"