Gwyneth Butera

The issue reported here was fixed with Gurobi v13.0.

The issue was resolved by using a newer version of Gurobi.

This is a numerical issue that arises due to the combination of nondefault parameters and the inability of floating point numbers to represent the entire number line (see Real numbers are not real ...

We did not receive a model, so we were unable to investigate this any further.

The issue here was likely caused by some transient network issues from AWS. One thing you can try is increasing the ServerTimeout parameter from the default 60 seconds. This will give your client m...

Here, the user resolved the issue by making the problem less sensitive to numeric problems.

The requested information was provided to the user in a Support Request.

Typically, the root cause of problems like this are that there are some significant numerical issues in the model. Generally speaking, a model with numerical issues can produce inconsistent or unex...

We sent the following to the user which we hope resolvedthe issue.Steps which have helped users with similar issues in the past include: re-running “library(gurobi)” rebooting the computer re-insta...

This issue was investigated and not reproduced. It is likely that the crash is caused by a hardware issue on your machine, e.g., unstable memory. We suggest that you test the memory. A useful way t...