Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Q&A: why default algorithms do not beat commercial solver ? #592

Merged
merged 4 commits into from
Sep 2, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/make.jl
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,8 @@ makedocs(
"Configuration" => joinpath("man", "config.md"),
"Algorithms" => joinpath("man", "algorithm.md"),
"Callbacks" => joinpath("man", "callbacks.md")
]
],
"Q&A" => "qa.md"
]
)

Expand Down
22 changes: 22 additions & 0 deletions docs/src/qa.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Question & Answer

#### Default algorithms of Coluna do not beat the commercial solver I usually use. Is it normal ?

Yes it is.

Solvers such as Gurobi, Cplex ... are handy powerful black-box tools.
They can run a very efficient presolve step to simplify the formulation,
automatically apply lots of valid inequalities (such as MIR or cover cuts),
choose good branching strategies, or also run heuristics.
However, when your formulation reaches a certain size,
commercial solvers may run for hours without finding anything.
This is the point where you may want to decompose your formulation.

Coluna is a framework not a solver.
It provides algorithms to try column generation on your problem very easily.
Then, you can devise your own branch-cut-and-price algorithm on top of Coluna's algorithms.
to scale up and hopefully beats the commercial solver.

To start customizing Coluna for your own problem,
you can [separate valid inequalities](../user/callbacks/#Separation-callbacks)
or [call your own algorithm that optimizes subproblems](../user/callbacks/#Pricing-callback).