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

Clean up is_fully_bayesian #1992

Closed
wants to merge 1 commit into from
Closed

Conversation

dme65
Copy link
Contributor

@dme65 dme65 commented Nov 14, 2023

Summary:
This attempts to clean up the usage of is_fully_bayesian and also separately treat fully Bayesian models from ensemble models.

The main changes in diff are to:

  • Add an _is_fully_bayesian attribute to Model. This is True for fully Bayesian models that rely on Pyro/NUTS to be fitted (they need some special handling for fitting and state_dict loading/saving.
  • Add an _is_ensemble attribute to Model. This indicates whether the model is a collection of multiple models that are stored in an additional batch dimension. This is hopefully a better classification, but I'm open to a different name here.
  • Rename FullyBayesianPosterior to GaussianMixturePosterior since that is more descriptive and plays better with the other changes.

Reviewed By: esantorella

Differential Revision: D50884342

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Nov 14, 2023
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50884342

Summary:
X-link: pytorch/botorch#2108

This attempts to clean up the usage of `is_fully_bayesian` and also separately treat fully Bayesian models from ensemble models.

The main changes in diff are to:
- Add an `_is_fully_bayesian` attribute to `Model`. This is `True` for fully Bayesian models that rely on Pyro/NUTS to be fitted (they need some special handling for fitting and `state_dict` loading/saving.
- Add an `_is_ensemble` attribute to `Model`. This indicates whether the model is a collection of multiple models that are stored in an additional batch dimension. This is hopefully a better classification, but I'm open to a different name here.
- Rename `FullyBayesianPosterior` to `GaussianMixturePosterior` since that is more descriptive and plays better with the other changes.

Reviewed By: esantorella

Differential Revision: D50884342
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50884342

@dme65
Copy link
Contributor Author

dme65 commented Nov 16, 2023

The failures here are expected and they should go away once the BoTorch part of this diff lands.

facebook-github-bot pushed a commit to pytorch/botorch that referenced this pull request Nov 16, 2023
Summary:
X-link: facebook/Ax#1992

Pull Request resolved: #2108

This attempts to clean up the usage of `is_fully_bayesian` and also separately treat fully Bayesian models from ensemble models.

The main changes in diff are to:
- Add an `_is_fully_bayesian` attribute to `Model`. This is `True` for fully Bayesian models that rely on Pyro/NUTS to be fitted (they need some special handling for fitting and `state_dict` loading/saving.
- Add an `_is_ensemble` attribute to `Model`. This indicates whether the model is a collection of multiple models that are stored in an additional batch dimension. This is hopefully a better classification, but I'm open to a different name here.
- Rename `FullyBayesianPosterior` to `GaussianMixturePosterior` since that is more descriptive and plays better with the other changes.

Reviewed By: esantorella

Differential Revision: D50884342

fbshipit-source-id: 0ba603416c1823026c4fdf2e445cefdf8036cda8
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 3985791.

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. fb-exported Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants