Author Topic: Execute  (Read 6550 times)

Tags:
  • All members
  • Posts: 829
Execute
« on: 06 Jun 2013, 10:13 »
hi,
can someone explain how to do continuous backing and greening up ?
I am a bit confused with the "Execute" condition in that it doesn't have "unlimited" as an option.
What I want to do is back and then greenup and at the same time back again and keep the process going to the end of the event. This would apply to all selections in the event.
Thanks in anticipation.
R
My grandma taught me not to run downstairs and never back odds on.

  • Administrator
  • Posts: 8821
  • Gender: Female
*
Always try your triggers in Test Mode before switching to real money!

Follow us on Twitter.

Join our WhatsApp chat!

Присоединяйтесь к официальному Telegram-каналу!

  • All members
  • Posts: 829
Re: Execute
« Reply #2 on: 06 Jun 2013, 11:40 »
Thanks Oxa, actually I am using the back and greenup one but for some reason I may have changed the "execute" setting to "once per market" I've now amended it to "once per selection" as per the original trigger you sent.
I am wondering how to set a condition in the "Back" trigger that will activate a "back" bet immediately after a "greenup" bet takes place rather than wait for the "back price leap" condition to be fulfilled.
Thanks if you can assist.
My grandma taught me not to run downstairs and never back odds on.

  • Moderator
  • Posts: 3597
*
Re: Execute
« Reply #3 on: 06 Jun 2013, 18:17 »
Hi
In that trigger there are two selection conditions that will wait until they are met:
•Its price has grown since the last refresh
•But its price has gone down over the last 12 seconds

If you delete both conditions:
and selections back price leap is greater than 0
and selections back price dif over 0.2 mins is less than 0

it will place a new back bet immediately after the greenup has been fully matched and there are no unmatched back or lay bets.
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: Execute
« Reply #4 on: 06 Jun 2013, 19:03 »
Thanks Mark, I will try that out tomorrow on the tennis.
I haven't fathomed out how the greenup works.
It says offset ticks 2 but how does it calculate what bet amount is required ?
I don't see a formula. I could work it out manually but can't
see how the trigger does that
puzzled
R
My grandma taught me not to run downstairs and never back odds on.

  • Moderator
  • Posts: 3597
*
Re: Execute
« Reply #5 on: 06 Jun 2013, 20:09 »
Hi
That’s the purpose of the green-up action – it automatically calculates everything for you according to minimum ticks profit you set and the current lay price. It's all built-in.

There are a number of different ways of greening (or dist loss), they all have the same purpose; an equal profit (or loss) across all selections. A common one used to green a back bet is (bm_backp*bm_backa)/lay_price

If you want to green-up a back bet “manually”
Action: Lay
Price: lay_price
Amount: (bm_backp*bm_backa)/lay_price
Condition:
Selection’s lay price is less than bm_backp

If you are interested in some formulae have a look here
http://community.welldonesoft.com/triggered-betting-10/formulas/
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • Moderator
  • Posts: 3597
*
Re: Execute
« Reply #6 on: 06 Jun 2013, 21:42 »
Hi again
To answer your first question on the Execute field running "unlimited":

You can execute a trigger
No more often than x seconds
means the trigger will repeat indefinitely at the frequency of x seconds

You can execute a trigger
Specific number of times x
means the trigger will repeat up to x times
so if your refresh rate is 1 second, and x = 86400, the trigger will repeat continuously for 24 hours and then stop.

In the case of the example trigger, the triggers execute once per selection, however the trigger block containing all the triggers repeats every 2 seconds indefinitely (subject to close block conditions).
In other words all individual triggers in the block execute once per selection, but the whole block repeats every 2 seconds.
 
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: Execute
« Reply #7 on: 06 Jun 2013, 21:49 »
There is no code evident that was why I raised the question.
I can only assume the greenup is hard coded.
It does work and works well !!
Thanks for the link to the formulas
R
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 829
Re: Execute
« Reply #8 on: 06 Jun 2013, 21:54 »
Hi Mark,
Thanks again, now I understand that once per selection and repeats each time block closes. I'm learning more every day :)
R
My grandma taught me not to run downstairs and never back odds on.

  • All members
  • Posts: 829
