Stop Belkhayate Indicator Repainting

Forums › ProRealTime English forum › ProBuilder support › Stop Belkhayate Indicator Repainting

  • This topic has 4 replies, 2 voices, and was last updated 5 years ago by avatarBard.

Tagged: ,

Viewing 5 posts - 1 through 5 (of 5 total)
  • 02/26/2019 at 5:35 PM #92390
    Bard

    Hi Nicolas,

    Because you’re English is very good I might have a chance here in the UK forum to understand your last Italian to English reply.
    Re: The Belkhayate Indicator and the DPO and past data: ( https://www.prorealcode.com/topic/center-of-gravity/page/2/#post-92378 )

    I would like to know if the Belkhayate indicator that uses the DPO can be modified to prevent or minimise the redrawing problem which changes the information it is displaying about past data as new data comes in, as per:

    https://www.prorealcode.com/topic/dpo/#post-8862

    https://www.prorealcode.com/topic/detrended-price-ocillator/#post-8266

    I think I get that you’re saying it can’t be modified but I’m not sure why now as I’m now confused by the post ==> #8862 and that the DPO can be calculated using future or past data?

    (From the Italian forum reply you’re reply was difficult to fully understand:

    “just use the money”?

    Bard Sorry, I think you have not understood what I explained in my previous post.
    The Belkhayate indicator uses the same DPO, the ProRealTime version uses the DPO indicator and reversed to know the price of the future (because the data protection agent knows this). Therefore, it is not logical to use the DPO of the data passed in this case, just use the money and you will get a similar channel to many others on the web site.
    The center of gravity is popular because it surprised everyone as to its accuracy by knowing the future? Then change its formula would use any other channel indicator! )

    Re: De-trending data, from the DPO page: https://www.prorealcode.com/documentation/dpo/

    Then it is necessary to move back the data of this average of n/2+1) days ago.

    I don’t see the point of the “+1” because the data is already half the “n” value i.e. it’s been pulled right back into the past by the n/2 and so is not at the current “n” value.

    I just hoped that those Belkhayate bands could be made to be more realistic and not such an amazing fit with the past (even if the current version of the indicator does give you a great sense of the current trend and it’s impending flattening or reversal).

    Saluti! (This was an attempt to use the Italian for “Cheers” but the website converted it, I had no idea… I’ve been copying and pasting from Google translate!)

    02/28/2019 at 11:13 AM #92512
    Nicolas

    If you want a non repainting COG, just add standard deviation bands (multiplied by the golden ratio) to a linear regression of the same period. The COG is similar to any other channels, the Belkahyate version had gain popularity because it was accurate on history due to its repainting behavior. So, asking for a non repainting version makes no sense since it will be like any other price channel, a mean with upper and lower bands.

    02/28/2019 at 7:34 PM #92558
    Bard

    Right, got it, thanks for taking the time to clarify. 

    Belkhayate’s “accuracy”… you must have been around long enough to have seen it all! 😁

    I’ll see if I can “add standard deviation bands (multiplied by the 1.618 golden ratio) to a linear regression” with my “cut and paste” coding skills..

    …Didn’t end up looking like I expected, the bands are very wide?

     

    03/01/2019 at 9:32 AM #92604
    Nicolas

    Because the standard deviation is calculated with totalprice while we want to know the std of the difference between the totalprice and the mean of the channel instead (that linear regression ..). Here is the code modified:

     

    1 user thanked author for this post.
    avatar atxeel
    03/01/2019 at 6:57 PM #92661
    Bard

    Nice one, thanks Nicolas.

    I’ve cleaned up some of my code labels, band colours and added 2.2 and 3.6 standard deviations to reflect probability distribution reality, i.e. Cynthia Kases’ skew found after empirical research on past market data:

    When these bands narrow, be warned. (See GBP/Yen screenshot with overlay of a 30 day Bollinger at 3.6 Std Devs for comparison).

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
sell at x stop / exitshort at x stop for a specific quantity
trailing stop on ib – stop repositioning on dax
adding a stop & pt to an existing order
atr based stop not working
atr stop active after reaching a target
atr stop not working
atr take profit and stop loss
auto stop error
belkhayate center of gravity conversion
default limit and stop loss settings

Create your free account now and post your request to benefit from the help of the community
Register or Login