-
Notifications
You must be signed in to change notification settings - Fork 718
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
Lookup Table for single feature and feature interaction terms #530
Comments
Hi @sauvikd -- One of the very nice things about EBMs, and GAMs in general, is that the scores are used when calculating the predictions AND what are shown on the graphs. EBMs have no hidden information. For graphing though, you also need the "bins" attribute, which for continuous features are the locations on the X-axis where the bin transitions occur. There's some code which creates graphs here: #325 And you might also find our documentation on EBM internals useful: https://interpret.ml/docs/ebm-internals-regression.html |
Thank you so much @paulbkoch for answering my query. It helped me solve my problem. There's a 2nd part of my query if you can answer my query. Although I can retrieve the individual feature importance plots showing scores using the following piece of code. for feature_idx, feature in enumerate(best_ebm_model.term_names_):
iplot(ebm_global_explainer.visualize(feature_idx)) How can I separately plot the - EBM Summary Global Importance bar plot, like the one below? |
Hi @sauvikd -- We usually recommend the show function: But, if you want to use iplot, try this: |
Thanks @paulbkoch, it worked for me. |
How can I extract a lookup table for the red-line (score values for the each of the features) and similarly the data for the heatmap.
I had tried downloading the ebm_global.data(1)['scores'], but those are values for each of the bins, from what I understand. Even if I'm able to extract the bin boundary values, I will be able to connect them with the feature values.
The text was updated successfully, but these errors were encountered: