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

feature attribution: adapt api for bounding box #17

Closed
fel-thomas opened this issue Apr 26, 2021 · 1 comment · Fixed by #85
Closed

feature attribution: adapt api for bounding box #17

fel-thomas opened this issue Apr 26, 2021 · 1 comment · Fixed by #85
Assignees
Labels
enhancement New feature or request feature-attribution New feature or issue concerning Attribution methods question Further information is requested
Projects

Comments

@fel-thomas
Copy link
Member

Add the ability to explain predictions using feature attribution on model that predict bounding box.
A state of the art and an inventory of the methods that could work is necessary before proposing a solution.

@fel-thomas fel-thomas created this issue from a note in Roadmap (April-June) Apr 26, 2021
@fel-thomas fel-thomas self-assigned this Apr 26, 2021
@fel-thomas fel-thomas added enhancement New feature or request feature-attribution New feature or issue concerning Attribution methods question Further information is requested labels Apr 26, 2021
@lucashervier lucashervier moved this from September - December 2021 to January - March 2022 in Roadmap Jan 27, 2022
@lucashervier lucashervier moved this from January - March 2022 to To Do ASAP in Roadmap Jan 27, 2022
@lucashervier lucashervier linked a pull request Jan 28, 2022 that will close this issue
@lucashervier
Copy link
Collaborator

The PR closed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature-attribution New feature or issue concerning Attribution methods question Further information is requested
Projects
Roadmap
To Do ASAP
Development

Successfully merging a pull request may close this issue.

2 participants