Lesson 6.3Lesson 6.3 · Data & Analysis
Simulation & Analysis
A simulation lets you watch a possible city move before you build it - genuinely illuminating for some things, and a seductive false prophet for others, because all models are wrong
A simulation shows you a city that does not exist yet moving as if it did - which is exactly why it is so easy to believe.
There is nothing quite as persuasive as a simulation. Little dots stream along the streets you designed; traffic backs up or flows; a wind study paints the gusts around your towers; the sun rakes across a square hour by hour. It looks like a window onto the future, and audiences believe it the way they believe a photograph. That persuasiveness is the whole problem, because a simulation is not a window onto the future. It is a deliberate simplification of reality, built on assumptions, that can only show you the consequences of the rules you put into it.
This lesson takes simulation seriously as a genuinely valuable tool and refuses to be seduced by it. We separate the kinds - pedestrian and crowd, traffic, agent-based, environmental - and, crucially, grade how much to trust each, because a sunlight study and a twenty-year land-use forecast are not the same kind of claim at all. Running through it is the statistician George Box's warning, which applies to cities with special force: all models are wrong, some are useful. The skill is knowing which, and for what.
Sun/wind (physics) = trust it. Traffic/pedestrian = useful but bounded. Agent-based long-horizon = think with, don't decide with. All models are wrong, some useful. Cities adapt to forecasts (induced demand). Simulate to compare, not to prophesy.
What we simulate, and how it works
Urban simulation spans a family of methods, and it helps to see them as a range from the physical to the human, because trust falls as you move along it. Environmental simulation models physical processes on and around urban form: how sunlight and shadow fall across a square through the day and year, how wind accelerates between towers (computational fluid dynamics), how heat builds in a street canyon, how noise propagates, how stormwater flows. Because these obey well-understood physics, they are the most reliable kind of urban simulation - genuinely useful for shaping massing, orientation, open space and comfort.
Pedestrian and crowd simulation models how people move on foot through a space - flows along a street, congestion at a station concourse, evacuation from a stadium. It is valuable for the physical mechanics of movement, especially safety-critical crowd questions, though it rests on assumptions about how people choose paths and respond to density that are only ever approximate. Traffic simulation models vehicles on a network - queues, junction performance, the effect of a new road or signal timing - and is long-established and useful for engineering questions, while carrying a famous trap we return to.
Agent-based modelling is the most ambitious: populate a model with many autonomous *agents*, each following simple behavioural rules, and let large-scale patterns *emerge* from their interactions. It is the natural tool for a city understood as a complex system, and it can illuminate how simple individual behaviours produce collective outcomes - segregation patterns, the spread of an epidemic, the rhythm of a market. It is also the method whose outputs depend most delicately on assumptions you can neither fully justify nor validate: change the agents' rules a little and the emergent city can change a lot. Across all four kinds, the same structure holds - a model is a set of rules and assumptions about how the world works, run forward to show their consequences. It is only ever as good as those assumptions, and it can only compute what it was told to represent.
All models are wrong, some are useful
The statistician George Box's line - all models are wrong, but some are useful - should hang over every urban simulation, and it is not a throwaway. It is *literally* true. Every model is a simplification; it leaves things out by design, because a model that left nothing out would just be the city itself. So the question is never 'is the model right?' - it is always wrong in the strict sense - but 'is it wrong in ways that still make it useful for this particular question?' A sunlight model ignores almost everything about a city and is extremely useful for whether a park will be in shadow, because the thing it does represent - solar geometry - is exactly what the question turns on. The same model is useless for whether the park will be loved.
Cities push this maxim to its limit for a specific reason: a city is a complex adaptive system, and it does the one thing models hate most - it *adapts to the model's own predictions*. The sharpest example is induced demand in traffic: simulate that a new road will ease congestion, build it, and the extra capacity attracts new trips that were not made before until the road fills up again - so the confident forecast is falsified by the very behaviour it failed to include. People are not particles; they respond, learn, game the system and change their choices, which means human-behaviour simulations are forecasting a target that moves *because* you forecast it. Physics does not do this - the sun will not change its path because you modelled it - which is exactly why environmental simulation is more trustworthy than behavioural.
The discipline that follows is not to abandon simulation but to hold it correctly. Know what each model leaves out and whether those omissions matter for your question. Trust physics-based models more than behaviour-based ones, and short horizons more than long ones. Validate against reality wherever you can - does the model reproduce the present before you trust it on the future? Run scenarios and compare options rather than seeking a single precise prediction; simulation is far better at 'which option is better and why' than at 'exactly what will happen'. And treat every simulation as an argument to be interrogated, not a fact to be accepted, however convincing the animation.
How much to believe each kind
Because 'all models are wrong' is true but not equally true, the practical skill is *grading* trust, and the grading is fairly stable. Put simulations on a rough ladder of credibility. Near the top sit physics-based environmental models - sunlight and shadow above all, which is essentially deterministic geometry you can bank on; then wind, thermal and noise studies, reliable in trend and direction though sensitive to setup and boundary conditions. These earn real weight in design decisions because what they omit rarely changes the answer.
In the middle sit traffic and pedestrian models. They are useful and well-established for bounded engineering questions - junction capacity, concourse crowding, evacuation times - where behaviour is constrained and short-horizon. But their behavioural assumptions make them shakier than physics, and the longer the horizon and the more the model's own outputs would change behaviour, the less to trust them; induced demand is the standing warning that a plausible traffic forecast can be confidently wrong.
Near the bottom for predictive confidence sit long-horizon behavioural and agent-based models - land-use and transport forecasts decades out, models of how neighbourhoods will change, property values, or social outcomes. This is not to dismiss them: agent-based models are superb for *insight* - for understanding how mechanisms work, exploring 'what kinds of things could happen', and building intuition about a complex system. But as *predictions* of what a specific city will actually do years hence, they carry deep uncertainty, because small changes in unvalidated assumptions produce large changes in outcome, and the system adapts. The rule of thumb: the more a model depends on human choice and the further out it reaches, the more you use it to *think with* and the less you use it to *decide with*. There is a second axis to watch alongside the horizon: how tightly the thing modelled is constrained. An evacuation down a fixed corridor in the next ninety seconds is highly constrained and fairly predictable; where people will choose to live and work in twenty years is wide open and barely predictable at all, however sophisticated the agents. Match the weight you give a simulation to where it sits on both axes - and never let a beautiful animation earn a model more trust than its assumptions deserve.
Using simulation honestly
Put the discipline into practice. First, be explicit about assumptions. Every simulation rests on inputs and rules - demand levels, behaviour models, boundary conditions, what is held fixed - and the credibility of the output is entirely inherited from them. State them, show how sensitive the result is to the shaky ones, and if the honest answer is 'the outcome flips when we change an assumption we cannot justify', that fragility *is* the finding. A simulation with hidden assumptions is not evidence; it is theatre, and the more polished the animation the more urgently the assumptions behind it need to be dragged into the light.
Second, validate and calibrate against reality wherever you can. A model that cannot reproduce the city as it is has no claim on the city as it might be. Where validation is impossible - as it often is for long-horizon behavioural models - say so plainly and downgrade the model from prediction to exploration. Third, use simulation comparatively. Its real strength is not a precise crystal-ball number but a structured comparison: this street layout floods less than that one, this massing gives the square two more hours of winter sun, this network spreads movement more evenly. Relative, like-for-like comparison under the same assumptions is far more robust than any absolute forecast, and it is usually what the design decision actually needs.
Finally, keep the boundary the whole course insists on. A simulation is an input to human judgement and public debate, not a substitute for them, and its persuasiveness makes this discipline more important, not less, because a convincing animation can stampede a decision. Present simulations with their assumptions and uncertainties visible, use them to open options and inform argument, and keep the binding decisions - about land, transport, displacement and a city's future - with the planning authority, the statutory and participatory process, the affected communities and the governing law, in India the master-plan process, the applicable DCR and the National Building Code of India. Simulate to illuminate and to compare; never to prophesy, and never to launder a decision as a forecast.
All models are wrong, some useful
The governing maxim
Every simulation is a simplification; ask not 'is it right?' but 'is it wrong in ways that still help this question?'. Interrogate the assumptions, not the animation. Modules 6.3, 9.3.
Grade trust: physics over behaviour
How much to believe each kind
Environmental (sunlight, wind) most trustworthy; pedestrian and traffic useful but bounded; long-horizon behavioural and agent-based models are to think with, not decide with. Modules 6.3, 5.2.
Cities adapt to their forecasts
Why behavioural models are treacherous
A complex adaptive system responds to predictions - induced demand is the classic case, where a road forecast to cut congestion fills with induced trips. People are not particles. Modules 6.3, 9.3.
The binding choice is democratic
Simulation informs, it does not decide
State and validate assumptions, use models comparatively, report uncertainty; keep decisions on land, transport and displacement with the process, communities and law - in India master-plan, DCR, NBC India. Modules 7.3, 7.4.
Workshop — grade a simulation you have seen
Take a simulation or model-based claim you have encountered - a traffic study, a crowd-flow visual, a growth forecast, a wind or sun study - and interrogate it. The aim is to practise separating what a model can genuinely tell you from what its persuasive surface only appears to.
A real simulation or model-based claim and a notebook. No simulation software needed - the skill here is critical reading of models; the simulation tools come later, and the binding urban decisions always stay with the planning authority, the community and the democratic process.
Goal: read a simulation critically rather than believe it Inputs: a real simulation or model-based claim (from a project, news story or report) + a notebook Time: ~40 minutes
- 1Name the model: what kind is it (environmental, pedestrian, traffic, agent-based), and what exactly does it claim - a comfort result, a flow, a forecast?
- 2Place it on the trust ladder: is it physics-based or behaviour-based, short-horizon or long, bounded or open? Where does that put its credibility?
- 3List the assumptions: what must be true for the result to hold - demand levels, behaviour rules, what is held fixed - and which of these are shaky?
- 4Test for adaptation: would the city change its behaviour in response to the very thing the model predicts (induced demand-style)? If so, how does that undermine the forecast?
- 5Rewrite the claim honestly: restate what the simulation can legitimately support and what it cannot, and note how you would use it - to compare options and inform debate, with the binding decision left to the process - flagged as reasoning.
You’ll walk away with
A one-page critical read of a real simulation: its kind and claim, its position on the trust ladder, its key assumptions and their fragility, a check for adaptive response, and an honest restatement of what it can and cannot support. Keep it as a template for reading any model-based claim.
Three altitudes on the same idea
Read the band that fits you — or all three.
For the architect or urban designer, simulation is a genuinely powerful way to test how a scheme will perform - and its persuasiveness is a danger you must actively manage, because a convincing animation can win an argument it has not earned. Trust physics-based environmental models most - sunlight above all, then wind, thermal and noise - and lean on them to shape massing, orientation and open space. Treat pedestrian and traffic models as useful for bounded, short-horizon questions, and long-horizon behavioural and agent-based models as tools to think with, not decide with. Use simulation comparatively - which option performs better under the same assumptions - rather than as a precise forecast, always state and stress-test your assumptions, and validate against reality where you can. Present results with their uncertainty visible, and keep the binding decisions with the planning authority, the participatory process and the affected communities. Simulate to illuminate; never to prophesy.
For the planner or urbanist, simulation can strengthen the evidence base and let you test scenarios - and it is most dangerous exactly where planning reaches furthest, because a long-horizon behavioural forecast can dress deep uncertainty as objective prediction. Environmental and bounded engineering simulations genuinely inform decisions; but a traffic forecast can be confidently wrong (induced demand), and a decades-out land-use or social model is exploration, not prophecy, because the city adapts to the very predictions you make. Insist that assumptions be explicit and stress-tested, that models be validated against the present, and that uncertainty be reported as a first-class result. Use simulation comparatively and to open options for public debate, never to close it down with a single confident number. Keep the binding decisions with the statutory process, the communities and the law - the simulation is an argument to interrogate, not a fact to accept, however persuasive the animation.
Learn to admire a simulation and distrust it in the same breath. The kinds run from physical to human: environmental (sun, wind, heat, noise, water), pedestrian and crowd, traffic, and agent-based - the last populating a model with many rule-following agents so large-scale patterns emerge. The maxim to carry is George Box's: all models are wrong, some are useful - every model is a simplification, so the question is never 'is it right?' but 'is it wrong in ways that still help this question?'. Cities strain the maxim because they are complex adaptive systems that adapt to their own forecasts - the clearest case is induced demand, where a new road predicted to cut congestion fills up with newly induced trips. So trust physics over behaviour, short horizons over long, and validate against reality. Use simulation to illuminate mechanisms and compare options - to think with - not to prophesy, and never let a beautiful animation earn more trust than its assumptions deserve.
“A good simulation shows us what the city will actually do. If the model is detailed and well-built - realistic agents, real network data, validated components - then its prediction of traffic, movement or growth is essentially a preview of the future we can plan on with confidence.”
Do it yourself
No software needed — reason it through.
- 1Name the main kinds of urban simulation and order them from most to least trustworthy as predictions, explaining why.
- 2What does 'all models are wrong, some are useful' actually mean, and why is 'is it right?' the wrong question?
- 3Explain induced demand and why it shows a city adapting to its own forecast - and why physics-based models do not suffer this.
- 4Why can a more detailed, realistic simulation sometimes be more misleading than a crude one?
- 5What does it mean to use simulation comparatively rather than predictively, and why is that usually more robust?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Simulation — Wikipedia — Simulation, 2026.
- 02Agent-based model — Wikipedia — Agent-based model, 2026.
- 03Complex adaptive system — Wikipedia — Complex adaptive system, 2026.
- 04Emergence — Wikipedia — Emergence, 2026.
- 05Cellular automaton — Wikipedia — Cellular automaton, 2026.
Data, network analysis and simulation all produce evidence - but evidence does not design a city; a person does. The last lesson of the module asks the hardest question: how do you turn analysis into form honestly, without letting the analysis launder a decision you had already made?
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →