-
Notifications
You must be signed in to change notification settings - Fork 11
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
PH models and probability estimates #30
Comments
I would echo Max and suggest using
|
Do people ever want (instantaneous) hazard estimates for this model? |
update: survival probabilities for leaving this open for the (instantaneous) hazard discussion |
I think hazards can be useful as a diagnostic (e.g., for understanding whether a parametric model seems reasonable, exploring non-proportional hazards). But I don't think they are nearly as useful as other summaries of the survival distribution, particularly in a prediction context. |
thanks for the feedback @dincerti ! |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
There is currently some code in
aaa_survival_prop.R
to estimate survival probabilities for Cox PH models. It might be better to usesurvift(coxph_object)
orbasehaz(coxph_object)
to get these since they take into account any stratification variables for that model. If that's the case, we might want to save the table produced by those functions in the model object and interpolate the step functions within each strata. Dealing with the strata is a pain, because of howsurvival
encodes them, but some of that work is already done for the parametric model engine.Also, I don't see any canonical ways of estimating the baseline hazard so that we can get
type = "hazard"
. There as some methods that layer another model on top of the PH model results. It would be good to get community feedback on this.We might also consider having a
type = "cumulative hazard"
method@dincerti
The text was updated successfully, but these errors were encountered: