The systems
Nine small parts, each with one job
I build Situ as small systems, made to inform the design of a game (research-creation). Each has one job, a blueprint and its own tests, and I try it in the Lab before the next one may use it. The status word says how far each one stands (what the words mean).
| System | Job | Status | More | |
|---|---|---|---|---|
| Walking network | Add the city’s off-street paths before space syntax is calculated | verified, by the checks in its report | how it is built | |
| S1 | Streets | Which streets connect, and who may use them in which direction | verified | how it is built, checks on photos; in the Lab |
| S2 | Scores | Attach the space syntax values to each street | verified | how it is built; in the Lab |
| S3 | Rules | Stop signs, traffic lights, forbidden turns, speed limits | verified | how it is built, checks on photos; in the Lab |
| S4 | Buildings | What each building is, and where a walker reaches it | verified | how it is built; in the Lab |
| S5 | Rhythm | When the streets are busy, and which places say they are open | verified | how it is built; in the Lab |
| S6 | Streetscape | What stands on the streets: trees, hydrants, lights, cameras, crossings, sidewalks, benches, road works | verified | how it is built; in the Lab |
| S7 | Commuters | How people commute and when, and how far homes are from transit | verified | how it is built; in the Lab |
| S8 | Views | What a walker can see from each point of the streets | verified | how it is built; in the Lab |
| S9 | Observer | Imagines people moving from what the other systems say, and compares them with the counts and space syntax | partial: commuters on foot on a weekday morning; drivers planned | how it is built; in the Lab |
Each system has an overview page, which says what it found, and a page on how it is built and tested. The job each one does in a game is on From systems to a game. To follow one number from its source to the Lab, see Tracing a result.
Reading the diagrams
Every blueprint uses the same key. A grey outline is data coming in. A dashed grey one is a decision I made and kept in a file. A white outline is a processing step, and a thick white one is a result written to disk. Pink marks a test.
On the map sheets, labels never overlap. When a label has to move, a thin line points back to what it names.