I get this output :"Solver stopped prematurely. No integer feasible point found" in intlinprog function

I got this output:" Solver stopped prematurely. No integer feasible point found." when using intlinprog function to solve a linear optimization problem. The codes has been attached.

[梦娇 何]

Have you solved it yet? I have the same problem.

Answer 1

[Aravind]

Hi @sahar,

The message "Solver stopped prematurely. No integer feasible point found" suggests that the “intlinprog” function was unable to find a solution that meets all the integer constraints of your linear optimization problem. You can try the following steps to troubleshoot and potentially resolve this issue:

1. Check Constraints: Ensure your constraints are correctly defined and that a feasible region exists. Overly restrictive constraints are a common cause of infeasibility.
2. Initial Solution: If possible, provide an initial feasible solution or a good starting point to help the solver converge to a solution.
3. Relax Constraints: Temporarily relax some constraints to see if the solver can find a solution. If successful, gradually reintroduce the constraints to identify the one causing infeasibility.
4. Increase Iterations or Time Limit: The solver might need more time or iterations to find a feasible solution. Consider increasing the “MaxTime” or “LPMaxIterations” options in the solver settings.
5. Review Variable Bounds: Make sure the bounds on your variables are correctly set and not overly restrictive.
6. Scaling Issues: Poor scaling can lead to numerical difficulties. Try normalizing your data if you suspect scaling might be an issue.
7. Review Problem Formulation: Double-check your problem formulation to ensure it accurately represents what you intend to solve.

Additionally, reviewing the documentation of the “intlinprog” function at https://www.mathworks.com/help/releases/R2022a/optim/ug/intlinprog.html can be helpful to understand its limitations and assumptions. Certain problem types or sizes may exceed the solver's capabilities, or specific settings might be needed for optimal performance.

I hope this helps address your query.