Less/Greater than OR Equal to

[MLDGM]

Hi,

I'm looking to place a bet just after the off if the price of a horse is between X and Y.
e.g:
Place back bet if horse is priced between 3.30 and 3.50
Take best offered price
Trigger once as near to the off as possible

I've been testing and found that in Guardian Automation - rules - 'Conditions', I can't have Actual SP <3.50 and =3.50, the trigger simply doesn't fire. I'm guessing that's because the '= condition' is overriding the '< condition'.
(It seems I can't have the option to have <= or >= [less than/equal to - greater than/equal to])

I hope this is clear.
In other words, I would like to have the conditions to be:
Place back bet if:
Actual SP <=3.50
Actual SP >=3.30

Is there a way to do this?
Does this mean the same thing?:
Place back bet if:
Actual SP <3.50
Actual SP >3.30

Or will I have to set my conditions just outside; e.g:
Place back bet if:
Actual SP <3.55
Actual SP >3.25

Also If I did this and the SP is 3.28/3.54 will my bet get taken?
I'm not sure how bet angel has the SP, but on betfair the SP may be inbetween odds. This is crucial as I'm using % differences to determine what price the SP needs to be, e.g: 3.30 - 3.52 --- (in this instance, I wouldn't want to be if SP was 3.54 but having <3.55 as a condition I would be taking the bet as it actually does fall inbetween 3.25 and 3.55)


----

I do hope this is clear, I tried to be as clear as possible.
I also hope somebody can help me with this, I'd love to use the automation.

Thanks in advance

[ShaunWhite]

All Guardian conditions are ANDed, you need to test for

Actual SP <3.55
and Actual SP >3.25

That will trigger for all values of SP from 3.251 -> 3.549

There's no guarentee that any bet will be taken but you will never get worse odds if it, or part of it, is.

[MLDGM]

Thanks for the quick reply.

To clarify, 1. there's no inbetween odds on BetAngel for SP? and 2. I will need to set the odds outside of what I want: I want 3.30-3.50, need to set 3.25-3.55?

Just clarifying for ease of mind, cheers again

[ShaunWhite]

Try running this over a few hundered races, you'll see that those odd 10ths of a percent won't be the biggest problem. Getting matched will no doubt be a much bigger issue.

[MLDGM]

I have also thought of another way around, possibly.

Place three rules files for each horse selected:
1:
Actual SP <3.5
Actual SP >3.3

2:
Actual SP =3.5

3:
Actual SP =3.3

What I wouldn't want to happen is have the bet fire off twice if 3.5 was the SP

[MLDGM]

I will be doing, thanks. I may be overthinking this all ha, this is the first automation I'm trying out but I was wondering how accurate I could get it.

Overtime, I wouldn't miss that many and probably wouldn't have a major downfall from that but I'm a bit particular. Also curious as to how far BetAngel can go and whether I can get exactly what I want from it, or have to go a backwards route.

Getting matched is step 2.

Cheers for the help

[ShaunWhite]

BA knows about the inbetween odds/the Actual SP, but testing that it's above or below a 'normal' tick is more than adequate in the real world...even if it isn't in the idealised world of spreadshhets and data.

edit...I assume BA rounds the BF SP to the nearest tick for comparisons.