This implementation supplements the article
This code depends on the following packages:
- A
C++compiler supportingC++ 17, such as gcc or clang - CMake
>= 3.1 - Boost
>= 1.62 - GoogleTest
- SCIP
>= 7.0.0
The following commands build and test the code when executed in the root folder of the project:
mkdir buildcd buildcmake ..make
To build and run the unit tests following the build, execute the following
commands in the build/ folder:
make build_testsmake test
This code includes several benchmarks used to obtain the results in
the article mentioned above. To build the benchmarks following the
build, execute the following commands in the build/ folder:
make build_benchmarks
The benchmarks are stored as executables in the src/perf subfolder
of the build/ folder. Following the build of the benchmarks, you can
run all benchmarks and collect the results by executing
make collect
The results will be stored as .csv files in the src/perf subfolder
of the build folder. Alternatively, you can collect the results from
individual benchmarks using
make collect_<benchmark>_<size>
where size is either medium or large (again, see the article for
details). This will produce a file <benchmark>_<size>.csv in the
same folder as mentioned above.
Alternatively, you can run the benchmarks on their own in order to study the behavior of the solvers during the execution.
Beware: To obtain correct (i.e. comparable) timing results, ensure the following:
- Instruct
cmaketo compile optimized code by setting an appropriate build type. - Use Gurobi as a back end for SCIP.
- Ensure that SCIP itself is compiled in release mode (this should be the case by default)
The instances were generated as mentioned in the article, using a deterministic random number generator. Thus far, they are not persisted. If you need access to instance files, please contact us.