|
JCapper Message Board General Discussion
|
| Home |
Register
Log In |
| By | JCapper WagerHistory Module (Coming Soon) | |
| jeff 1/27/2012 5:41:11 PM | JCapper WagerHistory Module Screenshots Below are some some screenshots of the (soon to be released) JCapper WagerHistory Module. Data Entry http://www.JCapper.com/Messageboard/Avatars/WagerHistoryDataEntry01.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryDataEntry02.jpg The above screenshots show the WagerHistory Data Entry Screen. Note that the UDM Races List displayed in the lower left hand screen area populates with a click of the Populate button and that the list of races with UDM plays is generated/regenerated each time a SQL Mode Calc Races is run. To begin the data entry process, double click the desired race and click the NEW button. From there, begin filling in the info you wish to capture. Keep in mind that when finished the module will interface with the StarterHistory table - meaning that data items such as CPace rank, surface, distance, rider, trainer, sire, dam, WoBrill, etc. need not be captured during data entry. Such data items can be auto populated into the wager record once the race in question becomes part of a SQL Mode Build Database routine. Ticket Calculator http://www.JCapper.com/Messageboard/Avatars/WagerHistoryTicketCalculator01.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryTicketCalculator02.jpg The above screenshots illustrate the WagerHistory Module Ticket Calculator being used to generate tickets prior to having them persisted to the Data Entry Screen. The design of the Ticket Calculator is such that it can be used to generate any ticket that a mutuel teller can generate. My intent down the road is to make the Ticket Calculator capable of writing tickets to a text file which in turn can be uploaded to various ADWs that support text file upload. Reports http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports01.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports02.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports03.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports04.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports05.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports06.jpg http://www.JCapper.com/Messageboard/Avatars/WagerHistoryReports07.jpg The above screenshots show my own actual wagering activity over the past two weeks. My purpose in posting isn't to brag or redboard. Truth be told, I'm less than happy with these results. (They could have been better.) In the next few paragraphs I'll attempt to use the above screenshots to illustrate why - as well as illustrate the value of how proper record keeping can improve the player's bottom line going forward. All Wagers Are Not Created Equal - Short Description The first point I want to make is that all wagers are not created equal. In the WagerHistory Module there is a concept introduced called a SHORT DESCRIPTION. Simply put, a Short Description equates to THE REASON THE PLAYER MADE THE BET IN THE FIRST PLACE. Reasons for making bets vary from one player to another and are therefore user defined. Short Descriptions must be created ahead of time in the Setup Screen. But once you have one set up you can use it over and over each time you use the module to record a wager. The idea is to use unique Short Descriptions tied to the actual reason the player has for making each bet. The first screenshot above shows ALL wagering activity. The second screenshot above shows wagering activity for Short Description HATC only. Note the difference between the two. This speaks to the essence of the WagerHistory Module: If all wagers are not created equal, it follows that analyzing wagers using data points - the reason the bet was made in the first place is a data point - gives the player the ability to recognize strengths and weaknesses. Through the simple act of recognizing and avoiding known mistakes, the player gains the ability to improve wagering performance going forward. In my own world HATC is an acronym that stands for Horse Above The Curve. HATC is another way of stating the following: A single horse flagged by one or more of my business UDMs where the odds and conditions as the horse goes to post lead me to believe that making a bet on this horse is a play that carries a long term positive expectancy. The third screenshot above shows all wagering activity for Short Description EXASVR. As you might have guessed by now, EXASVR is a short description I use to describe an exacta saver bet. The negative results found in the report should come as no surprise. In fact they closely mimic long term results seen in the Data Window whenever I run business UDMs through the Data Window and look at what happens if I play them underneath other horses using an exacta. Despite being fully aware of this phenomenon ahead of time (for some dumb reason) I just could not help myself – and made (and recorded) these losing bets anyway. One aspect of my game that I have worked on over the years is the ability to look at a horse and quickly assess its physical condition. I might not always be right – but I am right more often than I am wrong. To this end, one of the things I built into the WagerHistory Module was the ability for the player to capture a number called a PhysScore – which is simply the players assessment (visually) of the physical condition of the horse. In my own world, PhysScores exist on a scale of 0 to 5 – with 0 being lowest and 5 being highest. The fourth screenshot above shows all wagering activity where min PhysScore for the primary horse was at least 3. The fifth screenshot shows all wagering activity where PhysScore for the primary horse was less than 3. Note the difference between the two reports. If learning to assess physical condition of a horse is something you are interested in, I recommend starting the journey with The Body Language of Horses by Bonnie Ledbetter and Tom Ainslie. Another aspect of my game that I have worked on over the years is the ability to watch races and equate race outcomes to Track Weight. Most players are quick to dismiss track bias. However, I use it as an integral part of my game. To that end I added a data field for Track Weight to the WagerHistory Module Data Entry Screen. The sixth screenshot above shows all wagering activity where Track Weight (pre-race) was thought to be between 1 and 2.. The seventh screenshot above shows results where track weight (identified pre-race) was thought to be between 3 and 5. Note the difference between the two reports. Also note that in my world, Track Weight exists on the same scale that I have written about before: 1 through 5, where 1 and 2 is speed favoring - and where 4 and 5 is speed tiring. If you guessed by the above results that most of the business UDMs I am using are designed to point out horses that possess advantages in early speed you would be correct. A quick analysis of the reports suggests these types of UDMs perform better on speed favoring surfaces. I freely admit to knowing that ahead of time and also admit to purposely ducking track surfaces I thought were speed tiring as much as possible. My belief is this skewed the overall results shown in the screenshot number one above – causing them to exceed the normal expectation that comes with making every possible play generated using my business UDMs. One other note about screenshot number 7: Each of the 28 UDM horses that I played on speed tiring surfaces had PhysScores that I thought would be strong enough to enable the horse to overcome the influence of track surface. This turned out to be sheer fallacy on my part (as evidenced by the results.) My purpose in developing this module is to give the player the tools to: 1. Create a detailed set of records. 2. Analyze those records. 3. Improve the bottom line going forward through the act of a. recognizing and b. not repeating mistakes. I plan to publish the WagerHistory Module as part of a JCapper Program Update (all program versions) on or before February 1, 2012. Going forward I plan on adding significant improvements to this module. (If you are thinking about asking me to do custom work for you in other areas over the near term: STOP! This module is going to get my focus in terms of programming hours for at least the immediate foreseeable future.) In the beginning this module will give you basic data capture and some canned reports. Going forward it will give you the ability to write tickets to text files that can be uploaded to ADWs as well as the ability to perform data analysis about your own wagers that mimics the capability of the Data Window when it comes to slicing and dicing data about your UDMs. -jp . ~Edited by: jeff on: 1/27/2012 at: 5:41:11 PM~
| |
| STUBALL 1/27/2012 5:51:05 PM | Jeff thank you again and again....you never cease to amaze me. what I can only dream you can conceive. I intend to make use of this module and can forsee a vast improvement...we all make mistakes in judgement regardless of the fact that we use computers...this will help loads to eliminate some of these errors and help the bottom line...we don't bet horses to win races but when we win and demand the proper return then lady luck certainly smiles on us...we are so lucky to be part of the JCapper family... Well back to work Stuball
| |
| Windoor 1/30/2012 8:25:20 AM | Although I pride myself for my detailed record keeping, I can see were this would make things easier and maybe give some insight on the types of races I play and lose I too, have a weakness for playing exacta's even though I know I lose money long term with them. I keep them at $2 so as not to hurt the bottom line that much. I think of it as entertainment costs:) If fact I played two this morning. Parx: R__2, I boxed the 3,6,9 Parx: R__3, I boxed the 1 & 3. Regards, Windoor
| |
| Windoor 1/30/2012 2:39:37 PM | With the typical results. The sad part is, I punched the wrong race numbers in and had to cancel the wagers to correct them. Had I not realized my mistake, the 6,3 (In the third race) exacta pays $222. Oh my! Regards, Windoor
| |
| Charlie James 2/3/2012 1:30:45 PM | Really looking forward to this Jeff.
| |
| tanix 2/7/2012 8:54:32 PM | Windoor, one piece of racing superstition that I've held on to through the years is that I *never* change a ticket once I've placed the wager. If I made a mistake I may bet another ticket that is consistent with my original intent, but I keep the error ticket just the same. Does this win me money in the long run? Probably not, but I think of it as an investment in my mental health. :-)
| |
| parshooter 3/13/2012 1:01:57 PM | Just wondering what status of wager history module is. Or have I missed an update somewhere? I also am very much looking forward to this feature.
| |
| jeff 3/13/2012 3:15:13 PM | I've been working on it as much as free time allows - and have made significant progress on all fronts... especially the reporting area. I've essentially created a Reporting Engine that enables the player to analyze wager history broken out by all aspects found in the JCapper Sql Data Window as relates to horses -- plus attributes found in the new module itself: Short Description, UDM Profile, Wager Type (WIN, WP, WPS, PLACE, SHOW, EXA, TRI. SUPER, P3, P4, P5, P6), Track Weight, Physicality, and Player's Estimated Edge. Absolutely and without question, some of the info found in the reports (at least for my own wager history) is eye opening. I have to admit, a Feb 01 launch date was a bit ambitious.  Although the module is not officially released yet, for those of you who want to poke around and see what the screens look like: The download package for the latest program update includes an .exe file for the new module. The filename is wagerhistory.exe and the file can be found in the c:\JCapperBuild folder. Double click the file to run it... or manually copy it to the c:\JCapper\Exe folder - and launch from the WagerHist button on the face of the JCapper Main Module (The new button becomes active once the .exe file is present on the c:\JCapper.exe folder.) There is still much to do... I've started a Help Doc which needs to be taken a little further before others can be expected to operate the module (without bombarding me with questions about using it.) A video is also in the works. I also need to finish the Ticket Calculator. Right now the numeric keypad/buttons are active for wager amounts only. Horse (or saddle cloth) number for purposes of ticket generation can only (currently) be selected using drop downs. -jp .
| |
| parshooter 3/13/2012 10:07:13 PM | Thank you Jeff for update. I know you have been very busy with JCapper upgrades, questions and with HANA. And of course time to actually wager. All I am certain is much appreciated
| |
| jeff 3/14/2012 11:03:46 AM | Also coming soon to a program update in the very near future... screenshot: The JCX File Exports Module This is an interface that facilitates creation of comma delimited export files. (For those of you who are using 3rd party apps to work with JCapper data outside of JCapper.) -jp .
| |
| mjkkost 3/16/2012 9:48:20 AM | Will data for P3 payoffs have to be entered manually?
| |
| jeff 3/16/2012 2:20:12 PM | All payoffs no matter what pool or wager type are entered the same way. Step 1. Create a Ticket. Screenshot - Ticket Calculator On the Data Entry Sheet, click the Ticket Calculator button to launch the Ticket Calculator. Use the Ticket Calulator interface to create a ticket and hit a persist button to persist the ticket back to the Data Entry Sheet. Step 2. Work up Amt Collected. Screenshot - Amt Collected Tool Double click the Amt Collected field on the Data Entry Sheet to launch the Amt Collected Tool. The Amt Collected Tool has two sides to it: A. The left side which relates to the base amt on YOUR TICKET. B. The right side which relates to the mutuel payoff reported by the track/chartcaller that is used as a basis for calculating the AMT COLLECTED. When the Amt Collected Tool initializes it will pickup the base wager amt that was persisted (from step 1 above) to the Data Entry Sheet and use it to auto populate the left side of the interface. Your job as a user is is to work up the amt collected and persist it back to the Data Entry Sheet. The steps are: a. Key in the numbers on the right side of the interface... mutuel payoff and base amount and hit the Calc Amt Coll button. This will calculate the amount you collected on the ticket. b. Double check your amount collected and persist it back to the Data Entry Sheet by hitting the Persist To Data Entry Sheet Button. Once you get the hang of it, it's actually fast and easy. -jp .
| |
| jeff 3/20/2012 10:59:55 PM | The 3/20/2012 Platinum new program update contains both the WagerHistory and JCX File Exports modules. Read the release notes before downloading. Partial help doc (so far) for the WagerHistory module. No help doc yet for the JCX File Exports module (but the release notes contain a screenshot along with a pretty good set of basic operating instructions.) -jp .
| |
| jeff 5/11/2012 7:26:56 PM | The WagerHistory Module Help Doc has been recently updated. The revised doc now covers a lot of ground - although there are still a few things I plan on adding to it. The revised doc now contains links to lots of screenshots as well as separate sections covering General Overview, The Setup Screen, The Data Entry Sheet, The Ticket Calculator, The Amt Collected Workup Screen, the Report Generator, and Interpreting WagerHistory Reports. There's even a section towards the end where I write about using wager history data as part of a strategy for retooling your game. Link to WagerHistory Module Help Doc: http://www.jcapper.com/helpDocs/JCapperWagerHistoryHelpDoc.htm -jp .
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |