Summary
Most real-world optimization problems contain a mix of continuous, categorical, binary, and ordinal variables and might be high-dimensional. Although there are some methods that have investigated this problem, they are not always reliable with regard to finding a satisfactory optimum. In order to tackle this problem, the authors propose Bounce (Bayesian Optimization Using iNcreasingly high-dimensional Combinatorial and continuous Embeddings). This work seems to be a natural extension of BAxUS, which used a similar embedding strategy as for Bounce but only for continuous variables. It uses a novel trust region management system to grow or shrink the trust regions. The proposed method is tested on a representative range of test problems and compared with state-of-the-art benchmarks and shows convincing results.
Strengths
- Most real-world optimization problems have mixed spaces and are high-dimensional for which vanilla Bayesian optimization methods are not suited, this work thus addresses an important problem.
- The proposed algorithm is tested on a broad range of problems and compared with state-of-the-art benchmarks and has a strong performance.
- The authors provide proof that the algorithm converges in the limit of infinite iterations, making it a reliable method.
- The paper is well-written and well-structured.
Weaknesses
- In general, the paper is very complete and well-written and contains a very complete related work section. However, the paper does expect the reader to have a significant amount of knowledge of previous work. Especially about BAxUS and papers using TR management strategies. Perhaps the authors could provide a little bit more information and illustrations in this work to make it more easily accessible. For instance, provide an illustration of the binning procedures and/or about the TR management.
Questions
- Although I do understand that this is a typical question in BO paper reviews, for most problems, benchmarks are performed for 200 iterations. Would you say that this is enough for the dimensionalities of the benchmark problems? For instance, for the 125-D MaxSAT, you would say you probably need a lot more data points for the surrogate model to model the objective function effectively. What are your thoughts on this and do you think some of the benchmarks can be better than Bounce at a higher budget?
- It is mentioned in Appendix C that the original implementations for COMBO, BODi and Casmopolitan are used. And that you use the same setting as in those works, what kind of settings are these exactly? Do these approaches use the same kernels for the GP models for example? Could this influence the performance on the benchmarks?
- Have the authors contacted Oh et al. regarding the bug in COMBO? If it is possible, it would of course be ideal if results using a bug-less version can be provided.
- I really like the results shown in Figure 5 regarding the efficacy of batch acquisition. In general, I like that the # batch evaluations are used on the x-axis as this directly shows what is good to use for users who are optimizing parallel processes. However, I'm also interested in how these plots look as a function of function evaluations. My intuition would say that b=1 is always better, as in this way the model is as informed as it can for the next iteration. Just out of interest, could you elaborate on this here or could you add a plot to the appendix that shows these results as a function of iterations?
- As a suggestion to your citations regarding chemical engineering and materials discovery. There also is a range of works regarding the optimization of lab equipment for sample analysis. See for instance [Hagan et al.](https://pubs.acs.org/doi/full/10.1021/ac049146x?casa_token=dnIitFW7lO4AAAAA%3Ado8InveDdcPw3TwtOVSQuRvM5NQhSFEo3M1jmpdpEHvRbzA0f1jYTJ2_bloYb7he8-Ofb8u96oMXvCvO), [Boelrijk et al.](https://scholar.google.nl/citations?view_op=view_citation&hl=nl&user=1z-BBwkAAAAJ&citation_for_view=1z-BBwkAAAAJ:9yKSN-GCB0IC). These problems can typically contain mixed spaces and many variables.
Some small textual remarks:
- Could it be that d_0 and d_{init} are interchangeably used? For instance lines 2 and 3 of Algorithm 1.
- Line 90, 'sequencies' should be 'sequences' or was this the originally proposed name by the BODi paper?
- Lines 277-278, as well should be as well as?
- Typo in Ass. 5. in Appendix Section a. One should be once?
Rating
7: Accept: Technically solid paper, with high impact on at least one sub-area, or moderate-to-high impact on more than one areas, with good-to-excellent evaluation, resources, reproducibility, and no unaddressed ethical considerations.
Confidence
4: You are confident in your assessment, but not absolutely certain. It is unlikely, but not impossible, that you did not understand some parts of the submission or that you are unfamiliar with some pieces of related work.
Limitations
The authors describe the societal impact of their work.
The authors do not describe the limitations of their work. Perhaps the authors could dedicate some sentences to this, for example, would the algorithm handle a noisy setting? Or does this violate the binning procedure to some extent?