GUardian Automation - Suggestion
Sorry I missed this..my apologiesBet Angel wrote:Just to clarify with PeterLe and the +1s on this thread:
The P&L in Excel (cells C9, C11 etc) is the current P&L of the market based on all bets currently matched. So if you place a £10 bet on runner 1 and it matches at 3.0, then C9 would be +£20 and every other runner would be -£10
So you're all after an Automation Condition that tests the current displayed P&L value for that selection.... understanding that it'll be impacted by other matched bets on other selections?
As long as everyone can agree that that is what is required and that the P&L values don't need to somehow be isolated from other bets on other selections, then it's shouldn't be too hard to implement in a future build.
Also if anyone else wants to +1 the suggestion then please comment as it'll up the priority.
BA wrote : So you're all after an Automation Condition that tests the current displayed P&L value for that selection.... understanding that it'll be impacted by other matched bets on other selections?
PL: Yes that's correct.
Some examples, You could then use this value to trigger another bet. (ill just refer to the value as C9 for illustration purposes)
EG IF C9>200, then lay at 1 tick above best reverse price, IF current back odss are less than 8...
Perhaps you could also determine the stake from the C9 condition. Ie lay stake is 10% of the C9 value (or even better of you could calculate the lay stake as the C9 value divided by current back odds?
When I was using excel a lot, I referenced this cell many times. I just think it will help others too
Happy to have a chat/email off line with the BA guys if that would help?
Thanks for considering
Regards
Peter
-
- Posts: 28
- Joined: Sat Nov 05, 2016 7:51 pm
+1 for everything PeterLe's just said please!! C9 / current reverse odds = lots of happy bunnies!!
Not sure if this is possible already in Guardian and Ive missed it...
It would be worthwhile having a condition that checks how many bets have been placed in the last hour to prevent charges, especially now we have streaming data..
I cant remember when I last incurred charges but if you have a few instances running and a loose criteria for placement, the number of bets could rack up together with eth charges..
It would be worthwhile having a condition that checks how many bets have been placed in the last hour to prevent charges, especially now we have streaming data..
I cant remember when I last incurred charges but if you have a few instances running and a loose criteria for placement, the number of bets could rack up together with eth charges..
You do not have the required permissions to view the files attached to this post.
Last edited by PeterLe on Sun Jan 15, 2017 12:03 pm, edited 1 time in total.
+1PeterLe wrote:Not sure if this is possible already in Guardian and Ive missed it...
It would be worthwhile having a condition that checks how many bets have been placed in the last hour to prevent charges, especially now we have streaming data..
I cant remember when I last incurred charges but if you have a few instances running and a loose criteria for placement, the number of bets could rack up together with eth charges..
Has this been added I may have missed it? If not +1PeterLe wrote: ↑Thu Feb 25, 2016 9:01 pmFor future developments could the BA team consider the following please:-
Would it be possible to include a condition that looks at the current P&L on that selection? (ie the same as cell c9, c11 etc in Excel?)
This is different than the close trade condition.
Take the following senario:
EG, You may have a strategy that places a lot of lay bets into the market (at say 1.9) iterations 100 times..0.5 rearm etc..and a condition that stops the bets being placed if the close trade condition <-10
Now if the selection stays around the 1.9 mark (or above it) it could place 100 lay bets into the market at 1.9 but the Close Trade condition wont be breached until the price falls to say 1.7, by which time it could be too late as you liability will get bigger as the price drops (and never come back if its the winner)
If we had a condition that looks at the P&L of the selection, we could simply say stop placing bets if the value is <-20 for example and in my opinion it would alow for greater control.
I can get around this at present as a workaround, but Id really like to step up the number of iterations ten fold or more what Im doing at present
Hope that make sense? and hopefully this should be easy to code?
Thanks for considering
regards
Peter
Thanks