timeline

syllabus deadlines (cannot-be-changed deadlines)

December 6: draft of paper, video, possibly demo
December 13: final presentation (slides + talking); final paper, video, demo
December 16: post revised slides

...which motivate these internal deadlines

Due November 25

run a pilot usability study; make sure you know what to say for the real thing
find someone you can run the study on, someone who doesn't know what we've been doing, business or not, doesn't matter
figure out if Suhas can provide user study people: if so, schedule them

Starting November 25

put someone on paper writing: review (and improve) background literature, start writing intro/background
put as many people as possible on path aggregation / representation: see below for subdivisions

Due November 27

get complete dataset (populated, accessible) on remote server: this is non-negotiable; we need usable data for path aggregation

Thanksgiving: TAKE A (SHORT) BREATHER

Due December 4

Finish running all participants: paper-writing person, aggregate observations and (possibly) make pretty charts

Due December 5

preliminary path aggregation algorithm + display: can be buggy, in separate chunks, written hideously, but must be there
enough of the paper drafted to put someone on making slides (because the slides need to look nice, too): this means intro + background + usability study

Starting December 5

wrap up paper; same person, different person, doesn't matter, just have someone doing it
rush path aggregation; there's little else we need to do
put someone on slide-making duty

Due December 9

complete paper draft
complete presentation draft
95% of the interface: function > appearance; drop the 5% in in appearance

Starting December 9

start sprinting
put someone on polishing duty (ideally only CSS, but will realistically require JS fiddling)
put 1 person on test + bug fix duty (bugs are bad)
put 1 person on paper editing (typos are also bad)
put 1 person on presentation polishing (rehearse!)
put 1 person on whatever piece needs the most help

Due December 11: EVERYTHING

December 12: SLEEEEEEEP.

path aggregation tasks

algorithm: how to combine many paths into one branching path

Look at Stanford's. Use it, port it, modify it, doesn't matter &emdash; whatever's best.

2 people. Best case: try different algorithms (on separate git branches) and pick the one that works best.

zooming: framework; how to switch smoothly between levels of aggregation

Probably with kinetic, possibly with raw JS or jQuery. Design a way to load (and cache) different levels of path aggregation. Using layers, likely.

1 person.

aesthetics: how to make a clean, clear metaphor

This'll primarily be working with with kinetic.js. Figure out how to draw nice-looking arrows, paths, bezier curves, whatever.