WIP: Enable (naive) minibatching within MCMC. #349
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.
Purpose
Content
x -> f(x, emulator, prior, data)
in the factoryover the data vector
y_i in Y. This is a naive formulation, requiring
n` evaluations of the emulator for every MCMC step.Misc
The net result of (Barbenet, Doucet, Holmes 2017) ) is that minibatching within MCMC is a very technically complex problem, and for computational benefit without loss of accuracy requires a nested procedure to approximate the accept-reject mechanicsm, and futher surrogates of the log-likelihood. It may be that simple parallelization or alternative (parallel) sampling methods would be preferred
ObservationSeries
object contains both data samples and noise covariance. Here it appears that MCMC requires only the data samples, while the emulator uses the noise covariance (for decorrelation), this should be addressed in a future issue to do with data processing but not here