Hi,
I am trying to set a trigger when a 3rd Fav goes under a certain price twice (but not the same 3rd Fav). Also when it occurs for first time
both the first & 2nd favs are signalled with Value 1 "Fav1sig" & "Fav2sig" (only 1 trigger allowed on "Fav1sig" & "Fav2Sig").
The signalling on the 3rd Fav allow 2 triggers and is for market by incrementing "Fav3sigtwice" and by selection I use "Fav3sig ".
The conditions I use for triggering are on the 3rd Fav the trigger are Fav3sigtwice = 2 and Fav1sig,Fav2sig & Fav3sig not set with a value for selection
I was hoping the 1st time a third fav goes under the designated price, all Signals are flagged 1 but the 2nd time only a newcomer not previously flagged 1as either Fav1sig,Fav2sig or Fav3sig would allow the Fav3sigtwice to go to 2 which is the ultimate trigger for a bet.
After 2 days nothing triggered and ive looked at everything and it looks like the signalling but I do not understand why not?
Grindhog
How is my signalling wrong?
You said “Fav1sig,Fav2sig & Fav3sig not set with a value for selection”
Should the Fav1sig,Fav2sig not be (set with a value)
“both the first & 2nd favs are signalled with Value 1 "Fav1sig" & "Fav2sig" (only 1 trigger allowed on "Fav1sig" & "Fav2Sig")”.
Should the Fav1sig,Fav2sig not be (set with a value)
“both the first & 2nd favs are signalled with Value 1 "Fav1sig" & "Fav2sig" (only 1 trigger allowed on "Fav1sig" & "Fav2Sig")”.
Hi,
Just to clarify my setup on which I set out incorrectly
My signal for the incrementation of "FavSigTwice" on the 3rd Fav is actually -Fav1sig,Fav2sig & Fav3sig not set with a value- and of course being under a certain price (an average 3rd fav price) at a certain time in the race relative to its distance (at a time when the prices begin to move). The bet rule itself has only 1 trigger condition FavSigTwice =2 taking its lead from the 3rd Favourite signalling. Hope somebody can help please.
Grindhog
Just to clarify my setup on which I set out incorrectly
My signal for the incrementation of "FavSigTwice" on the 3rd Fav is actually -Fav1sig,Fav2sig & Fav3sig not set with a value- and of course being under a certain price (an average 3rd fav price) at a certain time in the race relative to its distance (at a time when the prices begin to move). The bet rule itself has only 1 trigger condition FavSigTwice =2 taking its lead from the 3rd Favourite signalling. Hope somebody can help please.
Grindhog
hI Dabbla,
When the 3rd FAV reaches under the price all 1stfav,2ndFav & 3Rd Favs are tagged with a value 1 (under the condition of not having
previously been signalled with a value. For the 2nd round the newcomer 3rd fav (being an untagged 1st,2nd or3rd Fav) receives its 1st Fav3sig tag but the market signal for "FAV3SigTwice" is a second one creating the bet trigger to which its subject.
The overall conditions for this are infrequent but I am certain from what i see unfolding in prices that it can and should occur. In fact a check of TFBetfair in running prices shows how many horses reach a certain price is a fair indication (although the price so reached has
specifically to happen to 3rd favs in succession which cannot be categorically known specifically from TFtimeform).If that makes sense?
grindhog
When the 3rd FAV reaches under the price all 1stfav,2ndFav & 3Rd Favs are tagged with a value 1 (under the condition of not having
previously been signalled with a value. For the 2nd round the newcomer 3rd fav (being an untagged 1st,2nd or3rd Fav) receives its 1st Fav3sig tag but the market signal for "FAV3SigTwice" is a second one creating the bet trigger to which its subject.
The overall conditions for this are infrequent but I am certain from what i see unfolding in prices that it can and should occur. In fact a check of TFBetfair in running prices shows how many horses reach a certain price is a fair indication (although the price so reached has
specifically to happen to 3rd favs in succession which cannot be categorically known specifically from TFtimeform).If that makes sense?
grindhog
hi
No although im a junior space cadet thats not the problem. Thanks anyway
grindhog
No although im a junior space cadet thats not the problem. Thanks anyway
grindhog
Hi Dabbla,
If you can PM me I can send you the baf for checking.
Regards
Grindhog
If you can PM me I can send you the baf for checking.
Regards
Grindhog
Hi Dabbla,
Thanks for pointing out that the stored value was the issue and I think I see whats wrong. The stored Value is the "stake creator" for the bet. Both the Stored value and the back bet rule have the same signalled condition named "fav3sigtwice" but while all the conditions were showing up in "Automation2 & "Logs" because the Backbetrule was subject to the stake from stored values being in place it was not in place
occurring simultaneously with the "favsigtwice". It meant that the back bet rule was triggering without a stake in place (sometimes)
I think the solution is to either put an extra signal on the stored value and make the Backbet rule subject to it or increase the trigger time
on the backbetrule by 1 so that its caught when it cycles around again.Ill do both to be sure to be sure.
Grindhog
Thanks for pointing out that the stored value was the issue and I think I see whats wrong. The stored Value is the "stake creator" for the bet. Both the Stored value and the back bet rule have the same signalled condition named "fav3sigtwice" but while all the conditions were showing up in "Automation2 & "Logs" because the Backbetrule was subject to the stake from stored values being in place it was not in place
occurring simultaneously with the "favsigtwice". It meant that the back bet rule was triggering without a stake in place (sometimes)
I think the solution is to either put an extra signal on the stored value and make the Backbet rule subject to it or increase the trigger time
on the backbetrule by 1 so that its caught when it cycles around again.Ill do both to be sure to be sure.
Grindhog
Your solution sounds fine , just don’t do both at the same time, you will end up double betting.
The bet rule will fire properly as long as the stake rule is hit by 2 signals before the bet rule is hit by 2 signals.
So just make sure its directly above the bet rule.
I think the easiest way to SV your stake, would be to just sv for the ,market > price selection >nominated xx , that way its locked to the market and not a different runner.
The bet rule will fire properly as long as the stake rule is hit by 2 signals before the bet rule is hit by 2 signals.
So just make sure its directly above the bet rule.
I think the easiest way to SV your stake, would be to just sv for the ,market > price selection >nominated xx , that way its locked to the market and not a different runner.
Hi Dabbla,
I stayed with the increase of the trigger times bur decided because of the double bet risk to put a "number of matched bet in the market =0
to ensure 1 bet only. The signalling option I mentioned earlier was scrapped as it would have occurred on the 1st occurance.
I stayed with the increase of the trigger times bur decided because of the double bet risk to put a "number of matched bet in the market =0
to ensure 1 bet only. The signalling option I mentioned earlier was scrapped as it would have occurred on the 1st occurance.
Hi Dabbla,
No worries.Its ok now. Thanks
Grindhog
No worries.Its ok now. Thanks
Grindhog