Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: Jagge

In the 29 days ending Feb 29, 2012:

activity	#	time	miles		km		+m	load
Running	28	18:45:37	159.79		257.16		371	194.0
Skiing	4	6:09:16	44.55	(8:17)	71.7	(5:09)	122	60.0
Trail running	3	1:35:40	3.16		5.09			19.1
Generic training	1	1:35:05	9.41	(10:06)	15.15	(6:17)		19.0
Forest run	1	46:10	3.51		5.65			11.7
Total	37	28:51:48	220.43		354.75		493	303.9
[1-5]	32	28:45:12

2:00

0:00

» now

Wednesday Feb 29, 2012 #

Note
(rest day)

my last day at work. From now on I am full time 3k runner. not taking makkara bet anyhow seriously...

C • Uh-oh 1

Tuesday Feb 28, 2012 #

7 AM

Running 30:38 5.35 km (5:44 / km)
ahr:146 max:182

AM run. I tried to do most things "wrong" for test reasons. I started running immediately without waiting for satellites and held watch in position where antenna was shooting left-down. About worst track you can get with this unit. HR strap was too loose and was about to slide down, but that wasn't intentional.

9 PM

Running 18:36 2.93 km (6:21 / km)
ahr:127 max:141

Running 17:56 2.8 km (6:24 / km)
ahr:129 max:139

Monday Feb 27, 2012 #

Note

Last 6 training recorded with Ambit and uploaded using AP's batch import tool.

Note

ha ha, ridiculous camera phone, 41 (!?) megapixels.

7 AM

Running 30:39 5.31 km (5:46 / km)
ahr:138 max:178

Started without waiting for satellites, jogged clock hand a bit raised until heard the "satellites found beep" and then pressed start button and jogged on. Track accuracy is rather poor at first, surely waiting stationary for a while isn't a bad move at all.

Sunday Feb 26, 2012 #

9 AM

Skiing (skate) 1:14:38 15.54 km (4:48 / km)
ahr:126 max:154

8 PM

Running 16:26 3.02 km (5:26 / km)
ahr:140 max:177

9 PM

Running 10:11 2.5 km (4:04 / km)
ahr:167 max:175

Last half of my 5k test run route. loose snow made it slippery, face planting after after one minute did cut some of the speed and will to push really hard.

Running 9:01 1.39 km (6:29 / km)
ahr:124 max:142

Saturday Feb 25, 2012 #

9 AM

Skiing (skate) 1:53:09 23.43 km (4:50 / km)
ahr:133 max:164

Thursday Feb 23, 2012 #

7 PM

Running 21:18 3.29 km (6:29 / km)
ahr:117 max:137

Wednesday Feb 22, 2012 #

Note

About around Christmas all data from Rastivarsat DOMA dissappeared. No users, no maps. Jpg files were there but datamase was just empty. Same happenend here http://okvaal.blogspot.com/2012/02/new-pb-on-3000-...

Make sure you have backed up your data.

C • Hole ? 3

8 PM

Running 1 [0] 4.13 km ( / km)

http://www.routegadget.net/gps/gpx2dotmap.php?sess...

No matter what I do with this 910xt seems to find its way to be off. It tracks relative movements mostly just fine, it just gets off and drifts here and there all the time, even in open areas. I think it must know it is off, and to avoid sharp turns/jumps back to right track an algorithm moves gently during next minute closer to right track. that make track look fine without any reference and maybe distance is good too. It might be good for triathletes, but it may be a bit annoying for O use. You sure can move the track on map to right place, but I prefer it being spot on from the beginning and if there is errors i like to identify those by seeing those jumps. Definitely step back from x05 devices what it comes to gps.

Ambit is more close to right track but it has more little zigzag. Easy to filter if needed. There is no room in Ambit for bigger antenna and it has same sirf4 chip as in 910, so it can't be more accurate at lower level, this is some sort of post processing/filtering issue.

Running 24:29 4.15 km (5:54 / km)
ahr:130 max:153

http://www.routegadget.net/gps/gpx2dotmap.php?sess...

Tuesday Feb 21, 2012 #

7 AM

Running 1 [0] 9.53 km ( / km)

910xt. Had it the wrong way around, antenna pointing straight down. Tried to put it right but in hurry missed the rotation. At least this proofs position matters. track is funnily off about 10..40 meters. Better attempt on the way back. Better attempt in the evening.

Running 57:21 9.87 km (5:49 / km)
ahr:140 max:168

Ambit

5 PM

Running 1 [0] 9.76 km ( / km)

910xt, upper arm, antenna pointing upwards. Better, but not waited long enough satellites.

Running 49:20 10.25 km (4:49 / km)
ahr:153 max:187

Ambit, wrist. part of the track is missing.

These two logs show you really should wait for satellites to lock longer than the amsolute minimun/start moving before proper fix.

Looks like 910xt's track is more post processed and filtered, even if it is off a lot it looks smooth. Ambit's track looks more raw data. Hard to say how much usefull data is lost in garmin filtering.

Sunday Feb 19, 2012 #

Note

Ambit's track on O map with ISOMish sumbols sizes:

Used a sort of 3 point adjustment here.

7 AM

Running 1 [2]

910xt

C • Joke 8

Running 33:38 4.22 km (7:58 / km)
ahr:138 max:170

suunto ambit

2 PM

Forest run (deep snow) 1 [3] 0.0 km

Ghetto cap logger
Dot map analysis

C • Nice work 1

Forest run (in snow) 46:08 5.65 km (8:10 / km)
ahr:146 max:165

Suunto Ambit in left hand

Forest run (in snow) 1 [0]

910xt in left hand

Saturday Feb 18, 2012 #

8 AM

Running 29:37 4.94 km (5:59 / km)
ahr:137 max:163

From Ambit. I guess speed values here at AP aren't original "fused speed" ones and distance either since this is gpx upload. Elevation values are barometer ones.

Dot map analysis

C • Let the tests begin ? 1