I have 1.62 installed and I have noticed that in a Tennis automation that a back condition is not being observed.
The back condition looks like this
Backing should happen at specific intervals according to the criteria. One of them is greened1 = 0. This value is the initial value when the BAF starts. I then set it to 1 after the green rule condition is met.
The problem is the value of "greened1" (Market) is definitely set to 1 after initially greening - I even display its value in my grid. Therefore the back condition should never fire thereafter, but it does.
I have double, triple checked this.
The SV is being set on the green rule - its a shared value - see the log below - where the back bet is placed after greened1 is set to 1
I have restarted the machine
Has anyone else noticed this? Ideas
Occasionally the rule is observed correctly and I will get through a match where another bet isn't placed.
I guess the next stage is to go back to the previous version of BA - see if something has broken.
Back condition not being observed
-
jamesedwards
- Posts: 4366
- Joined: Wed Nov 21, 2018 6:16 pm
It will definitely be human error. If there were software errors like this the forum would be full of similar issues. Try marking every stage of the rule will notes in the log so you can track at what point it breaks down.
-
jamesedwards
- Posts: 4366
- Joined: Wed Nov 21, 2018 6:16 pm
Or, post your rulefile and someone will probably be able to seek out the issue.
You wont see it change in the log if the 'Note value assignments option is not ticked' on the rule clearing it
On more than one occasion I've copied a rule for its rule type conditions etc, made minor edits etc - but forgot it was also originally clearing a signal or stored value each time it triggers
Thanks Dallas. I would agree with you and I have fallen for the same mistakes in the past but in this case I am setting the note to log and don't see it being reset. On the face of it the BAF is very straightforward.
Without giving away my strategy, I have paired it down to a simpler BAF but there isn't a lot of in play matches right now so I hope tomorrow I can see it happening with that.
Without giving away my strategy, I have paired it down to a simpler BAF but there isn't a lot of in play matches right now so I hope tomorrow I can see it happening with that.
Is that SV "greened1" is set to 1 when greening is done? Cause in the log it's = 1 before Greening rule to be triggered or there are more than one greenings up in the log which couldn't be seen on the screenshot.sibur wrote: ↑Sat Oct 12, 2024 3:27 pmI have 1.62 installed and I have noticed that in a Tennis automation that a back condition is not being observed.
The back condition looks like this
Screenshot 2024-10-12 144247.jpg
Backing should happen at specific intervals according to the criteria. One of them is greened1 = 0. This value is the initial value when the BAF starts. I then set it to 1 after the green rule condition is met.
The problem is the value of "greened1" (Market) is definitely set to 1 after initially greening - I even display its value in my grid. Therefore the back condition should never fire thereafter, but it does.
I have double, triple checked this.
The SV is being set on the green rule - its a shared value - see the log below - where the back bet is placed after greened1 is set to 1
Screenshot 2024-10-12 152442.jpg
I have restarted the machine
Has anyone else noticed this? Ideas
Occasionally the rule is observed correctly and I will get through a match where another bet isn't placed.
I guess the next stage is to go back to the previous version of BA - see if something has broken.
"The greening rule keeps on triggering because the condition for the greening rule is set to trigger when the Stored Value (SV) equals 0. However, the SV is given a value of 1 when the greening rule is triggered. This creates a loop where the greening rule is continuously triggered because the condition is met (SV=0), and then the SV is set to 1, resetting the condition. To stop the greening rule from continuously triggering, you would need to adjust the condition or the value given to the SV when the greening rule is triggered."
"The greening rule keeps on triggering because it is not checking the updated Stored Value (SV) after it has been set to 1. The rule is set to trigger when SV=0, and it does so correctly the first time. However, after the first trigger, the SV is updated to 1. If the rule is not re-evaluated after this update, it will keep triggering because it is still operating under the condition that SV=0.
To prevent the rule from continuously triggering, you need to ensure that the rule checks the updated SV after each trigger. If it checks and sees that SV=1, it should not trigger again. This could be a matter of how the rule is programmed or the order of operations in your system.
In the context of the Bet Angel user guide, rules are set to trigger under certain conditions. Once those conditions are met, the rule triggers and performs its function, in this case, changing the SV from 0 to 1. After this change, the rule should ideally check the updated SV before deciding whether to trigger again. If it doesn't do this check, it is not re-evaluating after the update.
This could be due to the way the rule is programmed or the order of operations in the system. To prevent the rule from continuously triggering, it should be adjusted to check the updated SV after each trigger. If it checks and sees that SV=1, it should not trigger again."
That's BA AI support answer.
"The greening rule keeps on triggering because it is not checking the updated Stored Value (SV) after it has been set to 1. The rule is set to trigger when SV=0, and it does so correctly the first time. However, after the first trigger, the SV is updated to 1. If the rule is not re-evaluated after this update, it will keep triggering because it is still operating under the condition that SV=0.
To prevent the rule from continuously triggering, you need to ensure that the rule checks the updated SV after each trigger. If it checks and sees that SV=1, it should not trigger again. This could be a matter of how the rule is programmed or the order of operations in your system.
In the context of the Bet Angel user guide, rules are set to trigger under certain conditions. Once those conditions are met, the rule triggers and performs its function, in this case, changing the SV from 0 to 1. After this change, the rule should ideally check the updated SV before deciding whether to trigger again. If it doesn't do this check, it is not re-evaluating after the update.
This could be due to the way the rule is programmed or the order of operations in the system. To prevent the rule from continuously triggering, it should be adjusted to check the updated SV after each trigger. If it checks and sees that SV=1, it should not trigger again."
That's BA AI support answer.
Last edited by jtrader on Sat Oct 12, 2024 10:17 pm, edited 1 time in total.
Thanks but the AI tool doesn't have all the facts unfortunately. The green rule isn't triggered as you say and is not continuously triggered in any case. The green rule is triggered on green all profit condition greater than another SV plus some other condition.
The only time greening1 SV is set, is initially to 0 in first minute of inplay and set to 1 when the green rule is executed.
The reason greening occurs more than once is as a result of the subsequent back bets that fortuitously turn green later on.
The only time greening1 SV is set, is initially to 0 in first minute of inplay and set to 1 when the green rule is executed.
The reason greening occurs more than once is as a result of the subsequent back bets that fortuitously turn green later on.
Set it running last night on new simplified BAF and it happened again several times. Can't post the log as yet cos on my phone but I noticed the problem happens if the greening bet is unmatched or a back bet occurs at the same time as the green.
I don't know why it would affect it because greening1 is still being set to 1.
I had an idea to ensure greening and backing never occur at same time by using different prime numbers (7 and 11) for the time intervals of each.
I am rechecking this now.
Still stumped why it should happen tho
I don't know why it would affect it because greening1 is still being set to 1.
I had an idea to ensure greening and backing never occur at same time by using different prime numbers (7 and 11) for the time intervals of each.
I am rechecking this now.
Still stumped why it should happen tho
-
jamesedwards
- Posts: 4366
- Joined: Wed Nov 21, 2018 6:16 pm
Share the file and the problem will likely be found.sibur wrote: ↑Sun Oct 13, 2024 10:26 amSet it running last night on new simplified BAF and it happened again several times. Can't post the log as yet cos on my phone but I noticed the problem happens if the greening bet is unmatched or a back bet occurs at the same time as the green.
I don't know why it would affect it because greening1 is still being set to 1.
I had an idea to ensure greening and backing never occur at same time by using different prime numbers (7 and 11) for the time intervals of each.
I am rechecking this now.
Still stumped why it should happen tho
If you have clicked the stored value tab of all four of your rules to check there isn't a stray 'Clear stored Value' on one of them somewhere (with logging disabled), what about other files?sibur wrote: ↑Sat Oct 12, 2024 8:36 pmThanks Dallas. I would agree with you and I have fallen for the same mistakes in the past but in this case I am setting the note to log and don't see it being reset. On the face of it the BAF is very straightforward.
Without giving away my strategy, I have paired it down to a simpler BAF but there isn't a lot of in play matches right now so I hope tomorrow I can see it happening with that.
Do you have another automation file applied to rules column 2 or 3?
If so have you checked the stored value tab on each of those rules to see if any of them have a 'Clear stored Value' set when they trigger?