Pages:
Actions
  • #1 by racepro on 05 Apr 2013
  • hi,
    the program tried to lay the fav at 990/1 having backed it at
    1000/1. The result was no bet due to insufficient funds.
    That would have been a nightmare had it been in real mode
    and had sufficient funds.
    It happened with the same team 3 mins and 46 secs apart.
    I checked the trigger and program logs. The program logs highlighted the error
    in red and blamed trigger 1
    I have used "favourite" in my triggers in all the triggers for
    both the main blocks and conditions.
    Anybody any idea what the problem could be.?
    should I be using market selection or similar instead of "favourite"?
    it is worrying :(
    R
  • #2 by Oxa (WellDoneSoft) on 06 Apr 2013
  • It is one of the limitations of test mode compared to the real money mode. It can't make assumptions as to whether you will generate enough profit from the forthcoming trade to cover your liability, like the real exchange does. It can only work with the actual available funds.
    Had you been trading in real mode, your bet would have been allowed.
  • #3 by racepro on 06 Apr 2013
  • Good grief !! that would have been a disaster.
    My question was why did it put on such a big bet in the first place ?
    Considering I am only betting the favourite.
    Should I be selecting something other than "favourite" in the conditions
    or in the block ?
    Should I be selecting "matching Selections" instead of"favourite" ?
    Thanks
    R
  • #4 by MarkV on 06 Apr 2013
  • Hi
    Try putting in a condition that restricts bets within an acceptable price range, for example:
    and selection’s lay price is less than <your max lay price>

    It sounds like the market you were trading was an unmanaged market. If the back price offered was 1000 the event was probably over but the market was still open. The above condition should deal with it, but you should also be careful in your choice of markets you wish to trade in.
  • #5 by racepro on 06 Apr 2013
  • Thanks, that all makes sense now.
    I was a bit concerned I was selecting the wrong
    selection method ie: fav or matching sel. etc.
    perhaps volume limit would also help.
    R
  • #6 by Oxa (WellDoneSoft) on 06 Apr 2013
  • Sorry, I misinterpreted your question, but MarkV seems to have explained it very well!
  • #7 by ifyesthenno on 06 Apr 2013
  • hi,
    the program tried to lay the fav at 990/1 having backed it at
    1000/1. The result was no bet due to insufficient funds.


    sorry if I misunderstand it: if the program has backed it at 1000/1 first, why is it a problem than to place the lay bet at 990 reguarding the total funds? the back bet brings the amount that is needed for the lay bet. or not?
    • ifyesthenno
  • #8 by MarkV on 06 Apr 2013
  • Hi
    Oxa tries to explain it in reply#1

    In test mode you need enough test funds to cover the liability of the lay bet on its own, or any individual bet.
  • #9 by ifyesthenno on 06 Apr 2013
  • Hi
    Oxa tries to explain it in reply#1

    In test mode you need enough test funds to cover the liability of the lay bet on its own, or any individual bet.

    ok. but in real-mode there wouldnt have been any problem of funds, I think. I wondered because of this sentence:

    Good grief !! that would have been a disaster.

    • ifyesthenno
  • #10 by MarkV on 06 Apr 2013
  • Real mode will be fine, except you will probably lose the back bet :)
  • #11 by racepro on 06 Apr 2013
  • Thanks for all your replies.
    I only wanted to bet the favourite.
    The program made a back bet of 5 @ 1000/1  
    Then tried to lay 5 @ 990/1
    It is no wonder there was insufficient funds. But that was not the issue.
    The issue was, why did it bet it in the first place?
    I have a max price in place now to hopefully avoid that happening again
    as suggested by Mark and also he explained why it could have happened
    as it may have been an 'unmanaged market' and that I should be more selective in loading up my markets.
    Thanks again and still on the learning curve :)
    R
  • #12 by racepro on 07 Apr 2013
  • hi,
    I think I understand this now about how to unequivocally select the fav.
    in the block section
    selections "favourite"
    in the conditions section
    choose     "selection's"
    Is that correct?
    thanks
    R
  • #13 by MarkV on 07 Apr 2013
  • Hi
    In the program The Favourite is defined as the selection with the lowest back price.

    In the trigger Selections field, Favourite refers to the above

    In a Condition you can use Favourite's which means the same as above
    In a Condition you can also use Rank:
    Selection's Rank is equal to 1

    these all refer to the selection with the lowest back price at the time the trigger executes, and works well in high liquidity markets.

    If you are trading in markets where there is a large gap between back and lay prices, the program still refers to the Favourite as the selection with the lowest back price. However, this is quite likely to be a false, or ambiguous "fav", so you need to help the trigger along a bit with some other conditions. For example:

    Selection: Favourite
    Conditions:
    Selection's Lay Price is less than 2.00
    and All Other Selections lay price is greater than 2.00

    however, if as is shown in your first post, the trigger is backing and laying for 1 tick, you really do not want to be trading in markets where there is a big gap between back and lay prices:

    Market's back book% is less than 105
    and Selection's Triggers expression g_ticks(back_price, lay_price) is less than 3

    the above allows max 2 ticks between back and lay prices
  • #14 by racepro on 07 Apr 2013
  • thanks Mark,
    that has cleared that up.
    The Fav I was using in both Trigger block and conditions
    were not at fault as I thought, and hoped was the case.
    The problem may have been caused by
    using in a low liquidity market when all conditions
    can comply just for a few moments and in that time
    a bet can be placed.
    Cheers
    R
Pages:
Actions