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

Training Log Archive: Jagge

In the 31 days ending Oct 31, 2013:

activity # timemileskm+mload
  Running9 5:46:32 24.63 39.6393.1
  Orienteering5 5:29:03 26.19(12:34) 42.16(7:48)115.1
  Trail running2 2:29:17 13.43(11:07) 21.62(6:54)29.9
  Total15 13:44:52 64.25 103.4238.1

«»
2:14
0:00
» now
TuWeThFrSaSuMoTuWeThFrSaSuMoTuWeThFrSaSuMoTuWeThFrSaSuMoTuWeTh

Wednesday Oct 30, 2013 #

8 PM

Running hills 51:41 [2] 7.12 km (7:16 / km)

Saturday Oct 26, 2013 #

1 PM

Orienteering 2:14:30 intensity: (45:00 @2) + (1:29:30 @3) 14.15 km (9:30 / km)

Tuesday Oct 22, 2013 #

Running 37:00 [2]

Sunday Oct 20, 2013 #

4 PM

Orienteering hills 52:27 intensity: (37:27 @2) + (15:00 @3) 8.36 km (6:17 / km)

5 x Malminkartano hill

Saturday Oct 19, 2013 #

Note

Orienteering race 42:30 [4] 6.4 km (6:38 / km)

Halikko.

Wednesday Oct 16, 2013 #

7 PM

Running 45:50 intensity: (30:50 @1) + (15:00 @5) 7.46 km (6:08 / km)

4 x 1000m

Tuesday Oct 15, 2013 #

7 PM

Trail running 1:10:59 [2] 10.26 km (6:55 / km)

Head lamp run

Monday Oct 14, 2013 #

Note

25-manna check-in. They used bar code reader to get number from bib number and SI unit to get card number. Then we had to wait 20 sec, apparenty the app connected to a (remote?) database and inserted data there. Makes me wonder was/is the whole system based on that approach, central database server and clients connecting there storing data there. And when something is wrong, server, database, network, power etc, one can't do anything but wait for system to become up and functional again.

I'd say there is room for improvements there, one can't expect all systems are up and running all the time and that there would be no hardware failures.

As a comparison, system used for Jukola is based on sort of separate standalone apps. You read barcode and card number and data gets stored to local file/database. You can immediately take next runner without having to wait for anything. A background process syncs data with other computers. If network is down you can still keep on checking in runners in and when network is back data gets synced. Same with every app and feature, download, printing, the wailing wall, commentators apps etc. There is no central server every app depends on, even if half of the computers burns and network is down the rest of the stations would still operate. And they also test it before the event by taking computers down, shutting down routers and unpluging network and power cables to make sure everything still works and data gets synced when network and power is back.

Thinking of 25-manna entry incomes one would think there is enough resources to get that done a bit better. Simple and obvious things mostly, no innovations or rocket science needed. Just saying.

Sunday Oct 13, 2013 #

7 PM

Running 27:36 [2] 5.14 km (5:22 / km)

Saturday Oct 12, 2013 #

Note

12 PM

Orienteering 39:43 [4] 6.45 km (6:09 / km)

25-manna leg 5. Ok run. Should have gone straight to #13, 20sec lost palyed safe for no reason. And I wasn't flying, but I have had worse days, hard to say had those track workaouts any effect.

Dot map analysis

Running warm up/down 25:00 [1]

Warm down. I did not warm up much at all (othe than some jumping up and down at check-in line).

Wednesday Oct 9, 2013 #

5 PM

Running race 10:57 [5] 3.0 km (3:39 / km)

3k track again. No changes.

Running warm up/down 30:00 [1]

Tuesday Oct 8, 2013 #

8 PM

Running 27:31 [2] 5.05 km (5:27 / km)

Monday Oct 7, 2013 #

7 PM

Running intervals 55:00 intensity: (40:00 @1) + (15:00 @5) 8.86 km (6:12 / km)

4 x 1000m on gravel road with long rest in between.
Times 3.35, 3.33, 3.38, 3.35

Sunday Oct 6, 2013 #

7 PM

Trail running 1:18:18 [2] 11.35 km (6:54 / km)

Saturday Oct 5, 2013 #

Note

6 PM

Running race 10:57 [5] 3.0 km (3:39 / km)

3k track. awful. Over one minute too much. no need to wonder why I am so slow in forest, shape is just so poor and asthma doesn't make me any faster at the moment either.

Track pod measured it 2997m, three meters short. Well, I did stopped it a bit late, so it measured it maybe ten? metes short. GPS elevation was between 12 and 15 meters, so altitude accuracy was about +-1.5 m. not bad for a gps. I had ambit too and pod measured elevation better than ambit's barometer. And Ken says gps alti accuracy is so poor it's not worth importing to AP. Hmm...

Running warm up/down 25:00 [1]

Wednesday Oct 2, 2013 #

8 PM

Orienteering (night) 59:53 [3] 6.8 km (8:48 / km)

« Earlier | Later »