Pages:
Actions
  • #1 by racepro on 31 Aug 2014
  • Hi,
    I'm having some difficulty with a condition
    I want the back trigger to fire when the back price is x ticks lower then its price before the start of the event.
    I tried the following but it doesn't work  (using tcks as a constant)
    and selection's trigger expression back_price is less than r_ticks(last_backp, -tcks)
    any help appreciated
    Thanks
    R

  • #2 by LarpHager on 31 Aug 2014
  • Hi,

    You could just modify back-preoff-steamer


    Larp

    • LarpHager
  • #3 by racepro on 31 Aug 2014
  • Thanks Larphager, but doesn't appear to be suitable for tennis
    I think there is a condition I could add to my existing trigger.
    I thought the one I referred to should work but apparently not.
    Where am I going wrong ?
    R
  • #4 by MarkV on 31 Aug 2014
  • Hi
    Have you defined the selection either in the conditions or in the variable?

    selections index is equal to 2
    and selection's back price is less than r_ticks(last_backp, -tcks)

    selection's trigger expression s_2_back_price is less than r_ticks(s_2_last_backp, -tcks)
  • #5 by racepro on 31 Aug 2014
  • Hi Mark,

    At the moment I just want any player matching conditions
    I just need the basic settings
    Do I need to use 'set user variable' settings ? if so full details please.
    I thought I could just use the conditions block.
    The condition below sounds correct, but obviously not.
    and selection's back_price is equal or less than r_ticks(last_backp, -tcks)
    This should take the current price then adding the ticks and result should be less than the price before the start. If that makes sense.
    Maybe I do need the variable to record price before going in play.
    Thanks
    R
  • #6 by MarkV on 31 Aug 2014
  • Hi
    last_backp updates when idle and stops updating when the market turns inplay, retaining the last recorded back price for the selection before inplay. It should work without the need for a user variable.

    Try this condition block:
    AND
         selection's trigger expression s_1_back_price is less than r_ticks(s_1_last_backp, -tcks)
         or selection's trigger expression s_2_back_price is less than r_ticks(s_2_last_backp, -tcks)

    It should work for either selection using the correct prices for each selection. You can check that it works ok if you put into the variable viewer and compare them:
    r_ticks(s_1_last_backp, -tcks) <--- this one will return values for selection index 1
    r_ticks(s_2_last_backp, -tcks) <--- this one will return values for selection index 2
          
  • #7 by racepro on 01 Sep 2014
  • Hi Mark
    Works a treat. Thank You.
    First time I've used that Viewer Variable box. Kinda neat eh?
    Cheers
    R
  • #8 by racepro on 01 Sep 2014
  • Hi Mark,
    The viewer has highlighted the frailties of the Betfair market in that one event showed a zero odds price before it went in play despite monitoring market 10 mins before the off. Hence of course the trigger wouldn't fire.
    The market eventually had a matched volume of 1.4 million. Safeguards need to be put in place in the event of these occurrences...... (by the way I only tested 6 events)
    Proving once again the Betfair market has more tricks than the Cross on a Saturday night.
    (not that I know of course!:)
    R
  • #9 by fosterdrew on 22 Sep 2014
  • Absolutely right. I think they're on top for a reason. And that's one of them.
Pages:
Actions