Back after Consistent IR Backing - Guardian Automation Bot

Post Reply
kunas
Posts: 20
Joined: Fri Oct 12, 2018 8:44 pm

Thanks for the reply Dallas!!
The instructions I gave where just for the back bet to be applied to ANY selection and so that it would target the fav

I don't have BA open at the moment so can't check the file, what is it your using the signals for?
If we apply the "any selection" to the back bet rule (with the condition that it's price is less than the 2nd fav) .. that's the same as changing it from row 1 to first favourite ! No ??
My problem was with the signals ..these are the ones getting messed up if we appoint a favourite, as the trigger gets confused if the favouritism change..

Basically, I am not looking for anything specific, was just playing with this one to get a feel of what was possible with signals..and got me intrigued !!:

- if we can change this sinal to look especifically for the favourite or others as well, knowing the favouritism swaps
- if it was possible to follow multiple horses
- if we it's possible to restart the signal once the back bet was made..

As I said I don't have nothing specific, just wondering if it could be used as a good indicator/condition for scalp or swing .. :idea:
User avatar
jimibt
Posts: 3641
Joined: Mon Nov 30, 2015 6:42 pm
Location: Narnia

kunas wrote:
Mon Nov 12, 2018 4:37 pm
Thanks for the reply Dallas!!
The instructions I gave where just for the back bet to be applied to ANY selection and so that it would target the fav

I don't have BA open at the moment so can't check the file, what is it your using the signals for?
If we apply the "any selection" to the back bet rule (with the condition that it's price is less than the 2nd fav) .. that's the same as changing it from row 1 to first favourite ! No ??
My problem was with the signals ..these are the ones getting messed up if we appoint a favourite, as the trigger gets confused if the favouritism change..

Basically, I am not looking for anything specific, was just playing with this one to get a feel of what was possible with signals..and got me intrigued !!:

- if we can change this sinal to look especifically for the favourite or others as well, knowing the favouritism swaps
- if it was possible to follow multiple horses
- if we it's possible to restart the signal once the back bet was made..

As I said I don't have nothing specific, just wondering if it could be used as a good indicator/condition for scalp or swing .. :idea:
this is where it would be useful to have a property in the automation criteria that could be flagged by a signal (or shared value) for the runner ID (or name). altho this wouldn't be interesting as a visual data item, it would allow you to reset signals if the id of the fave changed (e.g if faveCurrentId != faveLastId then do something) etc... one of many uses for an ID property (if it were introduced to BA) ....
kunas
Posts: 20
Joined: Fri Oct 12, 2018 8:44 pm

this is where it would be useful to have a property in the automation criteria that could be flagged by a signal (or shared value) for the runner ID (or name). altho this wouldn't be interesting as a visual data item, it would allow you to reset signals if the id of the fave changed (e.g if faveCurrentId != faveLastId then do something) etc... one of many uses for an ID property (if it were introduced to BA) ....
Not sure if I'm following .. :lol:
what do you mean by runners ID ? why would it change..
But if you need to nominate runners, by name..that already exist, I think.. (kind of noob with this BA thing)
User avatar
jimibt
Posts: 3641
Joined: Mon Nov 30, 2015 6:42 pm
Location: Narnia

kunas wrote:
Mon Nov 12, 2018 8:41 pm
this is where it would be useful to have a property in the automation criteria that could be flagged by a signal (or shared value) for the runner ID (or name). altho this wouldn't be interesting as a visual data item, it would allow you to reset signals if the id of the fave changed (e.g if faveCurrentId != faveLastId then do something) etc... one of many uses for an ID property (if it were introduced to BA) ....
Not sure if I'm following .. :lol:
what do you mean by runners ID ? why would it change..
But if you need to nominate runners, by name..that already exist, I think.. (kind of noob with this BA thing)
in this instance, i'm referring to free running automation (where selections are picked by the rules). in the case of automation rules, it is not possible to (yet) flag a runner that is currently the favourite and then follow it if it becomes 2nd fave and then goes back to fave. well actually, you can (you could flag the 1st runner to become fave and then only perform actions when it returns to being fave). my proposal was that the Stored values could have an additional property made available (runner id or runner name etc) to allow you to track runners, no matter how much their position jostled around.

i freely admit that unless you are inside my head, you may not have a clue what or why i'm referring to this :D
Jukebox
Posts: 1576
Joined: Thu Sep 06, 2012 8:07 pm

jimibt - If it helps, be aware that you can fix the order of runners by favoritism at a given moment - and if you wish you can fix the new order if certain conditions are met. Additionally, although you cannot store the name of the runner that fulfills some initial requirement - you can effectively give it your own name by storing a value of your choosing on that runner.
kunas
Posts: 20
Joined: Fri Oct 12, 2018 8:44 pm

Got it jimibt,
thats an interesting thought.. automatic selection of runners ..
in this instance, i'm referring to free running automation (where selections are picked by the rules). in the case of automation rules, it is not possible to (yet) flag a runner that is currently the favourite and then follow it if it becomes 2nd fave and then goes back to fave. well actually, you can (you could flag the 1st runner to become fave and then only perform actions when it returns to being fave). my proposal was that the Stored values could have an additional property made available (runner id or runner name etc) to allow you to track runners, no matter how much their position jostled around.

i freely admit that unless you are inside my head, you may not have a clue what or why i'm referring to this :D
Now, The file I posted Sunday night .. i was testing it today with the late day races
actually the signals as I wrote work fine, set to check any runners but only increase signal on Fav and bet on Fav (although slighly slow :P)
I have however 1 doubt, here is the log .. (I changes a couple things on this test but it shoudnt interferer, it was: LTP instead of Last Lay price when reading.. and the Back firing at 5 ticks below best rev market price). SO, my doubt is with a 3rd bet on this log ?? why it happend, if the signal was clear and the runner only had signal =1

14/11/2018 18:01:01: Guardian has detected that the market is suspended
14/11/2018 18:01:02: Guardian has detected that the market is in-play
14/11/2018 18:01:03: Guardian has detected that the market is now unsuspended
14/11/2018 18:01:06: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:11: [G_Auto] : Automation Signal for Designated: shortening = 1
14/11/2018 18:01:13: [G_Auto] : Automation Signal for Designated: shortening - Cleared
14/11/2018 18:01:22: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:23: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:25: [G_Auto] : Automation Signal for Sonja Henie: shortening = 2
14/11/2018 18:01:27: [G_Auto] : Automation Signal for Sonja Henie: shortening = 3
14/11/2018 18:01:28: [G_Auto] : € 10.00 Back bet placed on Sonja Henie at 3.7. Entirely unmatched when it initially reached the market. Ref: 10018 ( Fill or kill bet with 5 seconds delay. Offsetting by 3 ticks with greening. )
14/11/2018 18:01:30: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:31: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:33: [G_Auto] : Automation Signal for Sonja Henie: shortening = 2
14/11/2018 18:01:33: [G_Auto] : € 10 unmatched bet (Ref:10018) was killed.
14/11/2018 18:01:35: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:37: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:39: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:44: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:46: [G_Auto] : Automation Signal for Sonja Henie: shortening = 2
14/11/2018 18:01:48: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:49: [G_Auto] : Automation Signal for Designated: shortening = 1
14/11/2018 18:01:50: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:51: [G_Auto] : Automation Signal for Designated: shortening - Cleared
14/11/2018 18:01:52: [G_Auto] : Automation Signal for Designated: shortening = 1
14/11/2018 18:01:53: [G_Auto] : Automation Signal for Sonja Henie: shortening = 2
14/11/2018 18:01:54: [G_Auto] : Automation Signal for Designated: shortening - Cleared
14/11/2018 18:01:55: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:55: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:01:57: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:01:58: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:02:00: [G_Auto] : Automation Signal for Sonja Henie: shortening = 2
14/11/2018 18:02:02: [G_Auto] : Automation Signal for Sonja Henie: shortening = 3
14/11/2018 18:02:03: [G_Auto] : € 10.00 Back bet placed on Sonja Henie at 1.65. Entirely unmatched when it initially reached the market. Ref: 10019 ( Fill or kill bet with 5 seconds delay. Offsetting by 3 ticks with greening. )
14/11/2018 18:02:06: [G_Auto] : Automation Signal for Sonja Henie: shortening - Cleared
14/11/2018 18:02:07: [G_Auto] : Automation Signal for Sonja Henie: shortening = 1
14/11/2018 18:02:07: [G_Auto] : € 10.00 Back bet placed on Sonja Henie at 1.49. Entirely unmatched when it initially reached the market. Ref: 10020 ( Fill or kill bet with 5 seconds delay. Offsetting by 3 ticks with greening. )
14/11/2018 18:02:08: [G_Auto] : € 10 unmatched bet (Ref:10019) was killed.
14/11/2018 18:02:09: [G_Auto] : Automation Signal for Sonja Henie: shortening = 2
14/11/2018 18:02:12: [G_Auto] : € 10 unmatched bet (Ref:10020) was killed.
14/11/2018 18:02:28: Guardian has detected that the market is suspended
Post Reply

Return to “Bet Angel Automation - Horse racing - In-running”