Skip to content
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

Explain leaf prediction path #278

Open
tlapusan opened this issue Mar 6, 2023 · 6 comments
Open

Explain leaf prediction path #278

tlapusan opened this issue Mar 6, 2023 · 6 comments
Assignees

Comments

@tlapusan
Copy link
Collaborator

tlapusan commented Mar 6, 2023

Kind of similar with explain_prediction_path(x).

When looking at the tree structure (or leaf visualisations), you can observe some interesting nodes/leaves and you want to know what characteristics have all the training samples from that node. We can use the split values from the root until the interested node and build some similar output like in explain_prediction_path(x)

@tlapusan tlapusan self-assigned this Mar 6, 2023
@lchakkei
Copy link

lchakkei commented Mar 8, 2023

You can use view() to show the leaf prediction path
e.g viz_model.view(x=X_testset[0])
image

@tlapusan
Copy link
Collaborator Author

tlapusan commented Mar 8, 2023

Indeed, but it is not convenient/easy to find an x sample which belong to a specific leaf/node.

what I thought was something like 'explain_node_path(node_id=3)'

@parrt
Copy link
Owner

parrt commented Mar 18, 2023

I guess that makes sense to me except I'm not sure how we know what the node id is. Do we have a way to display that?

@tlapusan
Copy link
Collaborator Author

I just put the mouse over a node and little pop-up appear with the node id.
We could include also other info in this way.

Screenshot 2023-03-19 at 11 04 17

@parrt
Copy link
Owner

parrt commented Mar 19, 2023

cool! Didn't know about that. kind of like the feature earlier we talked about where in leaf display we could pop up node id in bar chart, right?

@tlapusan
Copy link
Collaborator Author

yes, could be the same... but it's kind of a hidden functionality. The user has to know it upfront.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants