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
Reasons behind identified outcomes #123
Comments
Is this a duplicate of #14? Both seem to capture the requirement that the system explain itself. |
This is broader than #14 (which focuses solely on displaying the precedents used), and better articulated as a user story. |
What are the outcomes in the context of this story? Are they predicted outcomes of a judgement (i.e. 500$ punitive damage, 200$ restitutionary damages) or are they avenues of resolution that they system will "recommend" to the user (i.e. you should go to small claims court, you should send a cease and desist letter, etc)? |
Predicted outcomes of the judgment
…On Nov 2, 2017 5:57 PM, "Arek Manoukian" ***@***.***> wrote:
What are the outcomes in the context of this story? Are they predicted
outcomes of a judgement (i.e. 500$ punitive damage, 200$ restitutionary
damages) or are they avenues of resolution that they system will
"recommend" to the user (i.e. you should go to small claims court, you
should send a cease and desist letter, etc)?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Aexl3Yj6GV0D0GHfrcaDbFwYAv3Rsal_ks5syjrmgaJpZM4QO9xU>
.
|
Further discussions will be needed concerning this story |
This paper explains how to achieve trust in model predictions: https://arxiv.org/abs/1602.04938 Relevant to the story |
Description
As a user, I would like to understand why the system retains a given outcome
Scope of Work
Story Points
Priority
Risk
Demo requirement
Acceptance Criteria
Documentation, files, diagrams, etc. relating to this feature:
N/A
Changes:
The text was updated successfully, but these errors were encountered: