Feedback
jacky2, Betfair have specifically requested that we do NOT use their live scores. They are not exposed through the API at the moment. We thought it would be perfect for this tool but they have consistently declined the request to use this data. If you are aware of others that are using this then please send a note to support so we can use that in our case to Betfair.
-
mikelenard
- Posts: 33
- Joined: Fri Apr 24, 2009 7:12 pm
Thanks, I hope to see an update soon as some games can begin much later than 4 minutes.
Mike
Mike
-
mister man
- Posts: 363
- Joined: Tue Jul 27, 2010 2:10 pm
Bet angel
"Depending on how you set up the rule it's possible your 30 markets were on too slow a cycle to execute commands specifically within a time window."
thats what i summised...... what cycle should i have to do this in the cs market with 3 scores chosen, for approx 10-30 markets.
Ill keep plugging away but your help would be appreciated.
I stand by my comments on the trial response e-mail.
Also like another poster ive found multiple executions occuring even when setting unmatched bets to 0....
"Depending on how you set up the rule it's possible your 30 markets were on too slow a cycle to execute commands specifically within a time window."
thats what i summised...... what cycle should i have to do this in the cs market with 3 scores chosen, for approx 10-30 markets.
Ill keep plugging away but your help would be appreciated.
I stand by my comments on the trial response e-mail.
Also like another poster ive found multiple executions occuring even when setting unmatched bets to 0....
If you think you have found a bug in the latest beta version then please report it, but please help us by giving us the conditions to re-create it. Just saying something didn't work isn't very useful in solving any potential issues.
You can export your rules file and post it on this thread for others to try and that will help us isolate any potential issues you see.
When we were alpha testing we didn't see any issues, but there was some confusion on how the cycling around markets and timings would affect behaviour. Some times this can need a little thinking through.
We would recommend you always use practice mode while testing something new. It took a lot of effort to get the practice mode to work with the new automation, so please ensure you take advantage of it!
You can export your rules file and post it on this thread for others to try and that will help us isolate any potential issues you see.
When we were alpha testing we didn't see any issues, but there was some confusion on how the cycling around markets and timings would affect behaviour. Some times this can need a little thinking through.
We would recommend you always use practice mode while testing something new. It took a lot of effort to get the practice mode to work with the new automation, so please ensure you take advantage of it!
You guys are definitely rocket scientists 
Having spent a long time trying to implement my own effective automation on a spreadsheet, I know automation is definitely a very very tricky business, the market can throw exception after exception after exception at us. Great effort, looks very powerful.
Having spent a long time trying to implement my own effective automation on a spreadsheet, I know automation is definitely a very very tricky business, the market can throw exception after exception after exception at us. Great effort, looks very powerful.-
mikelenard
- Posts: 33
- Joined: Fri Apr 24, 2009 7:12 pm
Following up from my previous post regarding start times I've also been looking at stakes.
Let's say I am laying and I expect odds to be around 2.0 in-play when I want to get involved, £30 being my liability so I'll need a stake of £30. For whatever reason the odds end up being 1.9 instead of 2.0 in-play. In that case I would want my stake to be £33.33 and not £30.
Is there anything we can do about this?
Mike
Let's say I am laying and I expect odds to be around 2.0 in-play when I want to get involved, £30 being my liability so I'll need a stake of £30. For whatever reason the odds end up being 1.9 instead of 2.0 in-play. In that case I would want my stake to be £33.33 and not £30.
Is there anything we can do about this?
Mike
The in-play time should not reset on market suspension, the in-play time should start incrementing as soon as the prices are retrieved from betfair with the in-play marker set. All the time the market remains active in Bet Angel (by adding it to Guardian for instance) the time will continue to increment.mikelenard wrote:Inter Milan game started at exactly 17:04, but new automation tool takes starting time of 17:00. I place my trades on exactly 30 minutes, so 4 minutes really is a big deal to me. If I use the In-play time then that also causes me a problem as if market is suspended for whatever reason a new time will appear after each suspension.
Please confirm if you are seeing the time reset (and where you see it) and we'll investigate further.
You should be able to achieve your 30 minute timed trigger with the configuration shown in the attached screenshot.
You do not have the required permissions to view the files attached to this post.
It depends on your Guardian refresh rate, but say you have Guardian refreshing at 1 market per second and you've got it cycling round ten markets, then you are retrieving new price information for each market once every ten seconds.mister man wrote:"Depending on how you set up the rule it's possible your 30 markets were on too slow a cycle to execute commands specifically within a time window."
thats what i summised...... what cycle should i have to do this in the cs market with 3 scores chosen, for approx 10-30 markets.
The automation rules are tested each time new prices are retrieved from betfair (to ensure the triggers are based on current price information), so for this example you should allow each rule to stay active for at least ten seconds (probably 15 seconds to be on the safe side).
If you've got 30 markets loaded into Guardian (with a one second refresh), then you'll be getting new prices for each market once every 30 seconds, so you should increase the time the rules stay active accordingly.
If you are not trading manually with the Bet Angel trading screens, you could afford to increase Guardian's refresh rate and still stay within betfair's 20 calls per second data request charging threshold. Obviously if you're refreshing Guardian every 500ms, you'll cycle round 30 markets in 15 seconds.
How quickly were you re-arming the rule? Were you allowing enough time for the in-play delay to expire and for Bet Angel to retrieve the unmatched bet information for the market before re-arming the rule? When creating the rules you should consider how often the market will be updated (based on the number of markets in Guardian and the refresh rate) and re-arm the rules at a slower rate than that. The safest set-up would be to allow Guardian to cycle round the markets twice before re-arming to ensure all the market information is up to date.mister man wrote:Also like another poster ive found multiple executions occuring even when setting unmatched bets to 0....
-
mikelenard
- Posts: 33
- Joined: Fri Apr 24, 2009 7:12 pm
My configuration was set exactly how you set it in the image. I shall do a test on one of tonight's games and get back to you. From what I remember though the market was suspended after about 15 minutes and my bet was then placed 30 minutes after that, so on 45 minutes.Bet Angel wrote:The in-play time should not reset on market suspension, the in-play time should start incrementing as soon as the prices are retrieved from betfair with the in-play marker set. All the time the market remains active in Bet Angel (by adding it to Guardian for instance) the time will continue to increment.
Please confirm if you are seeing the time reset (and where you see it) and we'll investigate further.
You should be able to achieve your 30 minute timed trigger with the configuration shown in the attached screenshot.
Mike
-
mikelenard
- Posts: 33
- Joined: Fri Apr 24, 2009 7:12 pm
I have tested my in-play system this evening 30 minutes after the game began and this time it worked perfectly. Perhaps I wasn't ticking the right boxes before, I will continue to monitor it and if there are any problems I will report back.
Thanks for your help.
Mike
P.S. Any suggestions on the lay stake changing in accordance with the odds available at the time the lay is placed would be appreciated.
Thanks for your help.
Mike
P.S. Any suggestions on the lay stake changing in accordance with the odds available at the time the lay is placed would be appreciated.
I was also having this problem, but this could well be the reason. Shall change my rules accordingly and see if it works. Makes sense that this would be the reason.Bet Angel wrote:How quickly were you re-arming the rule? Were you allowing enough time for the in-play delay to expire and for Bet Angel to retrieve the unmatched bet information for the market before re-arming the rule? When creating the rules you should consider how often the market will be updated (based on the number of markets in Guardian and the refresh rate) and re-arm the rules at a slower rate than that. The safest set-up would be to allow Guardian to cycle round the markets twice before re-arming to ensure all the market information is up to date.mister man wrote:Also like another poster ive found multiple executions occuring even when setting unmatched bets to 0....