Excluding an activity from a specific metric

What metric exclusions do

An Activity can be excluded from contributing to specific MetricHistory types (like css_pace, cda, critical_power, etc.) while still counting toward Load and the PMC. This lets you keep an activity in the training load picture without letting its bad data corrupt a downstream calculator.

The data lives in Activity.metric_exclusions as a JSON list of metric type keys, e.g. ["css_pace", "cda"].

When to exclude

Common cases:

• A bad CSS test: stroke rate was off, the swim turned into a fartlek halfway through. Exclude css_pace so this activity does not feed the CSS auto-extract.
• A CdA test on a windy day: the field test produced a CdA value that does not represent the rider. Exclude cda.
• An unusual race day power: the race was an outlier (a crash, a mechanical, a deliberate pacing decision) and you do not want it pulling the critical power model.

In all these cases, the activity still counts as training load (Load, Fatigue, Fitness, Form) because the athlete still did the work and still needs recovery.

How to set exclusions

Open the activity detail page. The metric exclusions control exposes a list of MetricHistory types that this activity contributes to (e.g. CSS pace, CdA, critical power). Toggle the ones you want to exclude.

API endpoint: POST /api/athlete/<pid>/activity/<id>/metric-exclusions/ with a JSON body of {"metric_exclusions": ["css_pace", "cda"]}. Pass an empty list or null to clear all exclusions.

What changes after exclusion

• The next time the auto-extractor runs over recent activities (or recomputes existing metrics), the excluded metric types will skip this activity.
• Existing MetricHistory rows that came from this activity do not auto-delete; you may need to delete them manually or wait for the next refresh cycle if the workflow uses one.
• Load, Fatigue, Fitness, Form are unaffected. The activity remains in training load.

Difference from Load override

Use both together when an activity has both problems (e.g. a bad power test with broken AdjP).

See also: Load computation and override, Activity quality flags.