How to read the activity summary¶
What this is for¶
The sport overview shows completed workouts and body measurements. The activity heatmap and the general statistics also let you check task activity; each of these views uses different data.
How to get there¶
- SPORT → Overview (
/sport): workouts and measurements. - Insights → Heatmap (
/heatmap): Activity Heatmap. - Insights → Statistics (
/statistics): task and time statistics.
Step by step¶
- Finish a session with Finish session and check Overview.
- Compare the current week, the last six weeks and the yearly summary.
- In the workouts-vs-body comparison, choose the measured value, e.g. Weight or Waist.
- In Heatmap, change the range and hover over a day to see its date and task count.
- In Statistics, read e.g. Total Tasks, Total Hours and Meditation This Year. The meditation interpretation is described on a separate page.
Fields and options¶
| View or metric | What it shows and where the data comes from |
|---|---|
| Overview | Sessions, exercises and plans from the training services; weight and circumferences from Body records. |
| Yearly summary in Overview | Closed sessions in the current year up to today; total minutes, average time, active weeks, exercise completion and months. A session's date is its own date, then its creation date, and if both are missing — today. |
| Week streak in Overview | Consecutive weeks with a finished workout. An empty current week lets the count start from the previous week. |
| Weight trend in Overview | Weight entries from the last 90 days; the chart needs at least two. |
| Workouts vs. measurements comparison | 12 weeks of minutes from finished sessions and the chosen weight or measurements: Body fat, Waist, Chest, Hips, Biceps (avg.), Thigh (avg.). |
| Heatmap | Daily counts returned by the statistics service for 365 days, with gaps between returned dates filled with zeros. This is task activity data, not a workout list. |
| Active days, Tasks logged | Days with a count greater than zero and the sum of counts in the selected map range. The average covers active days. |
| Current streak, Longest streak | Day streaks counted from the whole fetched range, regardless of the visible window. |
| Statistics | Data from the statistics and dashboard services plus separate task and media reads. If the main read fails, the view tries to compute statistics from the task list. |
Common mistakes / pitfalls¶
- An open session does not increase the finished-workout summaries. Minutes come from the saved duration, not from a stopwatch measurement.
- The map does not compute task counts from exercises or body measurements. The frontend does not define the server rule that picks tasks for the daily count.
- An empty today does not break the current streak on the map. Changing the range does not shorten the streaks, because both streaks use the entire fetched dataset.
- The workouts-and-measurements comparison is not grounds for inferring the cause of a body change. With too few measurements, the chart or correlation is unavailable.