Andrew Johnson
Andrew Johnson
The warnings aren't properly displayed in rstan 2.26 (@bgoodri is submitting 2.32 soon which should fix this). In the interim, you can test using either the `experimental` branch: ```r remotes::install_github("stan-dev/rstan@experimental",...
If it's going to require fixing other package dependencies, I'd prefer to wait until 2.31 is on CRAN before removing. At the moment the submission path for 2.31 is relatively...
I'm on board with deprecation warnings
Could the `rstan` functions instead just be a wrapper that performs the unconstraining and then calls `bayesplot`? It could also be something that gets built into `bayesplot`
The idea being not to remove existing functionality, in case it's needed in a workflow somewhere
I either just `devtools::install()` the `StanHeaders` subdir and then the `rstan/rstan` subdir, or use the pre-built package source from any of the recent actions runs on the experimental branch
(and yeah I normally use StanHeaders 2.31 with it as well)
Ooh good question. Wouldn't it be easier to grep the Stan code in the stanfit object for the entries of the `parameters` block? Then it wouldn't be dependent on the...
Until we have rstan 2.26 on CRAN if you update to StanHeaders 2.26 then you need to also reinstall rstan 2.21 from source
@Enchufa2 if you want to use a newer version of the TBB than 2020, you need to add `-DTBB_INTERFACE_NEW` to the compilation flags