CdA from a TT, CSS from a swim test, fueling from a long ride — straight from the calendar.
The Hub's calculators (CdA, CSS, sweat-rate, fueling, pacing, …) each have a deep-link slot for an Activity or workout. If you pass one, the calculator's input fields pre-fill from that file — no re-upload, no manual copy-paste from your head unit.
From a completed workout or upload pill on the calendar: click the pill → workout detail page → in the Analysis card, click Open in CdA calculator (or CSS / pacing / fueling depending on sport).
From an activity directly: open the activity
(/athlete/<pid>/activity/<id>/) → top-right Analyze in…
menu → pick the calculator.
From the calculator catalog: open /calculators/<calc>/,
then in the Activity picker at the top of the calculator,
pick from a dropdown of the athlete's recent rides / swims / runs.
| Calculator | Reads from the activity |
|---|---|
| CdA | Speed, power, elevation, GPS track, wind direction (if available), temp, pressure |
| CSS | Distance, time per length, total time, 400/800/1500 splits |
| Sweat rate | Duration, temp, weight pre/post (you still enter the weights) |
| Race fueling | Distance, expected pace, course climbing, expected temp |
| Pacing | Power / pace history, recent CP / CSS |
| Goal feasibility | All of the above + race target you set |
The original workflow (export FIT from Garmin Connect → re-upload to calculator) costs about a minute per analysis. Deep-linking saves that minute every time, and the data is the same file the Hub already parsed — so there's no inconsistency between what the analytics page shows and what the calculator computes.
A few calculators (notably CdA, which fits an aero model to each
second of the ride) need the per-second streams, not just the
aggregate metrics. Those calculators call the
/api/athlete/<pid>/activity/<id>/streams/ endpoint internally —
the same source the analytics page uses. Cached for one hour; the
second open is instant.
When you save a calculator result with an activity in scope, the
saved CalculatorResult row links to that activity. The next time
you open the activity detail page, the result shows in the
Calculations section so you don't lose track of which CdA test
came from which ride.
Still stuck? Ask us a question and we'll write up an answer.
Ask a question