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
I have confirmed this bug exists on the lastest release of Linopy.
I have confirmed this bug exists on the current master branch of Linopy.
Issue Description
Using gurobipy with a non-academic license leads to issues with the license not being freed after the model was solved.
I would
Im not finished investigating the issue, but it probably arises from not closing the gp.Model before closing the gp.Env
The gurobipy website says the following:
It is good practice to use the with keyword when dealing with environment (and model) objects. That way the resources tied to these objects are properly released even if an exception is raised at some point. The following example illustrates two typical use patterns.
I would expect to be able to solve a linty model in a new python thread/console, after the model in another console finished.
This is not possible, due to the license not being released properly.
Version Checks (indicate both or one)
I have confirmed this bug exists on the lastest release of Linopy.
I have confirmed this bug exists on the current
master
branch of Linopy.Issue Description
Using gurobipy with a non-academic license leads to issues with the license not being freed after the model was solved.
I would
Im not finished investigating the issue, but it probably arises from not closing the gp.Model before closing the gp.Env
The gurobipy website says the following:
I will correct this and open a PR.
Is there any reason to not close the model after the solve? Maybe because of IIS calculation?
Reproducible Example
Expected Behavior
I would expect to be able to solve a linty model in a new python thread/console, after the model in another console finished.
This is not possible, due to the license not being released properly.
Installed Versions
The text was updated successfully, but these errors were encountered: