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
{{ message }}
This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
The output of print(getTuneResult(mod)) is already transformed as you probably noticed
As this is a noisy optimization problem mlrHyperopt suggests the point where the surrogate predicts the best performance. But only taking the points into concern that have really been evaluated. The plot generated by plotOptPath() highlights the point that has the best performance. This can be overly optimistic as this point might only have a good performance due to noise. plotOptPath does not (and can not) respect the settings of mbo in this case.
Ok, I understand. In the graph you just want to show evaluated points. It's just a bit confusing for the user, as he is not sure what point he should take, but probably the surrogate output is better. (Maybe an interesting question for research)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Maybe I have overseen something, but I get different optimal results in the plot and with getTuneResult. I really like the plotOptPath function!
The text was updated successfully, but these errors were encountered: