Author Topic: Matched price vs Required price  (Read 1637 times)

Tags:
  • Élite
  • Posts: 431
*
Matched price vs Required price
« on: 22 Oct 2016, 07:43 »
Hi All,

Can anyone help me to identify the gap between my bet back price and the matched back price?  I am sure it is simple but I seem to be brain dead this morning - I should have had a drink last night!

So, I place a bet and have calculated the price I want to back at is, say, 6.  The bet is placed but the price has moved and I get matched at say 7.

If the price has moved fast and far, I might get matched at say 10.  How do I identify these ones where the matched price is more than 'X' from the last back bet target price?

Any thoughts welcome please.  thankyou.

  • Élite
  • Posts: 431
*
Re: Matched price vs Required price
« Reply #1 on: 22 Oct 2016, 08:14 »
PS: in case it affects any suggestions I am betting on multiple selections in any one event in the UK horse racing markets.

  • All members
  • Posts: 405
Re: Matched price vs Required price
« Reply #2 on: 22 Oct 2016, 11:01 »
Hi Alfaman

I may have totally misunderstood your request (I'm pretty good at that!) but would bm_backp help you? it records the price of the last back bet that you placed on a selection (or bm_layp if it's a lay bet). So if the number of ticks between the current price and the value recorded by bm_backp is a certain number of ticks that would give you your answer maybe.

g_ticks(bmbackp,back_price) might work?

  • Élite
  • Posts: 431
*
Re: Matched price vs Required price
« Reply #3 on: 22 Oct 2016, 11:19 »
Thanks Armarnni,

I thought of something like that but it is the difference between bm_backp and the price that I triggered the bet at - which was calculated at the time from market signals.

It is almost like I need to "Remember" the value in the "Price" box at the moment the bet is placed but I would need to do that for every selection that I have bet on and refer to them individually in a trigger.

  • All members
  • Posts: 405
Re: Matched price vs Required price
« Reply #4 on: 22 Oct 2016, 12:10 »
All I can suggest is like you say, a variable that sets with the value of back_price when your triggers number of runs per selection is greater than 0. (but like you say, I think that would overwrite with a new value each time the trigger fired for another horse.)

Not much help for you I'm afraid, sorry

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Matched price vs Required price
« Reply #5 on: 22 Oct 2016, 17:10 »
hi
you said      but it is the difference between bm_backp and the price that I triggered the bet at - which was calculated at the time from market signals.
what do you do to TRIGGER,THE BET AT , is it manual or auto , variables are our godsend , use them..

mcbee
Please read the following  disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • Élite
  • Posts: 431
*
Re: Matched price vs Required price
« Reply #6 on: 22 Oct 2016, 21:47 »
McBee, thanks, lets say I trigger the bet at back price, at 6 and it gets matched at 10.

Please can you explain how I use a variable to record the "6" so that if the matched bet is at "X" points higher than 6 I can trigger an appropriate lay.

  • Élite
  • Posts: 3698
  • Gender: Male
*
Re: Matched price vs Required price
« Reply #7 on: 26 Oct 2016, 05:31 »
hi
sorry for the late reply'
if you want to lay X higher or lower than the matched back price you would use
to lay at a lower price
and selections trigger expression lay_price is equal or less than r_ticks(bm_backp,-X)
to lay at a higher price
and selections trigger expression lay_price is equal or greater than r_ticks(bm_backp,X)

mcbee
Please read the following  disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

 

Please note, BetFair is seems to be currently OFFLINE