From 900263d739b4b27b33dbb217b15d11053343c61a Mon Sep 17 00:00:00 2001 From: Diego Alejandro Tejada Arango <12887482+datejada@users.noreply.github.com> Date: Tue, 12 Nov 2024 19:52:05 +0100 Subject: [PATCH] [docs] Add troubleshooting for long names in the solver (#1134) --- docs/src/getting_started/troubleshooting.md | 5 +++++ docs/src/how_to/change_the_solver.md | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/src/getting_started/troubleshooting.md b/docs/src/getting_started/troubleshooting.md index 899f7e00e7..51f23f9400 100644 --- a/docs/src/getting_started/troubleshooting.md +++ b/docs/src/getting_started/troubleshooting.md @@ -8,6 +8,11 @@ Have you created a new project? File > New project ## I get an error that the 'model' object is not defined in the database That tends to happen when you accidentally switched your input and output in the Run SpineOpt tool. +## Solver throws error `Name too long` +Variables and constraints names in SpineOpt sometimes can be longer than the maximum name length the solvers allow. If you get this error, we recommend using the solver parameters to run it ingnoring the names. For instance, Gurobi has the parameter `IgnoreNames` which allows to run without the names but returning the solution with the original names in the model. + +To setup the solver parameters you can look at the [How-to section](@ref how-to-change-solver) guide change the solver and define its parameters. + ## SpineOpt and SpineInterface are out of sync Some of the development of SpineOpt depends on the development of SpineInterface and vice versa. At some points in time that can create an incompatibility between the two. diff --git a/docs/src/how_to/change_the_solver.md b/docs/src/how_to/change_the_solver.md index 376dc83f50..8d2f18f994 100644 --- a/docs/src/how_to/change_the_solver.md +++ b/docs/src/how_to/change_the_solver.md @@ -1,4 +1,4 @@ -# How to change the solver +# [How to change the solver](@id how-to-change-solver) If you want to change the solver for your optimization problem in SpineOpt, here is some guidance: - You can change the solvers in your input datastore using the `db_lp_solver` and `db_mip_solver` parameter values of the `model` object.