Training Log Archive: cmorseIn the 1 days ending Oct 22, 2017:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||
| |||||||
| Su |
Sunday Oct 22, 2017 #
Event: WCOC Ansonia Nature Center
7 AM
Note
rhr:44 weight:79.2kg
10 AM
Orienteering race (Ansonia - Green) 46:02 3.55 mi (12:58 / mi) +110m 11:50 / mi
ahr:143 max:169 spiked:8/10c shoes: 280 ORoc 2017
A little stiff from yesterday, so elected the age appropriate green course rather than the longer red course on offer. Never ran very hard (perceived effort), walked a few hills when called for. Clean run except for a 60 sec bobble on 4 (came over ridge too far S and noted marsh below me) and a hesitation in the circle on 7. Looks like GPS didn't get a lock until a few minutes in around control #3, usually connects within seconds so I didn't even look at the start. It did do a software update when I arrived, so maybe that explains the slow start.
{edit} comparing my track with the map, it appears I overshot and wandered on #7, but I distinctly remember coming in to the rocky reentrant, stopping, and scanning up and down looking for a 1.5m boulder (or a boulder of about the same size as #6, 1.5m that I had just come from). Eventually noticed a glimpse of orange about 30' below me on a boulder that, from my perspective above it, was barely bigger than the surrounding rocks and was in no way 1.5m. Went down and punched. But did not wander beyond the stony ground in search of the flag. But then the pace graph infers that I did so faster than 5 minutes per mile pace, no chance I could even run that fast on a track. Must be a GPS overshoot glitch - weird though, the watch is usually pretty good with tracking... Maybe the software update reset it to smart recording and it assumed I was still trucking along before realizing I had stopped to look for the flag.
{edit again} - yup, watch back to factory defaults, smart recording and GPS only. Reset it back to every second recording and GPS+GLONASS.
{edit} comparing my track with the map, it appears I overshot and wandered on #7, but I distinctly remember coming in to the rocky reentrant, stopping, and scanning up and down looking for a 1.5m boulder (or a boulder of about the same size as #6, 1.5m that I had just come from). Eventually noticed a glimpse of orange about 30' below me on a boulder that, from my perspective above it, was barely bigger than the surrounding rocks and was in no way 1.5m. Went down and punched. But did not wander beyond the stony ground in search of the flag. But then the pace graph infers that I did so faster than 5 minutes per mile pace, no chance I could even run that fast on a track. Must be a GPS overshoot glitch - weird though, the watch is usually pretty good with tracking... Maybe the software update reset it to smart recording and it assumed I was still trucking along before realizing I had stopped to look for the flag.
{edit again} - yup, watch back to factory defaults, smart recording and GPS only. Reset it back to every second recording and GPS+GLONASS.