Skip to content
This repository was archived by the owner on Jul 13, 2025. It is now read-only.

Fixes #177: handle responses of manual params in grouped_xai_expanded#178

Merged
Nikronic merged 4 commits intomasterfrom
fix177
Dec 24, 2023
Merged

Fixes #177: handle responses of manual params in grouped_xai_expanded#178
Nikronic merged 4 commits intomasterfrom
fix177

Conversation

@Nikronic
Copy link
Copy Markdown
Owner

@Nikronic Nikronic commented Dec 23, 2023

Fixes #177

Summary:

  • catch manual params: similar to other endpoints, it is required to catch manual params and remove them, hence preprocessing and ML models can work with the original training set.
  • add pretty print of manual params response: this is particularly useful when integrated with grouped_xai_expanded endpoint, where each response of each parameter takes a XAI value and grouped together.
  • add manual params responses to grouped_xai_expanded: since manual params didn't have XAI values per response in the original output of XAI, we couldn't report based on the given response the importance. Now, even these manual params are added to original XAI values, and we can report them like others. Note that these values are constant and won't change based on the change of other values.
  • add ability to use a human-readable description for params: when reporting XAI values, the name of the parameter and chosen response is concatenated and reported alongside the XAI value (or importance in case of manual params). In some cases, these values are not human-readable and needs to be replaced by a descriptive one. Now, attribute description is doing that. For domain-specific manual params, these human-readable descriptions have been provided yet can be overridden on-the-fly by the user.

this is particularly useful when integrated with `grouped_xai_expanded` endpoint where each response of each parameter takes a XAI value and grouped together.
since manual params didnt have XAI values per response in the original output of XAI, we couldnt report based on the given response the importance. Now, even these manual params are added to original XAI values and we can report them like others. Note that these values are constant and wont change based on the change of other values
@Nikronic Nikronic linked an issue Dec 23, 2023 that may be closed by this pull request
@Nikronic Nikronic changed the title Fixes #177: handle responses of manual params in grouped_xai_expanded WIP: Fixes #177: handle responses of manual params in grouped_xai_expanded Dec 23, 2023
when reporting XAI values, the name of the parameter and chosen response is concatenated and reported alongside the XAI value (or importance in case of manual params). In some cases, these values are not human readable and needs to be replaced by a descriptive one. Now attribute `description` is doing that. For domain-specific manual params, these human-readable descriptions have been provided yet can be overriden on-the-fly by the user.
@Nikronic Nikronic merged commit 514eb87 into master Dec 24, 2023
@Nikronic Nikronic deleted the fix177 branch December 24, 2023 07:02
@Nikronic Nikronic changed the title WIP: Fixes #177: handle responses of manual params in grouped_xai_expanded Fixes #177: handle responses of manual params in grouped_xai_expanded Dec 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

grouped_xai_expanded is not handling manual params

1 participant