Re: Execute
« Reply #9 on: 07 Jun 2013, 21:25 »
Hi,
Looking at the auto scalping back and greenup I notice the default is set
to "cancel". Hence "repetitive scalping" is restricted to time before event starts where little movement in odds generally is the case.
I have set it to "keep" to allow for more action with regular fluctuation in odds during "in play" as in the case today between Nadal and Djokovic.
I want to confirm that closing the block is still to be set at "once per market" ?
I am puzzled why there is little repetitive betting and have shown conditions for backing below.
selections back price is between 1.01 and max_price
and selections back price is equal or greater than r_ticks(lay_price,-2)
and market's back book % is less than 105
constants
offset ticks      offset ticks for greening up    2  start with initial value
max_price       maximum back price       4.50     start with initial value
I have disabled the stop loss trigger.
Closing the block
every selection's lay unmatched is equal to 0
and every selection's unmatched back price is equal to 0
and every selection's trigger expression ABS(back_payout - lay_payout is less than 0.1
This last condition I don't quite understand.
Perhaps you could from the above identify why there seems to be little action when conditions are true.
Thanks for any help
R
My grandma taught me not to run downstairs and never back odds on.

  • Moderator
  • Posts: 3597
*
Re: Execute
« Reply #10 on: 08 Jun 2013, 08:27 »
Hi
The example trigger works well in pre-off markets where there are no gaps in the prices, and there is some movement in the prices. UK pre-off horse racing being the best type of market. (no gaps, plenty of money, decent, but not too wild price movement)

If you look at how the in-play tennis markets work, you might observe among other things:
very wide gaps in the prices between back and lay prices
a smaller gap in the prices during rest periods (and the money disappears just before play resumes)
more money volume in the market at key points in the match

The idea is to design your entry and exit points for the trigger around your observations of how the market works. For example:
a good entry point might be a missed first serve because the price will be several ticks higher than a moment ago
then green-up if the player scores the point / or distribute loss if they do not
and repeat….

The basic framework of the trigger is fine. You will need to design your own entry and exit conditions.
Remove the 2 entry conditions:
and selections back price is equal or greater than r_ticks(lay_price,-2)
and market's back book % is less than 105
and re-instate the stop-loss
and run it in test mode. You should see plenty of action from the trigger albeit losing action.
You can now start to put in your own conditions based on how you want to trade the market.

update:
I have taken the example trigger and stripped it down. It will trade the favourite in any market in-play or pre-off according to the values you set in the constants for green up or dist loss ticks. You can use this as a template and start to add your own conditions as mentioned above.
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • Moderator
  • Posts: 3597
*
Re: Execute
« Reply #11 on: 08 Jun 2013, 13:48 »
Hi
The first serve is a suggested example of an entry point for a scalp trade. In most markets including forex, commodities and a lot of sports events the idea is to buy in a dip. So here you are getting a better price than before the first serve. It is a judgement, because you still have the advantage of the server, but a reduced advantage because the first serve failed, and this is reflected in the price. I am not suggesting back the fav when odds increase, just looking for the “dip” to buy.

I would say the main reason for less liquidity in-play has to be risk. If we take tennis as an example, how would you deal with a game where you have backed the server, and the current score is 0-30 and a break of serve could be looming? The clever people have already taken their money out of the market, because this could be a critical point in the match. Now you cannot trade out for a small loss because there is no lay price available.

On the other hand, pre-off trading carries much less risk, but proportionally smaller profits, and you have to join the enormous queue of money waiting to be matched. This queue of money waiting to be matched is evidence of the lesser risk and why so many people are doing it.

There are massive amounts traded in-play on big tennis matches, but you must be able to handle the risk involved. The risk is not much different from trading football in-play, where everyone knows the direction of the market....until a goal is scored.
Please read the following disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 829
Re: Execute
« Reply #12 on: 08 Jun 2013, 14:26 »
Hi Mark,
Thanks for this well constructed and informative reply.
So in a nutshell what you are saying is to back a fav when the odds increase ?
(in reference to your poor first serve example) as basic as it sounds it has to be included as a major condition.
I agree the matched volume tends to come pre "in play" or "rest periods" that puzzles me somewhat surrounding say tennis and cricket which could be construed coming from countries where 'in play' betting is against the law such as Australia, with the exception of horse racing. But Aussies are not really into sports betting especially in the middle of the night. Hence my puzzlement why English and other European and perhaps Indian punters don't bet more 'in play'  given there is plenty of market movement albeit sometimes poorer pickings. That four lettered word WORK could have something to do with it. But weekends should not be the case as account holders should have more time to bet 'in play' but apparently don't for whatever reason. As an example sometimes there may be several million matched and halfway through the event paltry amounts of a few pounds/dollars as low as 5 are on offer for the fav. It has me stumped.
I may have to rethink my strategy and go with the flow and bet before the off in these sports events perhaps this is where the profits are made !!
Does anyone have any logical conclusions ? (re sporting events - not horse racing)
R
My grandma taught me not to run downstairs and never back odds on.

 

Please note, BetFair is seems to be currently OFFLINE