Pages:
Actions
  • #121 by Oxa (WellDoneSoft) on 28 Jun 2012
  • The problem with the difference between the website prices and the prices returned by the API does exist. BetFair published some notes on how to do the conversion, and that's what we are guided by, but some rare cases are not covered by that guide, and that's what probably happened in that market.
    I will keep watching such markets in order to improve the conversion.
  • #122 by MartinSteiner on 28 Jun 2012
  • Today I will re-test the price problem, during 1st half with and during second half without "displaying prices exactly as they appear on Betfair website".

    If I find any strange market condition ( lay price less than back price ) I will take a screenshot. Betfair earns money with cross matching, because of descrete ticks between odd levels, betfair rounds cross match back odds to the next odd level below the calculated cross odd, and rounds cross match lay odds to the next odd level above the calculated cross odd. I wunder if betfair really has published this information...

  • #123 by pcal72 on 28 Jun 2012
  • Oxa

    Just wont to thank you and all team and to all users work to place this beauty working propertly.

    This last version is from 2 days 100% erros and shutdowns free, awesome work :)

    pcal72
  • #124 by MartinSteiner on 28 Jun 2012
  • Hi Oxa,

    I guess I have found the problem with "displaying prices exactly as they appear on Betfair website".

    MFPro applies this cross matching stuff in markets, where cross matching is not active in betfair. The Euro 2012 Winner Market hat NO cross matching in betfair. If I enable "displ..." in a market with no cross matching, the adjustment algorithm cauese strange results, because if cross matching is enabled, some book percentages close to 100% cannot occur.

    MFPro applied cross matching to EURO 2012 market. (there is no cross matching in betfair)

    On the other hand, in a market with cross matching (e.g. a tennis match), enabling "displa......" has does not cause any change in MFPro.

    MFPro does not apply cross matching in tennis match odds markets (but there IS cross matching in betfair.)

    Does MFPro know from API if market has cross matching enabled? MFPro's cross matching algorithm is applied to the wrong markets!

    I have to disable this feature, my triggers work better without it.......

    kind regards
    Martin
  • #125 by rubold on 28 Jun 2012
  • Martin, so in tennis match odds, should I not be displaying prices as on Betfair?  I'm a bit confused.
  • #126 by MartinSteiner on 28 Jun 2012
  • rubold,
    I did not see any change in tennis match odds markets if you play around with "displaying prices exactly as they appear on Betfair website" settings. So at the moment, this setting does not matter for tennis match odds markets.

    If this bug in MFPro is fixed, it depends in how you use MFPro if it is better to disable or enable this feature.

    Enable "displaying prices exactly as they appear on Betfair website"  for

    - manual ladder trading
    - manual (1 klick) betting
    - triggers which try to enter immedaite matching bets at bet price
    - any strategy which needs best price for a immediate match

    Disable "displaying prices exactly as they appear on Betfair website"  for

    - triggers which does book building
    - triggers which enter unmatched bets at an offset by best price
    - Auto-Dutching


    Sorry, this list is not complete, maybe your trigger or manual trading strategy does not fit in any of the above categories.

    Martin
  • #127 by MartinSteiner on 30 Jun 2012
  • Hi,
    are there still problems with crashes and logs? If MFPro 7 crashes with some of your triggers, but works fine with other trigger, I think I have found a hint for you.

    In trigger conditions, the AND NOT and OR NOT can be the reason for your problems.
    Try to transform your trigger not to use AND NOT and OR NOT. This is very simple in most cases.

    Instad of

    AND NOT    ...   is equal to   ...

    use

    AND   ... is not equal to   ...

    This is obviously the same, but for MFPro it is a big difference!


    Instad of

    AND NOT    ...   is greater than   ...

    use

    AND   ... is less or equal to   ...


    My biggest trigger caused MFPro crashed, or stopped responding within some minutes with AND NOT, but ofter I do not use AND NOT, everything works fine for hours!

    I will create a small sample crash-trigger and email to support.

    Martin
  • #128 by betfair winner on 01 Jul 2012
  • STATEMENT PROBLEMS

    Hi Oxa
    There appears to be an ongoing but intermittent problem with the statement on V7.
    Most days they are complete, but twice in the week only a few entries were downloaded from Betfair.
    I ran 3 different computers today on three different IPs and three different accounts. Two were running V7 and one running V6 all in test mode. Both V7 statements only downloaded the 13:50 race today and nothing else. The V6 test downloaded all the racing as usual.
    Maybe there is a problem here as the statement download is intermittent?
    Thanks 
  • #129 by mcbee on 01 Jul 2012
  • hi betfair winner
    what have you set the refresh account statement in the settings.
    ANYTHING more than 20.00 sec will miss statement records.
    the more secs you increase, the more records are missed.

    mcbee
  • #130 by betfair winner on 01 Jul 2012
  • YES Mcbee
    Thanks, I remember you mentioned this in an earlier reply. i reduced the refresh from 30 seconds to 20 seconds and afterwards for a couple of days everything was fine but today not. So i will reduce to 15 seconds tomorrow and see if that helps.
    What makes no sense is that the v6 test is still 30 second refresh, but got all the statement.
    Cheers
     
  • #131 by mcbee on 02 Jul 2012
  • hi
    that is because v6 uses a different method for storing and retrieving the statement.



    mcbee
  • #132 by Oxa (WellDoneSoft) on 02 Jul 2012
  • Quote from: betfair winner on 01 Jul 2012, 20:40
    STATEMENT PROBLEMS

    Hi Oxa
    There appears to be an ongoing but intermittent problem with the statement on V7.
    Most days they are complete, but twice in the week only a few entries were downloaded from Betfair.
    I ran 3 different computers today on three different IPs and three different accounts. Two were running V7 and one running V6 all in test mode. Both V7 statements only downloaded the 13:50 race today and nothing else. The V6 test downloaded all the racing as usual.
    Maybe there is a problem here as the statement download is intermittent?
    Thanks 

    What happens if you restart the program? Does it fetch the missing entries from BetFair?
  • #133 by betfair winner on 02 Jul 2012
  • Quote from: Oxa (WellDoneSoft) on 02 Jul 2012, 16:00
    What happens if you restart the program? Does it fetch the missing entries from BetFair?

    Hi Oxa and MCBEE
    Just to confirm the spasmodic statement download continued today albeit far better than yesterday where just one race was settled.
    Today with refresh rates of 15 seconds we did get a full statement on one account but regrettably around 70% on the other account.
    Tomorrow when it stops getting statements i will restart, but when i did this a few days ago the platform failed to get any of the missing statements.
  • #134 by betfair winner on 03 Jul 2012
  • Hi Oxa
    Is there a window of opportunity for statement downloads that closes after a certain time. Re your comment about re starting the program.
     
  • #135 by betfair winner on 04 Jul 2012
  • Statement problems
    Hi Oxa
    Just to confirm complete lack of statement so far today.
    despite hundreds of bets nothing has appeared at 17:55, and racing started at 14:10.
    This is on two different pcs ON two different accounts that yesterday seemed to get most of the statement OK.
    The left column shows the races now grey and no longer green, as if they have been settled but nothing on the statement.
Pages:
Actions