This PR updates batch trust-region classes to allow init_subspaces to be empty. The request came from this discussion. Default subspaces are created if init_subspaces is None, with the number of spaces equal to the batch_size/num_query_points in the base rule.
Unfortunately, there is no mechanism or concept in the base AcquistionRule for batch size. So this PR uses the dynamic type of the base rule, with current support for EfficientGlobalOptimization.
This PR also allows users to specify a single init-subspace more easily. That is, init_subspaces can now be None, a single value or a sequence.
Fully backwards compatible: yes
PR checklist
[X] The quality checks are all passing
[X] The bug case / new feature is covered by tests
[X] Any new features are well-documented (in docstrings or notebooks)
Related issue(s)/PRs: None
Summary
This PR updates batch trust-region classes to allow
init_subspacesto be empty. The request came from this discussion. Default subspaces are created ifinit_subspacesis None, with the number of spaces equal to thebatch_size/num_query_pointsin the base rule.Unfortunately, there is no mechanism or concept in the base
AcquistionRulefor batch size. So this PR uses the dynamic type of the base rule, with current support forEfficientGlobalOptimization.This PR also allows users to specify a single init-subspace more easily. That is,
init_subspacescan now beNone, a single value or a sequence.Fully backwards compatible: yes
PR checklist