Fetch rng_key
using prng_key
message in block handler.
#1957
+77
−24
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.
This PR seeks to address #1657 by fetching a
rng_key
after settingmsg["stop"] = True
in the block handler. This approach ensures that the values obtained fromsample
statements are always the same as if noblock
had been added to the stack.We can simplify a number of
block(seed(model, rng_seed=dummy_seed), ...)
toblock(model, ...)
statements for blocked auto guides because therng_key
s now propagate.Caveat: This currently only works for
block(hide=...)
becauseblock(expose=...)
blocks everything but the specified site, includingprng_key
messages. Not sure this is the right solution, but maybe a starting point.Illustration
Results on
master
BranchResults on
seed-block
Branch