[OUTDATED] How to repair missing split times

All threads that are outdated (e. g. problem with an older version that was replaced by a new one) are moved here.
Post Reply
User avatar
Harry
Site Admin
Site Admin
Posts: 10126
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

[OUTDATED] How to repair missing split times

Post by Harry »

THIS POST IS OUTDATED AS LT 16.6 AND LATER HAVE A FUNCTION BUILD IN TO RECALCULATE SPLITS

Hi,

LapTimer has a nice feature to derive a 'virtual best lap' from existing recordings. These are calculated by analyzing split times and adding up the best split times found. The place to best view lap times, split times, and resulting best virtual times, is in the data recording area - accessible from Lap Details.

But - what happens if LapTimer misses a split trigger and joins two sector times into one? Well, this will result in a lap with a lower number of splits than others. In addition, LapTimer starts adding up split times actually not related to each other - which in turn results in meaningless calculations.

There are two strategies to work around this situation:
  1. purge all split times from the errornous lap to at least not mess up the virtual lap calculation
  2. recreate the missing splits from the data recordings to get a correct virtual lap calculation
Strategy #1 should be applied in case it is too complicated for you to follow strategy #2. This at least produces no errors. Simply navigate from Lap List to the Lap Details for the errornous lap, press 'Edit' and purge the splits.

The rest of this post is on strategy #2, using a step by step. Please note this is really not trivial, so really go with #1 in case this produces a headache for you :-)

The first picture is the 'problem statement': the 9:40.15 lap misses one split, it has 3 compared to all the others...

Image

Navigating into the Laps Data Recording View shows what happens when LapTimer tries to align the sector times. Sector #1 and Sector #2 are taken into account correctly, but #3 is were other laps have #3 and #4, and #4 is what is #5 in other laps. So we potentially miss a better virtual lap in the joined #3, and probably get a wrong (too good) virtual best when #4 is a very short sector.

Image

The next picture gives an idea of what needs to be done: we need to insert a new split just before Split 3 - making it the new Split 3. Split 3 get #4 and so on...

Image

To add this split, we export the lap to the .hlptrl format - which is an XML document. We will edit this file / add the missing split and import it later to replace the old version. Export the .kml file in addition, we will use this later.

Image

Looking into the XML file, we see the <intermediates> section which lists the split times plus the distance from start in meters. Comparing it to the last picture, you see that we will add a line here later... In the sample below - as I'm an old fashioned guy - I did use a very old editor named 'vi' or 'vim'. Please take care that whatever editor you use, it needs to be able to edit plain text files. Do not use regular text editing programs like Word - this will mess up everything.

Image

What needs to be done? We need to understand what the correct split time has been, and at what distance from start it occurred... To find this out, open the .kml file exported above and navigate tho the area the problem occurred. In our example, the GPS sensor lost its lock near 'Ex-Mühle' / 'Posten 122' on our famous Nordschleife in Germany.

Image

To approximate the distance and time of the missed split, we select the GPS fix that best matches it's position.

Image

Looking into the GPS fix's Infos, we read out the polar coordinates of this fix. Write it down, we will copy it into the .hlptrl file later.

Image

Now we search for this fix in our .hlptrl file. Use the polar coordinates from above and enter an appropriate part of it as the search term in your text editor. Next, copy the <relativeToStart> section as it has prepared both the missing split time and the distance from start for us :-)

Image

Navigate back to the <intermediates> section now and enter the split time and distance in exactly the format all the other splits appear. You need to exchange the order of time and distance here... This is actually the only time you edit anything, everything else it just browsing.

Image

Save your .hlptrl file now and send it to an email address you use on your iPhone. Once it arrives in your Mail app, long-press the attachment and confirm import into LapTimer.

Image

Once it is imported, we have a new 9:40.15 lap with 4 splits - great! Delete the old lap now and we are done.

Image

Check the Laps section in Data Recordings again. Although this change did not change the virtual best lap time, everything looks nice and consistent now.

Image

- Harry
Image Image Image Image
K20Performance
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 4
Joined: Thu Aug 23, 2012 4:24 pm

Re: [FAQ] How to repair missing split times

Post by K20Performance »

Hi,

For the last couple of weeks i have been recording my laps to and from work without problems but since update 16.0.4 it doesn t record the split times anymore. The start and stop triggers still work but all my split triggers don't.
Do i need to do something to get this to work again?

Thank you.
User avatar
Harry
Site Admin
Site Admin
Posts: 10126
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

[FAQ] How to repair missing split times

Post by Harry »

Please export one of the laps missing the splits to KML and have a look into it. The KML export is very good as you see both the line and the POIs. I assume the split triggers are a bit away from the line driven and need to be readjusted. The change can happen e.g. because GPS accuracy is better than before - this makes LT narrowing the detection corridor.

Harry
Image Image Image Image
K20Performance
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 4
Joined: Thu Aug 23, 2012 4:24 pm

Re: [FAQ] How to repair missing split times

Post by K20Performance »

I ve checked it, all the split triggers are correct.
I did notice that the driven line is not on the road all the time.
I use the Tom Tom iphone holder while using LT.
I will try again tomorrow.
On my way home today it did catch almost all of the split triggers.
Keep you posted.
User avatar
Harry
Site Admin
Site Admin
Posts: 10126
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

[FAQ] How to repair missing split times

Post by Harry »

In this case, please set the detection corridor to 'Wide'. It is available in LT's Settings.

Harry
Image Image Image Image
K20Performance
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 4
Joined: Thu Aug 23, 2012 4:24 pm

Re: [FAQ] How to repair missing split times

Post by K20Performance »

Detection set to "wide", problem solved.
Detected all split triggers.

Thank you.
Post Reply