How to see if a bet went in-play
-
- Posts: 113
- Joined: Sat May 21, 2016 1:43 pm
Hello again. It's nice to see you making progress in your journey and I'm sure we all wish you well. It would be even nicer if in your threads you gave something back by telling us how you're doing, what you're learning etc.
Anyway, this is easy. When the market goes in play, set a signal called HELLO (or whatever name you like) to the value 1 (or any other value) and get it output in the log. That will tell you the exact time when the market went in play.
If you don't know about signals then google for and download v1.44 of BA.
Actually, come to think of it, the log already tells you when the market goes in play so you don't even need your own signal.
Anyway, this is easy. When the market goes in play, set a signal called HELLO (or whatever name you like) to the value 1 (or any other value) and get it output in the log. That will tell you the exact time when the market went in play.
If you don't know about signals then google for and download v1.44 of BA.
Actually, come to think of it, the log already tells you when the market goes in play so you don't even need your own signal.
Thanks Shaky, but although I can see when the race went off, I can't see if my lay bet was matched pre race, or in play because the log only tells me when the lay was placed
e.g.
16/07/2016 16:06:56: Market changed to Newb 16th Jul - 16:10 5f Stks
16/07/2016 16:08:44: [G_Auto] : £ 2.00 Back bet placed on Clem Fandango at 6. Entirely unmatched when it initially reached the market. Ref: 71222263426 ( Fill or kill bet with 60 seconds delay. Offsetting by 1 ticks with greening. )
16/07/2016 16:08:45: [G_Auto] : £ 2 of unmatched bet (Ref:71222263426) was filled before remainder was killed.
16/07/2016 16:08:45: [G_Auto] : £ 2.03 Lay bet placed on Clem Fandango at 5.9. Entirely unmatched when it initially reached the market. Ref: 71222266481
16/07/2016 16:12:11: Market has been suspended
16/07/2016 16:12:11: Market is in-play
16/07/2016 16:12:11: Market has been unsuspended
16/07/2016 16:13:11: Market has been suspended
I do have another rule that modifies the bet persistence 15 seconds before the off, to "Keep", and can see that was applied on a couple of races, but even then that still doesn't tell me if it was matched before the off, or matched in-play because there'll usually be another minute (on average) before it does actually go in-play.
I left the automation running all alone while out yesterday, so was interested later that evening to see what had actually happened, in detail. Interestingly, my automation ran from the first race at 13.50 at Cartmel right through until the 17:20 at Ripon uninterrupted, yet the only log dated 16th July only has detail from the 15:35 to the 17:20
Fair comment about giving back. All I'm mostly doing is following Peters videos for basic ideas (pre race manual scalping etc) and automation suggestions, I then set up my automation files from scratch (I find this helps my learning rather than downloading a file), and look to see how I might be able to tweak the rules, parameters, and conditions to suit my own experiments. Automation in general is something I've been involved in for many years and I love it. Whether that be at work, or at home.
Right now however, best I can give back is to re-iterate others comments about running any automation extensively in practice mode. And once you've done that, do it some more ! Yes it can be tedious, but fortunately I have a ton of patience and discipline to do this. Yesterday was the first time I ran anything in real mode for any length of time unattended, and felt confident I had things set up correctly. Even then it was for tiny stakes despite being fortunate to have a bankroll that could support jumping in with bet amounts that are larger. My "real 9-5 job" involves a ton of software testing and quality assurance, so this kind of scenario suits me well.
e.g.
16/07/2016 16:06:56: Market changed to Newb 16th Jul - 16:10 5f Stks
16/07/2016 16:08:44: [G_Auto] : £ 2.00 Back bet placed on Clem Fandango at 6. Entirely unmatched when it initially reached the market. Ref: 71222263426 ( Fill or kill bet with 60 seconds delay. Offsetting by 1 ticks with greening. )
16/07/2016 16:08:45: [G_Auto] : £ 2 of unmatched bet (Ref:71222263426) was filled before remainder was killed.
16/07/2016 16:08:45: [G_Auto] : £ 2.03 Lay bet placed on Clem Fandango at 5.9. Entirely unmatched when it initially reached the market. Ref: 71222266481
16/07/2016 16:12:11: Market has been suspended
16/07/2016 16:12:11: Market is in-play
16/07/2016 16:12:11: Market has been unsuspended
16/07/2016 16:13:11: Market has been suspended
I do have another rule that modifies the bet persistence 15 seconds before the off, to "Keep", and can see that was applied on a couple of races, but even then that still doesn't tell me if it was matched before the off, or matched in-play because there'll usually be another minute (on average) before it does actually go in-play.
I left the automation running all alone while out yesterday, so was interested later that evening to see what had actually happened, in detail. Interestingly, my automation ran from the first race at 13.50 at Cartmel right through until the 17:20 at Ripon uninterrupted, yet the only log dated 16th July only has detail from the 15:35 to the 17:20
Fair comment about giving back. All I'm mostly doing is following Peters videos for basic ideas (pre race manual scalping etc) and automation suggestions, I then set up my automation files from scratch (I find this helps my learning rather than downloading a file), and look to see how I might be able to tweak the rules, parameters, and conditions to suit my own experiments. Automation in general is something I've been involved in for many years and I love it. Whether that be at work, or at home.
Right now however, best I can give back is to re-iterate others comments about running any automation extensively in practice mode. And once you've done that, do it some more ! Yes it can be tedious, but fortunately I have a ton of patience and discipline to do this. Yesterday was the first time I ran anything in real mode for any length of time unattended, and felt confident I had things set up correctly. Even then it was for tiny stakes despite being fortunate to have a bankroll that could support jumping in with bet amounts that are larger. My "real 9-5 job" involves a ton of software testing and quality assurance, so this kind of scenario suits me well.
-
- Posts: 113
- Joined: Sat May 21, 2016 1:43 pm
Ah, sorry, I forgot that the log only tells you when the bet was placed. So ignore my idea.
A better idea is to add a rule that checks how many unmatched bets you have at any time. As soon as the number falls to 0, output a message in the log. That will allow you to infer when your bet got matched to an accuracy of less than a second.
I see we joined this place within a day of each other. I too prefer to write my own Guardian rules, as I learn more that way than by just copying Dallas' examples, though they do give me ideas. Nothing profitable so far but we all live in hope...
A better idea is to add a rule that checks how many unmatched bets you have at any time. As soon as the number falls to 0, output a message in the log. That will allow you to infer when your bet got matched to an accuracy of less than a second.
I see we joined this place within a day of each other. I too prefer to write my own Guardian rules, as I learn more that way than by just copying Dallas' examples, though they do give me ideas. Nothing profitable so far but we all live in hope...
- Dublin_Flyer
- Posts: 847
- Joined: Sat Feb 11, 2012 10:39 am
From the Guardian screen the log tab at the bottom will tell you what time the event went in play, the matched bets tab should show the time the bets were matched so you can see if they are pre-off or in-play by the matched time vs in-play time.
Leaving the Average odds unticked will show partial matches so you can see if you were fully matched pre-off or part pre-off and part in-play
Leaving the Average odds unticked will show partial matches so you can see if you were fully matched pre-off or part pre-off and part in-play