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
Issue when starting an AxClient with out-of-design points #2265
Comments
AngelFP
changed the title
Issue when starting an AxClient with out-of-design poins
Issue when starting an AxClient with out-of-design points
Mar 12, 2024
Cesar-Cardoso
added a commit
to Cesar-Cardoso/Ax
that referenced
this issue
Mar 14, 2024
Summary: See facebook#2265 Differential Revision: D54824195
Cesar-Cardoso
added a commit
to Cesar-Cardoso/Ax
that referenced
this issue
Mar 15, 2024
Summary: See facebook#2265 Reviewed By: esantorella Differential Revision: D54824195
Hi Angel! It is not the expected behavior, and it should be fixed after #2277. Thanks for flagging this issue! |
facebook-github-bot
pushed a commit
that referenced
this issue
Mar 15, 2024
Great to hear! Thanks for fixing this so quickly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
First of all thank you for the great library, we've been extensively using it for optimizing the performance of particle accelerators and it's been working really well.
We're currently using Ax within a higher level framework that, among other things, enables the user to update the search space. One use case for this is to resume an old optimization with a more narrowed-down parameter range.
To implement this, I've used the
fit_out_of_design
parameter to enable the model to use data outside of the updated range, as well as this workaround (#768 (comment)) to attach the old out-of-range data to theAxClient
. However, I'm facing an issue where, despite usingfit_out_of_design=True
, the out-of-design data is being filtered out. This is the error I get:Below is a simple reproducer of this issue:
I think the issue is in the
filter_constraints_and_fixed_features
function. In particular, if I comment out these two lines, everything seems to work wellAx/ax/models/model_utils.py
Line 563 in 800357a
Is this the expected behavior or am I doing something wrong?
The text was updated successfully, but these errors were encountered: