Very Latest John Ehler's Correlation Trend Indicator

Forums ProRealTime English forum ProBuilder support Very Latest John Ehler's Correlation Trend Indicator

Viewing 15 posts - 16 through 30 (of 32 total)
  • #129599

    If the returned value is only ever between -1 and 1 then simply add 1 then divide by 2 then multiply by 100.

     

    #129617

    Hola Vonasi

    Where can i place this parameters into the code ? I don’t know where

    thanks you

    #129619

    Just add the following above the return line.

     

    #129625

    Gracias Vonasi , viva la Pepa !!!

    code and graph attached

     

    #129630

    supertiti – It is better if you post an ITF file of the code that you have exported from the platform and a PNG file of the image rather than a DOCX for people to have to download.

    #129741

    Hi Bard, you have posted in the library but without the itf file. If I understand well, you want the code from the above post: https://www.prorealcode.com/topic/very-latest-ehlers-correlation-trend-indicator-2/#post-129559 to be featured in the library, right? Thanks.

    #129757

    For French traders Open office is free

    https://www.openoffice.org/fr/

     

     

    #129778

    For French traders Open office is free

    It is not about cost – it is about convenience for all forum members. ITF files can be saved and then directly imported into anyone’s PRT platform. PNG images when attached can be viewed with just one click. Code inserted into a post can be cut and pasted quickly and easily.

    #130232

    Hi @Supertiti, the Long and Short values need to be different. I added “S” and “L” so it doesn’t read Sx= 0 but Sum”S”x = 0, etc so that it can plot two periods for the CTI.

    #130333

    Hi Nicolas, great, thanks, sorry yes I only posted the new CTI system and Dev Stop itf.
    Yes please use the code in the link mentioned:

    https://www.prorealcode.com/topic/very-latest-ehlers-correlation-trend-indicator-2/#post-129559

    Thanks again for your help,  always appreciated.

    Looking good so far using Juanj’s Machine Learning code on the 5 and 10 period crosses and using ML on the CTI thresholds. About to turn the ML code on the period settings next…
    Cheers!

    #130416

    Hi @Nicolas, well, after a few hours I can’t get the machine learning (ML) code to work out the best value for the Ehler’s CTI Speriod and Lperiod of this new indicator.

    Typically when a ML system won’t work and the code is good (comparing an already working ML system with the non working one using a text-compare website) it’s the settings that the ML code works through — from Starting value to Max value etc — that aren’t working, but I already know a cross over of the 5 period and 10 period CTI are good for long positions and vice versa for shorts. I just want to find out if a 3 and 7 for example are better – I will see this from graphing Value X and Y.

    I can get the ML to work on a Ehler’s CTI system that looks for the best ML chosen thresholds of the CTI (graphing of  X and Y thresholds in increments of 0.1 plots okay on the variables chart with static CTI periods of 5 and 10, — which work well).

    Can you see from the screenshots below what is missing? The ML settings simply ask the ML algo to choose between CTI periods of 1 to 10 days for both the SPeriod short red CTI line and the LPeriod blue CTI line.

    Btw, I did re-read the lengthy post: https://www.prorealcode.com/topic/how-do-you-optimise-atr-stops-around-price
    again just to be sure I have done everything right in terms of labelling even though this is not a PRT optimisation but a ML algo coded “optimisation.” I hope this isn’t going to bring you out in a cold sweat!? 😅  Cheers!

    #130438

    Did you GRAPH the CALLed variables in a backtest to see if the indicator is computing correctly? First step for debugging!

    #130452

    Good morning all,

    scale from 0 to 100


    I would like to do a screener where:

    C1 = CTI short [1] < 30
    C2 = CTI short crosses over CTI long

    Short term strategy: when you have the result sell above 95
    thank you

     

     

    #130463

    Yes, I think so!? Screenshot 2!?
    I also tried, as is the normal way to use ML code in a system, with my ValueX and ValueY in the Call line “indicator name” [5, 10] as in: “indicator name” [ValueX and ValueY].
    Neither that way or using “indicator name”[SPeriod, L Period] works?

    #130498

    Good evening,

    I think this screener code is the right one after several tries.

    Each will modify the parameters to their liking.

     

     

     

Viewing 15 posts - 16 through 30 (of 32 total)

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