-
Notifications
You must be signed in to change notification settings - Fork 313
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
Wishlist: Tracking Issue #566
Comments
@lena-kashtelyan I already built a conda recipe see PR whenever we fix the windows compatibility I'll let you know. |
@lena-kashtelyan it is now available on conda-forge https://anaconda.org/conda-forge/ax-platform |
Wow, thank you so much, @rpanai! |
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
For "Exact equality parameter constraints" is the blocking factor an API design choice or a bandwidth choice? If it's bandwidth I am happy to take it on |
We should be able to just introduce a I think the key question is whether we'd want to work on a reduced space in the Ax land by eliminating one of the parameters, or whether we want to work on the full parameter space and pass the equality constraints down to botorch. The former would not support observations that do not satisfy the parameter constraints. Seems like it could be quite common in practice that users have such data that they'd want to use in the modeling (wdyt?) so maybe the latter option would be preferred here. That will require modifying how the constraints are passed through the modelbridge layer in different places. So overall I think it's largely a bandwidth constraint (doing this will require some nontrivial amount of work) |
My intent would have been to funnel everything down to botorch rather than trying to work in Ax land (I am a tourist). In my toy experiments so far playing with a sum to one constraint reformulated as an inequality constraint by excluding a parameter space and then using SEBO with FullyBayesianSaas I have observed quite pathological behaviour, using a single task GP the performance is better. I need to run a few ablations such as to shuffle the parameter order to make sure that this is due to the SAAS/sum-constraint-inequality interaction. |
Feature requests marked as 'wishlist' will be gathered here going forward, in order to:
Please still feel free to open new issues for feature requests (or comment them here if they are short/clear), and we will take care of adding them to this post.
Status: will likely be addressed in the short-term
[DONE] Obtaining best parameters (parameters on the Pareto frontier) for multi-objective optimization in Service API (ImplementAxClient.get_best_parameters
, returning the parameter configurations on the Pareto frontier #656)requirement.txt
for conda-forge compatibility #614)[DONE] Hierarchical search spaces (Hierarchical search spaces #140)AxClient.get_next_trial
(to conduct contextual BO using Service API) #746)Status: will likely be addressed in the long-term
optimize
: needs more documentation, maybe does not return the correct best parameters? #605)import ax
: Add commonly used plots to__init__.py
, so they can be available with justimport ax
#774Experiment._properties
andTrial._properties
(Wishlist: Tracking Issue #566 (comment))Data
for trials without Dataframes (associating potentially larger data, e.g. image data, with trials, and passing that data to the model directly; Question: Best way to include non-scalar types in experiment results? #880)DeterministicModel
and documentation for it (Request for documentation: example withDeterministicModel
#1192, Optimization of analytic functions #935)Status: uncertain
best_parameters
as optimal ranges instead of single values #320)PAUSED
trial status (Request for a feature. Please introduce the TrialStatus.PAUSED #862)numpy
values as well as Ax primitives (Parameter type checking #996)Suggestions for setup changes:
The text was updated successfully, but these errors were encountered: