|
JCapper Message Board General Discussion
|
| Home |
Register
Log In |
| By | 12-12-2008 Program Update | |
| jeff 12/12/2008 1:55:54 PM | 12-12-2008 Program Update What's Inside JCapper Platinum With today's progam update JCapper 2008 now becomes JCapper Platinum. Basically a name change with lots of new features. CXN Data Window Exports for Riders, Trainers, and Owners. I've expanded the CXN Report Format. It now includes columns showing trend data, recent activity days last start, sprint to route, and route to sprint. When you run an export you are now presented with a calendar control asking you to click/select something called a Trend Baseline Date. If you click the What's This? button you'll be given an explanation. The reports show trend info. Data flowing into the trend columns is based on the number of days back from the Trend Baseline Date you select when you fire up the export. Examples: If you are running a new export on a quarterly playlist file that contains data through 3-31-2008 it's probably best to use a trend baseline date of 4-1-2008 (the day after the playlist file ends.) If your playlist file is complete through yesterday (12-11-2008) it's probably best to use today (12-12-2008) as the Trend Baseline Date - again, the day after the playlist file ends. If you supply a bad trend baseline date the only thing affected will be CXN data flowing to the wrong trend columns. Everything else should work just fine. Make sense? Good. New Data Window Options RUN ALL ACTIVE UDMs You'll find this new option in the UDM drop down. Select it, hit the UDM button, open up a playlist or quick index file, and walk away from your computer. The Data Window will run each active UDM against the selected file, one UDM at a time, compiling results as it goes. When it's finished you'll be presented with results showing the effectiveness (or lack of it) for every active UDM that you have. Depending on the number of active UDMs and the size of the file you select - this operation could take a while. On most machines I can RUN ALL ACTIVE UDMs on a quarterly playlist file in 30-45 minutes... a smaller quick index file in 6-10 minutes. I recommend you try it out on a tiny file first. When you do decide to run this on a yearly playlist file you might want to plan ahead and allow several hours. This might be one of those cases where you start it at night and have it waiting for you when you wake up the next morning. New options in the factors drop down - BY TRACK, BY TRAINER, BY RIDER, BY SIRE, and BY DAM These new options work on the same technology/logic driving the KEY FACTORS REPORT. When any of these options are selected the Data Window performs an export to the SampleSummary table in the JCapper2.mdb file. The export is driven by your Data Window query. When the export/query is complete you are presented with the results from your query broken out by the factor you have selected. Example, to see the performance of your favorite UDM broken out by track, select BY TRACK as your breakout factor and then hit the UDM button and run the UDM against a playlist or quick index file. When the query is finished you'll see how your UDM performed at every track in the file. A word of warning though... When you start running this for sires and dams this operation could take a while. I have over 6000 separate sires in my collective Q1, Q2, and Q3 playlist files. The first time I hit the ALL button and ran a query broken out BY SIRE it took about 2.5 hours to run. Limiting the query parameters cuts down the query time immensely. For example BY SIRE when limited to 3yo in Turf Routes using the same file takes 10-12 minutes. There are far fewer trainers than sires. Queries BY TRAINER take far less time than BY SIRE and BY DAM queries. There are fewer riders than trainers. So they run faster than trainer queries do. If you decide you want a master list of sires for any given year plan on having it take a few hours. Start it and then walk away from your machine. One more thing. Many of you are going to find many instances/categories where the offspring of individual sires and dams are ignored in the betting. For obvious reasons I'm asking the following: Please refrain from public posting of JCapper Data Window results showing current sire or dam data on message boards. If you must post, do it in the private area of this message board. Or post some old sire data on someone else's message board if you're overcome with the need to show off. When you make a discovery - and most of you will - create a UDM for yourself. Then bet it for all it's worth until everyone else figures it out too. The longer you can keep quiet as a mouse the longer your run will be. Bug Fix In previous versions first time starters were being reported correctly as having 0 lifetime starts but with recent activity days last start of 45 days. I've tracked that down and in this program version you should see 999 days for first time starters both on the HTML Report and in your playlist files - after rebuilding them from scratch. Q. Should I rebuild databases from scratch after installing this update? A. Unfortunately yes. The bug fix in this program update addresses recent activity days last start for first time starters. When you use this program update to build as an append older first time starters sitting in a playlist file will show up as having recent activity days last start of 45 days while newly added first time starters will show up as 999 days. That's the only issue/reason to rebuild from scratch that I am aware of. Enjoy. -jp .
| |
| DeanT 12/13/2008 12:56:48 PM | Really amazing stuff dude.
| |
| DeanT 12/13/2008 12:56:48 PM | Really amazing stuff dude.
| |
| mikejlb 12/13/2008 5:57:18 PM | I agree, this upgrade offers so many things to look at that are difficult or expensive for most people. Thanks, Jeff. I started running All Active UDMs on dirt sprints (no poly) from 1/2004 thru 11/2008. The query started at around 8pm last night and it's still cranking away at 3pm the next day. It's running on my wife's computer so it's not a major problem for me ...except her bitching about her computer being tied up again. Women just don't understand how important this stuff is.
| |
| TPW 12/13/2008 9:09:07 PM | Jeff, Thanks for the "By Sire" report, very helpful information. Terry
| |
| Hdcper 12/14/2008 1:27:34 AM | Hey Jeff, Like everyone else said, Great Upgrade! Was wondering if you could add a column or replace a column on the "Run All Active Udms" output. Maybe it is just me, but the Win Impact column currently is all zeros. What I would like to replace it with(or have added) is a column that shows the Dollar gain or loss for the said Udms. ROI is important, but for me I like to keep track of actual gains or losses each month for each udm. Since number of plays varies each month, the ROI can be misleading in evaluating the Udm performance.
| |
| STUBALL 12/14/2008 11:05:12 AM | Hi Jeff Great additions to the program. I have 1 request for the CXN report.. I wonder if you can lock the name column on the left of the screen....when I scroll across I highlite the person I am looking at but sometimes notice something interesting on another line...have to scroll all the way back to find the name.. I hope you understand..I use foxpro and it has a command to lock in the name..very handy. Stuball
| |
| mikejlb 12/14/2008 2:37:04 PM | I'm still running the All UDMs feature on a 2004 thru 2008 DS database and it seems like it's been running too long (12/12 8pm). Is there a limit on file size or maybe multiple years?
| |
| jeff 12/14/2008 7:08:14 PM | None that I'm aware of. I tested it on a yearly database - about 27,800 races with a little over 200,000 starters. Q. What's the file size of your playlist file? -jp .
| |
| mikejlb 12/14/2008 10:28:24 PM | The file size is 1.1 gb. I stopped the query that seemed to stall. I'm doing each year individually and this seems to be a better way to rate the udm's. I'll try a longer All Udms query another time.
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |