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
Aside from generator specific keyword arguments I believe that there should be a simple standard set for specifying an input space (at least) as every generator (even random generators) need to know this information. This comes with the potential need to define if the input space is discrete or continuous.
upper_bound and lower_boundcould be standards, if not for discrete spaces.
batch_size as we've discussed seems very useful, in the event that the user asks for the same num_points every time.
maybe past_points or history, in case a generator needs to build a model from past results before it can be askd? Though maybe that data can just be passed in via tell.
Aside from generator specific keyword arguments I believe that there should be a simple standard set for specifying an input space (at least) as every generator (even random generators) need to know this information. This comes with the potential need to define if the input space is discrete or continuous.
For example:
Xopt
currently handles only continuous spaces specified by a dictionary of lists that specify the minimum and maximum of the bounds for each variable. This information is contained in a more complex object known as VOCS https://github.com/ChristopherMayes/Xopt/blob/main/xopt/vocs.py which also defines objectives/constraints/constants/observables and does validation on inputs. An example of this (taken from https://github.com/ChristopherMayes/Xopt/blob/main/docs/examples/single_objective_bayes_opt/bo_tutorial.ipynb) is below:The text was updated successfully, but these errors were encountered: