One HTML page: 200 or more fans leaving a stadium section through one gate, every person running the same push-and-personal-space rules. Two known crowd results are on the table: rushing can empty a room slower than walking, and a column in front of a door can speed an exit up. The model predicts both for its own page in seconds, and the on-screen timer settles them through #urgency=…&gate=…&column=… presets.
Run #urgency=0.3&gate=1.2&column=0 to evacuation completion and record the timer. Run #urgency=0.9&gate=1.2&column=0 and compare. Check whether the sign and magnitude of the difference match the model's prediction.
Run #urgency=0.9&gate=1.2&column=1 and compare evacuation time against the non-column run. Check whether the column alters throughput in the direction predicted.
Inspect the gate bottleneck at urgency=0.9 without the column. Jams should form as arches across the gate that halt the outflow and then break. A smooth stream at every setting means the pushing does nothing; check whether the prediction said so.
Inspect agent separation in dense jams. Pause near the gate and look for overlapping people. Overlap is the cheapest shortcut in crowd simulation and the easiest to see.
Verify the flow-rate meter against visual egress. The people-per-minute readout should fall during a jam and rise when it breaks. A number that stays flat while the gate is visibly blocked is decorative.
Check agent count. At least 200 people was stated. A page with sixty is a miss whatever it looks like.
Read the code for anti-jam routines. Hardcoded teleportation or periodic force pulses not disclosed in the written sections place the result in the lowest score band.
You write crowd simulations where the behavior emerges from rules each person follows.
Build me a single HTML page: a section of a football stadium emptying through one exit gate.
#urgency=0.8&gate=1.2&column=1 starts simulation at load with those settings: urgency 0.0 to 1.0, gate width in yards, column 0 or 1. Any values work.data: URIs are fine.localStorage, sessionStorage, cookies or indexedDB — sandboxed frame, they throw.html block.Before the file, two quantitative predictions: whether increasing urgency from 0.3 to 0.9 increases or decreases evacuation time at gate=1.2 and column=0, with the predicted difference in seconds; and whether enabling the column (column=1) increases or decreases evacuation time at urgency=0.9 and gate=1.2, with the predicted difference in seconds.
The single fenced html block.
Where your crowd behaves like a real one and where it does not. Name anything you special-cased: a nudge that breaks a jam, a speed cap at the gate, an allowance for overlap. If your page never jams at the gate, say so.