I've got a slight problem;
I'm laying horses in play with Guardian, set to "any selection" (with some conditions set, it tends to lay 2 or 3 losing horses most races) all good so far.
But even though I have number of matched and unmatched bets on current selection set to zero (I've also tried "less than 1") Guardian still lays the same selection twice or more occasionally. Normally when the selection wins. I presume it doesn't do it when it loses as the odds have quickly moved outside of the range I've allowed laying at.
Obviously a lay winning is always a risk - but when it's getting laid twice (9 seconds apart today at 22 and 15, wiping out more than todays gain) it gets very expensive!
Laying/betting on the same selection multiple times problem
It could be a number of things, if its actually triggering (not just matching) 9 secs apart that would tend to rule out conflicts between the re-arm time, in-play delay.
Other thing to look at is your guardian refresh rates and cycling (I have written some details on this and the effects it has on automation and will be posting over the next few days which you may find useful).
When your running the rule on a market is it in your main Bet Angel window and being refreshed at 200ms? or is it being run from within guardian along with other markets sharing the refresh rates?
Other thing to look at is your guardian refresh rates and cycling (I have written some details on this and the effects it has on automation and will be posting over the next few days which you may find useful).
When your running the rule on a market is it in your main Bet Angel window and being refreshed at 200ms? or is it being run from within guardian along with other markets sharing the refresh rates?
Guardian is set to switch markets 1 second before start time so should be in the main window. There was no other event that could have taken it.
Bets were placed 9 seconds apart. First one was initially unmatched.
Would "fill or kill" help maybe? Surely if it had to "watch" the bet it couldn't not know about it a few seconds later?
Or is that crediting a piece of code with an intelligence?
Bets were placed 9 seconds apart. First one was initially unmatched.
Would "fill or kill" help maybe? Surely if it had to "watch" the bet it couldn't not know about it a few seconds later?
Or is that crediting a piece of code with an intelligence?
"Would "fill or kill" help maybe? Surely if it had to "watch" the bet it couldn't not know about it a few seconds later?
Or is that crediting a piece of code with an intelligence?"
Not sure what you mean by that??
On your lay rule if your using both conditions Unmatched and Matched bets equal 0 then once a lay bet is triggered on that selection no further bets should be as either one or the other of those conditions should always prevent any more.
If you use fill and kill its not likely to solve this problem as you say its placing additional lays even when matched so the same will happen if using fill or kill or normal place lay.
Have you double checked your matched and unmatched conditions - in the past i have put 2 x matched or vice verse rather than one of each
Or is that crediting a piece of code with an intelligence?"
Not sure what you mean by that??
On your lay rule if your using both conditions Unmatched and Matched bets equal 0 then once a lay bet is triggered on that selection no further bets should be as either one or the other of those conditions should always prevent any more.
If you use fill and kill its not likely to solve this problem as you say its placing additional lays even when matched so the same will happen if using fill or kill or normal place lay.
Have you double checked your matched and unmatched conditions - in the past i have put 2 x matched or vice verse rather than one of each
Yes, definitely.Dallas wrote:Have you double checked your matched and unmatched conditions - in the past i have put 2 x matched or vice verse rather than one of each
Matched bets on selection = 0
Unmatched bets on selection = 0
resulted in
24/02/2016 17:19:17: [G_Auto] : £ 2.00 Lay bet placed on Snow Leopardess at 15.5. Entirely unmatched when it initially reached the market. Ref: 63160440898
24/02/2016 17:19:26: [G_Auto] : £ 2.00 Lay bet placed on Snow Leopardess at 26. Fully matched at 22.1. Ref: 63160452853
and
Matched bets on selection < 1
Unmatched bets on selection < 1
resulted in a similar "error" on Saturday.
Its a strange one with those conditions there is no reason why it should be allowing a 2nd or more bets to be submitted on a selection.
Do you have the whole log for that market or if not could you capture one next time it happens?
If its submitting the additional bets after one has been matched you could try adding the condition "Matched bets amount condition" as a extra precaution but if its submitting only while earlier ones are still unmatched on the selection this condition wont make any difference
Also just want to check that your not using the "checkpoint" rule type anywhere within your rule?
Do you have the whole log for that market or if not could you capture one next time it happens?
If its submitting the additional bets after one has been matched you could try adding the condition "Matched bets amount condition" as a extra precaution but if its submitting only while earlier ones are still unmatched on the selection this condition wont make any difference
Also just want to check that your not using the "checkpoint" rule type anywhere within your rule?
24/02/2016 13:59:59: Market changed to Donc 24th Feb - 14:00 2m Nov Hrd
24/02/2016 14:07:13: Market has been suspended
24/02/2016 14:07:13: Market is in-play
24/02/2016 14:07:14: Market has been unsuspended
24/02/2016 14:11:00: [G_Auto] : £ 2.00 Lay bet placed on Divine Spear at 38. Entirely unmatched when it initially reached the market. Ref: 63147163165
24/02/2016 14:11:03: [G_Auto] : £ 2.00 Lay bet placed on The Unit at 18.5. Fully matched at 15.38. Ref: 63147165809
24/02/2016 14:11:07: [G_Auto] : £ 2.00 Lay bet placed on Peter The Mayo Man at 36. £ 1.14 matched at 32 £ 0.86 unmatched when it initially reached the market. Ref: 63147170151
24/02/2016 14:11:21: Market has been suspended
24/02/2016 14:11:29: Market has been unsuspended
24/02/2016 14:12:27: Market has been suspended
24/02/2016 14:29:59: Market changed to Donc 24th Feb - 14:30 2m Juv Hrd
24/02/2016 14:35:32: Market has been suspended
24/02/2016 14:35:32: Market is in-play
24/02/2016 14:35:33: Market has been unsuspended
24/02/2016 14:39:29: [G_Auto] : £ 2.00 Lay bet placed on Our Thomas at 17. Entirely unmatched when it initially reached the market. Ref: 63148950620
24/02/2016 14:39:41: Market has been suspended
24/02/2016 14:59:59: Market changed to Donc 24th Feb - 15:00 3m Hcap Hrd
24/02/2016 15:05:45: Market has been suspended
24/02/2016 15:05:45: Market is in-play
24/02/2016 15:05:46: Market has been unsuspended
24/02/2016 15:11:04: [G_Auto] : £ 2.00 Lay bet placed on Theatre Goer at 27. Entirely unmatched when it initially reached the market. Ref: 63150984591
24/02/2016 15:11:09: [G_Auto] : £ 2.00 Lay bet placed on Nightline at 21. Fully matched at 15. Ref: 63150991161
24/02/2016 15:11:12: [G_Auto] : £ 2.00 Lay bet placed on Pinnacle Panda at 20. Fully matched at 17.5. Ref: 63150996074
24/02/2016 15:11:42: Market has been suspended
24/02/2016 15:29:59: Market changed to Donc 24th Feb - 15:30 3m Hcap Chs
24/02/2016 15:35:57: Market has been suspended
24/02/2016 15:35:57: Market is in-play
24/02/2016 15:35:58: Market has been unsuspended
24/02/2016 15:41:48: [G_Auto] : £ 2.00 Lay bet placed on Baileys Concerto at 18. Fully matched at 18. Ref: 63153365678
24/02/2016 15:41:50: [G_Auto] : £ 2.00 Lay bet placed on Grandads Horse at 29. Entirely unmatched when it initially reached the market. Ref: 63153369302
24/02/2016 15:41:59: Market has been suspended
24/02/2016 16:04:59: Market changed to Donc 24th Feb - 16:05 3m2f Hunt Chs
24/02/2016 16:10:30: Market has been suspended
24/02/2016 16:10:30: Market is in-play
24/02/2016 16:10:31: Market has been unsuspended
24/02/2016 16:12:16: [G_Auto] : £ 2.00 Lay bet placed on Major Malarkey at 36. Fully matched at 35.51. Ref: 63155493366
24/02/2016 16:12:19: [G_Auto] : £ 2.00 Lay bet placed on Barel Of Laughs at 17. Fully matched at 17. Ref: 63155497214
24/02/2016 16:12:27: [G_Auto] : £ 2.00 Lay bet placed on Railway Dillon at 34. Fully matched at 32. Ref: 63155507237
24/02/2016 16:12:30: [G_Auto] : £ 2.00 Lay bet placed on Cave Hunter at 17.5. Fully matched at 16.845. Ref: 63155509824
24/02/2016 16:14:47: [G_Auto] : £ 2.00 Lay bet placed on Nearest The Pin at 34. Entirely unmatched when it initially reached the market. Ref: 63155670052
24/02/2016 16:16:31: [G_Auto] : £ 2.00 Lay bet placed on One More Tune at 38. Entirely unmatched when it initially reached the market. Ref: 63155807701
24/02/2016 16:17:02: Market has been suspended
24/02/2016 16:39:59: Market changed to Donc 24th Feb - 16:40 2m NHF
24/02/2016 16:45:24: Market has been suspended
24/02/2016 16:45:25: Market is in-play
24/02/2016 16:45:25: Market has been unsuspended
24/02/2016 16:48:53: [G_Auto] : £ 2.00 Lay bet placed on Focaccia at 34. Entirely unmatched when it initially reached the market. Ref: 63158209357
24/02/2016 16:48:56: [G_Auto] : £ 2.00 Lay bet placed on Vive Le Roi at 18. Entirely unmatched when it initially reached the market. Ref: 63158213498
24/02/2016 16:48:59: [G_Auto] : £ 2.00 Lay bet placed on William Hunter at 23. Fully matched at 19.79. Ref: 63158217295
24/02/2016 16:49:44: Market has been suspended
24/02/2016 17:09:59: Market changed to Donc 24th Feb - 17:10 2m NHF
24/02/2016 17:15:38: Market has been suspended
24/02/2016 17:15:38: Market is in-play
24/02/2016 17:15:39: Market has been unsuspended
24/02/2016 17:19:17: [G_Auto] : £ 2.00 Lay bet placed on Snow Leopardess at 15.5. Entirely unmatched when it initially reached the market. Ref: 63160440898
24/02/2016 17:19:26: [G_Auto] : £ 2.00 Lay bet placed on Snow Leopardess at 26. Fully matched at 22.1. Ref: 63160452853
24/02/2016 17:19:37: [G_Auto] : £ 2.00 Lay bet placed on Rather Be at 17. Entirely unmatched when it initially reached the market. Ref: 63160467026
24/02/2016 17:19:41: Market has been suspended
24/02/2016 18:09:59: Market changed to Kemp 24th Feb - 18:10 1m Mdn Stks
24/02/2016 18:11:27: Market has been suspended
24/02/2016 18:11:27: Market is in-play
24/02/2016 18:11:27: Market has been unsuspended
24/02/2016 18:12:56: [G_Auto] : £ 2.00 Lay bet placed on Attitude Rocks at 17. Entirely unmatched when it initially reached the market. Ref: 63164277281
24/02/2016 18:13:05: Market has been suspended
24/02/2016 19:09:59: Market changed to Kemp 24th Feb - 19:10 1m4f Hcap
24/02/2016 19:11:27: Market has been suspended
24/02/2016 19:11:27: Market is in-play
24/02/2016 19:11:27: Market has been unsuspended
24/02/2016 19:13:57: [G_Auto] : £ 2.00 Lay bet placed on Biff Johnson at 23. Fully matched at 7.4. Ref: 63168629404
24/02/2016 19:14:05: Market has been suspended
24/02/2016 20:09:59: Market changed to Kemp 24th Feb - 20:10 2m Hcap
24/02/2016 20:15:48: Market has been suspended
24/02/2016 20:15:49: Market is in-play
24/02/2016 20:15:50: Market has been unsuspended
24/02/2016 20:19:16: [G_Auto] : £ 2.00 Lay bet placed on Jezza at 18. Entirely unmatched when it initially reached the market. Ref: 63174363489
24/02/2016 20:19:20: Market has been suspended
24/02/2016 21:03:32: Market changed to Ling 25th Feb - 14:35 1m Mdn Stks
What's the "checkpoint type" rule?
The question about "fill or kill" was referring to the idea that I could put a long time (longer than the race) on the time since active fill or kill time condition and it would be another trigger that a bet was on this selection.
This time the first bet placed was "initially unmatched", the old logs are now gone but I think it was last time as well, maybe, just maybe it's checking for matched bets not finding one, then before it checks for unmatched bets the bet is being matched and so once again it's not finding one?
24/02/2016 14:07:13: Market has been suspended
24/02/2016 14:07:13: Market is in-play
24/02/2016 14:07:14: Market has been unsuspended
24/02/2016 14:11:00: [G_Auto] : £ 2.00 Lay bet placed on Divine Spear at 38. Entirely unmatched when it initially reached the market. Ref: 63147163165
24/02/2016 14:11:03: [G_Auto] : £ 2.00 Lay bet placed on The Unit at 18.5. Fully matched at 15.38. Ref: 63147165809
24/02/2016 14:11:07: [G_Auto] : £ 2.00 Lay bet placed on Peter The Mayo Man at 36. £ 1.14 matched at 32 £ 0.86 unmatched when it initially reached the market. Ref: 63147170151
24/02/2016 14:11:21: Market has been suspended
24/02/2016 14:11:29: Market has been unsuspended
24/02/2016 14:12:27: Market has been suspended
24/02/2016 14:29:59: Market changed to Donc 24th Feb - 14:30 2m Juv Hrd
24/02/2016 14:35:32: Market has been suspended
24/02/2016 14:35:32: Market is in-play
24/02/2016 14:35:33: Market has been unsuspended
24/02/2016 14:39:29: [G_Auto] : £ 2.00 Lay bet placed on Our Thomas at 17. Entirely unmatched when it initially reached the market. Ref: 63148950620
24/02/2016 14:39:41: Market has been suspended
24/02/2016 14:59:59: Market changed to Donc 24th Feb - 15:00 3m Hcap Hrd
24/02/2016 15:05:45: Market has been suspended
24/02/2016 15:05:45: Market is in-play
24/02/2016 15:05:46: Market has been unsuspended
24/02/2016 15:11:04: [G_Auto] : £ 2.00 Lay bet placed on Theatre Goer at 27. Entirely unmatched when it initially reached the market. Ref: 63150984591
24/02/2016 15:11:09: [G_Auto] : £ 2.00 Lay bet placed on Nightline at 21. Fully matched at 15. Ref: 63150991161
24/02/2016 15:11:12: [G_Auto] : £ 2.00 Lay bet placed on Pinnacle Panda at 20. Fully matched at 17.5. Ref: 63150996074
24/02/2016 15:11:42: Market has been suspended
24/02/2016 15:29:59: Market changed to Donc 24th Feb - 15:30 3m Hcap Chs
24/02/2016 15:35:57: Market has been suspended
24/02/2016 15:35:57: Market is in-play
24/02/2016 15:35:58: Market has been unsuspended
24/02/2016 15:41:48: [G_Auto] : £ 2.00 Lay bet placed on Baileys Concerto at 18. Fully matched at 18. Ref: 63153365678
24/02/2016 15:41:50: [G_Auto] : £ 2.00 Lay bet placed on Grandads Horse at 29. Entirely unmatched when it initially reached the market. Ref: 63153369302
24/02/2016 15:41:59: Market has been suspended
24/02/2016 16:04:59: Market changed to Donc 24th Feb - 16:05 3m2f Hunt Chs
24/02/2016 16:10:30: Market has been suspended
24/02/2016 16:10:30: Market is in-play
24/02/2016 16:10:31: Market has been unsuspended
24/02/2016 16:12:16: [G_Auto] : £ 2.00 Lay bet placed on Major Malarkey at 36. Fully matched at 35.51. Ref: 63155493366
24/02/2016 16:12:19: [G_Auto] : £ 2.00 Lay bet placed on Barel Of Laughs at 17. Fully matched at 17. Ref: 63155497214
24/02/2016 16:12:27: [G_Auto] : £ 2.00 Lay bet placed on Railway Dillon at 34. Fully matched at 32. Ref: 63155507237
24/02/2016 16:12:30: [G_Auto] : £ 2.00 Lay bet placed on Cave Hunter at 17.5. Fully matched at 16.845. Ref: 63155509824
24/02/2016 16:14:47: [G_Auto] : £ 2.00 Lay bet placed on Nearest The Pin at 34. Entirely unmatched when it initially reached the market. Ref: 63155670052
24/02/2016 16:16:31: [G_Auto] : £ 2.00 Lay bet placed on One More Tune at 38. Entirely unmatched when it initially reached the market. Ref: 63155807701
24/02/2016 16:17:02: Market has been suspended
24/02/2016 16:39:59: Market changed to Donc 24th Feb - 16:40 2m NHF
24/02/2016 16:45:24: Market has been suspended
24/02/2016 16:45:25: Market is in-play
24/02/2016 16:45:25: Market has been unsuspended
24/02/2016 16:48:53: [G_Auto] : £ 2.00 Lay bet placed on Focaccia at 34. Entirely unmatched when it initially reached the market. Ref: 63158209357
24/02/2016 16:48:56: [G_Auto] : £ 2.00 Lay bet placed on Vive Le Roi at 18. Entirely unmatched when it initially reached the market. Ref: 63158213498
24/02/2016 16:48:59: [G_Auto] : £ 2.00 Lay bet placed on William Hunter at 23. Fully matched at 19.79. Ref: 63158217295
24/02/2016 16:49:44: Market has been suspended
24/02/2016 17:09:59: Market changed to Donc 24th Feb - 17:10 2m NHF
24/02/2016 17:15:38: Market has been suspended
24/02/2016 17:15:38: Market is in-play
24/02/2016 17:15:39: Market has been unsuspended
24/02/2016 17:19:17: [G_Auto] : £ 2.00 Lay bet placed on Snow Leopardess at 15.5. Entirely unmatched when it initially reached the market. Ref: 63160440898
24/02/2016 17:19:26: [G_Auto] : £ 2.00 Lay bet placed on Snow Leopardess at 26. Fully matched at 22.1. Ref: 63160452853
24/02/2016 17:19:37: [G_Auto] : £ 2.00 Lay bet placed on Rather Be at 17. Entirely unmatched when it initially reached the market. Ref: 63160467026
24/02/2016 17:19:41: Market has been suspended
24/02/2016 18:09:59: Market changed to Kemp 24th Feb - 18:10 1m Mdn Stks
24/02/2016 18:11:27: Market has been suspended
24/02/2016 18:11:27: Market is in-play
24/02/2016 18:11:27: Market has been unsuspended
24/02/2016 18:12:56: [G_Auto] : £ 2.00 Lay bet placed on Attitude Rocks at 17. Entirely unmatched when it initially reached the market. Ref: 63164277281
24/02/2016 18:13:05: Market has been suspended
24/02/2016 19:09:59: Market changed to Kemp 24th Feb - 19:10 1m4f Hcap
24/02/2016 19:11:27: Market has been suspended
24/02/2016 19:11:27: Market is in-play
24/02/2016 19:11:27: Market has been unsuspended
24/02/2016 19:13:57: [G_Auto] : £ 2.00 Lay bet placed on Biff Johnson at 23. Fully matched at 7.4. Ref: 63168629404
24/02/2016 19:14:05: Market has been suspended
24/02/2016 20:09:59: Market changed to Kemp 24th Feb - 20:10 2m Hcap
24/02/2016 20:15:48: Market has been suspended
24/02/2016 20:15:49: Market is in-play
24/02/2016 20:15:50: Market has been unsuspended
24/02/2016 20:19:16: [G_Auto] : £ 2.00 Lay bet placed on Jezza at 18. Entirely unmatched when it initially reached the market. Ref: 63174363489
24/02/2016 20:19:20: Market has been suspended
24/02/2016 21:03:32: Market changed to Ling 25th Feb - 14:35 1m Mdn Stks
What's the "checkpoint type" rule?
The question about "fill or kill" was referring to the idea that I could put a long time (longer than the race) on the time since active fill or kill time condition and it would be another trigger that a bet was on this selection.
This time the first bet placed was "initially unmatched", the old logs are now gone but I think it was last time as well, maybe, just maybe it's checking for matched bets not finding one, then before it checks for unmatched bets the bet is being matched and so once again it's not finding one?
-
sionascaig
- Posts: 1611
- Joined: Fri Nov 20, 2015 9:38 am
I had a similar problem and the placing an "unmatched bet time condition" seemed to resolve it... (in my case : time since market contained and unmatched bet condition > 3 secs)... That said, still in learning mode and there may have been something else going on that I'm not fully understanding..
Regards
Regards
"maybe, just maybe it's checking for matched bets not finding one, then before it checks for unmatched bets the bet is being matched and so once again it's not finding one?"
The rule would always check through all your conditions and make sure there all met before submitting any bet
"What's the "checkpoint type" rule?"
If you dont know what it is you wont be using it, what it does is resets the number or matched bets etc
So if your rule said matched bets = 0 once one bet is placed then no more should be
then if you use the check point rule type it resets this so the rule now thinks there is 0 matched bets again and will allow the next bet to trigger - its mostly used on tennis automation at the start of each game or set
Next time it happens if you can post the full log for that race including matched bet times etc so it can be identified if the 2nd lay is appearing with a unmatched bet still in the market or if its been matched then the 2nd is being submitted and what the timings are.
Ultimately with the conditions your using additional bets should not be happening on the same selection so there is is something amiss somewhere
The only other thing just going back to your timings and market cycles Doncaster had a 5min delay on all yesterday races and if it last happened on Saturday there could of also been delays or timing issues causing the problem there - you would need to check the arm times within your rules and the guardian cycling times to make sure all these where still ok despite the 5 min delay
The rule would always check through all your conditions and make sure there all met before submitting any bet
"What's the "checkpoint type" rule?"
If you dont know what it is you wont be using it, what it does is resets the number or matched bets etc
So if your rule said matched bets = 0 once one bet is placed then no more should be
then if you use the check point rule type it resets this so the rule now thinks there is 0 matched bets again and will allow the next bet to trigger - its mostly used on tennis automation at the start of each game or set
Next time it happens if you can post the full log for that race including matched bet times etc so it can be identified if the 2nd lay is appearing with a unmatched bet still in the market or if its been matched then the 2nd is being submitted and what the timings are.
Ultimately with the conditions your using additional bets should not be happening on the same selection so there is is something amiss somewhere
The only other thing just going back to your timings and market cycles Doncaster had a 5min delay on all yesterday races and if it last happened on Saturday there could of also been delays or timing issues causing the problem there - you would need to check the arm times within your rules and the guardian cycling times to make sure all these where still ok despite the 5 min delay