duplicate trigger execution

Morning all.

Was wondering whether anyone could provide any insight as to the best way to stop triggers firing at the same time - possibly by way of another condition.

in the 1st instance i have a block of triggers that monitor each horses last traded price during
the race based on the horses index (10 separate triggers).The triggers that control the betting are in a separate block for each horse (10 separate blocks with 1 trigger inside). They will place a bet when certain criteria is met in the price monitoring triggers.

so i have say 10 blocks of betting triggers that are identical except for the fact that betting trigger 1 is looking for a certain price change in the index 1 monitoring trigger.
Betting trigger 2 is looking at changes in price monitoring trigger 2, and so on...


I have set up conditions that say only place a bet if back / lay matched or unmatched = 0 and
set the bet refresh to update simultaneously with the market, which is 0.30 sec.

the issue is that two or more triggers are firing at exactly the same time, rendering the back / lay matched/unmatched condition useless.

i have also tried setting each betting trigger to monitor at different intervals, but this means that the betting trigger for horse 10 is only being looked at once every 4-5 secs. which means that opportunities are being missed.

any help is appreciated.

thanks

My knowledge of MFP is very limited and I cannot help you because of this. The reason for this post is that I was about to ask a similar question myself. My question is :

If I have several blocks of triggers, all monitoring the same market at the same time, how do I ensure that only one block functions and the rest are cancelled, please ?

I don't want a second block to function as it would make a mess of the results I hope to achieve by getting the first block to work.

Is this the same problem, redarme ?

Hi

a similar problem yes. in a nutshell i only need one betting trigger to execute, but that one execution could come from any one  of the 10 blocks that are looking for the opportunity at the same time.

In my case i dont think its possible to have one betting trigger as each horses price is being monitored separately.

hi
you would be better to use just 1 betting trigger.
with blocks of conditions, each with there own index number and conditions.
condition block 1
selections index is equal to 1
and (your other set conditions as per index)
block 2
selections index is equal to 2
and (your other set conditions as per index)
etc
this way it will only place 1 bet
or 1 bet per selection if that is what you want

mcbee

do you have triggers that fire at exactly the same time ?

if not then adding conditions to trigger 1 of dont execute if trigger 2,3 etc has been executed and repeating these conditions relevant to the trigger number will work for you..

Hi Mcbee.
 
so essentially, copying my 10 betting triggers into the conditions field of one trigger?

Am i right in thinking that the new trigger would then scan down starting from  the order i type them in, and if conditions are met at exactly the same time, pick the first index to place a bet on?

e.g index 5 and 10 meet the criteria at the same time, index 5 would be chosen as its conditions come before index 10.

hi
yes, if you set the trigger to first matching selection.
or if you would preferr the last selection, then set the trigger to last matching selection.
REMEMBER to set your condition blocks to OR
so it can be index 1 or index 2 etc

mcbee

Hi redarme
I would suggest maybe using a remember trigger using your 10 blocks of conditions in the one remember trigger as mcbee mentioned.
Then your back/lay trigger, with some double-check conditions if needed, and even filtering on remembered selection’s variables.   

Nigel
How about Deactivate Trigger or Block B  if Number of Runs for Trigger or Block A is greater than 0?
…then reactivate for start of next market