|Back when I first created the program that would eventally evolve into JCapper I had to draw the line somewhere --|
I decided to use one mile as the point of delineation between sprints and routes.
Everything under 8f was labeled as a sprint. And everything 8f and longer was labeled as a route.
There's no reason anybody has to adhere to that.
I certainly don't (and neither do you.)
Fyi, in my own work (mlr models, upr, userfactors, udms, etc.) I actually make it a point to look at data for individual track-surface-distances.
I even written about that in the Help Doc for keying logistic regression models into JCapper's UPR Tools.
"Q. What is a SubGroup?--end quote
A. In JCapper a SubGroup is a named collection of entries designed to handle a specific category - such as an individual track-surface-distance.
For example, both Belmont and Saratoga have two turf courses - an outer main turf course - and an inner turf course.
In UPR Tools, you could create one set of entries designed specifically for Belmont's inner turf course.
You could give that set of entries a name by keying "BEL-t" (without the quotes) into the SubGroup field. -- And at that point, in JCapper, that set of entries would qualify as a SubGroup."
While it's true that the drop downs for distance on the playlist file mode side of both the UDM Wizard and Data Window have available selections of S for sprint and R for route --
Those same drop downs also have available selections for individual distances.
If you are operating in playlist file mode, you also have the ability to use preset filters to set min and max distance as well as filter out individual distances in your udms.
Meaning that it's pretty easy to create udms to handle the 7.5f distance separately should you decide to do that.
If you are operating in sql mode, you have the ability to key min and max dist directly into the sql expressions driving your UDMs.
And in UPR Tools, you have boxes for keying min and max dist directly into the entries that drive your UserFactors and UPR.
So while there isn't a setting in JCapper that let's you define 7.5f or 1650 yds as the point of delineation between sprints and routes --
There's also nothing in JCapper stopping you from using 7.5f (or any distance for that matter) as the point of delineation between sprints and routes in your work.
I hope I managed to type most of that out in a way that makes sense.