-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Specifying fixed features to AxClient.get_next_trial
(to conduct contextual BO using Service API)
#746
Comments
Hi @MattiaVerticchio, I think right now the Service API does not support this case, but it definitely could –– it seems reasonable for In the meantime, you can hack around this like in this comment: #733 (comment), so basically generating the parameterizations outside of |
AxClient.get_next_trial
(to conduct contextual BO using Service API)
Yes, that’s definitely better, thanks for your help! |
Putting this on wishlist for now, but we will likely support this soon! |
@MattiaVerticchio, do you mind including a reproducer for this example if you have one available? |
Summary: Addresses facebook#746 (also in the wishlist facebook#566). As the title implies, this PR adds the possibility of specifying some `FixedFeatures` as `fixed_features` in `AxClient.get_next_trial` and `AxClient.get_next_trials` which is currently only possible with the developer API. Differential Revision: D56068035
Hi everyone. First of all, thanks for working on Ax! 😁
I have a setting where I’d like to optimize a function based on a certain context. The context is, in this case, the day of the week.
If I understood correctly, the only way to have contextual BO in Ax is by using the Developer API; setting the context as input covariates, and then generating a
new_trial
withfixed_features
:For this kind of task, the Developer API is more flexible but adds a lot of complexity. Is there any other way to do contextual BO, or pass
fixed_features
when using the simpler Service API?Thanks!
The text was updated successfully, but these errors were encountered: