Objects & where they live
Your collections (sidebar): reusable Events, Courses and Rider setups. Treat courses and rider setups as templates/bases you’ll reuse in your optimizations.
Events: a target race defined by a course + date. Link your pacing and equipment optimizations to an event to keep all race-day strategies in one place. See Events 📆.
Optimizations (sidebar, under Performance): working spaces that combine a course + rider setup + wind + power settings. Your inputs are saved automatically.
Two types: Pacing (find the fastest power distribution for a physiological target) and Equipment (compare setups).
Runs: each time you click Run optimization, a new run with its own result is created. Give runs a Run name, compare them via View results history, and change inputs with Edit & rerun. Use runs to try ideas without cloning your collection items.
Workflow pattern
Pick an Event (or a Course) and a Rider setup from your collection.
Inside the optimization, tweak (segmentation, surfaces, wind, CdA, gearing, grouping, etc.) without changing your collection. Changes made inside an optimization are specific to that optimization.
Run optimization, name the run, then iterate: adjust inputs with Edit & rerun to create more runs.
If an inline tweak proves reusable beyond this optimization, promote it back into your collection: Save as course (course card menu) or Save in my collection (rider setup card menu).
Once an optimization has results, its segmentation can no longer be changed. Duplicate the optimization to try a different segmentation.
Other core ideas
Segmentation & Groups: segments are the unit of physics; groups simplify execution by sharing power targets.
Wind model: per segment; use the forecast or define manual wind for some or all segments.
Manual vs optimized: anything with a fixed (manual) power is excluded from optimization.
Baselines (equipment results): pick the reference setup to make deltas meaningful.
Credits: each run uses one optimization credit; see Plans, trial & credits 💳.