stan-dev / stan-dev/rstan

RStan produces no output

Open
#739 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
1.1k
Forks
266
Avg merge
2h 56m
Merged PRs (30d)
1

Description

Summary:

There is no output from rstan while fitting

Description:

There is no output from rstan while fitting. I'm expecting messages such as:

Chain 1, Iteration: 1 / 1000 0%
Chain 1, Iteration: 2 / 1000 0%

This is occurring in Ubuntu 19.10 and Elementary OS 5.1. I have no issues in Windows 10 , but need to use linux since no multicore support for Windows

I have tried adding " refresh = 1 " to the stan command without success

I have reinstalled both "shinystan" and "rstan"

I know the fitting is being done because in the end it produces good data, but for longer analyses it would be extremely helpful to know the current progress. Any help would be much appreciated

Reproducible Steps:

Run command such as:

sflist = mclapply(1:4, mc.cores = 4, function (i) stan(fit=fit, seed=sample.int(.Machine$interger.max, 1), data = standata, iter=1000, chains=4, chain_id = i))

or

sflist = mclapply(1:4, mc.cores = 4, function (i) stan(fit=fit, seed=sample.int(.Machine$interger.max, 1), data = standata, iter=1000, chains=4, chain_id = i), refresh=1)

RStan Version:

2.19.2

R Version:

3.6.1

R Studio

1.2.5019 and 1.2.5033

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the stan calls shown in the reproducible steps, especially their use inside mclapply with mc.cores=4, and compare them with the refresh=1 variant. Verify whether fitting progress is emitted on Ubuntu 19.10 and Elementary OS 5.1 under the listed RStan and R versions; done means progress messages appear during fitting without preventing the final data from being produced.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.