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
time
to eval_time
#244
time
to eval_time
#244
Conversation
which contains `eval_time`
for deprecation messages
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
parsnip#880
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
`time` -> `eval_time`
@simonpcouch The changes are pretty boring to read - the more challenging aspect is if I overlooked anything to add. If you could tilt your review toward that, that'd be great! 🙌 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m on board with your deprecation approach—thumbs up for the unit testing comment and transition immediately to the more aggressive deprecate_warn()
.
I’m guessing many of these are false positives, but a few places where .time or time is still around in a way that isn’t immediately obvious to me:
censored/R/aaa_survival_prob.R
Line 28 in e61368d
.time = x$time, |
censored/R/aaa_survival_prob.R
Line 44 in e61368d
.time = rep(x$time, n), |
censored/R/aaa_survival_prob.R
Line 57 in e61368d
.time = 0, |
censored/R/boost_tree-mboost.R
Lines 192 to 193 in b8305bb
next_event_time = dplyr::lead(.time), | |
time_interval = next_event_time - .time, |
censored/R/boost_tree-mboost.R
Line 124 in e61368d
# survival_prob is length(time) x nrow(new_data) and |
I believe the intent here was to test formula vs xy rather than with the two different arguments:
time = c(100, 200) |
There are a good few places in this vignette that use time:
censored/vignettes/articles/examples.Rmd
Line 62 in b8305bb
time = c(100, 500, 1000) |
object %>% | ||
summary(times = time, extend = TRUE) %>% | ||
summary(times = eval_time, extend = TRUE) %>% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self / future GitHub sleuth--times
is the argument to survival::summary.survfit()
Thank you! The |
CI failures are due to changes in the new pillar, so unrelated to this PR |
This pull request 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. |
Closes #241
This PR completes the deprecation of the
time
argument to the prediction functions in favor of theeval_time
argument name laid out in tidymodels/parsnip#892.The commits are (mostly) working through the package model/engine combination by model/engine combination, but the aggregated pattern is
-data.R
files, prediction modules fortype
s"survival"
and"hazard"
need to expect theeval_time
arg instead of thetime
argsurvival_prob_coxph()
, also make the switch and since they are exported,time
is being deprecated. Since they are also@keywords internal
, there are no specific deprecation tests. Happy to add those but thought that this might be a bit much.time
toeval_time
parsnip#936eval_time
where appropriate.time
arg inparsnip::predict_survival()
andparsnip::predict_hazard()
are intest-survival_reg-survival.R