|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | UDMs using espraceshape | |
| bettheoverlay 10/8/2009 10:43:26 PM | After running some DAT files in SQL for Woodbine I noticed a discrepancy between the listed plays in the data window and the DAT HTML report. The HTML report was not showing the UDM plays for all of my Woodbine specific UDMs except for the 6F one. I have a bunch, one for each distance and surface. I downloaded Fridays Woodbine card and only the 6f UDM showed any plays. After much testing on the 7F UDM, I found tha culprit was ESPraceshape. When I eliminated the factor the 7f plays appeared on the HTML report and matched the data window. I eliminated the factor from the other WOX UDMs and they all appeared on the DAT file and on Friday's HTML report. I'm rechecking my other SQL UDMs to make sure all the plays from the data window queries are making it to the HTML report.
| |
| jeff 10/9/2009 2:21:29 AM | Edit 10-09-2009 11:00 pm Pacific: No way to hide it. It was a bug. Feel like such an ass for assuming it had to be odds based factors. What can I say? I owe you an apology. Thanks for paying attention and reporting it. Going to leave up what I posted earlier about odds based factors in a UDM Definition... even though it was not the case here - using them in a UDM Def could also cause what you described... -- end edit -- Odds based factors would be my first best guess... And even if what I'm about to post isn't the cause of what you're experiencing... I'm going to post a full explanation of what that means anyway... Because I'm 100% sure that it will help somebody understand exactly how SQL UDMs work in the Profile Marker... When we (meaning all of us) create SQL Expressions and run them through the Data Window, they execute against the StarterHistory Table - which has data fields in it for odds based factors such as: Odds, RankOdds, BettorsToteProb, E~BettorsToteProb, E~UPRZScpreProb, etc. It's very easy to add something like the following to a SQL Expression and store it as part of a UDM Definition: AND EBETTORSTOTEPROB >= 1.05 Now that works great in the Data Window because the StarterHistory Table contains a past history that includes the odds and all odds based factors. However, on race day - the results are not yet known - and at the time that the Calc Races button is clicked the Profile Marker has no way of knowing what the odds - or odds based factors are. For that reason, the odds and all odds based factors are treated as if they have values equal to zero. So something like AND EBETTORSTOTEPROB >= 1.05 stored as part of a UDMN Def will cause the UDM to not flag any horses. If your SQL UDMs have odds based factor constraints in them - my suggestion would be to set them equal to zero. Example - Change this: AND EBETTORSTOTEPROB >= 1.05 To this: AND EBETTORSTOTEPROB >= 0 And leave it as part of the UDM Defintion. Then add something like this: EB 1.05 to the BettingInstructions field so that you see it on your race day reports. Doing this will enable a SQL UDM to "fire" on race day. Now - if none of the UDMs you are posting about have odds based factor constraints - it's most likely related to your F-Factor setup... In that case shoot me an email or call and I'll help you figure out what's going on. -jp . ~Edited by: jeff on: 10/9/2009 at: 2:21:29 AM~
| |
| Charlie James 10/9/2009 11:31:24 AM | Don't be too hard on yourself Jeff. Been with you for about 5 yrs now. One of the first things that made me sit up and take notice is that you don't hide things. Bug gets reported - you fix it - tell us about it - and move on. I've seen other software vendors "airbrush" bug reports completely off their message boards. In 5 yrs never once seen that happen here. Just so you know I think that speaks volumes about you - as do the new features you keep introducing. A little tuneage to start your day: http://www.youtube.com/watch?v=FBnSWJHawQQ Chuck
| |
| bettheoverlay 10/9/2009 1:05:43 PM | Yea, I've had JCapper a few years now myself and have found Jeff's response time almost immediate to any problem I've had. No need for apologies as far as I'm concerned. Jeff fixed the bug, and the updated download allows UDMs using espraceshape to print on the HTML report. Thanks Jeff.
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |