Pages:
Actions
  • #1 by betfair winner on 14 Jun 2013
  • Hi Guys and oxa may need to be aware of this problem
    Having run a V6 trigger with no problems for 2 years based on silknumerator/silkdenominator
    i have a trigger which fires once the back price available exceeds the betfair fcs by a certain factor so once the back price available exceeds say  4 times the silknumerator/silkdenominator the trigger fires
    the expession looks like this.........."fitting selections back price is equal or greater than 1+silk_numerator/silk_denominator*1.5
    however in V7 this generates hundreds of bets that fire irrespective of the back price available relative to the Betfair fcs. Anyone have a solution that will fix this?
    cheers guys
  • #2 by mcbee on 14 Jun 2013
  • hi
    i have tested your   1+silk_numerator/silk_denominator*1.5
    on the v6 and v7 at the same time and both gave the same value.
    the only time different was when i first tried because i did not set the bot to download the silks in the v7, but after i set it to download the silks, then the values were the same.
    it could be some other condition that has not converted from v6 to v7.
    could you include the trigger, not the full set of triggers, that contains this condition.


    mcbee
  • #3 by betfair winner on 14 Jun 2013
  • Hi Mcbee and much thanks
    Just to confirm the trigger was conceived in V7 and not transferred.
    the one attached is the version that seems to fire at all prices.
    even allowing for the reduction factor the prices are well below the 1.5 times betfair fcs.
    Thanks again.
  • #4 by mcbee on 15 Jun 2013
  • hi
    i have tested the trigger and it works as it should,
    it only placed bets on selections that the price was greater than 1+silk_numerator/silk_denominator*1.5*(100-redfactor)/100 and less than 26.00
    also to check for any calculation error i monitored every selections value by using a separate variable for each one in the variables screen, so i could see the changes as they happened.
    there must be some other setting or trigger that is causing the problem.
    BUT, i did test with the DOWNLOAD HORSE RACING SILKS   NOT TICKED
    then the trigger placed a bet on ALL selections
    to stop this and just in case the silks were not available i added the condition

    and    selections    trigger expression    1+s_1_silk_numerator/s_1_silk_denominator*1.5*(100-s_1_redfactor)/100     is greater than  1

    this checks to see if there is a value with your calculation/formula and if the silks are missing it will not place a bet


    mcbee
  • #5 by betfair winner on 15 Jun 2013
  • Thanks a lot Mcbee
    I will do another test and perhaps mail you more log detail if I get more problems but it could be that some selections do not have a betfair fcs and maybe these are all being triggered.... so your update could work correctly for me also now.
    Thanks again you are a star.
  • #6 by betfair winner on 16 Jun 2013
  • Hi Mcbee
    Well done my friend your tweak on the trigger conditions has solved the problems
    BRILLIANT WORK YET AGAIN!
    You are a real genius at this what would Marketfeeder do without you sir!
  • #7 by peleus on 12 Dec 2013
  • Thanks McBee, I had this issue last week about silkdenominator and your solution is right on the money!
Pages:
Actions