The Simulation Tools Landscape

At the bottom of the stack sit the engines - the programs that actually solve the physics. For whole-building energy and comfort, the dominant free engine is EnergyPlus, developed by the US Department of Energy; it takes a fully-defined text model of a building and a weather file and computes hour-by-hour heat balances, loads and temperatures. For light, the reference engine is Radiance, from Lawrence Berkeley National Laboratory, a physically-based ray-tracer trusted for daylight and glare. These engines are rigorous, validated and free - but you rarely touch them raw. EnergyPlus's native input is a long structured text file; Radiance is a suite of command-line programs. Powerful, unfriendly.

So above the engines sit the interfaces: the tools that give you geometry, menus, defaults and readable output, and then quietly write the engine's input and parse its results for you. OpenStudio (from NREL) and DesignBuilder are interfaces to EnergyPlus; Ladybug and Honeybee drive both EnergyPlus and Radiance from inside Grasshopper; ClimateStudio drives Radiance (and more) inside Rhino. The engine does the maths; the interface makes it usable. Grasp this and the landscape stops being a jumble of names and becomes a two-layer stack: pick your engine by the physics you need, pick your interface by how you like to work.

For whole-building energy and thermal comfort, almost everything routes back to EnergyPlus. What differs is the interface. OpenStudio is NREL's free platform and SDK around EnergyPlus - powerful, scriptable, the backbone of a lot of professional and research work, though its learning curve is real. DesignBuilder is a polished commercial front-end: fast to build a model in, strong for ECBC/ASHRAE 90.1 compliance work, with good defaults and reporting - you pay for the smoothness. IES-VE is a comprehensive commercial suite with its own integrated engine (Apache) alongside dynamic thermal, daylight and airflow modules, common in large consultancies.

For early, iterative energy work, Honeybee (part of Ladybug Tools) wraps EnergyPlus inside Grasshopper, so you can spin a shoebox model from parametric geometry and test orientation or glazing ratio in minutes - free, visual, and made for the concept stage. The honest trade-off across this family is speed-of-setup and polish versus cost and openness: OpenStudio and Honeybee are free but ask more of you; DesignBuilder and IES-VE cost money but get you to a clean compliance model faster. None is 'best' - they share the same engine and mostly the same accuracy; they differ in workflow and price.

It is worth naming what 'polish' actually buys, because it is real. A commercial front-end ships tested constructions and system templates, catches input errors before they reach the engine, and generates the report an assessor expects to see - work you would otherwise do by hand in a free tool. On a fee-paying compliance job against a deadline, that time is money well spent. On a student project or an early comparative study, the same money buys nothing you cannot get free. The skill is knowing which situation you are in, and not paying for smoothness you will not use - or, conversely, not burning a week hand-assembling in a free tool what a paid template would have produced in an hour.

For daylight, glare and solar, the reference physics is Radiance, and again the interfaces differ. Ladybug handles climate, sun paths and solar radiation studies straight from an EPW file; Honeybee drives Radiance for daylight metrics such as spatial daylight autonomy (sDA) and annual glare - all free, inside Grasshopper. ClimateStudio (Solemma, the successor to DIVA) is a fast, polished commercial tool that also drives Radiance from Rhino, popular for its speed and clean daylight and glare reporting; it is a common professional choice where budget allows.

Beyond these, single-domain specialists exist for airflow - CFD tools such as OpenFOAM (free) or the CFD modules inside IES-VE and DesignBuilder - and dedicated lighting tools. The pattern repeats: a free, rigorous engine (Radiance, OpenFOAM) underneath, and a spectrum of interfaces above, from free-and-demanding to paid-and-smooth. For a student or a small practice, the Ladybug Tools stack alone - Ladybug, Honeybee, plus Butterfly for CFD - covers climate, energy, daylight, solar and airflow on free engines, which is why this course leans on it.

There is a strategic reason to prefer a single unified environment over a drawer full of separate programs. When climate, daylight and energy all run off the same Grasshopper geometry, a change you make once - a wall moved, a window enlarged - flows into every study without re-modelling, and the analyses stay consistent with each other. Stitching together five unrelated tools, each wanting its own geometry and its own file format, is where errors and wasted hours breed. Whichever ecosystem you settle on, value that coherence: a fluent workflow in one connected stack beats scattered fluency across many.

Two axes organise the choice. The first is free vs commercial. The engines are free; the free interfaces (OpenStudio, Ladybug Tools) are fully capable and used in real practice - the paid tools (DesignBuilder, IES-VE, ClimateStudio) buy speed, polish, support and streamlined compliance reporting, not fundamentally better physics. For learning, and for a great deal of professional work, free is genuinely enough.

The second axis is early-design vs detailed. Early tools favour speed and iteration over precision: a Ladybug or ClimateStudio study you can rerun in minutes as you push geometry around, ideal when the design is fluid and you are comparing options. Detailed tools favour completeness: a fully-specified OpenStudio or DesignBuilder model with real schedules, systems and constructions, slower to build but necessary for compliance submissions and final sign-off. The mistake is using the wrong one for the moment - a heavyweight detailed model on a concept that is still moving wastes days, while a rough early model presented as a final compliance figure oversells its precision. Match the tool to the design stage.

The two axes are largely independent, which is what makes the toolscape confusing at first. Free does not mean early, and commercial does not mean detailed: OpenStudio is free yet built for detailed work, while ClimateStudio is commercial yet prized for fast early studies. So you cannot choose on price alone or on stage alone - you locate a tool by both at once. Picture the map: fast-and-free in one corner for concept comparison, detailed-and-commercial in another for compliance, and real tools scattered in between. Knowing where each sits is what lets you reach for the right one without ceremony.

A last distinction: some tools answer one question well, others try to model the whole building. Radiance is single-domain - light, superbly. OpenFOAM is single-domain - airflow. EnergyPlus is whole-building - it couples the thermal zones, loads, systems and schedules so energy and comfort come out together, which is exactly what you need for an energy code path. Whole-building tools capture interactions a single-domain tool cannot (glazing that helps daylight but hurts cooling), at the price of more inputs and more ways to be wrong.

So how do you choose? Start from the question and the stage, not the software. Early, comparative, one-domain question - reach for a fast free tool (Ladybug for solar, Honeybee/Radiance for a daylight check). A whole-building energy or compliance question - an EnergyPlus-based tool (Honeybee early, OpenStudio or DesignBuilder for the detailed model). Learn one stack deeply rather than dabbling in five; the physics and the judgement transfer, the menus do not. This course teaches the free Ladybug/EnergyPlus/Radiance stack for exactly that reason - master it and every commercial tool becomes a familiar face with a different skin.