It means it was filled (Matched) at this time, just prior to that your log will show something like.
"Back bet placed on XXX Entirely unmatched when it initially reached the market. Ref: XXX"
using the same Bet Id (Ref) which is the bet being triggered and placed in the market
If it is triggered and matched immediately it would show as something like
"Back bet placed on XXX. Fully matched at 2.16. Ref: XXX"
This would be achieved by placing at 'Best Price' on the parameters tab
Scalping & Kill Unmatched Offsets Guardian Automation Bot
Ok, look at this situation, it just happened in one of the races just now. Its a clear example of an unmatched offset waiting and not getting greened out by the rules.
In the image the back bet is the offset bet, and it's sitting for 14 seconds waiting, and in my automation rules is set to green at 5 seconds.
The log shows this line for this bet:
And this bet reference appears again only at the end of the log, when it was greened up by the automation rule:
In the image the back bet is the offset bet, and it's sitting for 14 seconds waiting, and in my automation rules is set to green at 5 seconds.
The log shows this line for this bet:
Code: Select all
03/08/2016 21:51:28: [G_Auto] : € 9.76 Back bet placed on 4. Lets Go Smiley at 4.2. Entirely unmatched when it initially reached the market. Ref: 25776Code: Select all
03/08/2016 21:52:30: [G_Auto] : Cancelling bets 25776
03/08/2016 21:52:30: [G_Auto] : Greened up 4. Lets Go Smiley by Backing 14.24 at 2.88You do not have the required permissions to view the files attached to this post.
Because the start time for the race is 21:53:00 and your 'green up' rule is set to arm 29secs before the event start time.
As soon as it get to this time and arms its triggering straight away - hence the green up at 21:52:30
As soon as it get to this time and arms its triggering straight away - hence the green up at 21:52:30
Yes this is true and correct.Dallas wrote:Because the start time for the race is 21:53:00 and your 'green up' rule is set to arm 29secs before the event start time.
As soon as it get to this time and arms its triggering straight away - hence the green up at 21:52:30
But my concern is with the unmatched offset which is that back bet. The rule is set to green up at 5 seconds and as you can see it's 14 seconds and still didn't get greened up.
As i said in the last response this is because your 'green up' rule is not yet armed therefore it can't/won't green up till after it has become armed - which is not until 30 seconds before the scheduled event start time.
Once it is armed it will also need a the value of the signal named 'unmatched' to equal 5.
I would assume this condtion has already been met sometime prior hence the reason it triggers as soon as its armed.
Once it is armed it will also need a the value of the signal named 'unmatched' to equal 5.
I would assume this condtion has already been met sometime prior hence the reason it triggers as soon as its armed.
Oh I messed up the images.
Yes I have a final green up from 29 seconds before the off.
But I also have this "Cancel unmatched offset" rule from 15 minutes to 30s before the off with the unmatched signal set to 5 seconds. So this is the rule that was supposed to trigger but didn't, right?
Yes I have a final green up from 29 seconds before the off.
But I also have this "Cancel unmatched offset" rule from 15 minutes to 30s before the off with the unmatched signal set to 5 seconds. So this is the rule that was supposed to trigger but didn't, right?
You do not have the required permissions to view the files attached to this post.
Do you have a rule setting the actual signal for this green up to look at?
In the original set up of this rule there was a 'Set/Modify signal' rule type called 'unmatched' which was set each second there was a unmatched bet in the market and was increased the value by 1 each time, when that value reaches 5 (meaning 5 seconds have elapsed with a unmatched bet) then the green up rule your using looks at this and triggers.
In the original set up of this rule there was a 'Set/Modify signal' rule type called 'unmatched' which was set each second there was a unmatched bet in the market and was increased the value by 1 each time, when that value reaches 5 (meaning 5 seconds have elapsed with a unmatched bet) then the green up rule your using looks at this and triggers.
You do not have the required permissions to view the files attached to this post.
I attached all the rules and conditions I am using so that you can have a clear image of my system Dallas. What do you think, I am missing something somewhere?
I have 5 images and I can put only 3 attachments, so I've uploaded the images on an external website:
http://acu.ro/lay.png
http://acu.ro/reset.png
http://acu.ro/unmatched-signal.png
http://acu.ro/green-unmatched.png
http://acu.ro/final-green-up.png
I have 5 images and I can put only 3 attachments, so I've uploaded the images on an external website:
http://acu.ro/lay.png
http://acu.ro/reset.png
http://acu.ro/unmatched-signal.png
http://acu.ro/green-unmatched.png
http://acu.ro/final-green-up.png
It would be easier to view the rule in action but from briefly looking at those images i would change all the signal from being set on the 'selection' to 'market' and also change the condtions looking at the signals set from 'selection' to 'market'
The main problem may then be down to how your cycling/refreshing the markets in guardian - this thread will explain this process further and you will have a idea if this is a possible cause of your problem.
viewtopic.php?f=37&t=11491
So i would advise doing the above changes then loading just 1-2 markets into guardian and run the rule of them using the fastest 200ms refresh setting and see if that works - if not as Jimibt has said if you attach the actual rule it will be easier to spot the probelm through running it than going through all those images especially if its just one small element thats wrong.
The main problem may then be down to how your cycling/refreshing the markets in guardian - this thread will explain this process further and you will have a idea if this is a possible cause of your problem.
viewtopic.php?f=37&t=11491
So i would advise doing the above changes then loading just 1-2 markets into guardian and run the rule of them using the fastest 200ms refresh setting and see if that works - if not as Jimibt has said if you attach the actual rule it will be easier to spot the probelm through running it than going through all those images especially if its just one small element thats wrong.
I attached here the rules file, I do't know why I didn't do this from the start 
I have setup the refresh to 200ms and I control the bot from restrict refresh tab like in the image attached.
I have setup the refresh to 200ms and I control the bot from restrict refresh tab like in the image attached.
You do not have the required permissions to view the files attached to this post.
ok, had a very quick look here. i think the issue maybe due to the condition in the Cancel Unmatched offset. In that rule, you evaluate the number of unmatched increments of the signal. If it EQUALS 5, you then implement the green up. I think you may be better to change that to be GREATER than 5 as it could be that the signal value has been incrementing away in the background beforehand and has exceeded 5 by this point, thus will never fire as it has gone beyond your very precise criteria.zanpo wrote:I attached here the rules file, I do't know why I didn't do this from the start
I have setup the refresh to 200ms and I control the bot from restrict refresh tab like in the image attached.
just a thought...
Your rule worked absolutly fine in the first race two races i tried. Attached are the logs from the first race.
Top images shows the log as normal bets are placed and then cancelled after 5 seconds, there was just the one bet matched and offset - this offset was also cancelled 5secs later just as expected (bottom image)
What i have noticed from the guardian image you have just posted is that you have restricted the refresh to the final five mins (300secs) yet your rule is running during the last 15mins - you would need to change this to 900 secs
Top images shows the log as normal bets are placed and then cancelled after 5 seconds, there was just the one bet matched and offset - this offset was also cancelled 5secs later just as expected (bottom image)
What i have noticed from the guardian image you have just posted is that you have restricted the refresh to the final five mins (300secs) yet your rule is running during the last 15mins - you would need to change this to 900 secs
You do not have the required permissions to view the files attached to this post.
Yes the bot works well....but all of a sudden, at least once a day, something goes wrong. If you try to run it for example in all horse racings for the day for sure it will give out that error from my past print screen with the unmatched offset.
The 300 seconds restrict refresh was because I used it in Greyhound races and it was no use for 15 minutes. For horses I use 600 seconds (10 minutes). It was easier to modify it in the restrict refresh than from the rules of the bot, I don't think it affects the bot, no?
If I restrict refresh to 15 minutes, then some races overlap and guardian takes longer to cycle through them.
I also tried jimibt's advice and put "greater than" 5 seconds instead of "equal to" 5 seconds, in "Cancel Unmatched Offset" rule, in Greyhounds race, and still the unmatched offset doesn't get greened up. It gets greened up only by the final rule "green all selections" 29seconds before the off.
I will try your advice also and change "selection" to "market" and see what happens.
The 300 seconds restrict refresh was because I used it in Greyhound races and it was no use for 15 minutes. For horses I use 600 seconds (10 minutes). It was easier to modify it in the restrict refresh than from the rules of the bot, I don't think it affects the bot, no?
If I restrict refresh to 15 minutes, then some races overlap and guardian takes longer to cycle through them.
I also tried jimibt's advice and put "greater than" 5 seconds instead of "equal to" 5 seconds, in "Cancel Unmatched Offset" rule, in Greyhounds race, and still the unmatched offset doesn't get greened up. It gets greened up only by the final rule "green all selections" 29seconds before the off.
I will try your advice also and change "selection" to "market" and see what happens.