Repository navigation
Output and Logs
Lemutisme edited this page Nov 7, 2026
·
1 revision
A log of the command-line runner contains, in order:
- The command line (
#CMD ...) in the released logs. - A
Configurations:block. It lists the argument defaults, not the values in effect; the values in effect are those of the preset or YAML file (Configuration). - Progress lines of the stages that run: the incumbent search, lower-bound computation and branching. Lines starting with
[Op]are the work ledger of a stage, with the timet, stage times, and the change in the dual (dD) and primal (dP) values. - The final lines:
Primal Solution ..., Dual Solution ...,Solution gap: ...,[best-primal] objective=... x=[...], andproblem_name=<name> status=<status> success=<bool>(Quick Start).
logs/ holds one archive per solver, with one log per instance (505 each):
| Path | Content |
|---|---|
logs/<solver>.tar.xz |
final 180 s runs of the 12 AMPL baselines |
logs/gear.tar.xz |
GEAR, 180 s, one NVIDIA RTX 5090 |
logs/gear_results.tsv |
GEAR per instance: certified, status, P and D in the model's sense, relative gap, time |
logs/configs/int3p_crownmerge.yaml |
the GEAR configuration of these runs |
logs/MANIFEST.tsv |
solver, family, instance, bytes and sha256 of every log |
logs/SHA256SUMS |
checksums of the archives, the configuration, gear_results.tsv and the manifest |
Archives unpack to <solver>/<family>/<instance>.log.
With --result_json <file>, nlp_example.py and gear.cli solve write the result as JSON; the Python API produces the same record with Result.to_json(). Fields are listed in Python API.
| Column | Meaning |
|---|---|
family, instance
|
Instance key |
sense |
minimize or maximize
|
certified |
1 if solved under the scoring rule |
status |
certified, certified infeasible, unknown or no status
|
P, D
|
Primal value and certified bound in the sense of the model |
relative_gap |
`(P - D) / max(1, |
time_s |
Wall-clock seconds |