-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix Claret Unit test #441
Fix Claret Unit test #441
Conversation
@gravesti - I've left the testing code in the design folder just in case we need to explore this again in the future. |
Code Coverage Summary
Diff against main
Results for commit: 8ea38b9 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 180 suites 6m 9s ⏱️ Results for commit 8ea38b9. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 996dee3 ♻️ This comment has been updated with latest results. |
Closes #421
In the end I believe the issue was simply from the priors being too uninformative. Making them moderately informative completely resolves all issues (no warnings and decent sample size).