Open be-marc opened 4 months ago
the SurrogateLearner is now tightly coupled with rush, and its imputation for async optim. I think this is not good design. Inherit from SL, create SLAsync. only do the impute there, don't touch the existing class.
we have to handle failed stated. but MBO should ALREADY cover that? just use the same mechanism.
we might slightly change the impute mechanism. we could a) sample between min/max b) instead of mean provide a "quantile value" which is constantly used (e.g. 0.5 would always use median). in any case, a reference should be provided?
OptmizerAdbo
to behave similar asOptimizerMbo
OptimizerAdbo
to be configured w.r.t surrogate and acquisition function optimizer.OptimizerAdbo
or async loop functions directly