More than the algorithm, there are a lot of interfaces, classes which don't have any sort of documentation. How are they executed, their execution order, parameters etc.
Algorithm can be understood from the books and the white papers, but understanding someone else's library without document increases development time exponentially.
The library is excellent, but without proper documentation (c

The current readme is, hum, quite sparse on information. Considering this is the entry point for the project on GitHub, it should be improved to contain more high-level information and pointers to other resources. What should be added:

• supported problem types
• more detail on features
• supported routing engines
• the kind of tests we have in place (CI builds, runs on various benchmarks)

Looks like v6.7.1 of or-tools has been released. We're currently only linking against 6.0 (from May, 2017). We should update, and see if there are new knobs we can expose.

The function Cut::getCuts uses the function Cut::createIloRange to translate vector<CutReturn> into vector<IloRange> such that the valid inequalities can be used by CPLEX. We should also add a function that translates our CutReturn objects into objects that can be used by Gurobi.

Do not forget to update the wiki page that describes how to use another solver as this now explains how t