stan-dev / stan-dev/rstanarm

rstanarm stan_jm crash - Error in check_stanfit(stanfit)

Open
#485 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
401
Forks
136
PR merge metrics
No merged PRs in 30d

Description

Summary:

I was following the example in the rstanarm joint model vignette. I was at the very basic mod1 in the vignette and as I ran it, an error message pops out.

`SAMPLING FOR MODEL 'jm' NOW (CHAIN 1).

Chain 1: empty_nested() must be true before calling recover_memory()
[1] "Error in sampler$call_sampler(args_list[[i]]) : "
[2] " empty_nested() must be true before calling recover_memory()"

error occurred during calling the sampler; sampling not done
Error in check_stanfit(stanfit) :
Invalid stanfit object produced please report bug`

I then ran mod1 again and the following pops out:

Error in sampler$call_sampler(c(args, dotlist)) : empty_nested() must be true before calling recover_memory()

So it looks like I'm requested to file a bug report. Any help would be very much appreciated.

RStanARM Version:

The version of the rstanarm package I am running is 2.21.1

R Version:

The version of R you are running 3.6.2

Operating System:

My operating system is Mac OS X 10.15.5

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 by reproducing mod1 from the rstanarm joint model vignette with the reported RStanARM, R, and macOS versions. Trace the failure through sampler$call_sampler and check_stanfit(stanfit), then compare behavior with supported versions. Done means the cause of the empty_nested() error is established and the issue has a verified fix or compatibility explanation.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.