By |
Results File - CBY Sat July 19 2014 - R7 |
jeff 7/20/2014 1:35:48 PM | Email received a few minutes ago from Ron Tiller at HDW:
--quote:"I posted CBY results files for July 19th. Because of race 7, which was a 8 horse dirt field racing simultaneously against a 12 horse turf field, the results are problematic and will potentially cause problems for some programs.
In the racefile, race 7 had all 20 horses running in a turf race. Concurrently, race 11 was the turf part of the race and race 12 was the dirt part of the race. Race 7 is now listed as cancelled but all the payouts are in race 7 as that is the only race that has all 20 runners loaded into it. As the first 4 finishers were dirt runners, there is no WPS or exotics payouts, even though there is a 1st, 2nd and 3rd place finisher in the turf part of the race.
In short, it may be best to just eliminate this race card from your program. There is just no good way to finesse the data.
Ron" --end quote
Right now I'm involved in live play - which takes precedence.
As soon as a free time window presents itself this afternoon - I will take a look at the CBY text chart results file from yesterday Sat July 19, 2014 and determine what impact - if any - the results formatting has on a JCapper build database routine.
FYI, I've downloaded the CBY results file from the HDW site so that I can look at it - but have asked Ron Tiller to remove it from the HDW site - at least for the time being. (Don't know if he will do that or not but I did ask.)
In the meantime, I strongly recommend the following:
DO NOT DOWNLOAD the results file for CBY 07-19-2014
DO NOT try to create an .xrd file for CBY 07-19-2014 by running a file build routine involving results for CBY 07-19-2014.
DO NOT run a build database routine on any folder where a results file for CBY 07-19-2014 is present. (This applies to both HDW and Brisnet customers.)
At least not until after you see me come back in this thread and make a follow up post.
-jp
.
| jeff 7/20/2014 10:09:59 PM | Following up on the results File for CBY Sat July 19, 2014 - Races 7, 11, and 12...
Based on the way Equibase distributed entries/pps data, the .JCP File is impacted in the following manner:
R7 - All 20 runners are listed as entries in this race and the surface listed as Turf.
R11 - Contains entries for the 12 turf runners only with the surface listed as Turf.
R12 - Contains entries for the 8 dirt runners only with the surface listed as Dirt.
Based on the way Equibase distributed results data, the HDW Text Chart Results File and resulting JCapper .XRD File are impacted in the following manner:
R7 - Odds are missing for all horses in this race. Because of this the .XRD File Build Routine skips this race when building an .XRD file.
R11 - Odds are included for all horses in this race.
However, only the turf runners are listed in this race.
You should be aware that none of the runners in this race hit the board. That said, during an .XRD File Build Routine this race does get added to the .XRD file and, despite none of the horses in this "race" hitting the board, all of the info in this race appears to be correct.
R12 - Odds are missing for all horses in this race.
Because of this the .XRD File Build Routine skips this race when building an .XRD file.
You should be aware that the top three finishers in this unique event came from this race and that odds and payoffs for them will not make it into your databases.
Bottom line:
1. You can download the CBY0719F.zip file from the HDW site.
2. You can run an XRD File Build Routine that includes the CBY 07-19-2014 race card to create a CBY0719.xrd file.
3. If you run a Build Database Routine on the folder where that CBY0719.xrd file is stored you will (technically) not break anything.
4. You will get a CBY0719.DAT file that contains data for races 3, 4, 5, 6, 8, 9, 10, and 11 (the thoroughbred races on the card.)
5. You will get a pl_profile.txt file that contains data for races 3, 4, 5, 6, 8, 9, 10, and 11 (the thoroughbred races on the card.)
6. Your StarterHistory table (provided your build mode is 3, 4, or 5) will contain data for races 3, 4, 5, 6, 8, 9, 10, and 11 (the thoroughbred races on the card.)
7. Your CBY0719.DAT file will not contain data for races 7 and 12 (because the odds and possibly other data fields are missing.)
8. Your pl_profile.txt file will not contain data for races 7 and 12 (because the odds and possibly other data fields are missing.)
9. Your StarterHistory table (provided your build mode is 3, 4, or 5) will NOT contain data for races 7 and 12 (because the odds and possibly other data fields are missing.)
I am going to ask Equibase to cut a revised Chart that includes odds and any other missing results data for R12. That would fix the problem - at least from a JCapper perspective.
That said, I'm not sure how high a priority this one race might be for them.
Now you know what I know.
-jp
.
~Edited by: jeff on: 7/20/2014 at: 10:09:59 PM~
| Caveat 7/21/2014 9:14:09 AM | Thanks for the info...
I will by-pass downloading the file till you say its OK
Mike
| Caveat 9/19/2014 9:03:11 AM | Jeff..
Its 2 months after this happened...
I didnt do anything with result file or build...
What do you suggest?
If you say its Ok to build database , I need xrd file.
Thxs Mike
| jeff 9/19/2014 11:04:55 PM | EDIT - Not made clear in my above post:
On Sat July 19, 2014 Canterbury ran a 'gimmick' race: http://www.racingpost.com/news/horse-racing/usa-battle-of-the-surfaces-pits-dirt-against-turf/1692831/#newsArchiveTabs=last7DaysNews
Somehow - I'm thinking because of the unique nature of this "race" Equibase disseminated the chart data in a way I have never seen before. (Certainly not in a way I have ever programmed JCapper to expect.)
Equibase basically took a field of 20 betting interests and broke them out into 3 "races."
From my above post:
--quote:"Based on the way Equibase distributed results data, the HDW Text Chart Results File and resulting JCapper .XRD File are impacted in the following manner:
• R7 - Odds are missing for all horses in this race. Because of this the .XRD File Build Routine skips this race when building an .XRD file.
• R11 - Odds are included for all horses in this race.
However, only the turf runners are listed in this race.
You should be aware that none of the runners in this race hit the board. That said, during an .XRD File Build Routine this race does get added to the .XRD file and, despite none of the horses in this "race" hitting the board, all of the info in this race appears to be correct.
• R12 - Odds are missing for all horses in this race.
Because of this the .XRD File Build Routine skips this race when building an .XRD file. " --end quote
My notes show that Equibase (apparently) didn't see this as a high priority item because they never did publish revised chart data that included odds for the horses in R12 (the "race" where all the horses that hit the board in this event were listed.)
I do have the zip file that contains the 07-19-2014 chart from HDW - as originally published - and will be more than happy to send it to anyone who shoots me an email asking for it.
That said, I would urge you to think twice before asking for the file and before including that chart in a build database routine.
The way Equibase compiled the chart data, they left R12 for that race card incomplete:
The odds for all of the horses in R12 are blank!
As relates to my own database:
I made a decision to NOT process the CBY0719F.zip file.
I did not want my database to include a race where half the field has odds (horses from R11) and therefore get recorded in the database - and the other half gets excluded from the database because none of those horses have odds (the horses from R12.)
-jp
.
~Edited by: jeff on: 9/19/2014 at: 2:16:05 PM~
~Edited by: jeff on: 9/19/2014 at: 11:04:55 PM~
| Caveat 9/21/2014 6:46:27 AM | Thx Jeff...away it goes....
finally off my list :)
~Edited by: Caveat on: 9/21/2014 at: 6:46:27 AM~
|
|