-
Notifications
You must be signed in to change notification settings - Fork 416
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
Check for feasibility in gen_candidates_scipy and error out for infeasible candidates #2737
Conversation
This pull request was exported from Phabricator. Differential Revision: D69314159 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2737 +/- ##
=======================================
Coverage 99.99% 99.99%
=======================================
Files 203 203
Lines 18691 18689 -2
=======================================
- Hits 18690 18688 -2
Misses 1 1 ☔ View full report in Codecov by Sentry. |
…sible candidates (pytorch#2737) Summary: As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch#2708 Also includes a couple lint fixes in optimizer tests. Differential Revision: D69314159
24dc091
to
6373914
Compare
This pull request was exported from Phabricator. Differential Revision: D69314159 |
…sible candidates (pytorch#2737) Summary: As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch#2708 Also includes a couple lint fixes in optimizer tests. Differential Revision: D69314159
6373914
to
0320224
Compare
This pull request was exported from Phabricator. Differential Revision: D69314159 |
…sible candidates (pytorch#2737) Summary: As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch#2708 Also includes a couple lint fixes in optimizer tests. Reviewed By: esantorella Differential Revision: D69314159
0320224
to
1dc3435
Compare
This pull request was exported from Phabricator. Differential Revision: D69314159 |
…sible candidates (pytorch#2737) Summary: As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch#2708 Also includes a couple lint fixes in optimizer tests. Reviewed By: esantorella Differential Revision: D69314159
1dc3435
to
8e2a8c1
Compare
This pull request was exported from Phabricator. Differential Revision: D69314159 |
…sible candidates (pytorch#2737) Summary: As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch#2708 Also includes a couple lint fixes in optimizer tests. Reviewed By: esantorella Differential Revision: D69314159
8e2a8c1
to
8dc4d98
Compare
This pull request was exported from Phabricator. Differential Revision: D69314159 |
…sible candidates (pytorch#2737) Summary: As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch#2708 Also includes a couple lint fixes in optimizer tests. Reviewed By: esantorella Differential Revision: D69314159
8dc4d98
to
bf9a56b
Compare
This pull request was exported from Phabricator. Differential Revision: D69314159 |
…sible candidates Summary: X-link: pytorch/botorch#2737 As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch/botorch#2708 Also includes a couple lint fixes in optimizer tests. Reviewed By: esantorella Differential Revision: D69314159
This pull request has been merged in 104df60. |
…sible candidates (#3335) Summary: Pull Request resolved: #3335 X-link: pytorch/botorch#2737 As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed. Resolves pytorch/botorch#2708 Also includes a couple lint fixes in optimizer tests. Reviewed By: esantorella Differential Revision: D69314159 fbshipit-source-id: ccbc759274b2ae0fc2b38fa19d0e95abf35a2928
Summary:
As titled. Previously, it was possible to return infeasible candidates to the user, with or without warnings alerting the user to the issue. This diff makes it so that the optimizer will error out when infeasible candidates are generated, so that the user can adjust the setup as needed.
Resolves #2708
Also includes a couple lint fixes in optimizer tests.
Differential Revision: D69314159