MIP Solution Pool errors

The index col_index of the first column passed to XPRS_msp_getsol is outside the range [0, <num_cols> - 1]

The index of the first column passed to XPRS_msp_getsol is greater than the index of the last column.

A problem cannot be attached to more than one MIP solution pool.

A check if the solution being loaded is a duplicate of an existing solution cannot be made since no global model is available. No model is available because no problem has been attached to the MIP solution pool.

A check if the solution being loaded is a duplicate of an existing solution failed because of a memory allocation failure.

A check if the solution being loaded is a duplicate of an existing solution cannot be made because the problem from which the solution originates does not match the global model used for duplicate checking.

A check if the solution being loaded is a duplicate of an existing solution cannot be made because a required update of the global model could not be made reliably.

A check if the solution being loaded is a duplicate of an existing solution cannot be made because a required update of the global model could not be made.

A check if the solution being loaded is a duplicate of an existing solution cannot be made because a required capture of the global model could not be made from the problem being attached.

The MIP solution pool is being destroyed and problems are still attached. This should be ok although the user should be aware. This message can be avoided by detaching the attached problems before destroying the MIP solution pool.

A reset operation for the duplicate solution information failed. The duplicate solution checking may now not work reliably.

Failure calculating the information for a solution with respect to a problem.

A check of the problem state information failed when trying to calculate a check sum.

An unexpected failure when attempting to capture a solution.

An object failed to register to receive system events.

An object failed to deregister the receipt of system events.

A call made by the user failed because of a memory allocation failure.

A memory allocation failed when attempting the operation < operation_attempted >. The system may still continue to function normally.

The numbers of columns of solution <solution_id> and of problem <prob_id_string> are required to be the equal (but they are not).

The user has attempted to access information for the solution with id <solution_id> but the solution has been deleted.

The user has attempted to access information for the solution with id <solution_id> but the id is for a solution that does not exist.

An attempt to make a list of solutions that relate to problem <prob_id_string> failed because state information of the problem could not be reliably accessed.

The user seems to want a list of solutions sorted by some attribute but the attribute id is not recognized.

The numbers of columns of a given solution vector and of a given problem are required to be the equal (but they are not).

An unexpected failure was encountered writing solution(s) to file <file_name>.

An unexpected failure was encountered opening file <file_name> for writing.

An unexpected failure was encountered opening file <file_name> for reading.

A failure occurred when loading solution <solution_id> into problem <prob_id_string>. The failure is described in string <message>.

Loading was interrupted of solution <solution_id> into problem <prob_id_string>.

The user has attempted to set an unrecognized value <policy_id> for the control MSP_DUPLICATESOLUTIONSPOLICY.

The solution named <solution_name> was skipped while reading solutions from file. A previous message describes why the solution could not be read.

A rigorous duplicate solution checking routine found an anomaly described in <message>.

A warning that the user is changing the tolerance <tolerance_name> (MIPTOL or FEASTOL) for a solution from the value it was set to by the system <system_tol_value> to a different value <user_tol_value>.

No solutions were written in a call to XPRS_msp_writeslxsol.

The operation <operation_name> is only allowed for problems attached to the MIP solution pool.

The user has attempted to access information for the solution with id <solution_id> but the solution seems to have been deleted.

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.

A call made by the user failed because of a memory allocation failure.

The metric id <metric_id> passed by the user is unrecognized.

The user is attempting to access information about the stored solutions but the solution storage is empty.

The user is attempting to run the enumeration while the enumeration is already running.

The MIP solution enumerator failed accessing the MIP solution pool state with access operation <access_operation>.

The MIP solution enumerator failed accessing the problem state with access operation <access_operation>.

The MIP solution enumerator failed to allocate memory.

Arguments passed to the enumeration-run routine (e.g., XPRS_mse_minim) were required to be non-NULL but were passed as NULL.

The column dimension of the problem used by the MIP solution enumerator was changed by user.

A memory allocation failure meant that a solution could not be captured.

A solution could not be captured because of a failure accessing the state of the MIP solution pool with access operation <access_operation>.

A solution could not be captured because of a failure accessing the state of the problem with access operation <access_operation>.

Access to a parameter with a call to routine <routine_name> failed because of error described in <error_message>.

Failure calculating the information for a solution with respect to a problem.

A problem <prob_id_string> attached to the MIP solution pool was unexpectedly detached by the user.

The user has attempted to attach an internal problem being solved by the parallel MIP search to a MIP solution pool.

A row vector of length <num_row_vector_cols> passed to the MIP solution pool for evaluation against a solution does not contain the same number of columns as the solution <num_solution_cols>.