Skip to content
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

Update cost function, use qLogEI in discrete MFKG tutorial #2711

Closed

Conversation

Balandat
Copy link
Contributor

The cost function has pretty high fixed cost, whcih isn't the best to illustrate the algorithm (see #2523 (reply in thread) for discussion).

Also updates to use qLogEI instead of qEI to get rid of the deprecation warning.

The cost function has pretty high fixed cost, whcih isn't the best to illustrate the algorithm (see pytorch#2523 (reply in thread) for discussion).

Also updates to use `qLogEI` instead of `qEI` to get rid of the deprecation warning.
@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Jan 29, 2025
@facebook-github-bot
Copy link
Contributor

@Balandat has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Copy link

codecov bot commented Jan 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.98%. Comparing base (36097db) to head (a30cc69).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2711   +/-   ##
=======================================
  Coverage   99.98%   99.98%           
=======================================
  Files         202      202           
  Lines       18602    18602           
=======================================
  Hits        18600    18600           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@saitcakmak
Copy link
Contributor

Do we need the comparison to LogEI in the notebook? We're not even plotting the comparison

@Balandat
Copy link
Contributor Author

I think the comparison is still useful, you can see that you get a competitive suggestion for less budget even with one eval

@facebook-github-bot
Copy link
Contributor

@Balandat merged this pull request in f463b52.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity. Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants