jeff
1/23/2013
10:37:25 AM | Scratch BOT contains two separate mechanisms for getting scratches:
1. The XML button
2. The Live Tote Links
FYI, I use the XML button exclusively because the XML button allows me to parse the XML directly. The XML is where scratches and changes show up first. The tote links at Brisnet are where they show up later (and sometimes that involves lag time.)
However, both work.
But you need to understand the requirements for each in order to make them work for you.
Info for how to meet those requirements follows below.
Scratch BOT Live Tote Links
If you are talking about clicking the tote links in Scratch BOT and not being able to get scratches for a specific track: Click this link to read about changes Brisnet made to Super Tote and how to use the new Tote Codes Table Mgr so that you can parse it again.
Hint: The first few posts in the above thread contain relevant background info.
Hint: The 7th post down from the top of the thread is where you'll find explicit instructions for using the new Tote Codes Table Mgr.
Scratch BOT XML Button
If you are not getting scratches for a specific track when you click the XML button, the first thing you should suspect is that you don't have a valid table entry for that track.
Below is a cut and paste of an earlier post containing explicit instructions for the required table entries:
Requirements for making the XML button work:
Table Entries
Screenshot #1 - Scratch Bot Track Abbreviations Table Entry - click here -
• The characters "PHA" (without the quotes) entered in the Track Code field are an exact match of the first 3 characters of the file name of the .jcp data file.
Note: If you are using Brisnet files, instead of "PHA" use "PRX" in the Track Code field. Why? Because the first 3 characters of the file name for a .drf or .mcp file for this this track is "PRX" (without the quotes) and you need to create an exact match between the track code field and the first 3 characters of the data file name.
• The characters "PARX RACING" (without the quotes) entered in the Notes field are an exact match of the track_name as shown (highlighted in yellow) in the next screenshot.
Screenshot #2 - Equibase XML from Tues 2/20/2012 -
This screenshot was taken after expanding the XML and clicking to the desired track - in this case Philadelphia Park (or PARX RACING.) Before taking the screenshot I scrolled through the xml so that the part I wanted to emphasize in this post was displayed at the very top of the screenshot - Of course I am talking about the track_name attribute... displayed as the top line and (crudely) highlighted in yellow so as to make it stand out.
• The track_name as listed in the xml is "PARX RACING" (without the quotes.) You need to create an exact match, character for character, between the track name recorded by you in the Notes field of the track abbreviations table (see the first screenshot) and the track_name as listed in the XML.
Sometimes It's All in the Timing
The system was designed so that a track employee would key in the early scratches and changes as soon as they were finalized in the racing office. From there, early scratches and changes for that track would immediately propagate to the xml - where they would (immediately) become available to the outside world... Players, Equibase, ADWs, other tracks, otbs, etc.
Charles Town is a track that embraced the system - and if you are paying attention you can't help but notice that early scratches and changes for CTX are available in the XML a good 5-6 hrs prior to post time for R1 most nights.
PHA, of PRX, or Philly Park or whatever you want to call it is one of the few tracks in North America that (to this day) resists in their adoption of the Exquibase Scratches and Changes system. (NYRA being the only other example I am aware of.)
By way of contrast, scratches and changes for PHA or PRX sometimes don't show up in the xml until 10-15 mtp for R1.
My point being that if you have made the correct table entries (as shown above) and you are still not picking up scratches for a track - chances are it's a timing issue.
Verify by clicking the + button on the interface, scroll through the xml - and visually check to see if scratches for that track are actually in the xml. If no scratches and changes for the track appear in the xml, then yes: It's a timing issue. In that case, try again later in the day.
With that said, you mentioned Magna owned tracks. Three Magna/Stronach tracks running right now that come to mind are GPX, SAX, and GGX.
Screenshots of my own table entries:
GPX:
Gulfstream Park Table Entry
Gulfstream Park track_name in the XML
SAX:
Santa Anita Park
Santa Anita Park track_name in the XML
GGX:
Golden Gate Fields
Golden Gate Fields track_name in the XML
Again, the keys are:
1. First 3 characters of the data file name - persisted in the Track Code and Tote Code Fields.
2. The track_name exactly as it is listed in the Equibase XML persisted in the Notes field.
That's it!
-jp
.
~Edited by: jeff on: 1/23/2013 at: 10:37:25 AM~
|
