*Handle*- Handle to a solver state
*NumConstraints*- Number of constraints in the IIS
*NumVars*- Number of variables in the IIS
*ConstraintIdxs*- List of Indexes of the constraints in the IIS
*VarInfos*- List of Variable:Status pairs where Variables are the variables in the IIS and Status is the status of that variable

If the solver found that the problem was infeasible, this predicate will return an IIS (Irreducible Infeasible Subsystem or Irreducible Inconsistent Subsystem) for the problem, if supported by the solver. An IIS is a subset of the problem constraints and variables which defines an infeasible subproblem. It is usually irreducible in that any proper subset of the IIS is feasible. Finding an IIS allows the diagnostic analysis of the infeasible problem. Note that a problem may have more than one infeasibility, and thus more than one IIS, but this predicate only returns one.

NumConstraints and NumVars are the number of constraints and variables that are in the IIS. ConstraintIdxs is a list of the constraint indexes of the constraints in the IIS, these indexes are the indexes that are returned by lp_add_constraints/4 and lp_add_cutpool_constraints/4, and can also be used to retrieve the constraint with the constraints_norm(Indexes) and constraints(Indexes) options of eplex_get/2 and lp_get/3. VarInfos gives information for the variables in the IIS, and is a list of Var:Status pair, where Var is a variable in the IIS, and Status is its status. Status is a one character string, and can be:

- "b":
- if both bounds of the variable are involved in the infeasibility
- "u":
- if the upper bound of the variable is involved in the infeasibility
- "l":
- if the lower bound of the variable is involved in the infeasibility
- "x":
- if it is unknown which bound is involved in the infeasibility

An IIS is returned only if finding IIS is supported by the external solver. In addition, the solver may limit the type of problems and the information returned by the IIS, for example, finding an IIS may be limited to linear problems, and/or bound status information may be unavailable for the variables (hence the need for the "x" status). Consult the manual entry for infeasibility analyses for more detail.

The current solver state must be infeasible when this predicate is called to obtain the IIS. However, the default behaviour is to fail when the solver determines the problem to be infeasible. Therefore, this predicate must be called inside a user-defined infeasible handler, which can be defined during solver setup, or with eplex_set/2 or lp_set/3 after solver setup.

The IIS can only be obtained from the external solver before any change is made to the problem in the external solver. Unfortunately, certain eplex functionality does change the problem soon after solving the problem, before the user have any chance to obtain the IIS information, e.g. cutpool constraints or probing -- in the case of the cutpool constraints, the removal of the active cutpool constraints, and in the case of probing, To get around this problem, the cache_iis option can be used to instruct eplex to obtain the IIS information whenever the problem is determined to be infeasible, and this information is then cached by the eplex instance, so that when the user request the IIS information, it can be obtained from the cache.

For some external solvers, and for problems on the boundary between feasible and infeasible, it is possible that the routine that finds the IIS will conclude that the problem is feasible, even though it was considered infeasible when the problem was solved. In such cases, an empty IIS will be returned.

*(141) unimplemented functionality*- External solver does not support finding IIS