New beta version of Bet Angel v1.44.0

Post Reply
Bet Angel
Bet Angel
Bet Angel
Posts: 3514
Joined: Tue Apr 14, 2009 3:47 pm

Tue May 17, 2016 11:30 am

A new version of Bet Angel is available: -

Download it from here: -

http://www.betangel.com/securedownloads ... _beta1.exe

The main feature of this version is the introduction of Automation Signals giving automation a huge amount of new flexibility and control. It opens the door to many new possibilities.

In its simplest form, a signal allows one Automation rule to control the behavior of another. E.g. Only green up if the Place Bet rule has triggered three times, or only place a bet on the Away team if a bet hasn’t already been placed on the Home team.
Working together, a group of signals can produce a complex set of betting logic that was previously only possible using Excel macros.

Also in this build is a new action for the Keyboard Shortcut editor - to allow the selection of a specific preset stake on the Ladder screen. This was requested during the last beta and completes the set of staking keystrokes available in the editor.

More about Signals

A signal is a named value that can be applied to a selection or the market as a whole. See the new Signals tab in the Automation Rules Editor. Each rule can, optionally, set/clear/modify one signal for a selection and one for the market. You can create as many named signals as you wish in the rules file and use any number of them in the Automation Conditions section to control the activation of other rules.

Signals are initialised with the integer value of your choosing and if required can be increased & decreased on each trigger. In this way it is very easy to create trigger counters for a rule (or for multiple rules working together).

You can attach a signal to an existing Rule Type (so that they are set when Place back bet, Place lay bet, Cancel unmatched bets, or Green all selections etc are triggered).
Alternatively you can create a rule specifically to manipulate a signal (using the Set / Modify a Signal Only rule type) when your specific automation conditions are met.

New Automation conditions have been added to specifically test for the presence or absence of a named Signal and to test if a signal value is equal, greater or less than your specified amount. You can even test when a signal value changed.

Example: if you have a back bet rule that triggers once its conditions are met, you can now also choose to set a named signal when it triggers (for this example we’ll call it "BACKED")

You also have a lay bet rule that triggers when its own conditions are met, but now one of these conditions can be a ‘Signal Set Condition’ defined to look for the presence of the "BACKED" signal - this will mean that in addition to its other conditions the lay bet can only trigger after the back bet has been triggered and the “BACKED” signal has been set.
In other words, signalling has allowed you to control that the lay bet can only trigger AFTER the back bet has been placed.


Here are some of the things that you will be able to do using Signals:

- Control the order that rules are triggered into the market.

- Delay the placements of bets once conditions are met (including tennis scorelines).

- Ensure a selection has traded above or below X odds for a period of time before triggering a rule.

- Check that the number of ticks between one selection and another remains over or under X amount of ticks and/or for a period of time.

- Close a position based on the time the position was opened rather than at a fixed point in time.

- Only close a position if a profit or loss amount has been exceeded for more than X seconds.

- Cancel unmatched offset bets after X seconds.

- Trigger bets based on the value of matched or unmatched bets in the markets.

- Check that one or more selection has traded above or below X odds and/or within a period of time.

- Create two mutually exclusive sets of rules in the same rule file (the first rule to trigger sets a signal that prevents the other set of rules from ever triggering).

- Prevent bets being triggered in certain situations that other automation conditions cannot manage.

User avatar
boardrep
Posts: 73
Joined: Fri Nov 27, 2015 4:52 pm

Tue May 17, 2016 11:38 am

wow
sounds very useful and impressive ..
well done and thank you for the continual improvement and development of the product

User avatar
LeTiss
Posts: 3930
Joined: Fri May 08, 2009 6:04 pm

Tue May 17, 2016 11:40 am

Tremendous stuff mate

Before long, you'll have to offer courses purely to explore BA automation, as that alone will take a day of extensive brain aching!

icarus121
Posts: 259
Joined: Mon Nov 16, 2009 10:07 pm

Tue May 17, 2016 11:51 am

Bet Angel smashes it out the park again.Proper!
Good work gents.

DavDvo
Posts: 73
Joined: Tue Nov 19, 2013 2:55 pm

Tue May 17, 2016 12:11 pm

Technical question -
if
rule 1 is - Place Back bet and set the signal "A"
rule 2 is - Place Lay bet if signal "A" is set

will the rule 2 execute in the same refresh cycle as rule 1 places Back bet or next refresh cycle?

User avatar
jimibt
Posts: 874
Joined: Mon Nov 30, 2015 6:42 pm

Tue May 17, 2016 12:27 pm

this all sounds really great, in particular, THREE big issues for me are covered by this addition:
- Check that the number of ticks between one selection and another remains over or under X amount of ticks and/or for a period of time.

- Only close a position if a profit or loss amount has been exceeded for more than X seconds.

- Cancel unmatched offset bets after X seconds.
keep up the great work -might even use the remaining time between now and 13:50 to implement some of the above -lol

Bet Angel
Bet Angel
Bet Angel
Posts: 3514
Joined: Tue Apr 14, 2009 3:47 pm

Tue May 17, 2016 1:29 pm

DavDvo wrote:Technical question -
if
rule 1 is - Place Back bet and set the signal "A"
rule 2 is - Place Lay bet if signal "A" is set

will the rule 2 execute in the same refresh cycle as rule 1 places Back bet or next refresh cycle?
Rules are processed in order from first to last (and then only if their start & end time are appropriate). So yes, if rule 2 was based on a signal from rule 1 being set, it would occur in the same cycle. If you wanted a one cycle delay, then you'd swap the order so that rule 2 was tested first (when the signal hadn't yet been set). And if, for instance, you wanted a two second delay, you'd use the time based 'signal change' condition as the trigger for rule 2.

ricardodeano
Posts: 136
Joined: Tue Oct 06, 2015 2:03 pm

Tue May 17, 2016 3:47 pm

I'm eagerly awaiting Dallas signal examples :D

User avatar
Dallas
Posts: 6337
Joined: Sun Aug 09, 2015 10:57 pm

Tue May 17, 2016 4:04 pm

ricardodeano wrote:I'm eagerly awaiting Dallas signal examples :D
Ill be posting some info detailing each section shortly and will be following that up with some actual examples.

ricardodeano
Posts: 136
Joined: Tue Oct 06, 2015 2:03 pm

Tue May 17, 2016 4:27 pm

Dallas wrote:
ricardodeano wrote:I'm eagerly awaiting Dallas signal examples :D
Ill be posting some info detailing each section shortly and will be following that up with some actual examples.
Legend. Many, many thanks.

Post Reply
  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest