How Do You Optimise Bands Based on Price?:

• 08/02/2018 at 12:53 AM #77380
  Bard

  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

  

  Bard

  Participant

  Topics: 138

  Replies: 814

  Been thanked: 99 times
  08/16/2018 at 3:00 PM #78390
  Nicolas

  Just optimize any or all the settings from the indicator, which are:

  inpDesPeriod  = 20          // Dev-stop period

  inpSlowPeriod = 21          // Dev-stop slow period

  inpFastPeriod = 10          // Dev-stop fast period

  inpStdDev1    = 0.0         // Deviation 1

  inpStdDev2    = 1.0         // Deviation 2

  inpStdDev3    = 2.2         // Deviation 3

  inpStdDev4    = 3.6         // Deviation 4

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
• Author
  Posts