#litpro

The good news is that we think we can change.  And btw, the visuals aren’t just an attempt to make things look cool.  We’ve been researching solutions to the problem for quite some time.  Our first approach was to curate them ourselves (notice the curated and HD Trackmap icons in the screenshot below):

manual curation effort

We realized months ago that that wasn’t going to work either since there are just too many tracks getting created every day.  So for the last few months we’ve just been letting our customers suffer through it... Sorry!

Our next approach... this one actually... is to do a combination of automation as well as some internal tools to help us look for clusters of tracks.  Generally we think that if there are more than 3 options at any one spot, then it is asking too much of the LITPro user to figure that out and typically something not-so-good happens, which is the user creates yet another new track... further exacerbating the problem.  So our tools now help us look for clusters of tracks where problems exist and after applying automation, one of our admins can quickly jump in and sort things out further manually.

Australia track map clusters

Two-stage Track Config Cleanup Strategy...

Starting immediately you’ll notice that we’ve built some automation to clean things up.  This means that we use some pretty simple logic to look at the track config and if it isn’t what we would consider a “good one” or rather a good one for the general public, we just delete it.  This makes sense because a lot of times a track config is created to solve a short-term need, like learning how to use the system, or maybe even looking at a crash.  So you create a custom config and it isn’t valuable to the public, or even you really after the analysis has been made... you’ll notice that most likely that track is now hidden in the system.  NOTE! your data isn’t hidden, your sessions at that track will exist forever, but your ability to log new laps at that track are now gone.

In the next release or two you’ll notice some improvements to track configs in the sync app that will enable us to do a lot of cool things that we’ll announce later.  But most importantly new changes coming to the app will make it easier to name a track if you are creating a new one, version a track if you are just making changes to a track, and last but not least make it easier to know if there’s already a suitable track to select from that someone else has already created.  More on these new app features coming soon.

What you need to know (BRIEF VERSION)...

We have dramatically cleaned up the track configs across the globe deleting the ones we didn’t think were good “public” tracks

NONE of your existing session data is lost, even if we did delete the underlying track config

If we deleted a track config you are still using and you want us to restore it just ask... restore deleted track config request Just let us know the name of the track you want restored.

If you are still seeing too many track config options at your local track also let us know and we’ll scrub it a little cleaner.  Track config scrub request  Just let us know the general area and we can do the rest.

REMINDER: Quick tips on creating a good track config

Give it a good name... i.e. Milestone Main V2

Create it with 3 to 5 segments

If a moto track, use the same start and finish line

Here’s what you can expect to see with this release:

Added ZOOM (custom zoom ranges)

Added ZOOM (automatic by track segment)

Ghost lap feature fully supported in this new zoom view

Completely re-worked segment summary, segment details and segment map view reporting (the old segment reporting is gone!)

10X faster HD Track Map rendering

Added Drift Correction

Session Weather now works for non-US sessions

Better metric unit support, including showing Celsius vs Fahrenheight appropriately

We think this is the biggest release we’ve ever made as a company, so we hope you’ll be as excited about it as we are.  Our goals for this release are as follows:

To better identify the areas on the track where you can make the biggest performance improvement.

To better compare performance in specific sections or turns/jumps between laps. Now you can see exactly what line or rhythm choice was faster.

To better match up your line with the underlying map of the track.

Everything we do is to help our riders get faster and we hope that these new features translate exactly in to that.

MORE ABOUT ZOOM

We’ve been asked tons of times why we didn’t support pinch/pull/pan, all the typical mapping application gestures.  Well here’s the answer...  NONE of the LITPro app interface is map based except setting up a track configuration.  This spawns from a few different things...

1). Our GPS resolution is higher than Apple/Google maps allow currently in their SDKs. Prior to iOS7 when they went to a 64-bit architecture/instruction set, Apple’s internal floating point numbers weren’t event big enough to store the lat/long resolution of a coordinate at the precision level that LITPro was tracking them at.  So our lines had this ugly jaggedness as the coordinates rattled around in the sub-epsilon ranges of what could be stored in Apple’s MapKit coordinate system.  Floats in a 64-bit architecture now solve that, but not the zoom level we want to achieve with HD Track Maps.  In other words a LOT of complexity gets solved for us to present the data in the way that we do - and yeah we’re pretty awesome!

2). Even though it seems logical that pinching to zoom in is the correct way to interact with our data - and we’ve struggled with this for a while now internally - ultimately we’ve just decided a mapping environment isn’t what we want.  With a map you have the freedom to go explore anywhere you want and this degree of freedom limits the precise level of analytics we want to deliver.  For example we want to let a swipe gesture bring across a Ghosting lap, not move the viewport.  Many other examples exist...

We also don’t just show zoomed in areas of a map, instead we prioritize context and comparison.  So setting a starting and ending point for some analysis is really important to us, and you’ll see that this is handled quite elegantly when you get a chance to check this out.

ZOOM... ergo DRIFT CORRECTION

