Dan, something like this? It took me about 5 minutes, as you said (so I feel like I didn't waste much time away from other stuff to try this
). Line graphing the info would take longer.
In just this example, not sure what use to make of these figs ... I will leave them in for the next round of RDSS Update testing, though not guaranteeing they will make a final/public cut.
I do recall something similar in maybe PaceLauncher, or Quad-Rater, maybe Synthesis as you suggest. Anyway, a differential between PoR and PoH velocities to see how a horse is setting or overcoming (or not) the pace of its race.
I have been guided by Doc - in person early on with RDSS - and then in 'spirit' by asking the question: why is such and such a readout (from earlier software) NOT included in Validator (the reference point for RDSS along with Speculator, since I had the source code). I have to believe, in a larger context, that Doc only removed things, compared to earlier software, because he believed it was more noise than signal - more confusion than clarity - too much detail. I don't know if this Pace Vector idea qualifies as too much, or redundant. I am open to being persuaded otherwise, but there would have to be multiple scenarios where this info provides BETTER info than what is existing.
In other words - every new readout has to earn its keep. Already, people try RDSS and are overwhelmed. I don't want to disservice future users by adding more. But - if it can be turned into some kind of (even situational) secret sauce, then lets keep on researching.
Ted
