How to use the calibration workspace tabs

The calibration workspace is not one single action.

Each tab answers a different question, and most users should move through them in order instead of changing values everywhere at once.

The tabs at a glance

  • Ingest: load FIT data and decide whether the dataset is usable enough to continue
  • Speed Shape: compare the modeled speed-shape curve against the FIT-derived baseline
  • ΔHR Shape: validate how the HR-response shape behaves after the speed-shape work
  • COT Shape: inspect the cost-of-transport shape against the FIT proxy
  • Effort Intent: review or edit effort-intent speed and energy scalars
  • Propagation: decide whether the current workspace is only a preview or should become a saved profile used by trips

A good operating rule

Do not start by editing everything.

Use the earlier tabs to decide whether the dataset and shape are believable first, then use the later tabs only to save, apply, or deliberately override.

Ingest

Use this tab to:

  • select the FIT folder
  • review the ingest gate and dataset summary
  • decide whether the dataset is representative enough to calibrate from

Make decisions here about:

  • whether to continue ingest at all
  • whether the selected folder is too broad, too risky, or too unrepresentative

Move on when:

  • the dataset summary looks believable enough to review further
  • the preflight warning no longer feels like a blocker

Do not move on just because ingest completed technically.

If you want the detailed walkthrough for interpreting the post-ingest charts and summary, read How to use diagnostics after FIT ingestion.

Speed Shape

This is the first true shape-review tab.

Use it to answer:

Does the modeled TRIPS speed-shape behave enough like my FIT-derived baseline across observed grades?

Focus on:

  • the overall agreement between the modeled curve and the FIT baseline
  • the shape advisor score
  • mismatch severity and where the mismatch happens
  • whether downhill or uphill behavior is the main problem

Adjust here when:

  • the speed shape clearly misses the observed baseline and the diagnostics say the mismatch is meaningful

Leave it alone when:

  • the fit is already directionally good enough for planning use

Move on when:

  • the shape looks believable
  • the major mismatch warnings are resolved or at least understood

If you want the detailed walkthrough for this tab specifically, read How to use the TRIPSpeed Shape tab and controls.

ΔHR Shape

Use this tab after speed shape, not before.

It helps you evaluate whether the heart-rate response still looks believable after the earlier shape work.

Use it to answer:

Do the HR-response diagnostics still support the calibration, or did the shape work create a new problem?

Focus on:

  • whether the chart still looks believable
  • whether the advisor supports leaving the fit alone
  • whether any mismatch is clear enough to justify a small, targeted edit

Treat this tab more as validation than as a place to make casual edits.

If you want the detailed walkthrough for this tab specifically, read How to use the ΔHR Shape tab and controls.

COT Shape

Use this tab to inspect the cost-of-transport shape.

This is more advanced than the basic ingest and speed-shape workflow, so most users should treat it as a later-stage review step rather than the first thing to tune.

Use it to answer:

Does the TRIPS COT curve look directionally consistent with the FIT-derived proxy, especially across grade?

Focus on:

  • whether the red TRIPS curve and blue FIT proxy are directionally aligned
  • whether the advisor says the shape is believable enough
  • whether the current view is revealing a real mismatch or just normal noise

Be conservative about edits here.

If you cannot clearly explain why a change improves realism, do not change it just because the controls are available.

If you want the step-by-step walkthrough for this tab specifically, read How to use the COT Shape tab and controls.

Effort Intent

This tab is about whether the calibrated effort bands still look believable for you.

Use it to answer:

Do the effort-intent bands look believable for this calibrated user, and do I need to override the profile values?

Start with:

  • the status card
  • the summary table

Those give the shortest user-facing answer about what each effort band means for this calibrated user.

Only use manual override when:

  • the inferred FIT-based values are not believable
  • you understand which intent band you are changing
  • you intend to save that change into a profile deliberately

If you are only exploring, review the tables and leave manual override off.

If you want the detailed walkthrough for this tab specifically, read How to use the Effort Intent tab and controls.

Propagation

This tab is where calibration becomes operational.

Use it to decide:

  • whether the current trip should use system default
  • whether the current trip should use a saved calibration profile
  • whether you only want a temporary workspace preview

This is also where you:

  • load an existing profile into the workspace editor
  • save a new calibration profile
  • update a loaded profile
  • delete a profile
  • choose the default profile for future trips

The most important distinction here is:

  • workspace preview is temporary
  • saved profile is reusable
  • assigned trip profile is what makes the trip planner actually use the calibration

If you want the detailed walkthrough for this tab specifically, read How to use the Propagation tab.

Recommended tab order

For most users, the safest order is:

  1. Ingest
  2. Speed Shape
  3. ΔHR Shape
  4. Review Effort Intent
  5. Use Propagation to preview, save, and assign
  6. Use COT Shape only if you still need deeper review

What most users should adjust

Usually:

  • adjust the dataset by changing which FIT files you include
  • adjust only when a tab clearly shows a meaningful mismatch
  • save and assign only after previewing on a real route

Usually avoid:

  • making manual scalar edits early
  • saving profiles before comparing route behavior
  • treating every diagnostic difference as something that needs fixing

Still need help? Send a Little Note to Backpacking Light Send a Little Note to Backpacking Light