JCapper Enhanced Settings Module
Overview
The JCapper Enhanced Settings Module provides a way for the JCapper user to:
The JCapper Enhanced Settings Module is designed to act as an adjunct to the JCapper User System Definitions Screen.
Program Operation
Select a setting option from any of the drop downs and click the Save button. Clicking the Save button causes your settings to be persisted to the UserSysDefs table in the c:\2004\JCapper.mdb file where they can be read (and used) by other JCapper modules.
Important: Making a selection isn’t enough. If you want JCapper to be able to read (and act on) your settings – you have to click the Save button whenever you change the settings.
Settings
HDW Downloaded File Version
Element Type: Simple Drop Down
Purpose: This setting provides a way for the user to select the type of binary race file (File Version) downloaded from the HDW website.
Options:
What are the differences between the two file types?
Version 4.0 files contain more data and provide a more robust data experience to the
JCapper user.
Background:
HDW began offering JCapper data on March 01, 2010. The file format of these
initial files is known as an HDW JCapper version 3.0 file. From the time that
HDW began offering JCapper data files, I have made quite a few requests to
have additional pieces of data inserted into the JCapper file spec.
Rather than risk interruption of your ability to download HDW data, HDW created
a separate new directory on the HDW website where files containing the new
added pieces of information could be maintained. The file format of thse
new data files is known as an HDW JCapper version 4.0 file.
With the release of the 8/2/2010 JCapper Program Upgrade, the File Download
Tool found in JCapper's HDW File Manager now has the ability to download
HDW JCapper version 4.0 files from the HDW website. The file version downloaded
from the HDW website is controlled in Enhanced Settings by the HDW Downloaded
File Version setting.
Note: JCapper Platinum users have the option of which setting to use. JCapper Silver users are limited to using the 1 HDW JCapper V4 File option.
HDW Track Download List
Element Type: Text Box
Purpose: This setting provides a way for the user to
restrict data and results files downloaded from the HDW website to a list of
user defined track codes.
To create a track code list, key in a 3 character track code for each desired track. Separate multiple track codes with a dash or minus character. See the screenshot below.
Note: Whenever the text box for this setting receives focus, it auto-expands giving you room to type in your track list. When the text box loses focus (use the tab key to get out of the text box) it will auto collapse back to its original size and position.
JCP File Build Type
Element Type: Drop Down
Purpose: Controls type of pace figures inserted into .JCP files during file build routine in the HDW File Manager.
Options:
Effect: Option 1 Build as JCP Silver File causes the data to “behave” more like Brisnet data. Option 0 Build as JCP Platinum File causes the data to behave in a more unique way. Numbers and ratings produced with this setting will be seen by fewer pairs of eyes each day. In addition to Late Pace Figures, this setting also impacts JCapper’s HDW PScore algorithm.
Note: JCapper Platinum users have the option of which setting to use. JCapper Silver users are limited to using the 1 Build as JCP Silver File option.
Suggestion: A reasonable R&D project might be to maintain separate databases for a while. Place one set of files built using option 0 Build as JCP Platinum File on one folder - and a second set of files built using the 1 Build as JCP Silver File option on a second folder. Depending on the factor mix used in your modeling and UDM types, it is not unreasonable to expect one JCP File Build Type to outperform the other.
Time Zone Hrs From GMT
Element Type: Drop Down
Purpose: Provides a way for the user to integrate a time zone preference into past performance data reports.
Usage: Select your time zone preference from the drop down and click the Save button. This will cause past performance reports generated by JCapper’s Past Performance Generator as well as HTML and Text Reports generated during Calc Races routines to display post time(s) in the time zone you have selected.
PPS Post Time Display
Element Type: Drop Down
Purpose: Provides a way for the user to customize post time display on past performance data reports.
Options:
Implications and Recommendations:
Use the 0 Military Time option if you are customizing your SQL Mode HTML Report by sorting races on the report by post time. If you are not sorting races on your SQL Mode HTML Report by post time, use whichever setting is most cosmetically appealing to you.
PPs Company Line Display
Element Type: Drop Down
Purpose: Toggles display of Company Line info on or off when past performances are rendered by JCapper's Past Performance Generator.
Options:
Note: Company Line is the term used by Equibase to refer to information about the top three finishers in a given running line.
PPs PaceLine Display
Element Type: Drop Down
Purpose: Provides a way for the user to customize display of past performance data reports. Selections made by the user (after clicking the Save button) will cause JCapper’s Past Performance Generator to display only those running lines that match the user selection.
Usage: Select an Option, click the Save Button, and use the Past Performance Generator to render past performances for a race.
Notes:
In future versions of JCapper, a checkbox will be added to the interface, enabling the PPs PaceLine Display setting to be combined with the user’s PaceLine Selection Rules persisted on the User System Definitions Screen – enabling more exacting control of paceline selection rules during Calc Races and Build Database routines.
The E or EP Lines and P or S Lines options use HDW-JCapper numeric values for Run Style and are only available when HDW data is used.
Zoom Level
Element Type: Drop Down
Purpose: To enable JCapper Modules to auto-size themselves upon startup based on user preferences.
Note: This feature is not active yet.
Scratch BOT
Element Type: Drop Down
Purpose: Controls the type of parse routine used by Scratch BOT when the XML Button is clicked.
Options:
Note: Be aware that no matter what option is persisted above, you will need to create a valid entry
in the TrackAbbreviations Table for each track that you want Scratch BOT to parse from the XML.
A valid Scratch BOT TrackAbbreviations Table entry is defined as:
STAT ROI Display Type
Element Type: Drop Down
Purpose: Provides a way for the user to control the display type for roi numbers inserted into .JCP files during file build routines performed by JCapper’s HDW File Manager.
Usage: Select the desired display type for roi and click the Save button.
CXN Names Formatting
Element Type: Drop Down
Purpose: Provides a way for users to control formatting of rider, trainer, and owner names inserted into .JCP files during file build routines performed by JCapper’s HDW File Manager.
Options:
Implications and Recommendations:
I recommend using the 0 Remove Punctuation Characters option. Doing so facilitates using the UDM Wizard’s Name Selection Tool as it finds CXN name matches in the database. To have CXN Names inserted into your back .JCP data files, select the 0 Remove Punctuation Characters option and click the Save button. Then go back and use the HDW File Manager to rebuild all previous folders where you have them stored. Follow that up by using the Database Builder to Rebuild databases for those folders from scratch. Follow this up by using the UDM Wizard’s Name Selection Tool to re-work the CXN Names in any of your CXN Name based UDMs.
This will accomplish three things:
1. Your back .JCP Files as well as .JCP files going forward will contain CXN Names that have been stripped of punctuation characters.
2. Your pl_profile.txt files and StarterHistory Table will contain CXN Names that have been stripped of punctuation characters – making them compatible with the name matching algorithm found in the UDM Wizard’s Name Selection Tool.
3. You will gain the ability to work faster when doing R&D involving CXN Names.
Internal Fractions and Time
Element Type: Drop Down
Purpose: Provides a way for the user to control internal fractions and time inserted into .JCP files during file build routines performed by JCapper’s HDW File Manager.
Options:
Implications and Recommendations:
Unless you plan on making your own set of speed and pace figures, use the 0 Fields #876-1045 use raw RACE Time option. This will cause JCapper’s HDW File Manager to insert raw race fractional times into your .JCP files – which are displayed in turn on past performance reports created by JCapper’s Past Performance Generator.
CXN Tnr STATS 1147-1151
Element Type: Drop Down
Purpose: Provides a way for the user to control Trainer STAT Category inserted into data fields 1147-1151 for .JCP files created during file build routines performed by JCapper’s HDW File Manager. This in turn controls STAT Categories displayed on past performance reports rendered by JCapper’s Past Performance Generator.
Options:
Recommendations: Use either the 0 Last 365 Days or 1 Current Year option for this selection.
CXN Jky STATS 1157-1161
Element Type: Drop Down
Purpose: Provides a way for the user to control Rider STAT Category inserted into data fields 1157-1161 for .JCP files created during file build routines performed by JCapper’s HDW File Manager. This in turn controls STAT Categories displayed on past performance reports rendered by JCapper’s Past Performance Generator.
Options:
Recommendations: Use either the 0 Last 365 Days or 1 Current Year option for this selection.
CXN Tnr STATS 1152-1156
Element Type: Drop Down
Purpose: Provides a way for the user to control Trainer STAT Category inserted into data fields 1152-1156 for .JCP files created during file build routines performed by JCapper’s HDW File Manager. This in turn controls STAT Categories displayed on past performance reports rendered by JCapper’s Past Performance Generator.
Options:
Recommendations: Use either the 0 Previous Year or 3 Last 90 Days option for this selection.
CXN Jky STATS 1162-1166
Element Type: Drop Down
Purpose: Provides a way for the user to control Rider STAT Category inserted into data fields 1162-1156 for .JCP files created during file build routines performed by JCapper’s HDW File Manager. This in turn controls STAT Categories displayed on past performance reports rendered by JCapper’s Past Performance Generator.
Options:
Recommendations: Use either the 0 Previous Year or 3 Last 90 Days option for this selection.
PPs Variable Trainer Stat Display
Element Type: Drop Down
Purpose: Provides a way for the user to control display of variable trainer stats beneath each horse’s running lines on past performance reports rendered by JCapper’s Past Performance Generator.
Options:
Notes: Equibase includes dozens of trainer stat categories in the data transmitted to third party data vendors such as DRF, HDW, Brisnet, and Trackmaster. I spent some R&D time looking at performance of these various trainer stats categories. Much of the time this type of data is meaningless. At other (rare) times it can be spot on. During my R&D I developed a hierarchy whereby I ranked the various stat categories in terms of relevance exhibited during my R&D. From that I wrote an algorithm into JCapper’s HDW File Manager so that the most relevant stat categories for each horse on the trainer stat category row are inserted into the data file in order of their relevance. The more relevant (powerful) the stat category, the earlier in the data file it will appear.
This enables JCapper’s Past Performance Generator to display data in the trainer stat category row from left to right using this same hierarchy. The more relevant (powerful) the stat category, the more to the left the individual stat category will appear in the trainer stat row. The weaker the stat category, the more to the right it will appear on the trainer stat category row.
Important: This algorithm only applies when HDW data is used. When Brisnet files are used, trainer stat categories are displayed on past performance reports in whatever order they happen to be appear in Brisnet’s data files.
Screenshot