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
The cost of an unsuccessful configuration such as a crash, time out or mem out is not the lowest in the run history. I think the issue is due to the worst_possible_result of r2 to be 0 instead of a large negative value.
Currently, we assume that the worst r2 value is 0, however, it can be worse as well. So, for this test, get_incumbent_results is giving a failed configuration.
The cost of an unsuccessful configuration such as a crash, time out or mem out is not the lowest in the run history. I think the issue is due to the worst_possible_result of r2 to be 0 instead of a large negative value.
Currently, we assume that the worst r2 value is 0, however, it can be worse as well. So, for this test,
get_incumbent_results
is giving a failed configuration.run_history.data
incumbent_results
The text was updated successfully, but these errors were encountered: