You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am uncertain how to cope with kHighsStatusWarning of Highs_run. It seems to be returned in cases where the optimization result is unreliable. But what is the difference to kHighsStatusError? Is there a function to get more information about the meaning of the warning? I'd like to see a clarification in highs_c_api.h or in the documentation.
The text was updated successfully, but these errors were encountered:
Having looked at your example from #1561, to be more precise Highs_run(highs) returning kHighsStatusWarning indicates that something unusual has happened, but that the problem may have been solved OK. To determine this, the user should look at the model status and number of primal and dual infeasibilities.
Beyond looking for logging lines with the prefix "Warning", here is no current way for users to identify retrospectively the reason for the kHighsStatusWarning return. The same is true for kHighsStatusError. The difference between the two is that when Highs_run(highs) returns kHighsStatusError, it is known that the solve has failed
I am uncertain how to cope with
kHighsStatusWarning
ofHighs_run
. It seems to be returned in cases where the optimization result is unreliable. But what is the difference tokHighsStatusError
? Is there a function to get more information about the meaning of the warning? I'd like to see a clarification inhighs_c_api.h
or in the documentation.The text was updated successfully, but these errors were encountered: