|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | track weight table interface | |
| rkskipster 4/28/2008 5:27:23 AM | Is there a writeup on using the track weight table interface? How does it work and what does it do ? rick
| |
| jeff 4/28/2008 12:51:54 PM | Rick, haven't done a formal write up yet but this post will get you started... The Track Weight Table Interface allows the user to store entries in a table named TrackWeight, which exists in the JCapper2.mdb file (found in the C:\JCapper\EXE folder.) The entries actually allow the user to adjust for track weight (or bias) on the fly for daily live play. Here are the basics: Table Name: TrackWeight File Name: c:\JCapper\Exe\JCapper2.mdb Relevant field names and functionality: Active -1 indicates True... which makes the table entry active - meaning that it WILL be used during calculations. 0 indicates False... which makes the table entry inactive - meaning that it will NOT be used during calculations. Track Key in a 3 character track code to indicate a single track. The entry, when active, is only used during calculations when a track match exists between the track code stored in the table and the track code of the current track. Surface Key in a 1 character surface code (D for main dirt course, d for inner dirt course, T for main turf course, t for inner turf course) to indicate surface. The entry, when active, is only used during calculations when a surface match exists between the surface code stored in the table and the surface code of the current race. MinDistance and MaxDistance You can create table entries for individual distances as well as broad ranges of distances. Key in the number of furlongs. For example: if you want to restrict the table entry to 5.5f races then key in 5.5 for MinDistance and 5.5 for MaxDistance. TrackWeight Currently, the TrackWeight field performs no function other than to act as a label to help you categorize different degrees of bias. I have been conceptualizing track weight on a scale of 1-5 where 1 represents a paved highway and 5 represents a sand trap. This past winter I used 1 for the AQU inner and 5 for the poly at TPX. But feel free to use your own scale if you like. CPaceWTAdj The interface works by adjusting factor weight for both CPace and Compoundlate up or down based on your own table entries. When an active entry is found for the current race, the value stored in the CPaceWTAdj field is read. The factor weight for CPace read from the IVTable during UPR and UserFactor calculations is then multiplied by the CPaceWTAdj value read from the TrackWeight Table. For example, let's say for the sake of argument that in your UPR you've assigned a weight of 50 to CPace. But today you notice an expecially strong speed bias. By having an active entry in the TrackWeight Table with a CPaceWTAdj value of 1.3, you actually increase the importance of CPace in your UPR from 50 to 65... meaning that strong CPace horses will score higher in your UPR so long as you keep the TrackWeight Table entry active. CompoundLateWTAdj The interface works by adjusting factor weight for both CPace and Compoundlate up or down based on your own table entries. When an active entry is found for the current race, the value stored in the CompoundLateWTAdj field is read. The factor weight for CompoundLate read from the IVTable during UPR and UserFactor calculations is then multiplied by the CompoundLateWTAdj value read from the TrackWeight Table. For example, let's say for the sake of argument that in your UPR you've assigned a weight of 50 to CompoundLate. But today you notice an expecially strong anti-speed bias. By having an active entry in the TrackWeight Table with a CompoundLateWTAdj value of 1.3, you actually increase the importance of CompoundLate in your UPR from 50 to 65... meaning that strong CompoundLate horses will score higher in your UPR so long as you keep the TrackWeight Table entry active. Summary The TrackWeight Table interface opens up a world of possibilities. Active values stored in this table are used both during Calc Races routines and Build Database routines. If you believe in track weight (or bias) and want to incorporate it into your UPR, then think of the TrackWeight Table as an extension of the GroupName entries already in your IV Table. The advantage of having a separate TrackWeight Table is that you can have entries sitting there that you can activate (or deactivate) on the fly as you encounter different track weight (or bias) conditions during daily live play. -jp . ~Edited by: jeff on: 4/28/2008 at: 12:51:54 PM~
| |
| jeff 4/28/2008 1:07:46 PM | One further note about the TrackWeight Table... the importance of backups. Once you start using this table you'll need to add the following file to the list of files you back up religiously: c:\JCapper\Exe\JCapper2.mdb There are several changes (some VERY nice feature additions) planned for this file over the next few weeks. Currently (and until I get to the point where this part of the program becomes a finished product) the Extractor simply overwrites the existing JCapper2.mdb database file with the latest version of the file every time you get the latest program version... Which means you lose your table entries UNLESS you make a file backup. This is the best (only) way that I can think to publish new content to this file as I work towards the finished product. Otherwise, I end up getting bogged down writing a never ending stream of import routines which pushes back the timeframe for having this part of the program become a finished product from sometime in May 08 to maybe Oct or Sept. So bear with me and bite the bullet and keep backup copies of this file until things are far enough along to where it becomes time to have the Extractor treat this file the same as the original JCapper.mdb database file. -jp .
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |