|
JCapper Message Board General Discussion
|
| Home |
Register
Log In |
| By | AQU vs. BAQ | |
| jeff 9/17/2022 9:07:17 PM | This was posted in the private section of the board. Wanted to post this out in the open where everyone can see it. "Q. Is HDW doing anything for data users to deal with this BAQ track code - still coming through as AQU? Will we ever see BAQ?" • HDW Data: Ron Tiller at HDW gave me the choice of which track code AQU or BAQ to insert in JCapper data. I told him to use AQU because: AQU is where the races are being run. 1. For HDW data AQU is the track code being used for running lines, workouts, data file names, and result file names. 2. Stats for rider-trainer-post position-sire, damssire, etc. are handled in the same manner as all past AQU meets. (Everything 'flows' under track code AQU with no special handling required.) 3. Prob Expressions using "AND TRACK = {TRACK}" (without the quotes) will continue to work just fine because the track code remains the same. • Brisnet data: Brisnet decided to use track code BAQ. BAQ is the track code being used for running lines, workouts, data file names, and result file names. 2. I have no idea how this might impact their speed and pace figs, pedigree ratings, and stats for rider-trainer, etc. 3. Prob Expressions using "AND TRACK = {TRACK}" (without the quotes) might need a few weeks to reach a point where there is enough BAQ data in your StarterHistory table for the Prob Expression to become reliable. Imo, this really depends on the Prob Expression and the half life if you are using time decay. If you are using a short half life (7 or 8 days) it's probably ok to start relying on the Prob Expression a few days in. If you are using a longer half life (120 days or so) it's probably better to wait until you have at least a few weeks of data before relying on the Prob Expression. • Scratch BOT: Equibase is inserting track_name "BELMONT AT THE BIG A" (without the quotes) in the scratches and changes xml. If you are using HDW Data the entry in your TrackAbbreviations Table should look like this:  If you are using Brisnet Data the entry in your TrackAbbreviations Table should look like this:  Note that in both cases the track code matches the first 3 characters of the data file name (either AQU or BAQ depending) and the notes field entry matches the track_code Equibase is inserting in the xml: "BELMONT AT THE BIG A" (without the quotes.) -jp . ~Edited by: jeff on: 9/17/2022 at: 9:07:17 PM~
| |
| jeff 12/29/2022 6:12:31 PM | Screenshot showing the TrackAbbreviations Table Interface with the correct settings persisted for the current AQU meet that began on or about Nov 1, 2022: Track Code: AQU Tote Code: AQU Notes Field: AQUEDUCT The screenshot also shows Scratch BOT with today's XML for AQU race 1 in the background. You can clearly see Equibase is now using AQUEDUCT as the track_name. Important: The keys, to making it work no matter what the meet are: 1. The Track Code entry in the TrackAbbreviations Table Interface must match the first 3 characters of your Data File Name (in this case AQU.) 2. The Notes Field entry in the in the TrackAbbreviations Table Interface must match the track_name Equibase is using in the XML (in this case AQUEDUCT.) If Equibase changes the track_name in the xml for any reason you need to change the Notes field entry in the TrackAbbreviations Table Interface. That's It! -jp .
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |