Historic Relative Odds Condition

[BetScalper]

Hi,

Is it possible by using the Historic Relative Odds condition to capture selections that have only moved <= 6 ticks (Up or Down) in 60 seconds, if yes, how ?

Thanks,

[MemphisFlash]

try this.

6 ticks.PNG

that would give 6 tick movement one way.
then copy the rule and reverse for other way

[BetScalper]

try this.


6 ticks.PNG

that would give 6 tick movement one way.
then copy the rule and reverse for other way

Cheers,

[eightbo]

that'd capture prices which have come in 7 ticks or more vs. 60s ago

it sounded like you were looking for a way of identifying if a price has remained in a 6T range for the entire past 60s or not, no?

If so that would be an interesting problem I don't mind having a go at solving.

[BetScalper]

that'd capture prices which have come in 7 ticks or more vs. 60s ago

it sounded like you were looking for a way of identifying if a price has remained in a 6T range for the entire past 60s or not, no?

If so that would be an interesting problem I don't mind having a go at solving.

Ah yes, correct.

Basically i only want selections that have traded within a 6 tick range in the last 60 seconds. So if they have traded 7 ticks in the last 10 seconds then they should be ignored etc.

Thanks,

[eightbo]

I'll whip something up later.

[BetScalper]

I'll whip something up later.

[eightbo]

Not poss. with just the Historic Relative Odds condition. You can do like Memphis suggested and add/minus 3T to either side to make an artificial 6/7T range but if price drifts out between 60 and 0 the automation won't know. If it goes 4T either way it breaks the artificial range but would still be within the 6T range. Similarly 6T either way makes a 12T range and again it can break out and come back and your rules will still be firing.

I did the workings and it's possible using a few stored values to do everything properly.
It'd take some time to implement needing over 100 rules per selection. The reason it's so tricky is you need to work out the difference in ticks between any two prices which is really longwinded using just the Automation Rules Editor - no VLookups or match formulas here. You also need to use a different formula for the first 60sec compared with each update after that. But once you have the 60s cycling you're good to go.

You'll need to:
- Make a stopwatch signal that cycles through 1-60 (Clear signal @ 60s — make sure the rule's below any rules you want to fire on the 60th second)
- Store Min/Max LTP values for the first 60 seconds (update Min/Max with LTP if LTP < Min / LTP > Max)
- Use stored values named LTP60, LTP59, LTP58 through to LTP1 for the last 60s price cycle (match up with Stopwatch 1 through 60)
- After 60s has passed, start updating Min/Max values if LTP is lower than the Min / higher than the Max of all LTP60-LTP1 values.
- Lastly to calculate the difference in ticks between the Min & Max price for the last 60s you'll need to check if LTP is within 1.01-1.99, 2.00-2.98 etc. before doing your calculation (duplicate rules for each range) and then do further ghetto calculations to arrive at the number you need.
  Take LTP and depending on the price range...
  1.00 - 1.99: divide by 0.01 then minus 100
  2.00 - 2.98: divide by 0.02
  3.00 - 3.95: divide by 0.05 then plus 90
  4.00 - 5.9: divide by 0.1 then plus 130
  6.00 - 9.8: divide by 0.2 then plus 160
  10.0 - 19.5: divide by 0.5 then plus 190
  20 - 29: divide by 1 then plus 210
  30 - 50: divide by 2 then plus 225
  ...That will allow you to do Max minus Min to find the difference in ticks & quantify the size of the range (e.g. 9.6 to 11.5 = 5 Tick dif.)
  ...You then need to plus 1 to the answer (e.g. 2.62 - 2.62 is a 1 Tick range) to arrive at RangeInTicks
 - Then, at last, you can place your bets if RangeInTicks < 7 ... hah

Another thing to note is that even after doing all of that, if a price is slowly shortening/drifting, it can still be trading inside a 6 Tick range for the last 60s, so you'd probably want to check which is happening and back/lay first as appropriate.

[Atho55]

Would it be possible by using HRO condition to trigger an incremental counter via Signals every second, bet to place when value > 60 type thing

[Dallas]

If you're prepared to use fixed time points in some form then it's not to difficult to set up,

ie, at 5mins to post store the LTP then at 4mins to post trigger a bet/s if it's not moved X ticks +/- during that time.

Also at 4mins to post store the LTP again then repeat above and trigger bet/s if its not gone X ticks +/- when 3mins to post

and so on.....