Eli Towle

Since we did not receive a model file, we're unfortunately unable to investigate this behavior further and will close this thread. Please feel free to open a new post with a reproducible example if...

This issue was fixed in Gurobi 12.0.3. Thanks for letting us know about it.

Did you manually add the - 94 to the objective function? Gurobi's LP reader interprets this as a variable named 94 with objective coefficient -1. This should instead be written as - 94 Constant wit...

Can you try passing Pyomo's \(\texttt{symbolic_solver_labels}\) setting like this instead?opt = SolverFactory("gurobi") results = opt.solve( model, tee=True, options={"SolFiles": "foo"}, symbol...

The variable names in the .sol files match the names Pyomo gives Gurobi when it is creating the Gurobi model. You need to direct Pyomo to preserve the names of the Pyomo components when passing the...

The machine Gurobi is running on is having trouble communicating with our WLS license servers. It could be a DNS or firewall issue. Can you ask the HPC system administrators to investigate why mach...

The behavior you expect is how ObjNAbsTol behaves for multi-objective MIPs. However, this attribute behaves differently for multi-objective LPs. From the documentation:Objective degradations are ha...

Thanks again for reporting this issue. This incorrect declaration of infeasibility/unboundedness is fixed in the recently released Gurobi version 12.0.1.

Does the latest version of Gurobi (12.0.0) also fail to find one of the optimal solutions when setting PoolSearchMode to 2? If so, can you please write out an MPS model file and post the file conte...

Thanks for reporting this issue. I'll open a support ticket on your behalf so we can investigate further.