Why are some properly formulated constraints missing from the Constraints Table in Solver’s Sensitivity Reports?
There could be several reasons why some properly formulated constraints may be missing from the Constraints Table in Solver's Sensitivity Reports.
1. Feasibility: The missing constraints could be infeasible, meaning that there is no feasible solution that satisfies all the constraints. In such cases, Solver may not include these constraints in the report because they are not relevant to finding an optimal solution.
2. Not binding: Solver only includes constraints that are binding or actively affecting the solution. If a constraint is not binding, meaning it does not affect the optimal solution, it may not appear in the Constraints Table.
3. Linear Programming only: Solver's Sensitivity Reports are primarily designed for linear programming problems. If the missing constraints are part of a non-linear programming problem or include non-linear elements such as integer or binary requirements, they may not be included in the Constraints Table.
4. Multiple optimal solutions: In cases where there are multiple optimal solutions, Solver may only report on a subset of the available solutions. Therefore, some constraints may not be included in the Constraints Table.
It is important to note that the exact reason for missing constraints may vary depending on the specific optimization problem and the Solver tool being used.