MIP Solution Enumerator errors
- 869 Soln is deleted and no longer available: <solution_id>
-
The user has attempted to access information for the solution with id <solution_id> but the solution seems to have been deleted.
- 870 Soln id does not exist: <solution_id>
-
The user has attempted to access information for the solution with id <solution_id> but the id is for a solution that has not yet been encountered.
- 871 Unrecoverable memory allocation failure
-
A call made by the user failed because of a memory allocation failure.
- 874 Unrecognized solution metric id: <metric_id>
-
The metric id <metric_id> passed by the user is unrecognized.
- 875 No solutions available
-
The user is attempting to access information about the stored solutions but the solution storage is empty.
- 876 Enumerator is already running
-
The user is attempting to run the enumeration while the enumeration is already running.
- 877 Failed to access XPRSmipsolpool state: <access_operation>
-
The MIP solution enumerator failed accessing the MIP solution pool state with access operation <access_operation>.
- 878 Failed to access XPRSprob state: <access_operation>
-
The MIP solution enumerator failed accessing the problem state with access operation <access_operation>.
- 879 Failed to allocate memory
-
The MIP solution enumerator failed to allocate memory.
- 882 Missing required arguments for running enumerator
-
Arguments passed to the enumeration-run routine (e.g., XPRS_mse_minim) were required to be non-NULL but were passed as NULL.
- 883 Problem no longer has the same number of columns
-
The column dimension of the problem used by the MIP solution enumerator was changed by user.
- 885 Failure storing solution with memory allocation failure
-
A memory allocation failure meant that a solution could not be captured.
- 886 Failure storing solution(s) with failed access to XPRSmipsolpool state: <access_operation>
-
A solution could not be captured because of a failure accessing the state of the MIP solution pool with access operation <access_operation>.
- 887 Failure storing solution(s) with failed access to XPRSprob state: <access_operation>
-
A solution could not be captured because of a failure accessing the state of the problem with access operation <access_operation>.
- 1000 Invalid parameter access : <error_message> (<routine_name>)
-
Access to a parameter with a call to routine <routine_name> failed because of error described in <error_message>.
- 1007 Unexpected failure evaluating solution difference metric
-
An unexpected failure occurred while evaluating difference metrics for solutions.
- 1008 Solution difference metric value is reserved : -1.7976931348623158e+308
-
The double value -1.7976931348623158e+308 to be assigned for a difference metric between two solutions is reserved by the system.
- 1009 Unexpected failure evaluating solution differences
-
An unexpected error occurred while evaluating the diversity of the stored solutions.
- 1010 User signaled failure in solution difference metric callback
-
The user signaled a failure in the callback defined by a call to XPRS_mse_setcbgetsolutiondiff.
- 1011 Cannot evaluate diversity of new solution: Column number mismatch: <num_solution_cols> != <num_prob_cols>
-
The solution passed down to XPRS_mse_getcullchoice for the diversity metric does not have the same number of columns as the problem used in the enumeration run.
- 1015 Destroying while enumeration running
-
The user is attempting to destroy the MIP solution enumerator while it is running.
- 1016 Failed to update MIPABSCUTOFF
-
The MIP solution enumerator failed to update the MIPABSCUTOFF on the problem running the enumeration.
- 1017 Unable to check if loaded sol is dupld: Sol cols (num_solution_cols) does not match global model (num_global_model_cols)
-
A check if the solution being loaded is a duplicate of an existing solution cannot be made because the solution array does not have the same number of columns as the global model used for duplicate checking.
- 1018 Global model unavailable for diversity: <reason_string>
-
The MIP solution enumerator is setup such that internal solution diversity calculations may be made although this will fail because it requires that an appropriate problem is attached to the MIP solution pool (see <reason_string> for details).
- 1019 Cannot handle diversity: <reason_string>
-
The user has called a function that requires solution diversity calculations to be made internally by the MIP solution enumerator and this has failed because it requires that an appropriate problem is attached to the MIP solution pool (see <reason_string> for details).
© 2001-2019 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.