This repository has been archived by the owner on Dec 18, 2023. It is now read-only.
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:
An issue with the U-turn condition was discovered and discussed in this post in Stan forum
TL;DR: we can make the U-turn condition more robust by introducing two additional checks across subtrees. This can help us avoid missing U-turns for approximately iid normal models.
{F619223264}
Since the tree combining code are almost identical in
_build_tree
andpropose
, I also take the chance to refactor them into a common function called_combine_tree
. If you look closely you will notice that most part of_combine_tree
are moved from existing code as-is. The only addition is the two additional call to_is_u_turning
Related PR that implements this change:
Differential Revision: D28735950