This is archived documentation.
Track Description Heuristic
- How many sections of track are there?
- A section is a continuous length of track.
- For each section:
- Where is its location relative to the screen.
- Establish a reference system for the screen: top, bottom, left, middle, right.
- If it overlaps another section in an interesting way, describe it.
- What is its general shape?
- top-bottom, left-right
- Common vocabulary for shapes: loops, hills, spikes, valleys, drops
- Common vocabulary for descriptors: gradual, gentle, steep, sharp
- Common vocabulary for physical size: large, medium, small
- Common vocabulary for direction: up, down, left, right, vertical, horizontal
Skater Movement Description Heuristic
- Where is the skater going?
- stereo sound for left / right location
- how do you represent up or down? Pitch?
- General labels read as the skater moves
- "Entering loop", or "Going up steep slope". Make this configurable - disabled by default and rely on sonifications initially.
- Use the same vocabulary used in the track description (see above)
- How fast is the skater going?
- Speed: sound of wheels (sonification) with noticeable "ticks" like cracks on the pavement / sidewalk. The more frequent the ticks, the faster the skater is moving. Sound should be like smooth, polished concrete.
- Skater states:
- Off the track
- use a distinct sound than the track surface. Perhaps something that sounds a bit rougher (like asphalt), but without the distinct ticks of the track?
Programmatic Track Analysis
Since we know the location of each section of track, it should be possible to programmatically generate track descriptions.
For example if X value repeats itself, and y-value goes from low to high, then you have a loop.