Optimisation of ATR Dev Stops

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #76092 quote
    BardBard
    Participant
    Master

    Hi
    (Reposting as I can see no trace of this question when originally posted this morning)

    How you would optimise the Kase Dev Stop when using it in a system? (Dev Stop = Std Deviation Stop based on ATR).

    It’s not like I am able to optimise values eg: between -1 and +1 by increments of 0.1 on a custom indicator like the Ehlers Supersmoother Oscillator — (it’s on this forum, and -0.8 cross-overs to buy and + 0.8 cross-unders to sell are good values btw), — because the Dev Stops ATR bands are on the price chart and are not bound, they are  “fluid” in their ATR 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?

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

    Cheers for any help or suggestions,

    Thanks
    Bard

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.
ProRealAI ProRealAI New

Stuck on this ProBuilder code?

Describe what this topic is trying to build, in plain English, and ProRealAI writes the ProRealTime™ indicator, screener or system for you.

Available in 7 languages
Try ProRealAI

Optimisation of ATR Dev Stops


ProOrder: Automated Strategies & Backtesting

New Reply
Author
author-avatar
Bard @brad Participant
Summary

This topic contains 1 voice and has 0 replies.

Topic Details
Forum: ProOrder: Automated Strategies & Backtesting
Language: English
Started: 07/16/2018
Status: Active
Attachments: No files
ProRealCode ProRealCode
Loading...