Closed Bug 721434 Opened 14 years ago Closed 13 years ago

A11Y_CONSUMERS histogram shows 100% for 2 bars

Categories

(Mozilla Metrics :: Frontend Reports, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME
Unreviewed

People

(Reporter: vladan, Assigned: paulo.pires)

Details

(Whiteboard: [Telemetry])

I might be misinterpreting the chart, but it looks like the A11Y_CONSUMERS histogram covering 2011/01/01-Today has 2 buckets with 1 sample each, yet the histogram bar for each bucket is 100%. Is this a bug?
Note: I confirmed with Marco Zehe that running both NVDA (value 0) and Jaws (value 1) simultaneously should not happen much if at all in the wild.
The normalization is wrong, we'll fix it. But what that means is that it's a 50% / 50% situation. What filters are you using?
(In reply to Pedro Alves from comment #2) > What filters are you using? I was using the default filter settings (AppName="Firefox", everything else blank or "All")
I dont know what the values mean - is it unexpected to have them in the same order of magnitude?
It's fixed now, we have a result of (0,1), (1,1), (2,0) so the bars are equal. All the data is normalized correctly.
Assignee: nobody → paulo.pires
(In reply to Pedro Alves from comment #4) > I dont know what the values mean - is it unexpected to have them in the same > order of magnitude? Each value represents the presence of a known distinct screen reader injected dll into our process space. There are 7 possible values right now.
(In reply to Paulo Pires from comment #5) > It's fixed now, we have a result of (0,1), (1,1), (2,0) so the bars are > equal. > All the data is normalized correctly. Looks right. We don't really know what distribution to expect other than values 0 and 1 should dominate. One thing I'd like to be able to do is plot a line graph for each value 0 through 6, over time. Is that something I can do today?
Group: metrics-private
Whiteboard: [Telemetry]
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Version: 1.0 → unspecified
You need to log in before you can comment on or make changes to this bug.