By |
Tracking results of layered UDM's |
PT 5/29/2009 2:19:41 PM | Is there any way to test performance when multiple UDM's apply to either a horse, or a race?
By horse, take Jeff's examples of using layered UDM's-when both select the same horse, find the ROI when that occurs.
By race, let's say I have a positive UDM for higher priced runners that I use in combination with a negative UDM on ML favs. I only want to play when both UDMs hit the same race, and be able to test when that situation comes up.
-Paul
|
jeff 5/29/2009 3:25:26 PM | Use the Data Window's Export - Create New Quick Index File function:
1. Create two or more UDMs where you'd like to test convergence (what happens when multiple UDMs converge on the same horse.)
2. Point the Data Window at a target folder, then click Exports and select Quick Index File Create New. Using the dialog box that pops up at this point key in a file name for your new file and click Open. Hint: Make sure that the first three characters of the new file name are "pl_" without the quotes. This will cause the next Data Window query that you run to create a new quick index file having the file name that you specified - where the only horses in that file are those returned by the next Data Window query that you run. You'll see text describing that creation of a new quick index file has now been toggled "on" with the text running across the title bar at the very top of the Data Window.
3. Select your first UDM from the UDM drop down and run it through the Data Window against a playlist file using the UDM button. As the Data Window tabulates results for your UDM based query it will also write each starter from the larger playlist file that matches the UDM definition of the UDM currently being run through the Data Window to the new quick index file specified in step 2 above. When the query is finished running you will see your query results - BUT you now have a new quick index file that you can use in the next step.
4. Pick a second/different UDM from the drop down and run it through the Data Window against your new quick index file. The results returned in this step will answer the question you are after: What happens when two or more UDMs converge on the same horse?
That's it!
-jp
.
|
PT 5/29/2009 5:22:17 PM | And I thought the answer was going to be no...this opens up even more possibilities, and will cost me even more sleep!
Thanks! -Paul
Edit: As I read through that, that will work when the UDM converges on the same *horse*. What about when I have two UDM's that find different horses in the same race, as in my example above? I'd only want to play the positive UDM when the negative UDM flags a bad favorite.
~Edited by: PT on: 5/29/2009 at: 5:22:17 PM~
|
JustRalph 5/29/2009 8:46:07 PM | Jeff
correct me if I am wrong.......here
You can create this new index file based on any UDM .........then run a key factors report against it also?
right?
|
Hdcper 5/29/2009 11:00:36 PM | You could also run it against all active udms, to see how it effects each of your udms.
|
jeff 5/30/2009 1:42:54 AM | What about when I have two UDM's that find different horses in the same race, as in my example above? I'd only want to play the positive UDM when the negative UDM flags a bad favorite.
You'll likely have to track something like that in an app outside of JCapper... Excel, Access, etc.
I said "likely" because there ARE race level attributes built into JCapper that you CAN track completely from inside of JCapper.
For example, take JCapper's Vulnerable Favorite indicator. You can run any UDM through the Data Window broken out by Vulnerable Favorite and see the effect that both vulnerable and legit favorites have on the profitability of your UDM selections. You can also break the data out by other race level attributes such as Field Size, Race Volatility, Pace Index, etc.
If you create your own definitions for race level attributes, those are best tracked outside of JCapper. For that you could run a Cross Platform Text File Spot Play Data Window Export... which exports Track, Date, Race Number, Name of Horse to a comma delimited text file... which you could import into Excel... where you could add your own race level factors/indicators. That's one way. There are certainly others.
-jp
.
|
jeff 5/30/2009 1:43:32 AM | Ralph,
No correction needed. You have it right.
-jp
.
|
PT 6/12/2009 10:53:30 PM | --quote:"If you create your own definitions for race level attributes, those are best tracked outside of JCapper. For that you could run a Cross Platform Text File Spot Play Data Window Export... which exports Track, Date, Race Number, Name of Horse to a comma delimited text file... which you could import into Excel... where you could add your own race level factors/indicators. That's one way. There are certainly others. " --end quote
After getting off on another tangent, I gave this a try. Looks like that would work with some Excel tinkering, but that file isn't comma delimited.
code: | 09-03-2007LAD4SLEETWORTH 09-06-2007LAD10ANTE UP JESY 09-07-2007LAD2SWINGING STAR 09-12-2007LAD10LEEDY JONZ 09-15-2007LAD5LOBO TANGO
|
I started to use some of the text grabbing functions in Excel, but it gets messy (for me anyway) with Track+Race# being either 4 or 5 characters.
-Paul
|