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

Training Log Archive: Jagge

In the 7 days ending Apr 3, 2011:

activity # timemileskm+mload
  Skiing5 4:41:21 31.71 51.0360.0
  Running3 1:03:31 4.84 7.793.6
  Total8 5:44:52 36.55 58.8263.6
  [1-5]6 5:09:02

«»
1:25
0:00
» now
MoTuWeThFrSaSu

Sunday Apr 3, 2011 #

1 PM

Skiing (skate) 1:15:10 intensity: (27 @0) + (5:50 @1) + (55:43 @2) + (12:42 @3) + (28 @4) 10.35 mi (7:16 / mi)
ahr:138 max:170

wet and slow.

Saturday Apr 2, 2011 #

Skiing (skate) 1:25:00 [2]

At Paloheinä. Wet conditions, but decent glide. Not super fast icy tracks as yesterday. Usual t6c altimeter & hrm and globalsat gps merged data.

Here is original data from altimeter. As you can see weather changed and it tilted altitude data and values are also way to high, so here the gps based correction is handy, same data at AP looks and is far accurate.

Friday Apr 1, 2011 #

Skiing 1 [0]

same with AP elevation correction. Barometer data looks far better/accurate than this.

Skiing 1 [0]

Same, with gps elevation data. Not as good as barometer based data, but better than elevation corrected data. But gps was pretty accurate here, it's not always like this - and especially not all gps units.
7 PM

Skiing (skate) 1:08:20 intensity: (1:29 @0) + (22:39 @1) + (42:18 @2) + (1:54 @3) 18.72 km (3:39 / km)
ahr:129 max:159

At paloheinä again. No gps hickups. Elevation data is barometer based GPS calibrated from Suunto t6c.

Thursday Mar 31, 2011 #

Skiing (skate) 52:49 [3] 15.65 km (3:22 / km)
ahr:159 max:181

Here GPS track, hr data and altimeter based altitude data is in sync. You can nicely see how in downhills speed goes up, alttude goes down and hr goes down too with a little delay. altidude data is calibrated using gps altitude data at the start and end of the workout. So weather changes will not affect that much.

Strange gps error (@ about 47 min).

Wednesday Mar 30, 2011 #

Note



I removed original battery from the camera. it makes the camera part really lightweight, improves image quality because it doesn't bounce that easily. I added remote batter pack on the back of the head. 2 x AAA lithium ion cells gives about 100 minutes hours shooting time. Total weight camera + battery + headband + wires is 85g.

Note

excellent article here. I mean, if you focus on the O technique part and not too much think about head cam issues - there lots of good stuff and it works as a nice introduction to orienteering technique basics.

There is chapter about how on could adjust/optimize map reading strategy by terrain's runnability/visibility. I'd add/note each individual could or should do the very same by his own vision and map print quality/scale. Old folks (with glasses etc) can't see map so well while running and younger athletes cant read 15 000 map or badly printed 10 000 map that well. That's something I have been thinking about lately, would be fun to hear what someone like PG thinks about the issue.
7 PM

Running 33:52 [0] 3.13 mi (10:49 / mi)
ahr:140 max:181

sunset run to malminkartano hill

Tuesday Mar 29, 2011 #

Running 19:39 [1] 2.75 km (7:09 / km)

http://www.movescount.com/moves/move1578163

Testing t6c. works like a charm. This means barometer based altitude data for head cam videos.

Monday Mar 28, 2011 #

Running 10:00 [1]

to daycare and back

« Earlier | Later »