Closed
Bug 1062453
Opened 10 years ago
Closed 10 years ago
create analyzer view for examining classification data
Categories
(Input Graveyard :: Backend, defect)
Input Graveyard
Backend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: u=dev c=spam p=2 s=input.2014q3)
The spicedham classifier will be classifying incoming feedback responses. We need a way to examine the results and also mark correctness. This bug covers: 1. create an analyzer view that pulls from mysql and shows response and flag data 2. add ui bits to mark whether the classifier is wrong (spam-wrong, abuse-wrong) Plus we need: 3. add section that summarizes percent right/wrong for the last 24 hours (not sure how this is going to work, yet) Note: This is purely for the purposes of integrating the spicedham prototype. We're not trying to design infrastructure that will be used outside of this specific need. After we figure out how things should work, it's expected we'll wipe away all this stuff and "start over".
Assignee | ||
Comment 1•10 years ago
|
||
In a PR: https://github.com/mozilla/fjord/pull/343 I didn't do item 3, yet. I think what we really want is to further restrict the view for a specified day so we can reason about all the responses for a given day.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•10 years ago
|
||
Making this 2 points because I had to fight with django-cache-machine and I still need to implement item 3 or something equivalent.
Whiteboard: u=dev c=spam p= s=input.2014q3 → u=dev c=spam p=2 s=input.2014q3
Assignee | ||
Comment 3•10 years ago
|
||
Landed in master: https://github.com/mozilla/fjord/commit/0411d912f359983468599cc528a00a5db2448081 Waiting to deploy until Monday.
Assignee | ||
Comment 4•10 years ago
|
||
Pushed to prod last night. Also, I added a set of counts that show total responses, number marked as abuse, number of false positives and number of false negatives since when we pushed the integration.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•