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 #29

Closed
kywalker-rh opened this issue Apr 14, 2023 · 3 comments
Closed

Explainability #29

kywalker-rh opened this issue Apr 14, 2023 · 3 comments
Assignees
Labels
feature/explainability Model monitoring - Feature Tracker High-level issue that compiles other issues within it - like a Jira Epic

Comments

@kywalker-rh
Copy link

kywalker-rh commented Apr 14, 2023

@jkoehler-redhat
Copy link

Is a May 31 completion date for the UX still doable? My understanding is there are other changes that need to happen and this date may change?

@vconzola
Copy link
Collaborator

I'm not sure given the recent architecture change. I need to get up with @RobGeada about what exactly the UX requirements are for supporting the TrustyAI operator in each project. If it's as simple as asking the user if they want/need to monitor their models for quality and fairness in a given project, that's likely not too bad. If it involves additional operator configuration, that will be a little trickier.

@vconzola
Copy link
Collaborator

@jkoehler-redhat I pinged Rob about this. He said that "for Phase 1 it will be simply "yes/no I want monitoring" for models in this project, and we can deal with more advanced configs later". So given that, I believe the UX should be pretty simple and 5/31 is reasonable unless someone on the RHODS side expects more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/explainability Model monitoring - Feature Tracker High-level issue that compiles other issues within it - like a Jira Epic
Projects
Status: UX
Status: UX Done
Development

No branches or pull requests

4 participants