Yes there are always consequences!  Now that we let you get intimately close to your lap routes in this new version, minor variances in Satellite constellation positioning and atmospheric density changes DO cause drift even in our data sets.  These variances in drift are typically consistent, so usually you don’t see any impact between laps tracked in a single session, so while this has never impacted the value of our reporting and analytics, it is annoying to look at...  And totally unnecessary.  So introducing DRIFT CORRECTION.  See what this does in this video:

To use this, just sync your session, then inside the latest LITPro MX app, load one of your sessions, and click on the new “notes” icon in the upper right corner.  We’ve pre-populated a few data points in there, like weather, and a few section headings we think you would want to use to save some typing each time...  But as we see how it gets used (or not) we’ll adapt.

STEP #1 - BEGIN AT THE SEGMENT SUMMARY

The Segment Summary provide a very quick review of your segment performance. Before you begin your analysis, make sure you hide any laps that were abnormal. In this case, I’m showing you Ricky Carmichael’s LITPro data from one of his Legends Race practices at Ironman MX last month. I hid Lap 4 by swiping left on the lap because I didn’t want that slow practice lap to skew any of the data.

Based on a glance at this screen, you can see a total improvement opportunity of 1.8 seconds, with the most significant opportunity occurring in segment 1. In this view, the top bar is the fastest performance in that segment for the session. The middle bar is the average performance in that segment for the session. And the bottom bar is the slowest performance in that segment for the session. I primarily focus on comparing the fastest to the average performance in each segment.

STEP #2 - FOCUS ON SEGMENTS WITH THE MOST OPPORTUNITY

Now select the “Segments” view of Session Analytics. This view displays individual segment performance for every segment of every lap. This starts to complete the picture.

As you can see, RC continued to improve his segment 1 performance from lap 1 to 2 to 3 to 5. And in the bottom right corner we can see the fastest segment time was shorter (by 7.8 ft.), faster (by 0.5 mph) and included more airtime (by 0.9 sec) that the average performance in that segment. But at this point, we really want to exactly WHY the segment performance improved so much throughout the practice.

STEP #3 - DRILL DOWN TO ANSWER WHY

#1 An Awesome Experience!  Everyone who rides with LITPro will get a track-side analysis from one of our athlete team support staff.  We’ve had a lot of experience working with the best in this sport and no-matter what level you’re at, we’ll provide actionable insights that will help you get faster.  You will love the track-side experience, but you’ll also love that you get to take that experience home because we’ll copy all your LITPro performance data in to you own LITPro account that you can access on any device anywhere in the world.

#2 Ghost-with-a-Pro. LITPro is better when you have a riding buddy.  Maybe it’s the extra motivation from seeing your lap side-by-side with a friend or teammate, or maybe it’s the added analytical power of viewing what line choices they made that you hadn’t thought of.  But on DEMO DAYS, we’re taking this to a whole new level!  We’ll provide you in-app data from a pro who’s ridden the same track in the same time frame.  For #EdgeOfSummerMX, this pro is the race legend Ricky Carmichael.  For future DEMO DAYS, we’ll announce the athlete in advance and try and keep it amazing.  

We are really excited about this feature, and are even more happy that we’ve already been able to talk to so many current and former pros who are willing to give back to the motocross community in this way.

#3 Leaderboards & Giveaways!  We love leaderboards and can’t miss the opportunity to obsess just a little more about competing around these metrics.  But we do it all in good fun. In fact we’ve decided so far not to announce the metric or criteria for any giveaways until after everyone has ridden for the day.  We feel this has the best chance of keeping it fair, safe, and focused on fun.

We’ve also been putting a lot of thought into what the giveaways should be, and so far we think we’ve got some good ideas... but we’re going to leave this up to our fans.  So stay tuned over the next few weeks - or post your ideas in the comment fields below.

So where’s the next DEMO DAY??

We’re asking ourselves the same question.  If you have ideas, put them in the comments field below and get your friends to up-vote them.  Setting up for DEMO DAYS means doing HD track maps with our drone, and setting up our gear - so we’ll need permission from track owners.  

Here are a few of the new features we are excited about (already published to the Apple app store, just waiting for Apple’s approval cycle - maybe another few days):

Look for this new icon in the LITPro Sync app when picking from the list of existing track configs. This indicates we’ve created HD maps for the track you’ve ridden.  Hopefully you begin to see this more and more over the next few months as we make our way to more and more tracks.

Look for this new icon in the LITPro Sync app when picking from the list of existing track configs as it indicates the track has been curated by the LITPro team and probably a “good” choice.  We go through and make sure segments have been created, that the segments are in order, and that everything else is in order.

Look for this new icon in the LITPro Sync app when picking from the list of existing track configs to know that even if it hasn’t been curated yet by the LITPro team, that it does meet some of the basic “good practices” we’ve established. 

When you don’t see any of the above icons, you’ll probably be presented with a caution or warning indicating that we think there’s a problem, as well as some tips for how to correct it.

Most importantly though for this next release, what we are excited about is that we’ve made creating a new track config a lot more intuitive, and fault tolerant.  We’ve built in tons of automated checking and validation - our only worry is probably that we might have over-done it :)

So check it out!  We expect it to be available by this time next week (July 24, 2015).  As always, reach out to us if you have any questions.

Here are our latest tutorials too:

Getting Started Guide