|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Card Loader Conflict | |
| Jens 4/15/2008 6:10:12 PM | This won't affect those of you that don't play these tracks but when using tsn files and loading RDX and WRD the card loader is adding the WRD horses and changing the distance to the RDX card (on one occasion it also added the RDX horses to the WRD card). The only way I could get around this was to do them seperately; load RDX, get scratches, calculate races, and then clear the card and load WRD etc. I'm guessing it must have something to do with the common RD in the file name?
| |
| jeff 4/15/2008 6:55:55 PM | Jens - Thanks for pointing this out. I'll have a look at it. -jp .
| |
| dvlander 4/16/2008 10:20:21 AM | Jeff, I also pulled a text report that other day that had a likely conflict. I had a UDM that is limited to 7-8 tracks including LAD. It listed some LAX plays on the report.
| |
| ryesteve 4/17/2008 9:04:55 AM | Does this affect db builds, or just what goes on in the card loader?
| |
| jeff 4/17/2008 11:09:03 AM | Steve, GOOD QUESTION!! At this point in time I don't know the answer - although I DO plan on trying to get it handled TODAY. -jp .
| |
| jeff 4/17/2008 12:05:33 PM | The conflict is limited in scope to the Card Loader and Screen 2 of the File Downloader. The DB Builder is unaffected. -jp .
| |
| jeff 4/18/2008 8:04:09 PM | Just wanted to give you guys a heads up... Getting this fixed is taking me a lot longer than I thought it would at first. I'm having to find every instance in all of the modules (Card Loader, File Downloader, Scratch Bot, Scratches Parser, Manual Changes, Profile Marker, HTML Report Builder, Data Window, and Main Module) where track codes are evaluated. Every line of code in JCapper that deals with Bris/TSN track codes needs to be addressed so that a 3 character code is coerced ("RDX" or "LAX") from the 2 character track codes ("RD " or "LA ") as they exist in field #1 of the Bris/TSN data files. It's not rocket science but there are thousands of lines in JCapper where track codes are evaluated and handled. I can't publish anything else until this is taken care of and thoroughly tested. I might need another day or two. -jp .
| |
| Jens 4/18/2008 10:40:30 PM | Jeff, I hope you don't hate me for bringing up the card loader problem. Even worse, now I'm having a new issue with the manual changes. Tonight at Fairmont Park (FPK)there were no early scratches. When I ran the numbers I had a play on the 9 in the third race. A minute or so before the race started the 7 was scratched. When I tried to scratch the horse the manual changes wouldn't allow me to open the card. Lucky for me the J1 horse #8 was a real close UPR2 so I decided to put a saver on him. Paid $49.80, just wish I would have boxed the 8,9 as the 9 ran second. Anyhow (enough red boarding), I re-downloaded the file and tried again- same problem. I then downloaded tomorrows card- same problem. I can load the cards and calculate races, I just can't manually scratch anything. Don't hate me. Jens
| |
| jeff 4/18/2008 11:27:29 PM | Jens, have you tried simply clearing scratches? If that doesn't do the trick could you email a copy of one of your FPK cards to me? -jp .
| |
| Jens 4/19/2008 12:38:04 AM | Jeff, Tried clear scratches, refresh, clear cards etc. a number of times. Only have the problem with FPK. I emailed you todays file for that track.
| |
| jeff 4/20/2008 12:50:24 AM | Just an update... Re: Fairmont Park. Fairmont Park has a readily identifiable 3 character track code from its file name: FPK. Jens, the reason why the Manual Changes Module won't let you open up those FPK races is because the 3 character track code from the file name doesn't match the characters that TSN has in Field #1 of the data file. Inside the file, TSN file uses "FP " (with a blank space after FP) as the track code. How best to handle this? Initially my solution was to take any two character track code, trim out the blank space when there is one - and add an "X" character... For example BM becomes BMX... GP becomes GPX... OP becomes OPX, etc. This model actually works very well for every track - except for Fairmont Park. Why? Because track code FPX already belongs to Fairplex, that county fair meet run every Sept in Pomona CA. I'm going to try trapping for "FPK" being present in the file name along with "FP " being present in field #1 of the data file. When those two conditions exist I think simply coercing the track code to "FPK" in both the data and results file will do the trick. I've made a significant number of changes within JCapper to get this issue handled. Like I mentioned before it's not rocket science. But there are thousands of lines of code that had to be gone through. Almost every module handles track codes in some way. I plan to spend most of tomorrow unit testing these new changes - and realistically forsee updating the 08 download package sometime Monday afternoon. -jp . ~Edited by: jeff on: 4/20/2008 at: 12:50:24 AM~
| |
| Jens 4/19/2008 11:41:45 PM | Jeff, Just want to say thank you for all the time and effort you put in, not only by making awesome improvements to JCapper, but also by ironing out those seemingly inconsequential little problems that crop up from time to time. If only the pinheads in charge of this great sport would get a clue and put out just one percent of the intelligence and effort you do regarding customer service, etc., horse racing and track handle would be booming. Thank you. Jens
| |
| jeff 4/22/2008 3:23:04 PM | See my post under JCapper2008 Tech Support in the Downloads Forum. I believe the issue has now been handled. -jp .
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |