Can a coding agent invent a better optimizer schedule than the one we ship? A wind-farm-layout benchmark with held-out farms to find out.
Julian Quick · Pierre Réthoré
DTU Wind & Energy Systems · julianquick.com

Downstream turbines sit in the slowed, turbulent air of their neighbors. Layouts are optimized to squeeze wake losses out of a fixed patch of sea, and small modeled gains move real money.
Shid-Moosavi et al., “Modeling and experimentally-driven sensitivity analysis of wake-induced power loss in offshore wind farms,” Renewable Energy (2025).

Three farms, three turbine platforms, four wind roses, deliberately mismatched so schedules must generalize.
Layouts are optimized by stochastic gradient descent on the sample-mean gradient of power P and constraint penalties γ. The agent's only levers are the hyperparameter schedules.
Four schedules to design: the learning rate lr(t), the constraint-penalty weight α(t), and the Adam momentum terms β₁(t) and β₂(t). Everything else is fixed.
Quick et al., “Stochastic gradient descent for wind farm optimization,” Wind Energy Science (2023), the baseline this harness wraps. Background on the SGD algorithm →

Claude Code and Gemini CLI both climb past the 500-multistart baseline (dashed) on train and held-out validation AEP. Stars mark the deployed scripts.

Neither schedule family exists in the TopFarm baseline (dashed black).
Winning-seed trajectories over the rose-averaged flow field on the DEI training farm (N=80). Darker = wake; brighter = faster average inflow. Final AEP: baseline 8714 GWh · Gemini 8805 GWh · Claude 8821 GWh.

500-multistart comparison across 3 farms × 4 wind roses × turbine counts. The Claude schedule is generally better than or on par with Gemini and the baseline, including on farms and turbines it never trained on.
Claude · iter 192 · DEI, N=50
Gemini · iter 118 · DEI, N=50