Closed n-kall closed 3 years ago
Thanks for opening this issue. A segfault doesn't sounds that great and should probably be fixed rather from the rstan side, as there seems to be a problem in rstan::unconstrain_pars
. Would you mind opening an issue for rstan as well?
Filed an issue for rstan, stan-dev/rstan#939
Thanks! So I can add a check for save_pars(all = TRUE)
in brms but this may uncessarily stop some models from running that would otherwise have run, because those models do not actually have any parameters that were not saved. So I am not sure there is anything reasonable to do from the brms side, as rstan should capture the problem and throw an informative error that than brms can catch and enrich with the please use save_pars(all = TRUE)
info.
I agree, it seems there's not much to be fixed on the brms side. Also, I think it's the case that the bug is not present in rstan on cran (2.21.1), but is on the latest development version (2.26.1), so it's unlikely this will cause issues for users at the moment. So I think you can probably mark this as closed.
Ok, thank you!
As mentioned in #1126 loo with moment matching doesn't work without
save_all_pars=save_pars(all = TRUE)
. But it seems worse than just not having an appropriate warning message, as it can crash R if tried without the parameter.Example: With
save_all_pars
Yields:
Whereas,
Yields:
Session Info: