Initial AbstractMCMC.step
should not sample
#366
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.
Generally speaking, the first
AbstractMCMC.step
should just construct the initial transition and state, not actually perform any sampling. If it performs sampling in the initial step, it becomes increasingly difficult to test that arguments such asinitial_params
andinitial_state
are properly respected (since we can't just compare the resultinginitial_params
with the ones produced by the first step). Moreover, it can hide certain behaviors from the user since a traceplot will show the "starting value" as something different than what they set.This PR just makes the initial
AbstractMCMC.step
do exactly this.Should be a quick merge. @devmotion @yebai @xukai92