Register | Login
Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: Jagge

In the 7 days ending Mar 28, 2010:

activity # timemileskm+mload
  MTB4 12:33:13 68.05(11:04) 109.51(6:53) 270015.1
  Running7 10:18:11 55.83 89.84 30132.5
  Skiing1 1:06:0013.2
  Total11 23:57:24 123.88 199.36 2730160.8
  [1-5]7 11:24:11
averages - sleep:2

«»
7:31
0:00
» now
MoTuWeThFrSaSu

Sunday Mar 28, 2010 #

Running 1:22:27 intensity: (1:00:00 @2) + (22:27 @3) 18.25 km (4:31 / km)
slept:2.0

Just below aerobic thresold for 1h + slight faster last 20 min. By feeling, no HRMs around. Felt quite easy and relaxed. Maybe because I slept so well last night :)

Running warm up/down 12:00 [1]

Saturday Mar 27, 2010 #

Running race 19:33 [4] 5.0 km (3:55 / km) +30m 3:48 / km

5km test run. Flatish course, 800m soft wet snow, 4.2 km asphalt. Time is slightly dissapointing, but still about what I expected - I am far from fit.

This was my first hing intensity training since my calf injury two months ago.

Running warm up/down 36:00 [2]

Skiing (classic) 1:06:00 [2]

Classic skiing, easy recovery workout. +3C, modest grip.
10 AM

MTB 16:23 [0] 2.53 km (6:29 / km) +33m 6:05 / km

MTB 19:35 [0] 5.02 km (3:54 / km) +144m 3:25 / km

MTB 17:20 [0] 2.19 km (7:54 / km) +84m 6:38 / km

Friday Mar 26, 2010 #

1 PM

Running 1:48:00 [2] 15.0 km (7:12 / km)

Pram run. Phone's battery ran out of juice, so route is Holux gpx (if it works).
No, gpx upload gives error :(
So here it is as kml
http://www.routegadget.net/gps/GPS_test_20100326.k...
2 PM

MTB 5:06 [0] 0.13 km (38:04 / km)

MTB 1:48:24 [0] 15.08 km (7:11 / km) +415m 6:19 / km

MTB 1:48:52 [0] 15.02 km (7:15 / km) +292m 6:36 / km

Thursday Mar 25, 2010 #

Running 2:00:00 [2] 16.94 km (7:05 / km)

Pram run. Looks like holux doesn't work so well if its hidden in the bottom of jacket's pockedt and you don't wait for satellites much.

It also has default setting for sending accuracy and satellite info only once per 5 secondes. It sends coordinates every second, but the positioning framework I use in Nokia phones gives me coordinates only once per 5 seconds. Luckily there is workaround, I can send commands to the gps to send certain NMEA sentences more often so it works just fine, I just need to conect to gps myseld over BT and send the command every time before I start. RG_Tracker doest that now :)

Wednesday Mar 24, 2010 #

Note
(rest day)

http://www.routegadget.net/gps/gpstest2010-03-23.k...

Yesterday's head lamp run. More serious gps test. I ran in forest, lots of snow but there's paths made by dogwalkers. GPS conditions were a bit stange, Forerunner showed 9..12 m accuracy in the beginning, usually its better. I had to wait on top of Malminkartano artifical hill for quite some time to get it down to 6 meters. It was slowly snowing but nothing special. Maybe it was just bad satellite moment. Anyway, when I got good accuracy readings I ran X in two places and one triange. I changed directions and ran both X's both on my way to triangle and again on my way home.

Fore did good job at X but was in trouble at far end corner of the triangle. Holux did kind of better hob at triangle, but X's were not as accurate and it was kind of lost between last X and triangle.

The open area near triangle and second X is huge steep mountain of debris. It blocks that part of the sky.

Fore was on my wrist and Holux on my left shoulder. I did wear Holux like that just because I plan to carry it like that for O. As you can see X by Holux is not as tight as Fore's X. Also if you take a close look at east part of the first X it looks like I would have run loop instead of the same path out and back. That's what happens if you keep gps close to your body. Body shadow is stronger and when you turn around the opposite side satelites are shadowed and shadowed ones are shadowles after the turn. Fore is on wrist, body is furher away so the effect is not that strong. You can see the same in fore's track but effect is lot smaller. Holux's X is not as thingh as Fore's partly because this body shadow effect, so Fore may not be as much better as Holux as one might think after first look. Fore would suffer from same effect if held like Holux here. Also the track by Holux isn't that bad, accuracy at X is +- 15m at worst. Fore was actually worse than that at triangle, +-20m. But still I have feeling Fore may be a bit better. But we'll see that later.

In yesterday's test I had gps in pram pocked. So no body shadow. If you take a look at yesterday's track's "hooks" you'll notice that turn-around-body'shadow effect is missing. I think I will next try carrying Holux on my wrist just as Fore. But I guess I'll carry it on my shoulder while orienteering just as I did here. I am used to use my wrist to hit branches away - that's not a good place for electonics.

Anyway, Holux looks promising. Nothing spectacular and not better than those units I already had, but it's light and small asn accuracy looks just about fine. And no sign of spikes like ibt 474 (MTK 1) did.

Tuesday Mar 23, 2010 #

Note

Yesterday's GPS comparison tracklog. Garmin Forerunner, Globalsat bt335 and Holux m1200e.
http://www.routegadget.net/gps/GPSvertailu2010-03-...

Must do more tests to see is my new holux unit fine or not. Now looks like it most likely will not be quite as good as Fore and Globalsat, but maybe not really bad either for a 30 gram / 38 euros unit.

Running 1:09:02 [2] 9.29 km (7:26 / km)

.
2 PM

MTB 1:10:48 [0] 9.94 km (7:07 / km) +222m 6:24 / km

MTB 1:08:52 [0] 9.93 km (6:56 / km) +184m 6:21 / km

8 PM

Running 57:58 [2] 8.86 km (6:33 / km)

Head lamp run & gps test.

Monday Mar 22, 2010 #

Running 1:53:11 [2] 16.5 km (6:52 / km)

Pram jogging and gps comparison test.
3 PM

MTB 42 [0] 0.46 km (1:31 / km) +114m 41 / km

MTB 1:52:42 [0] 16.34 km (6:54 / km) +311m 6:18 / km

MTB 1:52:43 [0] 16.43 km (6:52 / km) +483m 5:59 / km

MTB 1:51:46 [0] 16.44 km (6:48 / km) +418m 6:02 / km

« Earlier | Later »