You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For WLS licenses, compute servers, cluster managers it's necessary to set parameters on an empty environment before starting it (if, that is, you don't want to keep those parameters in the license file).
It would be helpful if there were a way to provide these parameters without calling C API functions directly. In gurobipy we use the following pattern to pass a mapping of parameters to be set before the environment is started:
@odow would it be reasonable to provide a Gurobi.Env constructor that takes a Dict? That would generalise the approach currently in Gurobi.jl of having separate constructors for memory limits and compute servers.
The text was updated successfully, but these errors were encountered:
From jump-dev/Gurobi_jll.jl#30.
For WLS licenses, compute servers, cluster managers it's necessary to set parameters on an empty environment before starting it (if, that is, you don't want to keep those parameters in the license file).
https://docs.gurobi.com/projects/optimizer/en/11.0/concepts/environments/configuration.html#empty-environment-example
It would be helpful if there were a way to provide these parameters without calling C API functions directly. In gurobipy we use the following pattern to pass a mapping of parameters to be set before the environment is started:
@odow would it be reasonable to provide a
Gurobi.Env
constructor that takes a Dict? That would generalise the approach currently in Gurobi.jl of having separate constructors for memory limits and compute servers.The text was updated successfully, but these errors were encountered: