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 change to RBFKernel in 84fccd8 may break something about our prediction code.
I am not totally sure what the problem is yet, but I isolated this as the problem with git bisect and have a reasonable test case where results are significantly worse with the commit in compared to after a revert commit.
It seems like the stability issues we encountered when making this change in the past don't come up in the unit tests, but do on some real datasets.
I can try to push my test case to a branch as well, although it relies on a UCI dataset.
I am not sure what the problem would be other than maybe some issue with how the bounds on the lengthscales are being handled. Did you adjust the bounds appropriately given the new definition?
The change to RBFKernel in 84fccd8 may break something about our prediction code.
I am not totally sure what the problem is yet, but I isolated this as the problem with
git bisect
and have a reasonable test case where results are significantly worse with the commit in compared to after a revert commit.It seems like the stability issues we encountered when making this change in the past don't come up in the unit tests, but do on some real datasets.
I can try to push my test case to a branch as well, although it relies on a UCI dataset.
@Balandat @gpleiss
The text was updated successfully, but these errors were encountered: