The CRAN version of rstan prevents iteration printing of rstanarm models run in parallel
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1.1k
- Forks
- 266
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
This was reported on the forum and I was able to verify it on my computer:
https://discourse.mc-stan.org/t/controlling-stan-glm-output/18708/10
At least on Catalina, with the CRAN version of rstan this produces no iteration updates (regardless of the value of refresh)
options(mc.cores = 4)
fit <- stan_glm(mpg ~ wt, data = mtcars)
but running the chains sequentially the iteration updates print successfully.
Switching to the github version of rstan solves the problem, so this should be fixed by the next release whenever that is but will affect a lot of people until then.
@bgoodri Do you have a timeline in mind for the next rstan release?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported example with options(mc.cores = 4) and stan_glm(mpg ~ wt, data = mtcars) on the CRAN version, then compare it with the GitHub version of rstan. Check the linked forum report and release history; done means iteration updates print for parallel chains with refresh configured as expected in the released package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100