Instance Formats for Mathematical Optimization Models
Bibliographic record
Abstract
Abstract In order to use a piece of software—optimization solver, simulation package, model analyzer, and so on—on a mathematical model, it is necessary to communicate a model instance to the software. Additionally, such software typically accepts options to specify tolerances, set algorithmic parameters, and so on. Finally, the software must communicate the result instance back to the user. In this article we focus on optimization solvers and review existing formats for optimization instances, solver option instances and result instances, and describe the research issues involved in designing these instance formats.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.009 | 0.033 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.003 | 0.006 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.011 | 0.015 |
| Open science | 0.006 | 0.004 |
| Research integrity | 0.002 | 0.007 |
| Insufficient payload (model declined to judge) | 0.021 | 0.007 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".