Implement more robust jitter init (resolves #4107) #4298
Merged
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 addresses issue #4107, by allowing the starting jitter to be resampled when the sampled values generate an invalid probability for the model. There is a new optional argument
jitter_max_retries
insample()
andinit_nuts()
that controls the maximum number of times that a value can be resampled (per chain) before it gives up and returns whatever was last sampled. I arbitrarily set it to 10, but we can choose another default.I further refactored the code that applies jitter to the starting point of each chain into a helper function
_init_jitter()
, to avoid duplicated code between the two init methods where this is usedinit="jitter+adapt_diag"
andinit="jitter+adapt_diag"
. I added a unit_test for this function.Here is an example that (almost deterministically) shows an improvement following this PR:
If you happen to know other examples of models that have fragile starting points when jitter is applied it would be great to test it out.
Any thoughts?