condition not working

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

hi
if your variable gt2,is set to 2 then this is ok.
and you are correct that you do need a new condition for greater than 2
in the same block as the gt2 condition and after the gt2, you need
and selections back price is equal or greater than 2.00

mcbee

Hi mcbee,
the gt2 is a constant relating to 'ticks' dropping before
a lay bet is placed.
in the conditions section of the trigger I have:
and selection's back price is equal or greater than 2.00.
Am I supposed to add a the price condition to the formula
in the body of the trigger block ? I'm not sure how to do that.
thanks
R

hi
it might be easier if you include your trigger, then i can tell you exactly what you need to do.

mcbee

hi mcbee,
hope this works
R

hi mcbee,
Any news re what I need to do ?
Thanks
R

Sorry to butt in, I am probably telling you what you already know, but the condition

Favourite's back price is greater than r_ticks(lay_price, -2)

means back price is greater than lay price minus two ticks. so if the lay price is 1.81 it would fire if the back price is greater than 1.79.

If you want to say also that the back price is greater than 2.00 then why not just add that condition to the trigger?

hi racepro
after many hours of testing, i managed to recreate your problem for betting below the 2.00 price.
the reason been, your first bet was placed at 1.84 back price and matched, all ok.
then the prices altered very quickly over a short time, to above the 2.00 price.
so your triggers as you have set them with the formula r_ticks(bm_backp,-gt2) = a lay bet of 1.79, so 1.84 - 5 ticks(your setting)=1.79 and the bet got matched, ALL because the price went above the 2.00, BUT you have set your trigger to bet at 5 ticks less than the back matched price.

mcbee

hi alfaman,
thanks for your reply. The condition you suggested was already added. I changed it from back to lay ( as shown in attached trigger) but should make little difference.
see my first email
Hi,
I put a condition in the greening up triggers
and selection's back price is equal or greater than 2.00.
R

hi mcbee,
I would have thought the condition 'and selection's back price is greater then 2.00'
would have the last say as to whether the trigger fires.
If that is not the case, how should the trigger be written to ensure no lay bets are placed at less than 2.00 ?
Thanks for your patience on this one
R

hi
you are correct, the condition 'and selection's back price is greater then 2.00' , does have the last say.
but the problem was, your selection was true for all your conditions, including the greater than 2.00.
it was your price formula that placed the bet below 2.00, because your back bet was placed at 1.84, so when all the conditions were correct/true, the trigger sent a bet out at 5 ticks less than the back matched price of 1.84=1.79.
if you do not want to lay less than 2.00, then have a formula , IF(lay_price<2.00,2.00,r_ticks(bm_backp,-gt2))

mcbee

Hi racepro
What mcbee is saying is that the condition is working.
The greening trigger will not activate if the back price is less than 2.00
However
the formula in the price box is telling it to lay at gt (5) ticks below back matched price, which may be less than 2.00.

An IF formula might help here in the price box:
IF(r_ticks(bm_backp,-gt)<2.00,lay_price,r_ticks(bm_backp,-gt))

Edit: this reply refers to reply #7

Hi Mark,

Thanks for the formula, I can write if/and/or in Excel but get a bit lost with the
coding in MFP. That looks good, I'll test it out.
R

condition not working

Hello Guest