A.M. Total of 12. Benjamin did 7, Jenny 3, Julia 1, Joseph 2, Jacob 1, William 0.5. We are slowly recovering. I did a little workout to test my health and see how much fitness I've lost. Did a mile up the canyon in 6:08, and after a little rest another mile back down in 5:34. It felt hard, both up and down. Fast Running Friend was perfect with one small exception. Coming out of the canyon it reported pace 5:53, and then 5:57 when the actual pace was around 5:45. Then immediately after it reported 5:18 when the actual pace was around 5:28. However that spot is set up very well for signal distortion with the trail squeezing through a narrow opening between two tall rocks. I have not yet analyzed the data, but I've seen a similar pattern in another test sample and I am suspecting the problem is that we pick up the signal with virtual delay - that is the signal keeps us on the trail, at least the points the Fast Running Friend considers legitimate are on the route, but they are shifted back. So the GPS driver in other words tells the Fast Running Friend that we are now where we were in reality one second ago. If that indeed is the problem, there is absolutely nothing we can do to correct for that short of making the sampling distance too long because in the absence of some other feedback we cannot tell if the runner legitimately slowed down by 10 seconds per mile and then sped back up or if he ran evenly. Such a change of pace is completely legitimate and the erroneous point lies on the course.
I am still working on refining the GPS part of the Fast Running Friend, mostly the usability stuff - configuration file reading and writing, then UI to edit it on the device and via web browser if the device can connect to WiFi, support for splits of various kind, ability to upload workouts to the Fast Running Blog, etc, but I already ordered Garmin Footpod and will start research once it gets here. I have high hopes for the footpod - I think it will have more accuracy than GPS, and also less power utilization.