I've been working on a project for tbreds.
Using Equibase data that generates the Past Performance Running Line Preview chart below the detailed chart for each race in the Full Charts section.
For each race, I'm generating a line graph. One line per horse. Each horse assigned a different line color. Leftmost data point X axis is first call. So on, until the rightmost which is finish. Y axis is lengths behind leader (or leader "by" lengths)
So you have a line graph with i.e., 10 lines depicting - left to right - the running of the race.
On a day with a speed bias, you'll see more of the top finishers at the top of the entire chart.
On a day with an anti-speed bias, you'll see more of the top finishers start at/toward the bottom left and finishing at/near the top.
I find this a very useful visual
In reviewing one card of charts, the optimal result is finding a very small number of horses that ran well against whatever bias there was.
Now a lot of races fall apart on the front and the finishers just passed tired horses. Or the LAte Pace types were just trash and were never going to run well in any scenario. So while useful, limited. Plus defining track bias is very subjective.
So some of these horses are your first cut and go into virtual stable. Then you look for return race with a better pace/trip set up.
I've chosen Turfway because I want Synth (fewer shippers) and large fields. When Turfway ends, Woodbine starts.
I've worked through the prior two meets at Turfway and am still learning. About 40 hours in and at least that much more work to do.
I think its a fools errand but I've seen some very positive things.
I'll probably get bored and quit.
