Hi,
Is it at all possible to retrieve the matched bets column in BetAngel through the Excel capability?
Thanks, Mark.
Ability to retrieve matched bets column in Excel
-
Nero Tulip
- Posts: 708
- Joined: Wed Apr 15, 2009 5:29 pm
Currently it is impossible to do. BetAngel doesn't have it in the current version. There's been talk for some time about finding ways to include it. If you can make good design additions to the current sheet showing where and how you would display them and send it to their support email address they might appreciate the effort?
I would also love to have this feature, it would add greatly to my ability to analyse and also to the management of my positions, which is currently restricted.
I would also love to have this feature, it would add greatly to my ability to analyse and also to the management of my positions, which is currently restricted.
-
JacoboPolavieja
- Posts: 91
- Joined: Thu Sep 10, 2009 6:00 pm
Yeap! Totally waiting for it! Thanks a lot!
Well, unmatched and matched bet data is not fed to the spreadsheet from Bet Angel. So if you pay someone who says they can do it then you will be wasting your money.
I had a look at this and the obstacles are not insignificant. Where do you put all the data? In one horse race alone, you may have hundreds of bets, partial matches, backs and lays. ALL ON ONE RUNNER.
If you are dutching or bookmaking you may have hundreds of bets on ALL runners. How would you manage all this data?
I'm talking about price, stake, bet reference for matched, unmatched, back and lay. If all this is updated several times per second, or even once per second then I can see a considerable performance impact.
So, should there be a sheet for each runner? This could soon make a system stop with large markets.
Or maybe just a log sheet. That updates with all matched bets and unmatched bets in a particular market. We could then write code to sort out what is matched by runner. But if a bet is matched it would need to have it's 'unmatched' log entry updated instantly otherwise incorrect triggers could be set off. I can see where performance issues may come into this.
Or perhaps just a list of market runners with four columns - total matched, total unmatched. For Back and Lay bets. This would mean losing the bet reference, price matched at and so on but might be easier to implement?
Or perhaps an extra instruction. DATA_ALL or DATA_BACK and that populates a sheet with unmatched data for just that one time rather than a constant stream of performance troubling data?
Maybe someone else can think of something better?
I had a look at this and the obstacles are not insignificant. Where do you put all the data? In one horse race alone, you may have hundreds of bets, partial matches, backs and lays. ALL ON ONE RUNNER.
If you are dutching or bookmaking you may have hundreds of bets on ALL runners. How would you manage all this data?
I'm talking about price, stake, bet reference for matched, unmatched, back and lay. If all this is updated several times per second, or even once per second then I can see a considerable performance impact.
So, should there be a sheet for each runner? This could soon make a system stop with large markets.
Or maybe just a log sheet. That updates with all matched bets and unmatched bets in a particular market. We could then write code to sort out what is matched by runner. But if a bet is matched it would need to have it's 'unmatched' log entry updated instantly otherwise incorrect triggers could be set off. I can see where performance issues may come into this.
Or perhaps just a list of market runners with four columns - total matched, total unmatched. For Back and Lay bets. This would mean losing the bet reference, price matched at and so on but might be easier to implement?
Or perhaps an extra instruction. DATA_ALL or DATA_BACK and that populates a sheet with unmatched data for just that one time rather than a constant stream of performance troubling data?
Maybe someone else can think of something better?
statistics packages like SPSS or databases can handle that data. Sorting or handling data is not a big issue I believe.
Too bad matched bets can't be exported elsewhere.
But you are right. It will be quite cumbersome and tedious and even not practical...
Too bad matched bets can't be exported elsewhere.
But you are right. It will be quite cumbersome and tedious and even not practical...
