2nd June 2012, 12:34 AM
|
|
Member
|
|
Join Date: Jan 1970
Posts: 589
|
|
Shaun / Chrome Prince and interested others.
I have given this some heavy thinking on this. I have also undertaken a crash course in excel. I am still a long way from being competent as a beginner, but each day I am learning more. I know that soon I will hit a brick wall and will need lots of help. However I do want to learn and know how to do this and more.
Attached is a SS showing the chart that I want as the basis for this. Do not take any notice of the figures in the cells as they are just the average breakeven price for each ranking in my breakdown. Note that I have $200 in a few cells, this is because I consider all horses at least a 200 to one chance. There is a box showing the average breakeven for 5 runners at <$1.60 fav price. And down the bottom is the average breakeven in all the >16 runners. This is to indicate the variance as we go from 57.4% for the fav in the 5 runners down to 22.8% in > 16 runners. Equally variable is the second fav.
I want to list all these variances and lay based on those prices. The actual price will actually be a hybrid of the prices, laying to a set amount, plus a loading on certain ranked horses. How and why I achieve these prices I still need to work out and test.
My question is “Can this be done in this format?” “We would have to lay to set amounts just prior to start time. The way I see it is that the Gruss bot will tell us (1) how many runners, (2) the fav expected range 30 sec out (3) the ranking order. Then if # runners=5 and the range between $1.30 and $1.60 then the bot will be directed to lay the fav at the liability of C8, the second fav at the liability of D8, the third fav at E8, fourth at F8 and Fifth at G8. Some of these may have a zero value because there are instances already identified that it is not advantageous to lay all the horses.
The questions are for procedure. I don’t want to do all the charting to find that I have to list them differently. Or that there is 10% more selections than the bot can handle.
My initial testing at random has shown that it is worth pursuing. Thanks in advance Beton
|