-
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
Possibility to access Ranger object for Shap values #54
Comments
Interesting idea, thanks. The output of A complete API change is not possible (too much dependencies). I am considering the following idea: mr <- missRanger(data, other stuff, output = c("data.frame", "missRanger"))
This would not break current code, while offering necessary flexibility for further analysis. What do you think? |
Hi,
I think that would be indeed a good way forward to start building some statistics on top of what the model produces.
How long do you think that will take you to be implemented and tested?
…-------- Ursprüngliche Nachricht --------
Von: Michael Mayer ***@***.***>
Datum: 25.10.23 15:42 (GMT+01:00)
An: mayer79/missRanger ***@***.***>
Cc: "Brancatelli, Calogero" ***@***.***>, Author ***@***.***>
Betreff: Re: [mayer79/missRanger] Possibility to access Ranger object for Shap values (Issue #54)
Interesting idea, thanks.
The output of missRanger() is simply a data.frame with optionally some OOB performance results attached, so this is not possible at the moment.
A complete API change is not possible (too much dependencies). I am considering the following idea:
mr <- missRanger(data, output = c("data.frame", "missRanger"))
* output = "data.frame": current behavior
* output = "missRanger": A "missRanger" object is returned. Basically a list with imputed data, random forests and other stuff. With print() method any maybe summary().
This would not break current code, while offering necessary flexibility for further analysis.
What do you think?
—
Reply to this email directly, view it on GitHub<#54 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQY56AEZCF5N36ODJ4SI2OTYBEJK3AVCNFSM6AAAAAA6PKKSOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZZGMYDMMJQGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#54 (comment)", "url": "#54 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
|
I will ping you when a Pull Request is ready to be installed for a quick cross-check. |
Implemented in #55 You can use the new version via
|
thanks @mayer79, this implementation is great. thank you! |
With the new, extended |
In above example, all ranger objects are attached in the |
The project could be extended to cater for the production of Shap values and other metrics that the underlying package accounts for.
Is there a way to accomplish that in the current version already?
The text was updated successfully, but these errors were encountered: