|
JCapper Message Board JCapper 101
|
| Home |
Register
Log In |
| By | Using the Profile Table Interface | |||
| jeff 11/19/2008 4:14:53 PM | There used to be a thread on the old JCapper msg board about using the Profile Table Interface. Other commitments have (so far) taken precedence (and deservedly so) over resurrecting the old message board. I received the following email this morning from a Demo User:
Thought it might be a good idea to start a thread on this board where I illustrate using the Profile Table Interface.... -jp . ~Edited by: jeff on: 11/19/2008 at: 4:14:53 PM~
| |||
| jeff 11/19/2008 3:10:13 PM | Q. What form factors are good with procaps files? A. Run any of your UDMs through the Data Window broken out by AFR, Form, BasicFitness, WoBrill, Rec Activity Days Last Start, and Rec Activity Days Last Start and Work... do that and I'll make an educated guess you'll see areas/cutoffs that are both good and bad... IOW let the data tell you what's good and what's bad. Q. And several factors such as woscore and wopct are not in preset filters or factors dropdown. On your site it mentions profile table interface. How would you use profile table interface to enter these factors? First, from the Factors Glossary at JCapper.com: WoPct - This number represents the percentile of where a horse's most recent workout ranked in relation to the other horses that worked the same distance at the same track on that same day. Example, a horse's most recent workout was at five furlongs at Saratoga on Sept 1. The time was 59 and 2/5 seconds. If a total of 100 horses also worked five furlongs at Saratoga on that same day and the time of our horse's workout was the fifth fastest at Saratoga for that day, then WoPct = 5 (or 5/100.) (Accessible via the Profile Table Interface) WoScore - or Workout Score. This number represents total furlongs worked within the past 21 days. (Accessible via the Profile Table Interface) A. Using the Profile Table Interface to set factor constraints for these two factors inside of a UDM: 1. Use the UDM Wizard to create the basic "Template" for the UDM. By basic template I mean set factor constraints for basics such as track, surface, distance, class descriptor, trainer, rider, etc. This can be done from inside the Profile Table Interface but IMHO the UDM Wizard makes the task easier. 2. Click one of the Profile Table Interface Buttons - There's one on the Main Module and another on the Data Window. You'll be presented with an interface giving you a choice of views. WoScore and WoPct are form based factors... use the COMPLETE VIEW ALL PROFILE option to start with. Clicking the Split View Checkbox (for some) makes using the interface a little easier once you get used things. 3. In the Profile Table Interface itself, scroll vertically to get to the UDM that you want to work with. The easiest way to do this is to simply click inside the profile field of the top UDM and then use the down arrow key on your keyboard to scroll down until you arrive at the target UDM. There's also a scrollbar on the far right - and another in the center when you are using the split view - but IMHO use of the down arrow is easiest. 4. Once you arrive at the target UDM (it'll stay marked via the black arrow on the left edge of the interface) - then to scroll to the right until you arrive at the profile table fields that control the factor you want to work with. Let's do WoPct first. Using the right arrow (or the tab key) tab over to the right until you see the fields for WoPct. The following screenshot shows the interface in split view where I've done that for the UDM named 4HK: http://www.JCapper.com/images/4HK01.jpg From here what you want to do is key in a set of entries that define the factor constraints for your UDM. For example, let's say you want the HK UDM to only flag horses where WoPct was in the top 10 pct for the dist the day of its most recent work. a. Change the 0 to a -1 to set a test for the factor b. set min val to -999 c. set max val to .10 The following screenshot shows the interface after doing that: http://www.JCapper.com/images/4HK02.jpg Hints: ALWAYS, always, always (Ever get the idea I'm trying to emphasize that?) make a back up copy of the following file before working with the UDM Wizard or the Profile Table Interface: c:\2004\JCapper.mdb Also, ALWAYS check your work in the Data Window after using the UDM Wizard or Profile Table Interface to edit a UDM. Run the UDM through the Data Window. Make sure you see the desired factor constraints in the Data Window before moving on. I'll come back and post more as time allows... -jp . ~Edited by: jeff on: 11/19/2008 at: 3:10:13 PM~
| |||
| jeff 11/19/2008 3:43:30 PM | Continuing on from my post above... Let's do WoScore: Using the right arrow or the tab key, scroll to the far right until the fields controlling WoScore are reached. Let's say for the sake of argument that you want to set a WoScore min val of 4: 1. Key a -1 into the active field to activate a test for WoScore as a factor. This has the same effect as checking the test box for a factor in the UDM Wizard. In the Profile Table Interface, a -1 is true and a 0 is false. 2. Set min val to 4 and leave max val at 999. Here is a screenshot of the interface in split view after doing that: http://www.JCapper.com/images/4HK03.jpg -jp . to be continued...
| |||
| jeff 11/19/2008 4:17:02 PM |
fimsInLastFour is the number of in the money finishes (3rd or better) a horse has in its four most recent past performance lines. Currently, it's one of those factors that isn't "grabbable" in a UDM. One of the more common questions I get from new users is "Jeff, I see a numbered factor in the Data Window, why can't I use it in a UDM?" Many of the numbered factors aren't actually part of the program. Many of them are there because I'm still testing ideas about these factors. I haven't had time yet to either remove or re-label them - or maybe I still want to do further testing on them. In a few instances - when large data samples showed they pack some punch roi-wise I've taken the time to add proper handles for them in the program - either via preset filters or in the UDM Wizard. Many of the numbered factors are used as building blocks. IOW they are included as inputs along with other factors and fed into the algorithms used to generate many of the JCapper factors that you see in the UDM Wizard. For example, fimsInLastFour for each horse is one the many inputs used to arrive at Race Volatility. My point being that even though the numbered factors aren't explicitly "grabbable" in UDMs - quite often, they show up as inputs for or are closely related to other JCapper factors that are "grabbable" in UDMs. Another example would be that on an individual horse basis fimsInLastFour is somewhat similar to Quinn's concept of "a good race" - If you run a UDM through the Data Window broken out by 55 fimsInLastFour and then run the same UDM through the Data Window broken out by Form Cycle you'll often see patterns that are similar. -jp . ~Edited by: jeff on: 11/19/2008 at: 4:17:02 PM~
| |||
| Tom C 11/20/2008 2:26:06 AM | Jeff, Isn't fimsInLastFour available as a dynamic filter? Thanks, Tom C ~Edited by: Tom C on: 11/20/2008 at: 2:26:06 AM~
| |||
| jeff 11/20/2008 9:20:02 AM | Yikes. My apologies Tom... I'd completely forgotten about that. fimsInLastFour IS available via dynamic filter. It's actually one of those factors someone convinced me to add it to the program... in early 2005 I think. And I still need to be re-label it on the Data Window's factors drop down (remove the number) as well as update the Supported Factors page at JCapper.com. -jp .
| |||
| notchback 4/12/2009 12:50:49 AM | Quick question, I just tried the PTI for the first time. I wanted to use WOpct in a UDM. When I run the UDM, I see my cutoffs listed above in the UDM parameters, but the cutoffs shown still show up when I run it through the data window. What could I have done wrong? Thanks, Doug
| |||
| jeff 4/12/2009 4:21:23 AM | My first best guess would be that it's a decimal point issue. WoPct is actually a percentage but is displayed in the Data Window as a whole number. So most users key it into the Profile Table Interface as a whole number the first time they try it. If this is the case, try using a decimal point. Instead of 10 try .10 and let me know if that does the trick. -jp .
| |||
| notchback 4/12/2009 10:53:06 AM | No luck. I am trying to cut off 70.00 and above. Min is set to -999 Max I have tried .70 and 70 and 70.00 I can send you a screen shot if you like.
| |||
| jeff 4/12/2009 11:09:51 AM | A partial cut n paste from the second post in this thread... Using the Profile Table Interface to set factor constraints for WoPct inside of a UDM: 1. Use the UDM Wizard to create the basic "Template" for the UDM. By basic template I mean set factor constraints for basics such as track, surface, distance, class, etc... 2. Then use the Profile Table Interface for the rest: Use the COMPLETE VIEW ALL PROFILE option to start with. Clicking the Split View Checkbox (for some) makes using the interface a little easier once you get used things. 3. In the Profile Table Interface itself, scroll vertically to get to the UDM that you want to work with. The easiest way to do this is to simply click inside the profile field of the top UDM and then use the down arrow key on your keyboard to scroll down until you arrive at the target UDM. There's also a scrollbar on the far right - and another in the center when you are using the split view - but IMHO use of the down arrow is easiest. 4. Once you arrive at the target UDM (it'll stay marked via the black arrow on the left edge of the interface) - then to scroll to the right until you arrive at the profile table fields that control the factor you want to work with. Let's do WoPct first. Using the right arrow (or the tab key) tab over to the right until you see the fields for WoPct. The following screenshot shows the interface in split view where I've done that for the UDM named 4HK: http://www.JCapper.com/images/4HK01.jpg From here what you want to do is key in a set of entries that define the factor constraints for your UDM. For example, let's say you want the HK UDM to only flag horses where WoPct was in the top 10 pct for the dist the day of its most recent work. a. Change the 0 to a -1 to set a test for the factor b. set min val to -999 c. set max val to .10 The following screenshot shows the interface after doing that: http://www.JCapper.com/images/4HK02.jpg Q. Does your screenshot look like the second screenshot shown above? Is the factor made active with a -1 in the test field? Is min val set to -999? Is max val set to .10 (or some other number?) If you are using the split view are you sure that you've made the entries to the same UDM? Hey, I HAVE to ask that last one... I've seen it done by others before... < G > If you appear to be doing it just like in the second screenshot above yet can't see WoPct in the Data Window then email a screenshot to me and I'll have a look. -jp .
| |||
| busseb 4/12/2009 3:44:29 PM | Jeff = Started working with WOPct and saw next to it in the View Active Profiles fileds labeled "keyracestest". Is it something that could be of value? How about a quick explanation? ElPaso
| |||
| jeff 4/12/2009 4:51:34 PM | For the uninitiated, a "key race" is a race where several horses all come out of the same race to win their next out. Quite a lot has been written about key races. And much of it sounds very promising. Very early on, in 2003/2004, based on posts at PA and elsewhere that I had read, I did R&D that enabled me to subject key races to hard database testing. I had planned to possibly add key races to the program. That R&D did show some promise (4-6 pct winners w/roi in the mid .90's at extremely high odds ranges only across a calendar year's worth of data) but I considered it a bust compared to other things (CPace, PMI, OptPoints, AFR, JPR, UPR, etc.) that I have tested and added since. There's definitely something to the idea of key races, but as a stand alone factor key races has never quite measured up to other things that I have been able to create, test, and make part of the program. I really wish it were otherwise. But for that reason, the field remains inactive. -jp .
| |||
| busseb 4/13/2009 5:20:50 PM | Jeff = Is it really inactive or just not accessable in the normal filter areas. Can we play with the key race to see if works at more specific tracks (like WOX)? I would assume that -1 activates the test, but what would go in the other field for options? Would the options be 2 min and 7 max for the min/max referring to the number of followup winners from the horses last race? Just because it isn't accessable as a filter doesn't mean that some late night the urge to experiment won't consume me. Besides, maybe things have changed since you did all your work or maybe it isn't as universal as the other factors that you have developed. That doesn't mean it isn't useful in specific situations. ElPaso
| |||
| jeff 4/13/2009 9:54:22 PM | It really is inactive. Running it required running a stand alone reporting module that separately tracked which race every race winner came out of. When I saw actual results I moved on to other things. I never completed the reporting module to the point where it would run outside of the JCapper development environment. -jp . ~Edited by: jeff on: 4/13/2009 at: 9:54:22 PM~
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |