Kase Peak Oscillator, Kase CD and Kase Permission

Forums ProRealTime English forum ProBuilder support Kase Peak Oscillator, Kase CD and Kase Permission

Viewing 15 posts - 31 through 45 (of 46 total)
  • #74585

    Hi Bard, thanks for all these interesting documents about Cynthia Kase’s works and studies. The new version of the Dev Stop to be coded from MT5 is on my to-do list, don’t worry 🙂 I changed the featured image of your recent post with the new one you provided, thank you.

    #74603

    Thanks very much for doing that @Nicolas much appreciated.
    Can I / should I, repost the Kase Convergence Divergence code here in a new forum post? Maybe other members would like to take a look at it (and I will refer back to this url for readers to view Kase Research papers like the last pdf I posted)?

    Cheers
    Bard

    #74680

    You can repost it in this thread, since part of the topic title is Kase CD..

    #74796

    I managed to translate the MT5 code of Cynthia Kase Dev Stop, seems that we have the good version this time! I added it directly into the Library: Kase Dev Stop v3

     

     

    3 users thanked author for this post.
    #75453

    Hi,

    Would anyone like to take a look at coding the following from the top of this post/thread:?

    The combination of using both the Kase Peak Oscillator (already coded on this forum in the indicators section) and the Kase Convergence/Divergence indicator have solid statistical evidence in predicting market turns.

    2) Kase CD (Convergence/Divergence)

    3) Kase Permission Screen

    The Permissions Screener provides an easy visual on when to enter the market.

    The statistical reasons for using these indicators — apart from the fact the Kase Convergence/Divergence indicator actually draws lines showing when these occur, pls see green lines screenshot and the comparison of Kase indicators with the Stochastic and MACD indicator showing divergences —  are well explained in this presentation by the founder and designer of the indicators, the award winning market technician Cynthia Kase CMT.

    https://www.youtube.com/watch?time_continue=1&v=2h6zldXeTW0

    Kase was an energy trader and worked for Aramco consulting as a Director of Technical Analysis and Director of Risk Management.

    The screenshots shows the probabilities for an indicator signal predicting a market turn and preceding a turn using traditional indicators like the RSI and MACD and Kase’s indicators: The Peak Oscillator and the Kase CD indicator. The stats for the market moving to Kase Dev Stop 1 and 3 are also provided.

    “If there is a signal, there is a 71% chance that you will hit Dev Stop 1 using traditional indicators and a 75% chance if you use Kase indicators… for the big turns, so if you have a signal with a traditional indicator like the RSI and MACD there’s only a 28% chance you’re predicting an excursion to the third level stop (Dev Stop 3)… where with the Kase indicators there’s a 43.5% chance that you’re predicting a move to the third level stop (Dev Stop 3).” (Explained around the 25 min mark in the presentation link above).

    She then explains the probabilities of how often indicators precede turns. “Rather than looking at a signal and do I get a turn after it, I’m looking at turns then looking back to see how often I got a signal. Here the difference is much more dramatic.. (second stats screenshot), 55% (traditional indicators) versus 82% (Kase PO and Kase CD). What this mean is that you can rely on the Kase indicators to tell you there’s going to be a turn.”

    1 user thanked author for this post.
    avatar Bel
    #75460

    Kase Permissions Screenshot:

    1 user thanked author for this post.
    avatar Bel
    #75462

    Just found this one for Kase Peak and Kase CD in the same indi:

     

    #75478

    Thanks, but what made Kase’s Peak Osc and Con/Divergence indicators more accurate was their ability to adapt to changing cycle lengths, being logarithmic and be able to use a Serial Dependancy index.

    As an example from the code I posted at the top of this thread, I believe it’s this part of the code that covers the cycle length Nicolas:
    Ps// The code writer had been in touch with Kase)

    And this:

    Here’s a slide from her presentation where she writes out the features: (the scribble is Log P/P(n))

    Cheers
    Bard

    #78058

    Coding the Kase Convergence/Divergence indicator?

    Is there anyone that would like to convert Cynthia Kase’s Convergence/Divergence indicator?

    Kase has already statistically proven the validity of using her Kase Peak Oscillator (KPO) combined with the Convergence/Divergence (KCD) indicator and it out performs conventional indicators like RSI and MACD for picking out market turning points:
    http://www.kaseco.com/support/articles/Proof_That_Technical_Analysis_Really_Works.pdf

    Using the KPO and Kase’s Dev Stops have produced more profitable results — on many different currency pairs and also Brent Crude, the Dow and DAX, (just change which Dev Stop to use due to individual markets having their own volatility profile) — than any other system/indicators I’ve used on PRT including the stunning John Ehlers indicators.

    As @nicolas pointed out to me, the danger with mean reverting systems is that they can also potentially get you in on the wrong side of the trade resulting in wider movement against your position before the Dev Stop closes the position.

    When testing, look at the Maximum Adverse Excursion column figures in the Detailed Report to gauge validity. I have taken out the ADX > 25 part of the entry code to minimise complexity and help future results being less robust than back tests. The simpler the system with the less parameters the more robust it will be in the future.

    Please see screen shot for results on the (stable) Swissy (USD/CHF) usingi different time frames and Dev Stops:

    The code for the KPO is on this forum as is the code for the Kase’s Dev Stops is below (check out KRev (Reversal) Amounts too to calculate your monetary risk per trade per Dev Stop stop line).

    If anyone would like to add to this code below, maybe try different financial instruments or maybe add a trend filter or perhaps a Choppiness Index/Kaufman Efficiency Ratio – I haven’t had time yet – please feel free and post your results here.

    When adding a Trailing Stop results were sometimes better, sometimes worse.

    Thanks a lot,
    Bard

     

    #78063
    Fr7

    Hello Bard,

    Could you say the variables used in the Kase Peak indicator?

    en=p???
    len???
    smooth=c???
    nbdev??nbhigh??nblow???
    #78073

    Hi Fr7,

    I don’t recognise these variables?
    Try the latest version (V2) that Nicolas updated here:
    I left settings as standard.

     

    #78085
    Fr7

    this is different from what you say………………Could you say the variables used in the Kase Peak indicator?

    es = p ???
    len ???
    suave = c?
    nbdev ?? nbhigh ?? nblow ???
    #78092

    Thats version #1. Do NOT use it, it doesn’t work.

    Use the v2 I provided.

    Cheers
    Bard

     

    #91571

    I read the discussion about this really interesting system by Kase.

    Have Kase CD and Kase permission been coded for prorealtime?

     

     

    #91630

    Hi @ggolfet, currently just the Kase Peak Oscillator (KPO) has been coded, along with her Dev Stops. It’s a shame because only with the Convergence and Divergence indicator (KCD) being used in conjunction with the KPO – which has not been coded – can the statistically proven high probability entries be achieved. But to be fair, I believe it is a long a time consuming job to convert and I think Nicolas didn’t have the same feeling about these indicators as I did.

Viewing 15 posts - 31 through 45 (of 46 total)

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