Training Archive: JaggeIn the 1 days ending 2007-04-19:
| [csv] | ||||||||||||||||||||||||||
| « | » |
| » now | ||||
| H |
Thursday Apr 19 | ||
| Note | |
| About the GPS issue:
-We use GPS receiver with 1 sec point interval. Also 2 sec interval may work, but any "smart recording" will not do. - Track smoothing algorithms may spoil the data. Avoid using them. I haven't tried, but for example FRWD's smart post processing may cause you problems. - I have tried Forerunner 205&306 and Globalsat GH-615, both work just fine. These examples are done with Fore 305 and 205 devices.
Leg 2-3 Runner one Map 1 1. Control, punch. Start about right direction, hesitating route choice. 2. Stop, still trying to decide which way to go. 3. Stop - go - Stop - go - Stop - and finally with good speed to the path. Map 2 1. At path it looks like still some hesitating can be seen. Maybe checking is it he right path or what spot of the path we are. 2. On path, a stop to read map. Still unsure and hesitating. Map 3 1. Path crossing, full stop to to check something(?). 2. Leaving the path, very very slowly and carefully. 3. Good speed in forest, 4. stop to check direction/location. Map 4 1-2-3. Stops, slowling down, reading map. 4. Approaching slowly to spot the flag. 5. Punch, turn to right direction, making route choice. 6-7. Stops to check something... The same leg, runner two Map 1 1. Slowling down, reading map, then straight to control with great speed. 2. Punch 3. Leaving control to right direction, but using over 10 sec to make ruote choice. Apparently next leg wasn't much checked before control. 4. Still hesitating, finally decission to take the path, turn to that direction. 5-6. Making sure of something (had to go over a path here?). 7. Gerat speed to path and on path. Map 2 Good steady speed on path, no need slow down to check anyting. Map 3 1. leaving path, no hesitating, good speed. 2. Reading map, running ahad with good speed. Map 4 Good speed all the way from the path, here 1-2 reading the map to get located accurately, then nice approach to control. 3. Punch, leaving to the right direction, some 4. route choice and then smoothly towards the next control without any unnecessary stops. Leg 6, second half Runner one Map 5 1. Great speed on path, then full stop at path crossing, then to 2. forest. Maybe no idea which path crossing it was, first or second, 3-4 so had to check map to make sure and make direction corrections. 5. Step hill up to control. Runner two Map 5 1. Leaving path smoothly, right direction and without unnecessaty stops. 2. checkind direction, a little turn to left. 3. log way smoothly, here making sure to clinb up at the right place. 5. steep hill up to the control. As you can see, there was no mistakes here. We are analysing the good, succesful orienteering and we are trying to make it better. But sometimes it's usefull to take a look at also mistakes, so let's take a look at them next. Using Route Gadget RG is designed for drawing viewing routes on the web. It's not very good tool for accurate analysis, but you can find something out of it if you first draw your route as you thought you ran the coutse, and then you upload your gps track. If there is big differences somewhere, it's likely you had lost your map contact there and you are about to make mistake there. Here is one example
Yet an other mistake From control to right direaction, but then total blackout and a huge mistake. So what might have happenend? I guess this something like this. Right after leaving the control the focus was briefly lost. WHen it comes back, we had to try to relocate. But thumb didn't stay on the right spot of the map or we didn't trust it was on a right place, so we ended up guessing we were suddenly drifted 100m left. The it's logical to continue as we did and ended up to the wrong hill. If only could keep the thumb still we could have easily guessed it right, but sloppy thumb and lost focus together usually gives us disasters after disaster... OK, I guess/hope you got the point. Basicly it a lot like running/following behind and checking what the other person is doing out there. And the next and more importatn part is to think ways to improve, but it's an other isgue, maybe I'll write about it some other time. And what you need is a device accurate and sensitive enough with ability to record location every second. | ||
| C • Is smart recording really bad? 7 | ||
| Note | |
Here is my last race at Barbate, Spain. Map: http://www.routegadget.net/gpsoblog/cgi-bin/reitti... Dot images: No comments this time, you can try figuring out what was going on. The start of the race,six first controls: image1 image2 image3 image4 image5 image6 image7 My ~ 20 sec boom at # 10: image8 --- It's fast terrain, even my speed was about 5 min/km or a bit faster in the beginning and got a more slow later in the deeper forest. | ||