BernhardBuckel 497da7ca8b fix(pulse): make a day of pulse the mean of its hours' means ...

A watch samples pulse about every 5 to 10 minutes at rest and about every
5 seconds in a workout. The daily value was the plain mean over a day's
readings, so a workout hour of several hundred readings outweighed the other
23 hours: a day with one hard hour and 23 resting hours (60 bpm) read about
128 bpm, not 64.

A day of pulse is now the mean of its per-hour means, in the rollup DAY
bucket, the live per-day read the chart serves, and the series route's day
grain. Windows over several days weigh each day once instead of by its
reading count, so the bias does not return one level up. Reading counts,
min/max, and the regression sums still run over every reading. The chart
tooltip and the data table name the statistic, in all seven locales.

The statistic is limited to pulse; HRV, SpO2 and glucose keep the plain mean
(see src/lib/measurements/day-statistic.ts). Stored DAY rows are rewritten by
the next rollup recompute (admin recompute route), not on read.

Fixes #1107

2026-10-04 10:41:08 +02:00

..

fixtures/v137

Merge remote-tracking branch 'origin/main' into wip/v140-H

2026-10-03 22:52:49 +02:00

integration

fix(pulse): make a day of pulse the mean of its hours' means

2026-10-04 10:41:08 +02:00