Project · In progress since June 2026

Solar Modelling Web App

A physics-based model of how much energy a solar installation produces anywhere on Earth, hour by hour, built to design two-axis sun-tracking systems.

What it is

My honours thesis asked what limits the performance of solar panels that track the sun on two axes. This project turns that question into a tool. You drop a pin anywhere on a map, and the model simulates all 8,760 hours of a typical year at that spot using real weather records. It reports what a tracking system would produce against a conventional fixed-tilt array, and how much is lost to heat, dust, snow, shading and ageing.

The aim has narrowed as the work went on. Rather than one tool that does everything, it is one validated core from which precise single-purpose instruments can be cut: a site comparison, a battery sizing check, a shading study. That only works if every equation in the core is documented and checked, which is why so much of this page is about method.

A sample simulation

These numbers came from the model on 16 November 2026, with default module settings and no obstructions. Two sites: Perth, where I live, and Munich, for contrast.

Figure 1

Two sites, one model

Perth, AustraliaMunich, Germany
Two-axis tracking yield615 kWh/m²358 kWh/m²
Fixed-tilt reference yield424 kWh/m²263 kWh/m²
Tracking gain+45%+36%
Optimal fixed tilt27°42°
Yield exceeded 9 years in 10 (P90)601 kWh/m²340 kWh/m²
Year-to-year variability1.7%4.0%
Heat loss4.4%3.6%
Snow loss, no clearingnone6.5%
Dust loss, no cleaning0.2%0.2%
Climate-adjusted degradation0.68% per year0.38% per year
Output after 25 years83%89%
Annual figures per square metre of panel. Weather: PVGIS typical meteorological year, 2005 to 2020. Variability from a 39-year record.

The contrast is the point. Perth produces about 70% more energy per square metre, and its output barely varies from year to year. Munich loses more than 6% to snow if nobody clears the panels, while Perth loses more to heat. Hot sites also age panels faster: the model's climate-adjusted degradation rate is nearly double in Perth, so after 25 years a Perth panel has lost more of its output than a Munich one.

Figure 2

Perth, month by month

Two-axis trackingFixed tiltkWh per m² per month
Monthly energy yield, two-axis tracking against fixed tilt020406080Jan · Two-axis tracking: 70.9 kWh/m²Jan · Fixed tilt: 41.8 kWh/m²JanFeb · Two-axis tracking: 58.4 kWh/m²Feb · Fixed tilt: 39.0 kWh/m²FebMar · Two-axis tracking: 53.2 kWh/m²Mar · Fixed tilt: 38.5 kWh/m²MarApr · Two-axis tracking: 48.1 kWh/m²Apr · Fixed tilt: 35.1 kWh/m²AprMay · Two-axis tracking: 39.1 kWh/m²May · Fixed tilt: 30.5 kWh/m²MayJun · Two-axis tracking: 35.1 kWh/m²Jun · Fixed tilt: 26.7 kWh/m²JunJul · Two-axis tracking: 31.9 kWh/m²Jul · Fixed tilt: 24.8 kWh/m²JulAug · Two-axis tracking: 41.5 kWh/m²Aug · Fixed tilt: 32.0 kWh/m²AugSep · Two-axis tracking: 45.0 kWh/m²Sep · Fixed tilt: 33.4 kWh/m²SepOct · Two-axis tracking: 58.6 kWh/m²Oct · Fixed tilt: 39.7 kWh/m²OctNov · Two-axis tracking: 64.0 kWh/m²Nov · Fixed tilt: 40.2 kWh/m²NovDec · Two-axis tracking: 69.1 kWh/m²Dec · Fixed tilt: 42.0 kWh/m²Dec
View as a table
MonthTwo-axisFixed tilt
Jan70.941.8
Feb58.439.0
Mar53.238.5
Apr48.135.1
May39.130.5
Jun35.126.7
Jul31.924.8
Aug41.532.0
Sep45.033.4
Oct58.639.7
Nov64.040.2
Dec69.142.0
Tracking helps most in summer, when the sun travels furthest across the sky. Over the year it adds 45% in Perth.

