Objects & where they live
Collections: reusable Rider Setups and Courses. Treat them as templates/bases you’ll reuse in your optimizations.
Optimizations: working spaces that combine a course + rider setup + wind + pacing/equipment choices.
Two types: Pacing (find fastest power distribution for a physiological target) and Equipment (compare setups).
Versions: saved iterations of the same optimization. Use them to A/B ideas without cloning collections. Variants appear when you open an optimization on the overview.
Workflow pattern
Pick a Rider Setup + Course from your collection.
Inside the optimization, tweak (segmentation, surfaces, wind, CdA thresholds, grouping, etc.) without cluttering your collection.
Run → Save version, then iterate: adjust inputs and re-run to create more versions.
If an inline tweak proves reusable beyond this optimization, promote it back into your collection as a new Rider Setup or Course.
Other core ideas
Segmentation & Groups: segments are the unit of physics; groups simplify execution by sharing power targets.
Wind model: per segment; bulk actions can set manual wind or revert to forecast.
Manual vs optimized: anything marked Manual is excluded from optimization (fixed value).
Baselines (equipment results): pick the reference setup to make deltas meaningful.