Continuing the 31 Dec 2001 - 9 Jun 2002 log of ^z weekly (weakly!) miles in JogLogFog (9 Jun 2002), the scorecard for 10 Jun - 6 Oct 2002 in raw form looks like:
| M + | T + | W + | T + | F + | S + | S = | Total |
| 4 | 9 | 6 | 5 | 24 | |||
| 11 | 5 | 5 | 4 | 10 | 35 | ||
| 4 | 9 | 4 | 6 | 23 | |||
| 5 | 7 | 9 | 6 | 27 | |||
| 4 | 9 | 13 | 26 | ||||
| 4 | 5 | 9 | |||||
| 5 | 8 | 4 | 6 | 8 | 31 | ||
| 4 | 4 | 5 | 8 | 21 | |||
| 12 | 5 | 4 | 21 | ||||
| 7 | 4 | 5 | 16 | ||||
| 15 | 5 | 5 | 25 | ||||
| 13 | 4 | 10 | 27 | ||||
| 4 | 9 | 15 | 28 | ||||
| 4 | 8 | 20 | 32 | ||||
| 8 | 8 | 8 | 8 | 32 | |||
| 6 | 10 | 20 | 36 | ||||
| 3 | 7 | 6 | 4 | 20 |
... a forest of digits, of minimal interest except perhaps to the person who pounded the pavement for those distances. But put into a graphical form it becomes a bit more comprehensible. Here are the ^z daily runs (inverted red triangles) along with weekly totals shown as 7-day (green) and 30-day (blue) lagged moving averages.

There are some interesting phenomena visible, including troughs in May (muscle & joint soreness, perhaps from running too far too soon) and July-August (sultry weather & bad air quality), as well as a steady trend upward in peak distance covered during jaunts.
But much more can and should be done to process these data, remove "noise", and analyze "signal". This is a splendid example of a filtering problem, for which science has developed powerful technologies over the years. But pending that discussion, a fistful of memories from ^z runs of the past four months:
TopicRunning - TopicPersonalHistory - Datetag20021011
(correlates: FadingTraces, DazzlingDarkness, SeeingThought, ...)