Expanding on this a little...
Let's say for example one of the things you watch for are how horses gallop out after the race is over. Your own hand kept records indicate horses that gallop out strongly are often better bets than horses that don't. One way that I've seen it done is to write down their names with the track and race date on a page in a day planner.
Something like this:
Letter at top of page: S Individual Entries: ------------------------------------------ SMART DRESSED MAN WOX 8/12/2009 - GOS SLEWS KID WOX 8/13/2009 - GOS SLIGOVITZ WOX 8/09/2009 - PUS SLEW THE DRAGON WOX 8/08/2009 - GOS SMART AND FANCY SAR 8/09/2009 - PUS ------------------------------------------
A few weeks later as these horses return to race again, the player can look up each of their names by first letter of the horse name in the day planner and see if the horse has a trip note attached to its name. It's a painstaking process time-wise but one that can pay off handsomely for the player with a talent for recognizing what to look for.
Here the player is using codes to describe what he saw. GOS stands for Galloped Out Strongly. And PUS stands for Pulled Up Short. Please understand that the player who showed me this process is a keen observer and keeps very detailed notes about what he sees. But these are NOT HIS ACTUAL TRIP NOTES. Nor are they mine. It's just an example of how the process works.
The process allows the player to look up each horse running on a given card one at a time in a day planner.
Another way is to key them into stable mail and hope that you see the stable mail and remember why you added the horse's name to stable mail in the first place.
Or you can add the names of the horses to the WatchList field in the UDM Wizard for a UDM you created for the specific category of trip note that you want to be reminded about when the horse comes back to race.
Continuing with the example that you want to know about GOS horses...
You create a UDM and name it something like trip_GOS. From your own carefully kept records you've determined that a GOS is only really worthwhile when the horse comes back to race within 9o days. So you set a factor constraint where Recent Activity Days Last Start has a max val = 90 and you click the Test box and hit Save.
About that: YOU have to determine if 90 days is the right number. Let your own records tell you that. After you've accumualated a few hundred race results for a UDM like this you can certainly run it through the Data Windoe broken out by Rec Activity Days Last Start and SEE what the right number is. That's the only real way. Anything short of that is just a guess. A lot of people doing stuff like this manually have no real idea how to make best use of their own information.
Continuing on...
Given the above GOS horses, the WatchList field itself looks like this:
SMART DRESSED MAN-SLEWS KID-SLEW THE DRAGON
Individual horse names are added with each name separated by a dash character. Also note that the UDM Wizard strips out the apostrophe character from the horse names. Don't worry about it. That's done to facilitate a SQL name match. The WatchList field itself is large enough to contain several thousand individual names.
On race day, when a GOS horse comes back to race within 90 days (or the number you provide) of it's previous race where you made the trip note - the Profile Marker flags the horse on your HTML and/or Text Report so that you'll know about it.
If you're really into making detailed trip notes you might want to keep your notes in a spreadsheet concurrently with entering horse names into a WatchList UDM - and then periodically delete individual horse names from WatchList UDMs when appropriate. But that's up to you.
That's about as thorough a description of how WatchList works as I'm likely to write up.
The real benefit belongs to those with a sharp eye who are willing to keep at it.
-jp
.
|