Hi

How you would optimise bands based on price like the Kase Dev Stops when using it in a system?
(Dev Stop = Std Deviation Stop based on ATR that’s overlaid on the Price Chart).

It’s not like I am able to optimise values eg: of between -1 and +1 by increments of 0.1 on an indicator like the Ehlers Supersmoother Oscillator — because the Dev Stops ATR bands (or ATR or Error Bands or that matter) are on the price chart and are not bound, they are  “fluid” in their  values?
I know it can be done as a user on this forum did mention they’d optimised values and found that Dev Stop values of >4 and <5 worked best.

Any ideas greatly appreciated.

When I get more time I will post the results of this system that uses the Dev Stop because to date this combination of entry Oscillator and exit Dev Stops has worked better on more assets than anything else I’ve worked on in the last 2 years – including the sometimes spectacular and then other times not so reliable John Ehlers Oscillators. I did send you an email @nicolas about the results – but think I sent it to PRT support instead. I will resend.

https://www.prorealcode.com/prorealtime-indicators/kase-dev-stop-v3/

Cheers in advance for any help or suggestions,
Bard