How the model is built

The core is a chain of physical models, each feeding the next: where the sun is, how much light arrives, how much lands on the panel, how hot the cell runs, what power comes out, and what is lost along the way. Each link is documented with its equation, its source in the literature, and the exact code that implements it.

The models, in the order the energy flows:

  • Sun position and irradiance. Solar geometry for every hour, with measured beam, diffuse and ground-reflected light from the European PVGIS dataset.
  • Tracking and fixed-tilt incidence. Light on a panel that follows the sun, and on a fixed panel at its best tilt, with reflection losses at shallow angles.
  • Cell temperature. A wind-aware thermal model, because a breezy site runs panels more than ten degrees cooler than the industry's still-air assumption.
  • Electrical output. A single-diode model of the module, read from a real datasheet, including bifacial panels that collect light on both faces.
  • Losses. Dust build-up and rain cleaning, snow cover and shedding, far and near shading, and 25 years of climate-dependent degradation.
  • Confidence. Year-to-year variability from four decades of weather, so a result is a range rather than a single hopeful number.
  • Storage. Battery behaviour, wiring, conversion losses and the temperature inside the enclosure.

The documentation is part of the product. Every section of the model is explained inside the app to a teaching standard: a plain-language concept, a figure drawn from scratch, the real equations with a hover definition on every symbol, a worked example and a table of where each value comes from. If a user cannot follow how a number was produced, the number is not finished. The whole section is published as its own page, linked below, with the interactive map of the model beside the text.

Figure 3

The methodology section and model map

The methodology page: explanatory text, a figure of the Earth's orbit, and the interactive model map

Open the live methodology

The image is a preview. The button opens the real section in its own tab, exactly as the app renders it: scroll the text, hover any symbol in an equation, and double-click a double-bordered box on the map to open its subsystem. It is republished from the project each time a development phase closes.

Where it is heading

The model underpins a hardware idea: a solar, battery and backup generator system packed into a shipping container, with a two-axis tracking array that folds out on arrival. The app's landing page carries an interactive concept of it.

Figure 4

The container concept

Concept illustration of two containerised solar and battery units with tracking arrays deployed
A concept illustration from the app, not an engineered design. Mechanical loads and actuator sizing are not evaluated yet.

How the project is run

I direct this project and an AI system does most of the building. That arrangement only works with structure, and the structure has become as much a part of the project as the physics.

  • A notes vault as the single source of truth. Goals become tasks, tasks drive code, and code is recorded back as an as-built document, all in the same change. Each topic has exactly one owning document.
  • A written working agreement. A standing contract the AI reads at the start of every session: check primary sources before stating a fact, list everything a change affects before making it, challenge a flawed instruction rather than comply, and report outcomes faithfully.
  • Automatic checks. Scripts run after every edit, before every save to the project history and before every publish. They compare documented facts against the code, test the interface in a real browser, and block the change if anything disagrees.
  • Small reviewed increments. Work arrives in pieces I can audit, each with a short guide to what I should see and where the rough edges are.
  • The ratchet. Any rule that gets broken twice stops being a rule and becomes an automatic check.

Figure 5

The project in numbers

Changes committed since June 2026more than 630
Busiest monthsJuly (267) and August (305)
Hours simulated per site8,760
Blocks on the model map34
Subsystems that open into their own equations20
Weather record behind the variability estimate39 years
Counts from the project's own history as of November 2026.

The full governance structure is drawn as an interactive map, with excerpts from the actual rules and checks.

Figure 6

The process and governance map

The process map: written contracts, the notes vault, edit-time checks, commit and close gates, and the registries they audit

Open the process map

The image is a preview. The map opens in its own tab: the flow runs left to right from the written rules, through the notes vault they govern, to the automatic checks and the records those checks audit. Click any box for its detail and an excerpt from the real file.

Read more

Three essays use this project as their worked example: Terminology, Methodology, Technology on how the domain was mapped, Incentive Structures and Feedback Loops on why the rules are shaped as they are, and Co-Directing with AI on how the work is verified.