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

Explainability - Phase 1 #1127

Closed
andrewballantyne opened this issue Apr 14, 2023 · 5 comments
Closed

Explainability - Phase 1 #1127

andrewballantyne opened this issue Apr 14, 2023 · 5 comments
Assignees
Labels
feature/explainability feature/model-serving Model Serving Feature migrated tracker Non-completable ticket; used for tracking work - akin to a Jira Epic

Comments

@andrewballantyne
Copy link
Member

andrewballantyne commented Apr 14, 2023

Target Branch
f/mserving-metrics

Foundation Work

P0: Ability to navigate to a tab dedicated to model bias reporting for each served modelConfigured bias reports are unique to a served model.

P0: Ability to opt in to and configure bias detection for models already in production

Display message indicating model bias reporting is not configured
Provide option to configure bias metric reporting
Give users list of available fairness metrics
User to select a metric to monitor over the lifetime of the versioned model
Configure selected fairness metric, calculation and bias detection
User inputs the sensitive feature/group/label/column/facet and corresponding values applicable to their model
Default to Trusty-provided mathematically sensible baseline defaults and thresholds
Give user the ability to update thresholds to their preferred values
Configure metric resolution
User provided name for monitoring job
Allow user to schedule metric calculation job cadence
User has ability to update default interval
Button to save or cancel configuration
Store configuration state for use in dashboard
Configured dashboards persist over the lifetime of the served model version
Return to main page, ability to add new configuration
Allow user to configure multiple facets for any of their selected metrics For example, F1 and F2 for SPD, but only F1 for DIR

P0: Configured bias detection graphs over time

Clearly state the bias metric in the graph title
User can select which group/label/column to view from dropdown
User friendly description of monitoring job
Display calculated metrics over dates and time
Render baseline and threshold values and clearly indicate threshold violations
Ability to update the graph’s refresh rate
Adjust viewable time range, for example: 30 minutes to 3 days

P0: Ability to quickly reference bias detection documentation within product

Hover for description of metric and it’s usage

P0: Ability to update report as needed

User can update, add or remove metric configurations
User can add a metric configurations, same as above
User can remove/delete a configuration. Configuration instance will no longer be calculated nor displayed
User can update variables used in configuration instance. E.G.
User can update calculation resolution - 5000 -> 1000 observations
User can change threshold
Updates will recalculate and display new report
Current configuration persisted and used going forward

Additional Requirement [19/05/2023]:

User can add TrustyAI service per Data Science Project
User can edit TrustyAI service details
User can delete TrustyAI service per Data Science Project

Supplementary work

Additional issues raised

After incubation begins:

Dependent on:

@alexcreasy
Copy link
Contributor

Update: a PR has been raised for UWM (#1854) it is awaiting review and unblocks development of any remaining tickets for Explainability.

@alexcreasy
Copy link
Contributor

Update: development is in progress on the remaining issues.

@alexcreasy
Copy link
Contributor

Update: Still working through the last couple of issues, we have one new ticket before incubation, which is #2088

@dgutride
Copy link
Contributor

dgutride commented Dec 1, 2023

@dgutride
Copy link
Contributor

dgutride commented Dec 1, 2023

All subtasks migrated - moving tracker to closed

@dgutride dgutride closed this as completed Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/explainability feature/model-serving Model Serving Feature migrated tracker Non-completable ticket; used for tracking work - akin to a Jira Epic
Projects
Status: Done
Archived in project
Status: Dashboard
Development

No branches or pull requests

4 participants