Why SLOP6246 is built around one failure condition, how the semester is shaped, and what the course deliberately does not do.

About this course

The obvious way to organise renewable-energy teaching is by technology: a block on wind, a block on solar, a block on storage, a block on grids. That structure is easy to timetable and it quietly teaches the wrong lesson — that reliability is the sum of a set of components rather than a property of a system meeting a specific condition.

This course is organised the other way round. One failure condition, held fixed for twelve weeks, and technologies introduced only where they change how that condition is defined, detected, predicted, survived, allocated or bounded.

The condition#

A period when wind and solar output are simultaneously low, for long enough that normal planning assumptions stop holding. The course fixes an operative definition of it at the event — a threshold, a span, a recovery rule, a scope and a season — so that twelve weeks of argument are about systems rather than vocabulary.

That definition is deliberately contestable, and the first assessment asks you to move it and defend the move.

How the semester is shaped#

Three acts. What the event is, what survives it, and who decides — plus who explains it afterwards. Each of the twelve weeks owns exactly one property of the event and no two weeks own the same one, which is the structural rule that stops the course drifting into a technology survey.

Each week states whether it advances the central claim, complicates it or challenges it. The challenges are not decoration: week 6 attacks the mitigation weeks 3 to 5 make most attractive, and week 8 points out that the last line of defence is bought rather than engineered.

What the course runs on#

One synthetic teaching trace: fourteen days at hourly resolution, generated by a seeded function that lives in this repository. Every figure, studio exercise and worked example reads from it, so no two pages can disagree about the reference event.

It is not measured data. There is no reanalysis or historical record behind it, and it does not describe any real grid. It exists so that the whole cohort argues about the same fortnight. Anything derived from it is labelled Synthetic trace wherever it appears, and the course’s own chosen boundaries are labelled Course-defined, because those are different kinds of claim.

What this course does not do#

• It does not derive machine equations. No power-systems background is assumed.
• It does not rank technologies. A technology is interesting here only in relation to the event.
• It does not present a correct answer. The final studio is a critique of designs that are all defensible and all limited.
• It does not use figures from real electricity systems. Where a real empirical claim would be needed and no source is available, the course writes qualitatively instead of inventing precision.

What you leave with#

A system you specified, operated through an event, and can defend — together with a precise statement of the event that defeats it. The second half of that sentence is the part the course actually grades hardest.

Annual reporting#

The School requires each course to report a single headline figure for the annual review. SLOP6246 reports 87.4%.