Vitality Blast 2019
-
- Posts: 1075
- Joined: Fri Nov 20, 2015 9:38 am
How the %SP cricket lay bot ended tonight... Interesting test given rain & delays...
You do not have the required permissions to view the files attached to this post.
I wish I had applied it to the CMM as well.
(Just for clarification, the Leic red was No game), as were
most of them.
Today’s game at Chesterfield is in a local park. Drainage is
v average, any rain will probably kill it.
Hope to see some of the Kent game tonite.
(Just for clarification, the Leic red was No game), as were
most of them.
Today’s game at Chesterfield is in a local park. Drainage is
v average, any rain will probably kill it.
Hope to see some of the Kent game tonite.
Last edited by megarain on Sat Jul 20, 2019 8:31 am, edited 1 time in total.
Maybe try lay CMM at 1.35, looking for 5 tick green.
Only send lay, if LTP was between 1.30 and 1.6.
Maybe look for 2 loops
Only send lay, if LTP was between 1.30 and 1.6.
Maybe look for 2 loops
-
- Posts: 1075
- Joined: Fri Nov 20, 2015 9:38 am
Yes, mostly no result games but was keen to see what happened with bot / markets in the event of a delay...megarain wrote: ↑Sat Jul 20, 2019 7:49 amI wish I had applied it to the CMM as well.
(Just for clarification, the Leic red was No game), as were
most of them.
Today’s game at Chesterfield is in a local park. Drainage is
v average, any rain will probably kill it.
Hope to see some of the Kent game tonite.
The timers kick off when market goes in play and so if no play the bot strategy (in terms if timing & in the case of the surrey game limited overs) is way out of sync. Still thinking about whether need to cater for this.
The Yorkshire market was interesting in that the bot had completed 3 trades before the game was called off. If it had gone ahead we would have already have completed the strategy before the game actually started!
Do you think it would be worth while recording the lowest (or highest) traded price a few mins before the start rather than just the LTP?
-
- Posts: 1075
- Joined: Fri Nov 20, 2015 9:38 am
Tried running the Lay %of LTP version on the live markets today and ended up:
Derby £1.44
Kent £2.46
Had a problem with two lay bets firing at once on the second lay so closed the Kent position early, just before a wicket fell - result!
I'll post a copy of the baf file when I get the multiple lay position sorted - thought I did this yesterday on test so not sure what happened there...
Log for the Kent game follows in case you are interested:
20/07/2019 18:59:31: [G_Auto] : Store Value for Somerset: FavSP = 1.75
20/07/2019 18:59:31: [G_Auto] : Store Value for Somerset: FavSPAdj = 1.75 * 92% = 1.61
20/07/2019 18:59:58: Guardian has detected that the market is in-play
20/07/2019 18:59:58: Guardian has detected that the market is suspended
20/07/2019 19:00:00: Guardian has detected that the market is now unsuspended
20/07/2019 19:00:58: [G_Auto] : Store Value for Somerset: LayEntry = 1.49
20/07/2019 19:01:03: [G_Auto] : £ 10.00 Lay bet placed on Somerset at 1.61. Fully matched at 1.5. Ref: 171763014530 ( Fill or kill bet with 3600 seconds delay. Offsetting by 25 ticks with greening. )
20/07/2019 19:01:08: [G_Auto] : £ 8.57 Back bet placed on Somerset at 1.75. Entirely unmatched when it initially reached the market. Ref: 171763027825
20/07/2019 19:01:10: [G_Auto] : Modify bet persistence 171763027825 from 'Cancel' to 'Keep'
20/07/2019 19:24:17: [G_Auto] : Store Value for Somerset: LayEntry = 1.71
20/07/2019 19:24:22: [G_Auto] : £ 10.00 Lay bet placed on Somerset at 1.61. Entirely unmatched when it initially reached the market. Ref: 171767581435 ( Fill or kill bet with 3600 seconds delay. Offsetting by 25 ticks with greening. )
20/07/2019 19:24:32: [G_Auto] : Modify bet persistence 171767581435 from 'Cancel' to 'Keep'
20/07/2019 20:03:23: [G_Auto] : Store Value for Somerset: LayEntry = 1.59
20/07/2019 20:03:23: [G_Auto] : £ 10 of unmatched bet (Ref:171767581435) was filled before remainder was killed.
20/07/2019 20:03:28: [G_Auto] : £ 10.00 Lay bet placed on Somerset at 1.61. Fully matched at 1.56. Ref: 171774280189 ( Fill or kill bet with 3600 seconds delay. Offsetting by 25 ticks with greening. )
20/07/2019 20:03:28: [G_Auto] : £ 8.66 Back bet placed on Somerset at 1.86. Entirely unmatched when it initially reached the market. Ref: 171774280990
20/07/2019 20:03:30: [G_Auto] : Modify bet persistence 171774280990 from 'Cancel' to 'Keep'
20/07/2019 20:03:33: [G_Auto] : £ 8.62 Back bet placed on Somerset at 1.81. Entirely unmatched when it initially reached the market. Ref: 171774290882
Derby £1.44
Kent £2.46
Had a problem with two lay bets firing at once on the second lay so closed the Kent position early, just before a wicket fell - result!
I'll post a copy of the baf file when I get the multiple lay position sorted - thought I did this yesterday on test so not sure what happened there...
Log for the Kent game follows in case you are interested:
20/07/2019 18:59:31: [G_Auto] : Store Value for Somerset: FavSP = 1.75
20/07/2019 18:59:31: [G_Auto] : Store Value for Somerset: FavSPAdj = 1.75 * 92% = 1.61
20/07/2019 18:59:58: Guardian has detected that the market is in-play
20/07/2019 18:59:58: Guardian has detected that the market is suspended
20/07/2019 19:00:00: Guardian has detected that the market is now unsuspended
20/07/2019 19:00:58: [G_Auto] : Store Value for Somerset: LayEntry = 1.49
20/07/2019 19:01:03: [G_Auto] : £ 10.00 Lay bet placed on Somerset at 1.61. Fully matched at 1.5. Ref: 171763014530 ( Fill or kill bet with 3600 seconds delay. Offsetting by 25 ticks with greening. )
20/07/2019 19:01:08: [G_Auto] : £ 8.57 Back bet placed on Somerset at 1.75. Entirely unmatched when it initially reached the market. Ref: 171763027825
20/07/2019 19:01:10: [G_Auto] : Modify bet persistence 171763027825 from 'Cancel' to 'Keep'
20/07/2019 19:24:17: [G_Auto] : Store Value for Somerset: LayEntry = 1.71
20/07/2019 19:24:22: [G_Auto] : £ 10.00 Lay bet placed on Somerset at 1.61. Entirely unmatched when it initially reached the market. Ref: 171767581435 ( Fill or kill bet with 3600 seconds delay. Offsetting by 25 ticks with greening. )
20/07/2019 19:24:32: [G_Auto] : Modify bet persistence 171767581435 from 'Cancel' to 'Keep'
20/07/2019 20:03:23: [G_Auto] : Store Value for Somerset: LayEntry = 1.59
20/07/2019 20:03:23: [G_Auto] : £ 10 of unmatched bet (Ref:171767581435) was filled before remainder was killed.
20/07/2019 20:03:28: [G_Auto] : £ 10.00 Lay bet placed on Somerset at 1.61. Fully matched at 1.56. Ref: 171774280189 ( Fill or kill bet with 3600 seconds delay. Offsetting by 25 ticks with greening. )
20/07/2019 20:03:28: [G_Auto] : £ 8.66 Back bet placed on Somerset at 1.86. Entirely unmatched when it initially reached the market. Ref: 171774280990
20/07/2019 20:03:30: [G_Auto] : Modify bet persistence 171774280990 from 'Cancel' to 'Keep'
20/07/2019 20:03:33: [G_Auto] : £ 8.62 Back bet placed on Somerset at 1.81. Entirely unmatched when it initially reached the market. Ref: 171774290882
Hi,
Here are the logs from the 2 games.
Nothing fired in the Derby game, as SP was below the fixed value of 1.65.
Kent seems to have been pretty volatile .. would easily have got a few loops.
Here are the logs from the 2 games.
Nothing fired in the Derby game, as SP was below the fixed value of 1.65.
Kent seems to have been pretty volatile .. would easily have got a few loops.
You do not have the required permissions to view the files attached to this post.
The timers kick off when market goes in play and so if no play the bot strategy (in terms if timing & in the case of the surrey game limited overs) is way out of sync. Still thinking about whether need to cater for this.
The Yorkshire market was interesting in that the bot had completed 3 trades before the game was called off. If it had gone ahead we would have already have completed the strategy before the game actually started!
Do you think it would be worth while recording the lowest (or highest) traded price a few mins before the start rather than just the LTP?
I wouldnt worry too much about weather delaying an inplay strategy. A user could always re-set etc, if he was watching and wanted to.
In-play match markets which are rain-affected, do tend to trade a bit weirdly.
It cant hurt recording the high and low LTP before the start - and maybe adding a rule, that the Bot only fires if the gap pre-game is maybe no
more than 3 ticks. It also cant hurt to add a condition that Volume traded must be over 50k, pre game.
Here is the CMM baf I created.
Not tested anywhere yet, so anything might happen.
There are no Blast Tv games today. Be interesting to see the liquidity, with the golf on.
Not tested anywhere yet, so anything might happen.
There are no Blast Tv games today. Be interesting to see the liquidity, with the golf on.
You do not have the required permissions to view the files attached to this post.
The auto strat on the Hamps game won 2 loops.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 69
- Joined: Mon Jul 15, 2019 3:49 pm
-
- Posts: 1075
- Joined: Fri Nov 20, 2015 9:38 am
Interesting, mine only looped once (using 92% of LTP)...
Your LayEntry value is also quite different (v low) maybe entering market before fully formed? EDIT: I'll add a Back Entry stored value when the lay bets are made so can see if there is a significant difference between back & lay prices at that point..
Off up north this week so can't contribute much. Will look out for updates )
Attached the version I used today (in test).... Seemed to work fine...
Your LayEntry value is also quite different (v low) maybe entering market before fully formed? EDIT: I'll add a Back Entry stored value when the lay bets are made so can see if there is a significant difference between back & lay prices at that point..
Off up north this week so can't contribute much. Will look out for updates )
Attached the version I used today (in test).... Seemed to work fine...
You do not have the required permissions to view the files attached to this post.