You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In survival package, the most common way to encode time-dependent covariates is to use the (start, stop] form
of the model: Surv(time1, time2, status). Below is what the timedep vignettes of survival package said:
In mlr3, as_task_surv() do have parameters time2, for example, as_task_surv(mydata, time = "time1",time2 = "time2", event = "status"). However, when I run the codes below, the selected feature included the time2.
Does it mean the surv learners like glmnet regard the time2 as the predictor instead of the response variable Surv(...)? What survival models in mlr3 support Surv(time1, time2, status) encoding?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In survival package, the most common way to encode time-dependent covariates is to use the (start, stop] form
of the model:
Surv(time1, time2, status)
. Below is what the timedep vignettes of survival package said:In mlr3,
as_task_surv()
do have parameterstime2
, for example,as_task_surv(mydata, time = "time1",time2 = "time2", event = "status")
. However, when I run the codes below, the selected feature included thetime2
.Does it mean the surv learners like glmnet regard the
time2
as the predictor instead of the response variableSurv(...)
? What survival models in mlr3 supportSurv(time1, time2, status)
encoding?Thanks!!!
Beta Was this translation helpful? Give feedback.
All reactions