|
Jun 2013
1:06pm, 7 Jun 2013
15,645 posts
|
sioux
Just let me fire up laptop and Garmin and will be right back to you.
|
|
Jun 2013
1:09pm, 7 Jun 2013
4,650 posts
|
rf_fozzy
The raw data should be in miles though, as that's what I record on the Garmin. It's just that I do the import on here in km.
Which is what I've always done
Is there a big difference in the actual way the code is processing the data now? Or have you simply transferred a new version of the old code, with some tweaks etc?
|
|
Jun 2013
1:11pm, 7 Jun 2013
12,935 posts
|
fetcheveryone
The raw data is in degrees 
|
|
Jun 2013
1:18pm, 7 Jun 2013
4,651 posts
|
rf_fozzy
Yes, I know that!
The way you calculate distance is obviously based on that data - which is what the Garmin unit does itself. And then the difference in time gives you that particular split.
What I'm trying to understand is what's the difference between the way the code used to differentiate based on the splits I'd defined on my Garmin (i.e. 1mile units) and how you are calculating the splits based on the base unit defined in each users training log (i.e. in this case km). And what difference is there is defining the split as 1km or 1.61km?
Or is there a flag in the data file to indicate each recorded "lap" (whether 1mile, or when the "lap" button is pressed).
The importance of this is going to come for interval sessions, as I don't need to know my 1mile time, 1km time or whatever, but I do want to know what time I run for each interval over the session, so I can see if I hold my times etc.
|
|
Jun 2013
1:21pm, 7 Jun 2013
1,306 posts
|
trendy runner
Just uploaded very quickly from my 310XT, no freezing or anything
|
|
Jun 2013
1:22pm, 7 Jun 2013
4,652 posts
|
rf_fozzy
This is an example from my last 800m intervals session:
Split Summary
====
1) - 0.86km - 2:53(3:23/km) - 67cal
2) - 0.23km - 1:26(6:20/km) - 21cal
3) - 0.84km - 3:01(3:36/km) - 66cal
4) - 0.23km - 1:31(6:29/km) - 24cal
5) - 0.83km - 3:01(3:39/km) - 62cal
6) - 0.21km - 1:34(7:19/km) - 19cal
7) - 0.82km - 3:05(3:46/km) - 65cal
8) - 0.22km - 1:30(6:42/km) - 19cal
9) - 0.83km - 3:10(3:48/km) - 67cal
10) - 0.22km - 1:36(7:21/km) - 19cal
11) - 0.83km - 3:08(3:46/km) - 65cal
12) - 0.22km - 1:35(7:16/km) - 19cal
13) - 0.83km - 3:06(3:44/km) - 65cal
14) - 0.22km - 1:32(7:05/km) - 20cal
15) - 0.83km - 3:08(3:45/km) - 65cal
16) - 0.22km - 1:23(6:11/km) - 19cal
It's useful to see each 800m split (ok the Garmin gets the dist slightly wrong on the track) - I don't want this to autochange to 1km splits over the session, as it would be meaningless with the recoveries in there as well.
|
|
Jun 2013
1:29pm, 7 Jun 2013
3,667 posts
|
paul the builder
^^ Yes, this is important. The import (which I haven't and can't try yet, I'm currently sans Garmin until the postman delivers me a shiny new one) really needs to keep the "laps" in the same place as they occurred during the run. And Fozzy's interval session is the best example of why.
|
|
Jun 2013
1:38pm, 7 Jun 2013
15,648 posts
|
sioux
mine now seems to stick on -- Import complete, processing data
and goes no further
|
|
Jun 2013
1:39pm, 7 Jun 2013
15,649 posts
|
sioux
have not read the thread but hoping Fetch understands this in relation to the problems I've encountered.
|
|
Jun 2013
1:46pm, 7 Jun 2013
12,936 posts
|
fetcheveryone
Sioux - could you cut-and-paste the diagnostic information.
Fozzy - I do take your point, and I can get at the Garmin-generated lap data. Bear with me for a while, and I'll see if I can incorporate it.
|
