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
Describe the bug
When the pricing solver returns no solution, Coluna gives an error message stating that the subproblem is infeasible. This is not necessarily the case. In case of stages, the princing solver may have run only its heuristic version which was unable to find any feasible solution. It may also be the case that all solutions have been fixed by reduced cost, meaning that no improving solution could be found for the master but not meaning that the whole subproblem is infeasible.
To Reproduce
TODO. Any example where the pricing solver returns no solution at some point. Using pricing stages would help.
Expected behavior
The same behavior as for the case that no solution returned by pricing solver could be inserted in the master: [ Info: No new column generated by the pricing problems.
Environment (please complete the following information):
Julia version 1.8.1
OS: MacOs
The text was updated successfully, but these errors were encountered:
Describe the bug
When the pricing solver returns no solution, Coluna gives an error message stating that the subproblem is infeasible. This is not necessarily the case. In case of stages, the princing solver may have run only its heuristic version which was unable to find any feasible solution. It may also be the case that all solutions have been fixed by reduced cost, meaning that no improving solution could be found for the master but not meaning that the whole subproblem is infeasible.
To Reproduce
TODO. Any example where the pricing solver returns no solution at some point. Using pricing stages would help.
Expected behavior
The same behavior as for the case that no solution returned by pricing solver could be inserted in the master:
[ Info: No new column generated by the pricing problems.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: