-
-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too loose ASSERT_NEAR and wrong test values in compute_potential_scale_reduction_test.cpp #3273
Comments
Any suggestion on how we get values with which to test? Are there tests in the R or Python packages that compute these quantities? |
I used Arviz to generate test values for split-rank, no-split-rank, split-no-rank, no-split-no-rank.
|
Great. I'm curious to see whether tests pass. Getting the details on this kind of thing exactly matching can be painful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
I have tried reducing the accepted error in
ASSERT_NEAR
from 1 to 1e-4, but then the tests failed forComputeRhat.compute_potential_scale_reduction
andComputeRhat.compute_potential_scale_reduction_convenience
. Upon inspection, the test values are the same as forcompute_split_potential_scale_reduction
andcompute_split_potential_scale_reduction_convenience
, for which the corresponding functions output different values.Current Version:
v2.34.1
The text was updated successfully, but these errors were encountered: