1. How is the Track Weight interface used? My spread sheet is blank, what needs to be done for a database to be created for it etc...?
2. On the Track Weight Report via the data window how is the scale of 1 to 5 calcuated? Sometimes I am not sure I see where it gets the speed friendly vs. tiring when analyzing the respective results of cpace123 v. comlate123.
"1. How is the Track Weight interface used? My spread sheet is blank, what needs to be done for a database to be created for it etc...?"
--end quote
It's a two step process. If your report is blank my first best guess is that you haven't yet run a Data Window query after toggling the export function on.
Not sure what I am doing wrong, but that doesn't work for me. The Jeff's Export, John W.s export, or the Play History table don't do anything in relation to my Track Weight Table located via System Settings.
Not sure what I am doing wrong, but that doesn't work for me. The Jeff's Export, John W.s export, or the Play History table don't do anything in relation to my Track Weight Table located via System Settings.
Bill, my bad. I completely misunderstood you when you asked about the TrackWeight Table Interface. I incorrectly thought you were asking about getting a Track Profile Export to run. The TrackWeight Table and the Track Profile Exports are two completely different things.
Complete functionality (as in a Wizard) for the TrackWeight Table is still under construction. Basic bare bones functionality IS currently enabled.
The idea behind the TrackWeight Table is that it can be used to store entries that will affect UPR and UserFactors. But if and only if said UPR or Userfactors have Cpace or CompoundLate as part of their makeup.
Example: You are playing at a track you believe to be highly speed favoring. You can use the TrackWeight Table Interface to emphasize CPace for the duration of the bias. Bring up the TrackWeight Table Interface, key in your 3 character track code, surface code (D* or T*) min and max distance, track weight (integers on a scale of 1 2 3 4 5 with 1 being speed afavoring and 5 being speed tiring) followed by a positive impact value adjustment for CPace (1.25 for example) and a negative impact value adjustment for CompoundLate (.80 for example)... also be sure to activate the entry by keying -1 into the active field.
When you run a Calc Races or a Build Database, if your UPR uses CPace or CompoundLate, the program will adjust the UPR of horses with strong CPace upwards when the race is run at the track surface and distance specified by your track weight table entries.
You can keep sets of inactive entries stored in the table - and then activate them on those days where you notice a strong bias.
Just like UPR, it takes a fair amount of experimentation to get it right. But when done right, TrackWeight Table entries can boost the performance of your UPR.