stan-dev / stan-dev/rstanarm

Questions about stan_surv function.

Open
#626 0 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:

Questions about stan_surv function.

Description:

I want to utilize stan_surv to explore various variables' (including time-fixed covariate and time-varying covariate) impact on survival time. And the manual suggests give us examples of time-fixed covariate and time-varying covariate situations like this:
mod1 <- stan_surv(formula = Surv(recyrs, status) ~ group, data = bcancer, chains = CHAINS, cores = CORES, seed = SEED, iter = ITER)
and
mod_tvc <- stan_surv( formula = Surv(tstart, tstop, death) ~ log(bili) + log(protime), data = dat, chains = CHAINS, cores = CORES, seed = SEED, iter = ITER)
Time-fixed covariate and time-varying covariate are analyzed separately, and the model for time-varying covariates has a "start-stop" time structure.
Here I would like to ask that if I have time-fixed covariate and time-varying covariate at the same time, should I separate them? Moreover, the model for time-fixed covariate only contains one covariate, if I have a few covariates, should I separate them or put them together?
Looking forward to your answer and appreciate it!

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

The issue names stan_surv and the manual's fixed-covariate and start-stop examples, but no repository file or test. Start by reading the stan_surv documentation and those examples to determine how combined covariates are intended to work. Done would require a documented answer or an expanded example addressing the described use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.