Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
_is_fully_bayesian
attribute toModel
. This isTrue
for fully Bayesian models that rely on Pyro/NUTS to be fitted (they need some special handling for fitting andstate_dict
loading/saving._is_ensemble
attribute toModel
. 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.FullyBayesianPosterior
toGaussianMixturePosterior
since that is more descriptive and plays better with the other changes.Reviewed By: esantorella
Differential Revision: D50884342