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
Hi! I have a quick question regarding the future prospects for the package.
A common use case for optimization is to have a dataset that fully contains your set of choices, as opposed to an analytical, continuous one. In this case, instead of training a model to emulate the experimental surface, you might want an "oracle" that just retrieves the value at any point in the dataset.
Your algorithm would then be restricted to select points in the dataset, and query this oracle for the value.
Is this use case in the (future) scope of the Olympus?
The text was updated successfully, but these errors were encountered:
Hi! I have a quick question regarding the future prospects for the package.
A common use case for optimization is to have a dataset that fully contains your set of choices, as opposed to an analytical, continuous one. In this case, instead of training a model to emulate the experimental surface, you might want an "oracle" that just retrieves the value at any point in the dataset.
Your algorithm would then be restricted to select points in the dataset, and query this oracle for the value.
Is this use case in the (future) scope of the Olympus?
The text was updated successfully, but these errors were encountered: