Feature: computation of SHAP at different time points for survival data with {ranger} #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…anger_surv.unify(type=survival)
|
thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a feature to {treeshap} that allows computing SHAP values at different survival time points for {ranger}.
Therefore, the previously added API
ranger_surv.unify ()was reworked and now has the argumenttypeto distinguish between the computation of "risk" and "survival" SHAP values.The API was further refactored and the method
ranger_surv.common()now includes code relevant for both computations.Unit tests have been added as well. With respect to this some deviations have been noted between unified and original predictions which are yet unexplained (see #24).
It is planned to make use of this feature in the {survex} R package (see ModelOriented/survex#75).