Pages:
Actions
  • #16 by MarkV on 20 Sep 2013
  • Hi Mark,

    I have tested also and it appears to be working okay. The error I reported was an isolated case and not sure what the reason was.
    As regards your question re trading unmatched lay bets.
    I was originally expecting to place the same bet amount on both back and lay, as opposed to green up.
    The net effect would mean, at 5 ticks profit I would need 20 successful trades (back & Lay) to account for one losing bet amount.
    I propose the following change. In the greenup1&2 triggers
    'lay Price rticks(bm_backp,-5)  amount 5.00'    (-5 means 5 ticks)     or
    'lay Price rticks(bm_backp,-gt) amount 5.00'
    assuming 5.00 unit bets.
    Would that work? 
    Thanks
    R
    Hi
    Please see attached trigger file which has the modifications you asked for. Please use test mode to try it.
  • #17 by racepro on 20 Sep 2013
  • Thanks Mark
    R
  • #18 by racepro on 22 Sep 2013
  • Hi,
    I put a condition in the greening up triggers
    and selection's back price is equal or greater than 2.00.
    However the greening triggers still fire when back price is under 2.00.
    see below
    07:20:32   Going to LAY on 1 selections:

          Kurumi Nara, $ 5.00 at 1.79;

    07:20:32   Condition is: TRUE. valid for 1 selections: Kurumi Nara.
    07:20:32   Checking condition and Selection's Back Price is greater than 2.00.

    Maybe I need to amend the formula in the block
    r_ticks(bm_backp,-gt2)
    to include a greater than 2.00 clause.
    One other thought. Maybe the trigger is looking at the odds of the other player !
    Kindly assist
    Thanks
    R









  • #19 by racepro on 28 Dec 2013
  • Hi,
    I would like to ask two favours if I may.

    1) In my initial request I had asked for a trigger based around a price drop.
        However I forgot to mention "sudden" price drop. I wanted to make a trigger
        based upon falling wickets in one day matches or winning a set in tennis.
        So I'd like to have a 'time' condition added to the trigger, please.

    2) You may recall I was placing a 'back' bet if price drops by x ticks
        Instead I would like to place a 'lay' bet. I wish to test both theories.
    many thanks
    R
    ps..... trigger attached.

  • #20 by MarkV on 28 Dec 2013
  • Hi
    Please find attached 2x trigger files:
    momentum_scalping_3_4.mft
    Is an edited version of the original. It has an added constant for price drop ticks. This is the minimum number of ticks the price should fall from the highest recorded back price, before the back trigger will execute. If you set this constant to an appropriate number of ticks movement expected after a fall of wicket, it should do the job.
    Regarding a set in a tennis match, the price progression in the market is point related, so you would need to adjust the constant accordingly.
     
    momentum_scalping_4_over_time.mft
    Is a re-write to execute the back trigger when a selections back price has fallen a certain number of ticks over a specified time period.
    In the constants set:
    green-up ticks
    price drop ticks over time
    time span in minutes for price drop ticks over time.

    Please use test mode.

    I will post the laying trigger a little later.
  • #21 by MarkV on 28 Dec 2013
  • Hi
    Attached please find the laying trigger you asked for.
    Please note the value for the time constant to measure the price drop over should not exceed the default market history depth:
    Settings > Monitoring Options > Market Refresh > Default market’s history depth

    Please use test mode when trying the trigger.
  • #22 by racepro on 28 Dec 2013
  • Hi Mark,
    Thanks for both triggers. I will test them these next few days, starting with the Eng V Aust tonight, which looks like an Aussie victory.
    R
  • #23 by racepro on 29 Dec 2013
  • Hi Mark,

    I would like some clarification of the 'pdt' & 'tm' constanst in the version 4 you just sent regarding placing a 'Lay' bet.
    If we use the following settings as an example, have I understood correctly.
    pdt set to -10
    tm set to     .5
    If back price drops greater than 10 ticks within a half a minute period then place a lay bet. If so then that is what I want.
    How does the calculation of >10 ticks drop take place without a 'remember' function?
    eg: odds 30 seconds ago 3.20 odds now 2.60
    Thanks
    R
  • #24 by MarkV on 29 Dec 2013
  • Hi Mark,

    I would like some clarification of the 'pdt' & 'tm' constanst in the version 4 you just sent regarding placing a 'Lay' bet.
    If we use the following settings as an example, have I understood correctly.
    pdt set to -10
    tm set to     .5
    If back price drops greater than 10 ticks within a half a minute period then place a lay bet. If so then that is what I want.
    How does the calculation of >10 ticks drop take place without a 'remember' function?
    eg: odds 30 seconds ago 3.20 odds now 2.60
    Thanks
    R

    Hi
    The condition:
    and selections back ticks dif over tm mins is less than pdt
    takes care of it. From the manual:

    "28. Back Ticks Dif over ... mins
    The change of the back price over the specified number of last minutes, in price ticks. So, if the price has dropped from 2.0 to 1.82, this will be equal to -18."

    so for this condition I have made 2x constants to make it easy to adjust the values
    tm = the time to measure the price difference over
    pdt = the price drop ticks when to fire the trigger

    In the example you give:
    tm=0.5
    pdt=-10
    so if the price has dropped by 12 ticks in 30 seconds, the condition will be met
    because -12 is less than -10

    effectively "back ticks dif over x mins" is a built-in function. The "x mins" must not exceed the setting:
    Settings > Monitoring Options > Market Refresh > Default market’s history depth
      
  • #25 by racepro on 29 Dec 2013
  • Hi Mark,
    Thanks for the clarification It is now crystal clear.
    I'll be testing over the next few weeks.
    Cheers
    R
Pages:
Actions