Closed Bug 966067 Opened 10 years ago Closed 10 years ago

Generalize framediff view into a visualization for all frame-by-frame analysis

Categories

(Testing Graveyard :: Eideticker, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

References

Details

(Keywords: perf, Whiteboard: [c=automation p= s=2014.03.14 u=])

Attachments

(1 file)

Right now Eideticker has a "framediff" view which lets you visualize the pixel difference between frames:

http://eideticker.wrla.ch/framediff-view.html?title=Frame%20Difference%20Startup%20to%20nytimes%20%282014-01-27%29&video=videos/video-1390910639.46.webm&framediff=framediffs/framediff-1390910657.66.json&actionlog=

We are now doing (and considering doing) all sorts of other interesting and wonderful calculations in Eideticker (e.g. to try to detect checkerboarding in b2g, we are considering calculating frame entropy). To validate that the results of this, we should allow different things to be graphed inside this view.
Keywords: perf
Priority: -- → P2
Whiteboard: [c=automation p= s= u=]
Going to make this depend on consolidating metadata, as keeping track of a zillion different files that we parse out of captures is becoming annoying.
Depends on: 966457
I know this is kind of a monster patch, but various refactorings were IMO necessary to keep things reasonable while I was working on this. Note that this changes the schema of the metadata a bit (to workaround a problem with the routing library that we use, of all things) so we will need to convert the existing dashboard data over before applying this.
Attachment #8387875 - Flags: review?(dave.hunt)
Attachment #8387875 - Flags: review?(dave.hunt) → review+
Whiteboard: [c=automation p= s= u=] → [c=automation p= s=2014.03.14 u=]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: