r/AirmassWx • u/gmrmoment31 • 18d ago
What’s next: sharper ridge lift, a 1–3 km soaring model, and thermals and routes trained on WeGlide
Here’s what I’m working on next. I can't promise a date for when these will all be out but definitely before the next season in spring; training and validating important data takes a long time, and I want this model to be trusted:
1. Better ridge resolution
2. Airmass ML: a high-res 1–3 km soaring model
Every model has its strengths and blind spots. HRRR is detailed but can be overconfident, ECMWF is steady but coarse, and ICON varies by region. I’m building a machine-learning model that takes their strengths, and puts them into a 1–3 km grid, tuned for soaring: thermal strength, cloudbase, more exact cumulus locations, and when the day starts and dies. The aim is to catch small, detailed patterns better than any one model can: sea breezes, convergence lines, terrain-driven cu, and blue holes.
3. Thermal triggers and a route planner trained on WeGlide
Thousands of WeGlide flights show where pilots actually found climbs and which lines actually worked. I’m using them to train models on:
Thermal triggers: the likely hotspots and house thermals for the day’s conditions, not just a blanket strength map (also shown especially in 3D view).
The route planner: routes based on where gliders really went fast on similar days.
All of this gets checked against real flights before it goes live, and I’ll post how each one does and compare to real flights.
4. Faster loading times on slower devices
Right now, some layers are partly worked out on your device: where each thermal goes in the 3D view, and some wave calculations. That’s fine on a recent laptop, but older phones and tablets can be slow and get warm. I’m moving more of this onto the forecast servers, so your device mostly just draws the result. The new ridge model is built for this: the terrain’s effect is solved ahead of time, so your device only needs a couple of multiplications per point. Expect faster layers, smoother 3D, and less battery drain, especially on phones.
For now, working things out on your device doesn’t hurt the quality of the data, since the bulk of the forecasting is still done on servers; and the same data that would be used to compute the layers in the server is used on the browser. It’s just nearly impossible to compute a 10 m global grid with land cover and altitude every few hours and serve it efficiently without huge compute and storage costs. Hopefully soon I can figure out a better way to deal with this.