Bet Angel Automation - Horse racing - Pre off : Directional Scalping Pre Off Guardian Automation Bot

User avatar
Willygubbins
Posts: 109
Joined: Wed Nov 23, 2016 6:03 pm

Mon May 08, 2017 8:42 am

Dallas, I want to use the odds movement rules to make a signal to stop a bet being placed if the a nominated horse has drift out prerace, Which I can use the conditions in this rule but is it possible to add if has hit its BSP or it is at its highest traded price?
Thanks

greety
Posts: 134
Joined: Wed May 16, 2012 7:16 pm

Fri May 19, 2017 4:23 pm

Hi Dallas.
I've been playing around with this with minimum stakes. I've had some good days and then some bad days.
When the trade goes against you, is it possible to set a stop loss? Being pre race, it wouldn't be a problem, would it?

tony63
Posts: 11
Joined: Wed Mar 16, 2016 12:14 pm

Sun Jul 16, 2017 5:04 pm

Hi Dallas,

I've just downloaded the file and am just trialling it. Something that has confused me.

I had a red up at -£8 and so I thought I'd look in more detail to see if I could tweak it. In the log tab it placed 4 bets 100023 100024 100025 and 100026. All bets were then shown in the log as killed after 10 secs. All appears OK so far.

The log then shows greened up. Confused. If all bets are cancelled then there shouldn't be anything to green up.

Looking at the matched bets tab, it then shows bets 100025 and 100026 WERE matched. This explains why there was a green up.

However, no offset bet with greening appeared in matched bets. There were no unmatched bets showing in the unmatched bets tab.

I must be wrong but from the file I would expect:

1 The log and the matched bets to agree.

2 An Offset bet to be placed when the 1st bet is matched.

3) No second bet placed on the same horse until the first offset bet is matched.

I am running in practice mode.

The only changes I have made is to stop trading earlier than 20 secs and I've added export P&L.

From automation tab

16/07/2017 14:30:10: [G_Auto] : £ 10.00 Lay bet placed on Deep Breath at 6.4. Entirely unmatched when it initially reached the market. Ref: 10023 ( Fill or kill bet with 10 seconds delay. Offsetting by 1 ticks with greening. )
16/07/2017 14:30:20: [G_Auto] : £ 10 unmatched bet (Ref:10023) was killed.
16/07/2017 14:30:24: [G_Auto] : £ 10.00 Lay bet placed on Golden Spell at 3.8. Entirely unmatched when it initially reached the market. Ref: 10024 ( Fill or kill bet with 10 seconds delay. Offsetting by 1 ticks with greening. )
16/07/2017 14:30:34: [G_Auto] : £ 10 unmatched bet (Ref:10024) was killed.
16/07/2017 14:30:51: [G_Auto] : £ 10.00 Lay bet placed on Deep Breath at 6.8. Entirely unmatched when it initially reached the market. Ref: 10025 ( Fill or kill bet with 10 seconds delay. Offsetting by 1 ticks with greening. )
16/07/2017 14:31:12: [G_Auto] : £ 10 unmatched bet (Ref:10025) was killed.
16/07/2017 14:31:19: [G_Auto] : £ 10.00 Lay bet placed on Deep Breath at 7.2. Entirely unmatched when it initially reached the market. Ref: 10026 ( Fill or kill bet with 10 seconds delay. Offsetting by 1 ticks with greening. )
16/07/2017 14:31:39: [G_Auto] : £ 10 unmatched bet (Ref:10026) was killed.
16/07/2017 14:34:53: [G_Auto] : Greened up Deep Breath by Backing 28.00 at 5
16/07/2017 14:35:54: Guardian has detected that the market is in-play
16/07/2017 14:35:54: Guardian has detected that the market is suspended
16/07/2017 14:36:00: Guardian has detected that the market is now unsuspended
16/07/2017 14:37:08: Guardian has detected that the market is suspended

From Log file

Time Back/Lay Selection Odds Stake Reference
16/07/2017 14:30 Lay Deep Breath 6.8 10 10025
16/07/2017 14:31 Lay Deep Breath 7.2 10 10026
16/07/2017 14:34 Back Deep Breath 5 28 10028

What am I doing wrong?

Thanks

User avatar
Dallas
Posts: 8788
Joined: Sun Aug 09, 2015 10:57 pm

Sun Jul 16, 2017 5:27 pm

I suspect its to do with your refresh settings being used.

If you look at the 3 correctly killed bets they were all done exactly 10secs after they were placed (as per the fill/kill instruction)
The two bets which were actually matched but according to the log were 'killed' were both written to the log well after 10 secs had past (just the two lines were they say they were killed). The only reason i can think of for this is your refresh settings

If your not loading the race to a main trading screen and just running from within guardian make sure you have the refresh interval set at 200ms and then on the 'advanced settings' tab of the guardian banner ensure the restrict refresh option' is enabled and set to about
700 secs before event start
0 secs after event start

