Author Topic: Double firing In Running  (Read 3601 times)

Tags:
  • All members
  • Posts: 39
Double firing In Running
« on: 18 May 2015, 18:07 »
How can one prevent from double firing triggers when Horse racing In Play at fastest refresh.

This is already in the condition field:

-Selection's Number of matched back bets is equal to 0
-Selection's Number of unmatched back bets is equal to 0

So the triggers should ony fire once/selection, but sometimes in the race 2 back bets are placed......for the same selection..at exactly the same moment.

Any known way to prevent this , please?

Thanks for your input!

  • Guest
Re: Double firing In Running
« Reply #1 on: 18 May 2015, 19:39 »
Hi,


Maybe put the trigger Execute setting to "Once Per Selection"

  • All members
  • Posts: 39
Re: Double firing In Running
« Reply #2 on: 18 May 2015, 23:42 »
Hi,


Maybe put the trigger Execute setting to "Once Per Selection"

This setting was already in place, thanks LarpHager
I even added:

'and trigger xxxxxx number of runs is equal to zero'

But it still happens...


  • All members
  • Posts: 347
Re: Double firing In Running
« Reply #3 on: 19 May 2015, 06:58 »
You're not "reloading" the trigger once a bet has been placed already are you?

  • Nerd
  • Élite
  • Posts: 462
  • Gender: Male
  • I think I could be on to something here!
*
Re: Double firing In Running
« Reply #4 on: 19 May 2015, 09:12 »
Once Per Selection should work.

Enable and Check your logs.
Fortune favors the brave!

  • Guest
Re: Double firing In Running
« Reply #5 on: 19 May 2015, 09:32 »
If not the above,

Are the double fired bets below the minimum £2?

Or

try setting the refresh rate of the trigger execution to

Once Every 2 seconds

that might fire it once and then it waits, giving time for the API to respond to the bet and either match or unmatch it, and therefore the trigger should then not fire again.

But I would test that. And it cannot be tested on Tm as the response is immediate. So caveat emptor  ;)

  • All members
  • Posts: 39
Re: Double firing In Running
« Reply #6 on: 19 May 2015, 12:49 »
Cheers for all the input,

Been studying the logs.... I have a set(like 5 or 6) of 'Back' triggers running, all with a different set of conditions.

In Running Horse Racing, there are moments when 2 back triggers fire at once at the same selection, because the conditions of both back triggers are 'TRUE' at that particular moment.

Since I only want ONE back bet/selection(it's a rather substantial amount, not under minimum), I need to find a way to prevent a selection being backed twice or more.



-Slowing down refresh rate is not an option, I need fastest refresh available or I put myself out of the game, IP is like the 'Gunfight @ OK Corral' really.... ;D

-Reloading the trigger just once doesn't help either, since it involves 2 different 'back' triggers at the same selection when respective conditions apply.


There is probably some simple solution which I am overlooking.....when you tend to 'dive' in a rather complex set of triggers ( a result of months/years thinkering and trialing) you get the 'tunnel vision' syndrome, or the 'freeze reaction' rabbit in headlights thingy.......... I need some winegums or other mindbroading substances, come on MFP, a free bag of goodies with every subscription!    ;D


  • All members
  • Posts: 347
Re: Double firing In Running
« Reply #7 on: 19 May 2015, 13:37 »
Surely setting the trigger to run once per selection will fix it?

  • Administrator
  • Posts: 8821
  • Gender: Female
*
Re: Double firing In Running
« Reply #8 on: 19 May 2015, 13:58 »
The reason your trigger might be firing twice is the delay between the updates of your bets, both matched and unmatched. The frequency at which the program is checking your bets is defined by the Betting Options. By default bets are checked each time a market is refreshed. Meaning if you refresh a market once in 0.5 secs, MF Pro will request a list of your bets from BetFair every 0.5 sec. But this does not mean that if your trigger places a bet, it'll be in the list next time MF Pro refreshes the market and executes the trigger. Some bets take longer to be accepted on the exchange. So a situation may occur when you trigger checks next time and does not see that bet, and bets again, whereas the bet is already there, just not registered and returned by the exchange yet.

So the rules of a thumb is wait for a few seconds before assuming the bets have been placed, then check again. Or you may take a note of the timestamp when your trigger fired (through a user variable, e.g. my_bet_time), set it to now_time when the trigger is firing (with a separate action), then compare it to bm_laytime or bm_backtime - depending on the type of bets you're expecting. If the latter is greater than my_bet_time, then it means those are the new bets.
Always try your triggers in Test Mode before switching to real money!

Follow us on Twitter.

Join our WhatsApp chat!

Присоединяйтесь к официальному Telegram-каналу!

  • Guest
Re: Double firing In Running
« Reply #9 on: 19 May 2015, 14:50 »
Hi,

Yes Oxa explained much better than I ever could, but my theory of delaying the refresh for the trigger was at least correct.

If you attach a sample of what the trigger is doing, I will download and check to see can I replicate the process and perhaps offer a remedy. you can change any conditions you wish to remain private, just the basic mechanism will do me

  • All members
  • Posts: 39
Re: Double firing In Running
« Reply #10 on: 20 May 2015, 23:24 »
No 'double dips' today throughout the entire racing card  :)

I  added a condition to each 'back trigger', 'and sel tr. expr. last_order is not in list x,x,x' since it was aiming at certain favs pre off,  so each set of conditions is unique now, it appeared before they were not (although in test mode there wasn't more than 1 back bet/selection)......let's see what next days racing brings......fingers crossed.

 

  • Guest
Re: Double firing In Running
« Reply #11 on: 21 May 2015, 06:25 »
hi,

I did not realise from your initial posts that you had more than one trigger firing the bets, so the double-firing angle was a little misleading for us I think. But at least you got there anyway in the end  :)

Larp


 

Please note, BetFair is seems to be currently OFFLINE