# How to debug most errors during solving¶

Here I will put all the main questions and advice from years of solving and helping other solve problems with PuLP. Additional answers can be added via a PR.

## Giving feedback and asking for help¶

The two ways one can ask for help or report a problem are:

The PuLP Github Discussions page: https://github.com/coin-or/pulp/discussions

Stack Overflow pulp tag: https://stackoverflow.com/questions/tagged/pulp

Of course, the questions /problems (and their answers/ solutions) already in these sites can (and often do) include sufficient information to solve or understand the issue. So a good look at old questions and issues is highly recommended.

Several things need to be taken into account while asking for help, some of them are common to any project, other are particular to PuLP. General pointers (that are nonetheless, very important):

Always submit a minimum reproducible example (how to here).

Check this video on how to ask questions. Although aimed to another programming language, the message and recommendations are very good.

Now, specifically to PuLP:

Pass the msg=1 argument to the solver, i.e., prob.solve(PULP_CBC_CMD(msg=1)). This will give you more information on the error. Share this information when asking for help.

If possible, share an export version of the model. Check here how to export one.

Alternatively, share a mps version of your model. To produce one, use

`writeMPS()`

.

Other information that is also useful:

Version of pulp.

How did you install pulp (via pypi, or from github).

What operating system was used.

The version of the solver being used (e.g., CPLEX 12.8).

## Error while trying to execute cbc.exe¶

The complete message is usually something like pulp.solvers.PulpSolverError: Pulp: Error while trying to execute PATH_TO_CBC/cbc.exe.

The default solver is CBC and is run via the command line.

First of all, pass the msg=1 argument to the solver, to get more information.

**Check the precision of the numbers**. If you have very big numbers (with a high precision), this generally causes problems with solvers. For example, never use a parameter that is 100000000000 inside your problem. Specially if you then have another one that has 1200.09123642123. If you do not need decimals, round your values when building the model.**Duplicated variables / constraints**. If you have variables that have the same coefficients in*all*constraints and in the objective function, this is an issue. Also, if you have two constraints that have exactly the same variables and coefficients.**Memory issues**. Sometimes your pc runs out of memory. Check if this is the case.**python32 vs python64**. Sometimes you’re using the 32-bit version of python, even if your pc is 64-bit. Try to always use the 64-bit if possible, since it handles more memory.**Generate an mps file with PuLP**and pass it to the cbc.exe executable directly like so.

```
cbc.exe mpsfile.mps
```

And see what message you get.

Finally, sometimes you may want to try PuLP with a more recent version of CBC. To do this, download the CBC binary and pass the path to it to PuLP.

## Infeasible problems¶

Add slack variables. As described in this SO post.

Take out constraints and see if the problem becomes feasible.

Generate lp file

`writeLP()`

for the problem and open it with a text editor to see if the constraints are correctly built.Check the solver logs to additional message from the solver regarding the constraint or variable involved. The log can be seen by giving msg= as argument or exported with the logPath argument in some cases.