-
Notifications
You must be signed in to change notification settings - Fork 1
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
Numerical stability of beta_mix_trunc_lpdf
#62
Conversation
will look into it today/tomorrow (and the mac fail x/) - could you give me a link to the stan bug for reference? |
Unfortunately I haven't been able to easily reproduce it to be able to identify specifically where in Stan the issue is coming from, just that it is present with rstan 2.26 but not 2.31. Additionally, the failure only occurs when the tests are run through If you have any suggestions for the different behaviours under If you want to verify this locally as well, you can compare the results of running install.packages("rstan", repos = c("https://mc-stan.org/r-packages/", getOption("repos"))) Against the results from 2.31: remotes::install_github("stan-dev/rstan@experimental",subdir="StanHeaders")
remotes::install_github("stan-dev/rstan@experimental",subdir="rstan/rstan") |
While I still don't know exactly what caused it, I narrowed the issue down to a loss of precision in your Hopefully that's a better solution for you than just removing tests! |
@kkmann apologies to double-ping, but we're looking to make the submission soon. Would it be much trouble to merge and release this fix? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh wow, cool - thanks!
@andrjohns on its way to CRAN - there was/is a weird bug with ggplot2 on Mac and I do not have a Mac testing environment... fingers crossed. |
This PR updates your package's tests to temporarily skip one of the scale factors when testing. This was causing a test failure due to a bug in Stan 2.26, and will be safe to re-add on the release of rstan 2.31 (which will quickly follow the release of rstan 2.26).
I've also updated your package's NAMESPACE to avoid a
NOTE
about not importing fromrstantools
.If you could submit a new release to CRAN soon with this PR, it would be very much appreciated - we're trying to reduce the number of downstream failures so that we can submit