Skip to content

Add Interpretation Methods to the Core API #329

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

Closed
popescu-v opened this issue Jan 16, 2025 · 1 comment · Fixed by #367
Closed

Add Interpretation Methods to the Core API #329

popescu-v opened this issue Jan 16, 2025 · 1 comment · Fixed by #367
Labels
Priority/0-High To do now Status/InDevelopment The issue is in development by one or more team members
Milestone

Comments

@popescu-v
Copy link
Collaborator

In Khiops v11 a set of prediction interpretation features has been added, namely (see KhiopsML/khiops#223 (comment)) :

  • instance-based interpretation of scores
  • exact computation of Shapley values
  • creation of an intepretation dictionary, to deploy interpretation values
  • creation of a reinforcement dictionary, to deploy reinforcement scores, based on lever variabled

New API methods need to be added for these features.

@popescu-v popescu-v added the Priority/0-High To do now label Jan 16, 2025
@popescu-v popescu-v added this to the 11.0.0.0 milestone Jan 16, 2025
@popescu-v
Copy link
Collaborator Author

It suffices to add a build_interpretor function which takes a path to a prediction model kdic file as input and outputs an intepretation model kdic file. This intepretation model file can be used with deploy_model as any other non-coclustering model (classifier, regressor, encoder).

@popescu-v popescu-v linked a pull request Mar 18, 2025 that will close this issue
6 tasks
@popescu-v popescu-v mentioned this issue Mar 18, 2025
6 tasks
@popescu-v popescu-v added the Status/InDevelopment The issue is in development by one or more team members label Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority/0-High To do now Status/InDevelopment The issue is in development by one or more team members
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant