Lesson 5.3Lesson 5.3 · Daylighting Simulation
Climate-Based Daylight Modelling
Swapping one grey overcast sky for a full year of real skies - and the daylight-coefficient trick that makes an 8760-hour simulation feasible
A building does not live under one grey sky - it lives under 8760 different ones. Climate-based daylight modelling simulates them all.
The daylight factor asks one question under one fixed overcast sky. But a real room in Jaipur meets low winter sun, high summer sun, monsoon overcast and clear blue, hour after hour, all year. Climate-based daylight modelling (CBDM) replaces that single snapshot with the actual sequence of skies from the location's EPW weather file - and only then can it compute sDA, ASE and UDI.
The obvious worry is cost: surely simulating 8760 hours is 8760 times the work? The elegant answer is no. A method called daylight coefficients lets you do the heavy ray tracing once and then reuse it against every hour of sky - which is exactly why annual daylighting is now routine rather than exotic.
Trace the room ONCE. Multiply by every hour's sky. 8760 answers, minutes of compute.
From one sky to a whole year
The defining move of CBDM is the sky. Instead of the daylight factor's single, sunless CIE overcast sky, CBDM drives the simulation with a time series of real skies - one for every daylight hour of a typical year - reconstructed from the location's EPW file, which carries hourly direct-normal and diffuse-horizontal irradiance measured or modelled for that place.
Each hour's sky is generated with a model such as the Perez all-weather sky, which turns those two irradiance numbers into a realistic luminance distribution: where the sun sits, how bright the circumsolar region is, how the rest of the dome grades. The two inputs deserve a moment: direct-normal irradiance is the beam straight from the sun's disc (what a tracker pointed at the sun would see), and diffuse-horizontal irradiance is the scattered light from the rest of the sky dome. A clear day is beam-dominated and produces a bright circumsolar hot spot - the source of most glare and direct-sun ASE hours - while an overcast monsoon hour is almost all diffuse, giving a soft, sourceless sky. The Perez model reads that ratio hour by hour and shapes the dome accordingly, which is precisely why CBDM can tell a harsh clear afternoon from a gentle grey morning.
Sum or sequence 8760 of these and you have captured what the daylight factor cannot - orientation (a south room and a north room now differ), season (December's low sun versus June's high sun), local climate (Bangalore's mildness versus Delhi's clear harsh sun), and the sun itself, present in most hours. This is why every metric in Lesson 5.1 that carries a percentage-of-hours (sDA, ASE, UDI) is by definition climate-based: the hours only exist because CBDM simulated them. A daylight-factor world simply has no clock to count against.
CBDM sky = 8760 real skies from the EPW. DF sky = 1 grey overcast. That's the whole difference.
The daylight-coefficient idea - simulate once, reuse 8760 times
Running Radiance from scratch for every one of 8760 hours would be brutally slow. The breakthrough that made annual daylighting practical is the daylight-coefficient (DC) method. The insight: the room's optical response - how a given patch of sky ends up contributing light to a given sensor - is a fixed property of the geometry and materials. It does not change hour to hour; only the sky's brightness does.
So the method splits the sky dome into a manageable number of patches (a common Tregenza subdivision uses 145 patches, plus the sun). It then runs the expensive ray tracing once to find each sensor's coefficient for each patch - essentially 'if this patch alone glowed at unit brightness, how much light reaches this point?'. That produces a daylight-coefficient matrix. From then on, computing any hour is just fast arithmetic: multiply the fixed coefficients by that hour's patch brightnesses (from the Perez sky) and sum. The heavy physics is paid once; the 8760 hours are cheap multiplications. This 'simulate the room once, apply every sky' factoring is the conceptual heart of CBDM - and the reason a full annual illuminance run finishes in minutes, not days.
The three-phase method - so blinds and glazing can vary
The basic DC method treats the whole light path in one step, which is fine for a fixed room but awkward when the interesting part - the glazing or shading - is exactly what you want to change or operate. The three-phase method solves this by splitting the light's journey into separable stages, each its own matrix: D (a daylight matrix, sky patches to the outside of the window), T (a transmission matrix describing the glazing or blind system itself, via its bidirectional transmittance), and V (a view matrix, from the inside of the window to the sensors). The annual result is these multiplied together against the sky series: roughly V x T x D x sky.
Why bother? Because the T matrix isolates the fenestration. You can swap in a different blind, a fritted glass or a complex daylight-redirecting system - or operate the blind hour by hour - by changing only the small T matrix, without re-running the expensive interior and exterior calculations. This makes it the standard for studying switchable glazing, venetian blinds and complex fenestration across a year. You will not build these matrices by hand; Honeybee and ClimateStudio assemble them for you. But knowing the path is split at the glazing explains why annual shading studies are feasible and how tools model operable blinds - the exact controls Lesson 5.4 leans on for glare.
Why annual beats a snapshot - and its honest limits
The payoff of all this machinery is judgement you can trust. A single daylight-factor snapshot can be actively misleading: a north-lit studio and a south-lit one can post the same DF, yet the south room delivers far more usable annual daylight (and more glare risk) - a difference only an annual model reveals. Because CBDM counts real hours, it directly answers the questions clients and codes ask: for how much of the working year is this desk usefully lit? How many hours does that west wall get blasted? That is why LEED, IES LM-83, the Well standard and green-rating daylight credits worldwide have shifted decisively from DF to CBDM-based sDA/ASE.
Be honest about the limits, though. CBDM inherits the uncertainty of its weather file - a 'typical' year, not next year, and often from the nearest station, not your exact site (a real issue for Indian locations with sparse EPW coverage). Its realism depends on the sky model and on honest material and geometry inputs, just like any simulation. And it remains decision-support: superb for comparing options and demonstrating a target, but the absolute hours carry error bars, and statutory daylight compliance still defers to the relevant code and authority. Used well - comparatively, with sensible weather data - CBDM is the most defensible daylight prediction available, and the foundation of everything else in this module.
From an annual run to a design decision
It is worth walking one full loop, because CBDM is only valuable if it changes a drawing. Suppose you are testing a 10 m-deep open studio in composite-climate Delhi with a south facade, and the question is window height and overhang depth. You download the Delhi EPW, build the room in Honeybee, assign honest reflectances (ceiling 0.8, walls 0.5, floor 0.2) and a clear glazing VT of 0.65, drop a 0.5 m sensor grid, and run the annual daylight recipe. The daylight-coefficient method traces the room once and evaluates all 8760 hours in a couple of minutes, returning an sDA of, say, 64% and an ASE of 22% - daylit, but glary and over-sunned, well past the 10% ASE guard.
Now you iterate, which is the entire point of a fast annual method. Add a 0.6 m overhang: ASE drops toward 12%, sDA barely moves because the overhang mostly clips high summer sun. Add interior venetian blinds operated on a schedule - here the three-phase method earns its keep, because only the small T matrix changes, so the re-run is nearly free - and ASE falls under 10% while sDA holds near 60%. Raise the window head by 300 mm and the back third of the room lifts, nudging sDA to 68%. In four cheap runs you have converged on a section that satisfies sDA >= 55% and ASE <= 10% - a defensible, evidence-backed decision no daylight-factor snapshot could have produced. That loop - model once, vary the option, read the annual metric, decide - is the working rhythm of climate-based daylighting, and it is exactly why the coefficient and three-phase machinery was worth understanding.
Model once, then iterate cheaply: overhang, blind, window head. 4 runs -> a defensible section.
CBDM
Climate-based daylight modelling - annual simulation against real skies
Uses the EPW's hourly weather instead of one overcast sky; the basis of sDA, ASE and UDI.
EPW weather file
Typical-year hourly climate data for a location
Supplies the direct and diffuse irradiance that build each hour's sky. Result is only as representative as the file.
Daylight coefficients
Fixed per-sensor response to each sky patch
Computed once by ray tracing, then reused against every hour - what makes annual runs fast.
Perez all-weather sky
Model turning two irradiance values into a sky luminance map
Reconstructs realistic sun-and-sky distributions per hour from the EPW; the standard CBDM sky generator.
Three-phase method
Splitting the light path into D, T and V matrices
Isolates the glazing/blind (T) so operable shades and complex fenestration can be studied annually.
Workshop - reason about an annual daylight study
You will compare what a daylight-factor snapshot and a climate-based annual run each tell you about the same two rooms, and see why the annual result is worth the extra machinery.
Paper and reasoning. To run it, free: download the city's EPW from the EnergyPlus weather site and use Ladybug/Honeybee's annual daylight recipe (or ClimateStudio).
Goal: articulate what CBDM captures that a daylight factor cannot, on a concrete case Inputs: two imagined rooms - identical geometry, one facing north, one south - a notebook Time: ~30 minutes
- 1State the daylight factor result: since DF uses a sunless overcast sky, what would the two rooms' DFs be relative to each other, and what does that (fail to) tell you?
- 2Now switch to CBDM: describe qualitatively how the annual illuminance of the south room differs from the north across a year - think winter sun, summer sun, monsoon overcast for an Indian city of your choice.
- 3Predict the sDA and ASE ordering: which room has higher sDA, which has higher ASE, and why the daylight factor could not have distinguished them.
- 4Explain, in two sentences, the daylight-coefficient trick that let the tool compute both rooms' 8760 hours quickly.
- 5Decide: if the south room's ASE is too high, name one shading change and explain how the three-phase method would let a tool test an operable-blind version cheaply.
You’ll walk away with
A one-page comparison showing why two rooms with the same daylight factor behave differently over a real year, with predicted sDA/ASE ordering and a note on the coefficient and three-phase methods that made the annual study feasible.
Three altitudes on the same idea
Read the band that fits you — or all three.
CBDM is what lets you defend an orientation or a shading depth with a year of evidence, not a grey-sky ratio. Because it captures sun, season and local climate, it exposes the real differences between massing options that the daylight factor hides. When a reviewer asks 'how did you daylight this?', an annual sDA/ASE study from the site's EPW is the answer that holds up.
Annual modelling is how you prove a layout works through the whole year, not just at noon in June. It shows the winter-afternoon gloom or the summer-morning glare a snapshot misses - the very moments occupants complain about. Your finishes and blind strategy feed straight into the model, and the three-phase method is exactly what lets a tool test an operable-blind scheme.
'Climate-based daylight modelling' and 'daylight coefficients' are consultant vocabulary - use them correctly and you stand out. You do not need to derive the matrices; you need to explain why an annual EPW sky beats one overcast sky, and why the coefficient trick makes 8760 hours cheap. A studio project with a real annual daylight study reads as professional immediately.
“Simulating a whole year of daylight must take 8760 times as long as a single run.”
Do it yourself
Reason it through - the concepts matter more than the maths.
- 1In one sentence, what does CBDM replace, and with what?
- 2What two irradiance quantities from the EPW build each hour's sky, and via which sky model?
- 3Explain the daylight-coefficient trick that avoids re-tracing 8760 times.
- 4What does the three-phase method's T matrix isolate, and why is that useful?
- 5Give one honest limitation of a CBDM result.
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Daylighting — Wikipedia, 2026.
- 02EnergyPlus Weather Data (EPW files) — US Department of Energy, 2026.
- 03Radiance - Lighting/daylight simulation — LBNL, 2026.
- 04Ladybug Tools - Environmental analysis for Grasshopper — Ladybug Tools LLC, 2026.
- 05Sun path — Wikipedia, 2026.
CBDM gives us illuminance for every hour and point - which is exactly what we need to catch not just darkness but excess brightness. Next we turn to glare and visual comfort: how too much daylight becomes a problem, and how DGP measures it.
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 →