Quote:
Originally Posted by chrisl
Automatic scratches! you have got to be kidding. Thank goodness I was sitting down when I read your post.
|
Quote:
Originally Posted by mikesal57
I'm sorry crest...but I have to agree with chris.....
to pay that much money and praise the "scratch" part of the program is ridiculous..
|
I recently added several new features to JCapper Scratch BOT.
In chronological order from newest to oldest:
1. Created a new screen called the
Manual Race Override Tool.
This is a UI that enables the user to manually override bad race info in the xml: surface-distance-track condition... (07-15-2020.)
In
another thread, I mentioned that track condition for off turf races has become an area that requires special handling. Fyi, a rash of recent bad track condition in the xml is what caused me to create to create this new screen.
The new UI basically gives the user the ability to quickly bring up racea and do a manual edit for surface-distance-track condition - and from there 'lock' the current race by hitting a Save button.
From there, races that have been 'locked' are no longer overwritten with bad info from the xml during subsequent parse routines.
The new UI also enables the user to unlock races should Equibase or the track correct the bad race info in the xml (surface-distance-track condition) at some point later in the raceday.
2. Updated the parse routine to handle new ways surface changes keep showing up in the xml... (06-24-2020.)
3. Added an audible alarm that tells the user "
Hey you've got new scratches and changes" in a computer generated voice when new changes are present as a result of the most recent xml parse routine. (06-24-2020.)
In the past you had to be looking at the
Changes Report generated after each parse routine if you wanted to be alerted when new changes are present.
Now, as long as you're within earshot, you'll know when new changes are present.
I also added a setting so the user can turn this feature ON or OFF.
4. Added a button that when clicked runs Scratch BOT in Bot Mode.
Basically, Scratch BOT is put on a timer - and parses the xml once every 90 seconds or so.
Added a Pause button and a Resume button to the UI.
Also created a companion setting so the user can turn this feature ON or OFF.
5. Created a new screen that enables the user to key manual rider changes (when rider changes are missing from the xml.)
6. Redid the changes report. Link to an example report from earlier today:
http://www.jcapper.com/messageboard/...20-1139am.html
My objective with Scratch BOT is:
To enable the customer to parse and process scratches, rider changes, surface changes, distance changes, and track condition changes as seamlessly as possible.
Imo, if you are playing one or two tracks at a time:
Keying scratches and changes manually makes perfect sense.
However, if you are scanning (say) 12 plus tracks daily for playable races:
Imo, the more workload you can automate the better.
-jp
.
