|
JCapper Message Board
JCapper 101
--
Track Weight question
|
|
By |
Track Weight question |
forecast 10/17/2009 11:12:28 PM | Hi Jeff,
Is there a way to make a UDM NOT flag a horse when the TrackWeight field in the Track Weight Table Interface reads 5.0? Also, is there a way to automatically populate the Track Weight Table Interface from a Data Window query on Track Weight?
My UPR is speed-favoring and I would like to be alerted to UDM plays involving my UPR only when the play in question is going to be contested over a speed-friendly surface.
Thanks,
Jon
| jeff 10/18/2009 2:15:37 PM | Hey Jon,
Let's talk about your second question first. --quote:
Also, is there a way to automatically populate the Track Weight Table Interface from a Data Window query on Track Weight?
--end quote--
Currently no... although it's a feature I've often thought of adding as I think it would be useful.
For the benefit of those who may not be aware - here's an explanation of how the Track Weight Table Interface works:
Track Weight begins with classifying individual surface/distance categories into one of five categories for track weight:
1. Speed Favoring (Strong)
2. Speed Favoring (Somewhat)
3. Plays Fair
4. Speed Tiring (Somewhat)
5. Speed Tiring (Strong)
Track codes, surface, min and max distance, track weight (on a scale of 1 to 5 shown above), and IV adjustments for CPace and CompoundLate are all manually keyed into the TrackWeight Table using the Track Weight Table Interface available from the System Settings Interface.
During Calc Races and Build Database routines, JCapper gets track weight info from the TrackWeight Table and applies it to UPR and UserFactors using CPace and CompoundLate as part of the factor mix.
The Track Weight Table Interface can be a great way for users to adjust UPR for track weight on the fly.
On to your first question:
--quote:
Is there a way to make a UDM NOT flag a horse when the TrackWeight field in the Track Weight Table Interface reads 5.0?
--end quote--
The Profile Marker (where UDM Defintions are evaluated) does not make a separate evaluation of the TrackWeight Table. So technically, the answer to your question is "no."
However, the practical answer to your question is "yes."
Here's how:
Run each of your UDMs through the Data Window broken out BY TRACK. You'll see at a glance which tracks are your good performers and which are bad.
From here, IMHO there are two ways to aproach track weight in UDMs:
1. Use the Avoid Track Code(s) function. On the left side of the UDM Wizard Modify UDM Screen, check the Avoid Track Test Box, key the 3 character track codes that you want the UDM to avoid into the AvoidTrackList field, and hit the Save button. If you want the UDM to avoid multiple track codes, separate each 3 character track code with a dash character... like this: WOX-DMR-HOL-SAX-OSA-CDX. If you make your avoid track codes one and the same as the track codes in your TrackWeight Table where track weight=5 then your UDM never flags a horse at a track weight=5 surface-distance category.
2. You can also create a set of negative expectation UDMs based on each of your track weight=5 surface-distance categories. Your positive expectation UDMs will still mark horses at track weight=5 surface-distances... However you SHOULD be able to pass on such horses because they will also be marked by the negative track weight=5 UDM.
-jp
.
~Edited by: jeff on: 10/18/2009 at: 2:15:37 PM~
| forecast 10/18/2009 11:37:56 PM | Hi Jeff,
Thanks for the idea for making negative UDM's based on Track Weight, I hadn't thought of that. I have used the Avoid Track check box and codes for closer's tracks in my UPR-based UDM's, but I was/am hoping for a more streamlined, automatic approach - maybe in a future update? Automatically populating the Track Weight Table based on current results from each track/surface/distance will put real teeth into measuring the bias of the racing surface while saving a lot of time-consuming, tedious data entry.
Thanks again,
Jon
|
|