Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on api for competing and censoring #129

Open
uriahf opened this issue May 15, 2024 · 1 comment
Open

Decide on api for competing and censoring #129

uriahf opened this issue May 15, 2024 · 1 comment

Comments

@uriahf
Copy link
Owner

uriahf commented May 15, 2024

It seems natural to consider competing-event as just another status (non-event 0, event 1, competing 2), but it is unclear how to relate to censored event which is also in some cases considered as "2".

Also: what is the default competing state model and should rtichoke allow the user different state models?

Main references to consider:

@uriahf
Copy link
Owner Author

uriahf commented May 15, 2024

prodlim::Hist(time, event), riskRegression::Score(), pec::cindex

  • probs:
    One row (vector) for one observation, each column stands for a state.

  • If only one column is provided, the probability is for the primary event. If two columns are provided than one then the first column is for the primary event and the second is for the secondary.

  • reals:
    0 stands for non event or administrative-censoring, 1 for the primary event and 2 for the secondary event.

  • times_to_events
    The observed time for the first event or administrative-censoring for non-events.

Scope: time to first event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant