Open mb706 opened 4 years ago
This error occurs because updateSMBO
calculates the crit.vals
(acquisition function values) for the given x values to write them in the opt.path
. This is not essential, but a nice to have.
For the methods you mentioned (and probably more) it is not trivial to calculate them afterwards. I would suggest that we just not calculate the crit.vals in those cases. Using a tryCatch()
or ifelse
?
Why does it not crash in mbo()
?
parego fails:
gives error
similarly, mspot fails:
with error