|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Track Condition | |
| jeff 3/21/2013 1:44:57 PM | Searching through the help docs and previous posts made on this message board, as well as the old JCapper message board, I don't see a comprehensive write up for track condition. I recall doing one at some point... but I sure haven't been able to find it. (Probably sent it off as a private email to someone.) I've started writing one - and will post it here in this thread. My objective in doing this is to enable players looking for info about how to add track condition as a factor constraint to UDM Definitions so that horses can be flagged on race day - and how to run UDMs through the Data Window and break the data out by track condition - and how to restrict Data Window queries to specific track conditions (and maybe a related tangent or two) can be found going forward. -jp .
| |
| jeff 3/21/2013 1:45:46 PM | Track Condition - SQL Mode • Track Condition in the Manual Changes Module -On race day, track condition is not "known" by the software. The mechanism in JCapper for persisting a change in track condition - so that it can be "known" (and from there "handled" by the software) is to bring up individual races in The Manual Changes Module, select the new track condition in the Surface Drop Down, and persist the change by clicking the Save button... and from there, repeat as needed for other races on the same card. After persisting all changes, you'll need to run a Calc Races for that card - followed by refreshing all html reports. With all of the required tasks performed... all of the (refreshed) html reports should now display any horses flagged by active UDMs having a factor constraint for track condition as part of the UDM definition. • Track Condition in Calc Races routines - When a Calc Races routine is run (This is true for both SQL Mode and Playlistfile Mode) the JCapper Main Module parses the RaceHeaders.txt file on the folder where the Calc Races routine is being run - and gets info for user persisted changes to track condition (provided there are any.) The JCapper Main Module then writes the revised track condition to the TKCOND field in the StartersToday table - which in turn enables UDMs that have a factor constraint for track condition to "fire." • Track Condition in SQL UDMs - The data field named TKCOND, as documented in the Table Schema can be used to add track condition to a SQL UDM definition. For example, adding the following two lines to a SQL UDM definition causes the UDM to flag horses at AQU - but only when track condition is SY: AND TRACK = 'AQU' AND TKCOND = 'SY' • Track Condition in the Data Window - When you run a build database routine (Modes 3, 4, and 5) the Database Builder reads track condition from the results file and writes it to the TKCOND field in the StarterHistory table. This enables sql expressions executed in the Data Window to be: 1. Broken out by track condition. Hint: select "Track Condition" from the factors drop down before executing your query. 2. Restricted to specific track conditions. Example: AND TRACK = 'AQU' AND TKCOND = 'SY' More to come... -jp .
| |
| jeff 3/22/2013 9:00:19 AM | Track Condition - Playlist File Mode • Track Condition in the Manual Changes Module -On race day, track condition is not "known" by the software. The mechanism in JCapper for persisting a change in track condition - so that it can be "known" (and from there "handled" by the software) is to bring up individual races in The Manual Changes Module, select the new track condition in the Surface Drop Down, and persist the change by clicking the Save button... and from there, repeat as needed for other races on the same card. After persisting all changes, you'll need to run a Calc Races for that card - followed by refreshing all html reports. With all of the required tasks performed... all of the (refreshed) html reports should now display any horses flagged by active UDMs having a factor constraint for track condition as part of the UDM definition. • Track Condition in Calc Races routines - When a Calc Races routine is run (This is true for both SQL Mode and Playlistfile Mode) the JCapper Main Module parses the RaceHeaders.txt file on the folder where the Calc Races routine is being run - and gets info for user persisted changes to track condition (provided there are any.) The JCapper Main Module then writes the revised track condition to the ForBill.txt and ForJeff.txt files - which in turn enables UDMs that have a factor constraint for track condition to "fire." • Track Condition in Playlist File UDMs - Preset Filters are the mechanism that JCapper uses in Playlist File Mode to create factor handles for track condition. All of the filter codes that enable you to "grab" track condition begin with the characters "TK" (without the quotes.) Example: TK4IN Adding the above filter code to a playlist file UDM causes the UDM to flag horses only when the track condition is SY. • Track Condition in the Data Window - When you run a build database routine (ALL Modes 1, 2, 3, 4, and 5) the Database Builder reads track condition from the results file and writes it the designated field in the pl_profile.txt file. This enables playlist file queries run through the Data Window to be: 1. Broken out by track condition. Hint: select "Track Condition" from the factors drop down before executing your query. 2. Restricted to specific track conditions. Example: TK5OUT Keying the above filter code into the Filter Codes drop down in conjunction with setting the Data Window to "+ Apply Special Filters" causes the Data Window to AVOID starters racing on a surface where the listed track condition was MY. -jp . ~Edited by: jeff on: 3/22/2013 at: 9:00:19 AM~
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |