stan-dev / stan-dev/rstanarm

[QUESTION] `posterior_traj()` for `stan_mvmer`

Open
#591 2 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:

Is it possible to make dynamic prediction for a multivariate mixed model without the survival component?

Description:

Hi, thanks for developing rstanarm and stan! I am interested in modelling two longitudinal continuous outcomes (without any survival component). I can fit the model I am interested with using stan_mvmer (see steps below). Now I am interested in obtaining dynamic predictions, as it can be done for a stan_jm object using the post_traj function. I think (!) that it should be possible to obtain longitudinal dynamic predictions for a multivariate mixed model, but at the moment post_traj only accepts stan_jm objects. Would it be possible to extend post_traj?

Reproducible Steps:
fit <- stan_mvmer(
  formula = list(
    Y1 ~ TIME + BL1 + (TIME | PATNUM),
    Y1 ~ TIME + BL2  + (TIME | PATNUM)
  ),
  data = train_df, 
  # this next line is only to keep the example small in size!
  chains = 2, cores = 2, seed = 12345, iter = 1000
)
RStanARM Version:

2.21.3

R Version:

4.2.0

Operating System:

x86_64-pc-linux-gnu (64-bit)

Thanks for the help, best wishes
Francesco

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 post_traj entry point and the stan_mvmer object produced by the reproducible example. Determine how dynamic predictions should be represented for multivariate longitudinal outcomes without a survival component, then validate the proposed behavior against the example model and existing stan_jm usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
api, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.