An LP matrix generator for GMPL (MathProg) and (by extension) AMPL.
Can be used in two ways:
- Compile an MPS file for solving elsewhere
- Solve directly with the HiGHS integration, no other binary needed
Currently a work-in-progress.
It works for a subset of GMPL (specifically the subset required to run Osemosys). See Known limitations section below.
There are a number of examples of varying complexity in the examples/ directory.
Developed by and for Climate Compatible Growth.
cargo install mosoxbrew tap carderne/mosox-tap
brew install mosoxBinaries are built for a small set of systems and architectures. Available to download (compressed) from the Releases page. Please choose the appropriate archive.
Usage overview:
mosox help
MathProg Translation Kit
Usage: mosox <COMMAND>
Commands:
compile Load and output to MPS
solve Solve with HiGHS
normalize Normalize an MPS file for diffing
compare Compare two normalized MPS files with epsilon tolerance
help Print this message or the help of the given subcommand(s)
Options:
-h, --help Print help
-V, --version Print versionCompile MPS for one of the examples in this repo. Output will be written to to the provided file:
mosox compile examples/basic/model.mod -o output.mpsOr an example with a separate data file, piping MPS to a file:
mosox compile examples/sets/model.mod examples/sets/data.dat -o output.mpsResults will be saved to the output file:
mosox solve examples/basic/model.mod -o output.txt
# Loading model from model.mod
# Generating matrix
# Matrix compiled in 666.625µs
# Matrix: 3 rows, 2 cols, 6 nonzero
# Solving matrix with HiGHS
# Solved in 1.939083ms
# Objective value: 2200
# Results output to f.txtPlease install cargo-make:
cargo install cargo-makeThe most useful dev commands are listed in Makefile.toml.
You can view available commands by running cargo make.
cargo make fmt
cargo make lintIn addition to other tests, this will run mosox against all the examples under examples/ and confirm that the output is identical to the existing MPS files.
cargo make testThis will additionally run a regression test against examples/osemosys_large if present.
cargo make testlargeRun performance benchmarks across all examples (except osemosys_large):
cargo make benchInclude osemosys_large (requires the example to be present):
cargo make benchlargeRun with glpsol comparison (requires glpsol on PATH):
cargo make benchglpsolNote that some of the performance advantage over glpsol may be caused by the limitations enumerated below.
| Example | rows/cols/nonzero | N | glpsol | mosox | Speedup |
|---|---|---|---|---|---|
| osemosys_small | 6k/7k/15k | 50 | 68ms | 17ms | 4.0x |
| osemosys_atlantis | 180k/230k/510k | 10 | 2.4s | 373ms | 6.5x |
| osemosys_large | 1M/5M/12M | 4 | 130s | 20s | 6.5x |
The matrix generator uses very roughly 2,000 bytes per non-zero. This is a significant overhead over the 12 bytes bytes per non-zero that would be needed in a format like CSC. However, as the table below shows, the matrix generator will rarely (if ever) use more memory than the solver.
| Example | Mosox matrix | Glpsol matrix | HiGHS solver | Glpsol solver |
|---|---|---|---|---|
| osemosys_small | 13 MB | 12 MB | 24 MB | 16 MB |
| osemosys_atlantis | 244 MB | 287 MB | 386 MB | 416 MB |
| osemosys_large | 5 GB | 5.6 GB | 6.5 GB | ? |
This list of limitations is made with reference to the GNU MathProg Language Reference which can be viewed here or downloaded from the original here.
It is intended that all of these will ultimately be supported, and most of them are "trivial" to add.
- The following functions:
abs,atan,ceil,cos,exp,floor,gmtime,length,log,prod,round,sin,sqrt,str2time,trunc,Irand224,Uniform,Normal.
- These arithmetic operators:
less,div,mod - These symbolic operators:
&(string concatenation) - These set expressions: conditional set expressions
- These set operators:
diff,symdiff. - These logical iterated expressions:
forall,exists - These logical operators:
not
within(parsed, not enforced)dimen(parsed, not enforced)
- Relational condition (parsed, not enforced)
- Superset expression (parsed, not enforced)
- Type specifier (integer, binary, symbolic) (parsed, not enforced)
- Bounds specified as expressions (currently only constant accepted)
- Multiple expressions (comma-separated)
Support for these statements is not planned (results should instead be parsed from the solver output): display, printf, for.