-
Notifications
You must be signed in to change notification settings - Fork 312
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
Switch legacy LCE-A to qLogNEI from legacy ei_or_nei
#2352
Conversation
This pull request was exported from Phabricator. Differential Revision: D56037477 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2352 +/- ##
==========================================
+ Coverage 94.91% 94.93% +0.02%
==========================================
Files 491 495 +4
Lines 47788 48057 +269
==========================================
+ Hits 45356 45622 +266
- Misses 2432 2435 +3 ☔ View full report in Codecov by Sentry. |
Summary: Context for this stack: we've been meaning to deprecate ALEBO and REMBO for a long time. Tests on them break periodically and slow down development of `GenerationStrategy`, which these classes hack around, so there's substantial maintenance burden to keeping them. Context for this diff: LCE-A was depending on ALEBO for, it seems, no reason other than convenience of where the acquisition function constructor lived. This diff aims to address. **[RfC] But also this made me wonder: maybe better to replace use of `ei_or_nei` in LCE-A with something newer?** Reviewed By: saitcakmak Differential Revision: D56037477
f1387a5
to
d935cad
Compare
This pull request was exported from Phabricator. Differential Revision: D56037477 |
Summary: Context for this stack: we've been meaning to deprecate ALEBO and REMBO for a long time. Tests on them break periodically and slow down development of `GenerationStrategy`, which these classes hack around, so there's substantial maintenance burden to keeping them. Context for this diff: LCE-A was depending on ALEBO for, it seems, no reason other than convenience of where the acquisition function constructor lived. This diff aims to address. **[RfC] But also this made me wonder: maybe better to replace use of `ei_or_nei` in LCE-A with something newer?** Reviewed By: saitcakmak Differential Revision: D56037477
d935cad
to
4a7d5e9
Compare
This pull request was exported from Phabricator. Differential Revision: D56037477 |
Summary: Context for this stack: we've been meaning to deprecate ALEBO and REMBO for a long time. Tests on them break periodically and slow down development of `GenerationStrategy`, which these classes hack around, so there's substantial maintenance burden to keeping them. Context for this diff: LCE-A was depending on ALEBO for, it seems, no reason other than convenience of where the acquisition function constructor lived. This diff aims to address. **[RfC] But also this made me wonder: maybe better to replace use of `ei_or_nei` in LCE-A with something newer?** Reviewed By: saitcakmak Differential Revision: D56037477
4a7d5e9
to
ec91fda
Compare
This pull request was exported from Phabricator. Differential Revision: D56037477 |
This pull request has been merged in 25c4d0d. |
Summary:
Context for this stack: we've been meaning to deprecate ALEBO and REMBO for a long time. Tests on them break periodically and slow down development of
GenerationStrategy
, which these classes hack around, so there's substantial maintenance burden to keeping them.Context for this diff: LCE-A was depending on ALEBO for, it seems, no reason other than convenience of where the acquisition function constructor lived. This diff aims to address.
[RfC] But also this made me wonder: maybe better to replace use of
ei_or_nei
in LCE-A with something newer?Reviewed By: saitcakmak
Differential Revision: D56037477