tony63
Posts: 11
Joined: Wed Mar 16, 2016 12:14 pm

Sun Jul 16, 2017 5:32 pm

Hi Dallas.

Just to let you know that there is another example - all the instances detailed and so it's not a one off.

tony63
Posts: 11
Joined: Wed Mar 16, 2016 12:14 pm

Sun Jul 16, 2017 5:40 pm

Thanks Dallas.

Refresh was set to 200millisecs but I have changed the advanced screen settings to those suggested.

If I can, I'll try and run it tomorrow. I'll let you know if I am still having problems.

Thanks again.

User avatar
Dallas
Posts: 8788
Joined: Sun Aug 09, 2015 10:57 pm

Mon Jul 17, 2017 12:59 pm

tony63 wrote:
Sun Jul 16, 2017 5:40 pm
Thanks Dallas.

Refresh was set to 200millisecs but I have changed the advanced screen settings to those suggested.

If I can, I'll try and run it tomorrow. I'll let you know if I am still having problems.

Thanks again.
I had a look at this last night and have been able to recreate it a few times, it actually looks like a rounding issue when in practice mode.
If you want to keep an eye on it you can do but the main thing is the bets are matching ok so its really just a minor bug in the log report when in PM which could probably be debugged in the next build.

I would still change the settings i suggested in my earlier message as these will ensure the bot is able to trigger optimally

tony63
Posts: 11
Joined: Wed Mar 16, 2016 12:14 pm

Mon Jul 17, 2017 3:05 pm

Sorry, I can't agree.

I thought the idea was a bet was placed and if matched a reverse bet is then placed 1 tick away. If the second bet is matched then that gives us our profit.

What is happening is that a bet is being placed, matched, reported as being killed, no reverse bet placed 1 tick away, a second lay bet being placed, again matched, again reported as being killed, again no reverse bet being placed ( which could go go several times until green up) and then a green up by which time the price could have moved significantly in the wrong direction.

A rounding issue - sorry I can't see it. A timing issue I can see. I did think about extending the 3 seconds but that won't make any difference if the reverse bet isn't placed.

I also thought about seeing if back bets = lay bets (somehow) but that doesn't work as any 1 bet matched may split over more than 1 transaction.

It begs 2 questions. I'm guessing live and practice modes actually work slightly differently but

1) It potentially could hit any bot. I can't see it being the rules file but the timings or the way the rules files are inturpreted by the Bet Angel software.

2) Is it affecting live processing? Having seen the problem I know I won't be risking real money.

Today I am running on your revised settings. There haven't been any instances yet but there have only been a limited number of opportunities.

A thought that occured. Doesn't the settings given mean that any in play opportunities have to be excluded? EG I was looking at your file this morning. Soccer - lay the correct score after 80 minutes. Wouldn't that require unrestricted refresh rates. I'm just trying to improve my understanding here.

Thanks again Dallas!

User avatar
Dallas
Posts: 8788
Joined: Sun Aug 09, 2015 10:57 pm

Mon Jul 17, 2017 3:44 pm

tony63 wrote:
Mon Jul 17, 2017 3:05 pm

I thought the idea was a bet was placed and if matched a reverse bet is then placed 1 tick away. If the second bet is matched then that gives us our profit.

What is happening is that a bet is being placed, matched, reported as being killed, no reverse bet placed 1 tick away, a second lay bet being placed, again matched, again reported as being killed, again no reverse bet being placed ( which could go go several times until green up) and then a green up by which time the price could have moved significantly in the wrong direction.
When it happened for me i was using a different rule and just happened to notice it. Although the offset was still triggering perfectly it was just a simple case of the log mistakenly writing the opening bet had been killed.

If the offset is not being placed after a matched bet for you that's a different thing and something i never seen happen - this is done via a straight forward fill/kill order which has been used in 1000s of rules without issue in both PM and LM
tony63 wrote:
Mon Jul 17, 2017 3:05 pm

A thought that occured. Doesn't the settings given mean that any in play opportunities have to be excluded? EG I was looking at your file this morning. Soccer - lay the correct score after 80 minutes. Wouldn't that require unrestricted refresh rates. I'm just trying to improve my understanding here.

Thanks again Dallas!
The setting i gave were just for this pre-race rule, you would need to change them if using a in-play rule, this following thread explains how guardian refreshing/cycling works so you should get an idea of the best ways to set it up depending on your requirements
http://www.betangel.com/forum/viewtopic ... 37&t=11491

faris
Posts: 1
Joined: Sun Sep 18, 2016 4:13 am

Wed Nov 08, 2017 2:23 pm

Hllo Dallas,
The Directional Scalping Pre Off bot , is it possible to add a condition that it will automatically high light the market next to be traded in blue in the guardian without clicking manually as to go through all the market at 200 millisecond and that takes 13 to15 second to recycle to place a back bet to green up.where if it high light it in blue it take less than 1 seconds
thanks

Post Reply

Return to “Bet Angel Automation - Horse racing - Pre off”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest