|
Welcome Zimal!
Thanks for your query - and I realize I mistakenly gave incorrect information in my first post about where a route's 1st call beaten lengths were measured (correct answer is the 4f point for ALL routes), and also where the 2nd call beaten lengths (correct answer is the 6f point for ALL routes).
Perhaps that lead to the confusion.
So, for the horse shown, its last line, its beaten lengths at the 1st Call point (the route 4f point) were: 2.6. Thus, we use half of 2.6 or 1.3 for the extracted sprint's beaten lengths at the 1st and 2nd call points (2f and 4f). The horse's beaten lengths at the 2nd Call point (the route 6f point) were 3.5. Thus, we use half of 3.5 or 1.75 (rounded up to 1.8) for display purposes, for the extracted sprint's beaten length stretch and final call points (6f and final times in this extracted 7f sprint). I believe you were thinking perhaps that each call point's beaten lengths were simply halved, which is not the case: we only use up to the 6f point of the route (which covers most, or more, of all sprints) and presumes (as a generality, not a specific fact) that the horse will be closer to the lead over the shorter distance.
Having fabricated some beaten lengths for our extracted sprint, we employ those beaten lengths when calculating velocity for the sprint's 1st call (2f point), 2nd call (4f point) and final time (and thus by extrapolation, the 2nd fraction and 3rd fractions). The stretch beaten lengths and time are used internally in one factor only - the V/DC factor, otherwise they are ignored in all other calculations of Fraction 3.
Hope that clarifies things, and my apologies for incorrect information originally (I corrected my post above, and noted the change I made).
I hope that explains this.
Ted
__________________
RDSS - Racing Decision Support System™
|