Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #892
This PR deprecates the
time
argument to the prediction functions in favor of theeval_time
argument name.predict()
only takes this argument in the ellipsis, so I updated only the documentation. I replacedtime
witheval_time
, i.e. there is no mention of any deprecation but instead a direct swap. Should this talk about deprecation as well? I was trying not to overload that help page since it contains so much already.predict_survival()
andpredict_hazard()
both had atime
argument. Now they have bothtime
andeval_time
as arguments, andtime
is deprecated, including updates to the documentation.This PR starts the deprecation at
deprecate_warn()
rather than a soft-deprecation. Does that sound good?Tests on this deprecation are going to have to sit in censored since we need an engine for those prediction types. parsnip does contain
surv_reg()
, but that uses the mode"regression"
for which we don't predict survival or hazard probabilities.