Page 20 of 66

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 5:42 am
by Chickenspicy
mrtools wrote: Wed Dec 07, 2022 5:39 am The link is not working.
Ahh never mind
I also found one looking exactly identical

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 8:26 am
by Chickenspicy
Was too good to be true sadface
Ut bot/ Linear regression candle
Only looks profitable

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 8:35 am
by mrtools
moey_dw wrote: Tue Dec 06, 2022 10:55 pm Man lovely work Mrtoolz & Jacks....... good channel indicator & it is working superb thx guys!!!
Also don't forget Nwesterhuijs and Kvak they both got the ball rolling.

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 11:15 am
by kvak
mrtools wrote: Tue Dec 06, 2022 7:32 pm HIGH and LOW Optimized Trend Tracker HOTT LOTT

The HOTT LOTT is based off Anıl Özekşi's OTT - Optimized Trend Tracker.

This particular version has two lines of Optimized Trend Tracker which uses the HIGHEST price values (HOTT) and LOWEST price values (LOTT). The difference with this version is that the OTT uses a CLOSE price.

Guys I don't think this part is right for the upper channel

Code: Select all

if (MaType==ma_vidya)  valH[i]        = iVidya(MathMax(iHigh(NULL,0,iHighest(NULL,0,(int)PriceH,HLPeriod,i)),iHigh(NULL,0,iHighest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,VidyaSmoothPeriod,i,0);
      else  valH[i]        = iCustomMa(MaType,MathMax(iHigh(NULL,0,iHighest(NULL,0,(int)PriceH,HLPeriod,i)),iHigh(NULL,0,iHighest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,i,Bars,0);
and this for the lower channel

Code: Select all

if (MaType==ma_vidya)  valL[i] = iVidya(MathMin(iLow(NULL,0,iLowest(NULL,0,(int)PriceH,HLPeriod,i)),iLow(NULL,0,iLowest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,VidyaSmoothPeriod,i,1);
	  else valL[i] = iCustomMa(MaType,MathMin(iLow(NULL,0,iLowest(NULL,0,(int)PriceH,HLPeriod,i)),iLow(NULL,0,iLowest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,i,Bars,1);

I did something like this

Code: Select all

double hi   = high[ArrayMinimum(high,HLPeriod,i)];
      double lo   =  low[ArrayMinimum( low,HLPeriod,i)];
         wrk[r].valH = iCustomMa(MaType,hi,MaLength,i,rates_total,0);
         wrk[r].valL = iCustomMa(MaType,lo,MaLength,i,rates_total,1);
unless I am missing something please let me now, anyway, did a version too.
Image
Thank you for your valuable advice Mrtools...
I haven't finished it yet.....I still need to finish your logic for the candles....
I enjoy watching your work :)

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 2:24 pm
by mrtools
chickensword wrote: Wed Dec 07, 2022 8:26 am Was too good to be true sadface
Ut bot/ Linear regression candle
Only looks profitable
This is the linear regression candles; think I need more information on the UT Bot.

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 2:30 pm
by Chickenspicy
mrtools wrote: Wed Dec 07, 2022 2:24 pm This is the linear regression candles; think I need more information on the UT Bot.
Image
Thank you!, I found them almost like heikin smoothed

I have no idea what Ut bot is made of either, it’s atr and then something else I don’t know if it’s an average of something
Like the supertrend or step averages

Looks like Ema cross atr stop

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 2:42 pm
by Chickenspicy
Like this

If you put two moving averages it makes more sense I put 2Demas with adaptive advanced atr stop

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 2:53 pm
by Chickenspicy
The other way around looks better

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 3:40 pm
by nwesterhuijs
mrtools wrote: Tue Dec 06, 2022 7:32 pm HIGH and LOW Optimized Trend Tracker HOTT LOTT

The HOTT LOTT is based off Anıl Özekşi's OTT - Optimized Trend Tracker.

This particular version has two lines of Optimized Trend Tracker which uses the HIGHEST price values (HOTT) and LOWEST price values (LOTT). The difference with this version is that the OTT uses a CLOSE price.

Guys I don't think this part is right for the upper channel

Code: Select all

if (MaType==ma_vidya)  valH[i]        = iVidya(MathMax(iHigh(NULL,0,iHighest(NULL,0,(int)PriceH,HLPeriod,i)),iHigh(NULL,0,iHighest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,VidyaSmoothPeriod,i,0);
      else  valH[i]        = iCustomMa(MaType,MathMax(iHigh(NULL,0,iHighest(NULL,0,(int)PriceH,HLPeriod,i)),iHigh(NULL,0,iHighest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,i,Bars,0);
and this for the lower channel

Code: Select all

if (MaType==ma_vidya)  valL[i] = iVidya(MathMin(iLow(NULL,0,iLowest(NULL,0,(int)PriceH,HLPeriod,i)),iLow(NULL,0,iLowest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,VidyaSmoothPeriod,i,1);
	  else valL[i] = iCustomMa(MaType,MathMin(iLow(NULL,0,iLowest(NULL,0,(int)PriceH,HLPeriod,i)),iLow(NULL,0,iLowest(NULL,0,(int)PriceL,HLPeriod,i))),MaLength,i,Bars,1);

I did something like this

Code: Select all

double hi   = high[ArrayMinimum(high,HLPeriod,i)];
      double lo   =  low[ArrayMinimum( low,HLPeriod,i)];
         wrk[r].valH = iCustomMa(MaType,hi,MaLength,i,rates_total,0);
         wrk[r].valL = iCustomMa(MaType,lo,MaLength,i,rates_total,1);
unless I am missing something please let me now, anyway, did a version too.
Image
Thank you MrTools and Kvak for picking up on this. I had indeed corrected already some errors since then but was still aiming to debug more before posting an update.

Only saw your efforts this morning (after the daily download mention) and I yet need to drop it on a chart this evening, but MrTools can you check 1 thing:

You indicated you have incorporated the iVidya into the iCustomMa call, which sounds fine but you provide the following code:

Code: Select all

      double hi   = high[ArrayMinimum(high,HLPeriod,i)];
      double lo   =  low[ArrayMinimum( low,HLPeriod,i)];
         wrk[r].valH = iCustomMa(MaType,hi,MaLength,i,rates_total,0);
         wrk[r].valL = iCustomMa(MaType,lo,MaLength,i,rates_total,1);
Pls confirm but I reckon the High should be looking for the maximum and therefore look like this:

Code: Select all

      double hi   = high[ArrayMaximum(high,HLPeriod,i)];
      double lo   =  low[ArrayMinimum( low,HLPeriod,i)];
         wrk[r].valH = iCustomMa(MaType,hi,MaLength,i,rates_total,0);
         wrk[r].valL = iCustomMa(MaType,lo,MaLength,i,rates_total,1);
Also curious how the VidyaSmoothPeriod is handled now that the Vidya is incorporated in the iCustom call. Will see that tonight.

Furthermore, and again I need to see how it is handled this evening when I drop the indie on a chart, but I think it is lost in this latest version given that you are calling the arrays "high" and "low" which normally means you have replaced the "start"-function by the "OnCalculate"-function, which in turn would mean that the HOTTLOTT has lost the functionality (at least the one I added) of using the open and close as well as the high and low to create the channels. Is this deduction correct?

Nonetheless thank you both for pushing this one along quicker than I have managed thus far, much appreciated.

Cheers, Norbert

Re: Already Converted TradingView Indicators to MT4 Indicators

Posted: Wed Dec 07, 2022 4:22 pm
by Chickenspicy
Darks wrote: Tue Sep 13, 2022 4:19 am Added more features to the Range Filter
Image