A way to lock laps to prevent delete

ambordokan · Post by **ambordokan** » Thu Apr 17, 2014 1:44 pm

Hi,

Would be awesome to have a way to protect at least the best lap and the best partials so the cleaning up process after a track session would be easier. I would just delete all laps and save those ones, that are the ones that matter to me.

Cheers!
Andre

ambordokan · Post by **ambordokan** » Mon Apr 21, 2014 4:22 pm

Harry, what do you say about that?

Is this viable?

Thanks

Post by **Harry** » Mon Apr 21, 2014 4:28 pm

I have seen it but are not sure if this is another complexity added for power users disturbing the other 90%.
Like for all other feature requests, please give some time to let it grow or die

- Harry

ambordokan · Post by **ambordokan** » Mon Apr 21, 2014 9:40 pm

Hmm, I must be doing something wrong then:

When I have a practice or after a race weekend, the amount of data that stacks up is pretty high. It's not uncommon to have 50+ laps per weekend. Therefore, with a 10Hz GPS and with a 2'10" lap, you can imagine the iphone can run out of space quickly (1300 GPS points per lap, plus all the other data it logs, roughly 65000 GPS points per weekend).

All I'm asking is an easier way to do this clean up. The improvements you made recently helped greatly (sorting by session, day etc).

I don't think this feature have to disturb the others, you can simply hide this flag under advanced settings, something like "protect ideal lap". With this option, one could easily delete all his/her irrelevant laps with a swipe...

I can't see how everyone will not benefit from this feature. Any feedback from you is appreciated as always, Harry.

Cheers

gplracerx · Post by **gplracerx** » Mon Apr 21, 2014 10:40 pm

The text data for laps is measured in megabytes, probably not even one/lap. It's video that consumes memory. That's on the order of one megabyte/second at high definition.

ambordokan · Post by **ambordokan** » Mon Apr 21, 2014 10:45 pm

Harry once told me that 100.000 over points is too much, occasioning the iPhone to lag, therefore HLT to lag too. This is visible whenever you pass the Start/Finish line and the GPS miss some points, becoming inaccurate for this couple of seconds. This issue is actually even documented somewhere in this forum.

gplracerx · Post by **gplracerx** » Mon Apr 21, 2014 10:46 pm

If you want to save a lap, export it to Dropbox or email it to yourself. You can always reload it from there.

ambordokan · Post by **ambordokan** » Mon Apr 21, 2014 10:50 pm

Yes, this way you save one lap. But this do nothing about the ideal lap, the best your ever got. For me this is a big deal, I want to know how fast I ever was on a track, it build confidence.

Don't you guys care about the ideal lap? Maybe I'm overating it, but I love it. I can be wrong, though.

Post by **Harry** » Mon Apr 21, 2014 10:56 pm

The space required per position recorded is around 80 bytes. At 10 Hz, 4 hours of recording (a track day) will require 164 k bytes. So it is not about the space. LapTimer's DB scales a lot better today compared to 2 years ago. I have 300000 fixes on my device currently and cannot see an issue. This is certainly different on an iPhone4, HW development is huge... Personally I remove all incomplete laps, but keep everything else.

Harry

ambordokan · Post by **ambordokan** » Mon Apr 21, 2014 10:59 pm

Okay, so should I stop worrying about this, then? Not long ago (less than a year ago, IIRC) I had this issue, since then I always try to keep my lap list as slim as possible...