Indicators: T3 floating levels (2)

[Automated-Trading]

T3 floating levels (2):

Updated T3 floating levels

Author: Mladen Rakic

[Cenk]

Hi Mladen,
Thanks you for new indicator!

So far I have used T3 and T3 variation many indicators to generate signals in different EA's.

The problem was the same in all; They are extremely demanding on system resources and extremely slowing down the current EA (MT5).

I would be pleased to hear if you have any suggestions for EA implementation regarding this issue, which I think is caused by the calculation method of T3 indicators.

[ruozhuo]

埃德维亚奥 ： 嗨，Mladen， 谢谢您提供新指标！

到目前为止，我已经使用T3和T3变体许多指标来生成不同的EA中的信号。

所有人的问题都是一样的。 他们 对系统资源的 要求极高 ，并且极大地降低了当前EA（MT5）的速度。

如果您提出问题有任何实施EA的建议，我很高兴听到，我认为这是由T3指标的计算方法引起的。

that's good! Looking forward to adding MTF.

[Mladen Rakic]

Edviao:
Hi Mladen,
Thanks you for new indicator!

So far I have used T3 and T3 variation many indicators to generate signals in different EA's.

The problem was the same in all; They are extremely demanding on system resources and extremely slowing down the current EA (MT5).

I would be pleased to hear if you have any suggestions for EA implementation regarding this issue, which I think is caused by the calculation method of T3 indicators.

I don't see any such issue. They use as little resources as possible (you can not calculate t3 with less resources in a meaningful way) and as far as calculation is concerned, tested that version and the initial calculation for 10.000 bars takes less than 1 millisecond

Here is a very simple test expert typed up in order to test the above indicator, and when you run it you shall see that it does not cause any slowdown (neither in visual nor in non-visual testing mode)

input string             inpIndicatorPath = "";         // Indicator path (if not in default folder))
input double             T3Period         = 25;             // T3 period
input double             T3Hot            = 0.7;            // T3 volume factor
   enum enT3Type
   {
      t3_tillson  = (int)true,  // Tim Tillson way of calculation
      t3_fulksmat = (int)false, // Fulks/Matulich way of calculation
   };
input enT3Type           T3Original      = t3_fulksmat;    // T3 calculation mode
input ENUM_APPLIED_PRICE T3Price         = PRICE_CLOSE;    // Average price
      enum chgColor
         {
            chg_onSlope,  // change color on slope change
            chg_onLevel,  // Change color on outer levels cross
            chg_onMiddle  // Change color on middle level cross
         };
input chgColor           ColorOn         = chg_onLevel;    // Color change on :
input int                FlPeriod        = 25;             // Period for finding floating levels
input double             FlUp            = 90;             // Upper level %
input double             FlDown          = 10;             // Lower level %

//------------------------------------------------------------------
//
//------------------------------------------------------------------
//
//
//

int _t3Handle;
void OnInit()
{
   _t3Handle = iCustom(_Symbol,_Period,inpIndicatorPath+"T3 floating levels (2)",T3Period,T3Hot,T3Original,T3Price,ColorOn,FlPeriod,FlUp,FlDown);
}

//
//
//

void OnTick()
{
   static datetime _lastChangedAt = 0;
   
   //
   //
   //
   
   double _values[];
   double _valuesCopied = CopyBuffer(_t3Handle,4,0,3,_values);
      if (_valuesCopied==3)
         {
            if (_values[0]!=_values[1] && _values[1]!=0 && _lastChangedAt!=iTime(_Symbol,_Period,1))
               {
                  Comment(StringFormat("trend changed at %s to %s",TimeToString(TimeCurrent(),TIME_DATE|TIME_MINUTES),(_values[1]==1?"up":"down")));
                  _lastChangedAt = iTime(_Symbol,_Period,1);
               }                  
         }
   return;
}

PS: the copy buffer was used on each tick on purpose in this example (just to make sure that there is no slowdown from the call). That can be easily further optimized (to reduce when the copy buffer was used, since I am testing first closed bar there)

[Cenk]

Thank you for the detailed explanation and sample code!

On the MT5 "Indicator" tester, I compared the performance values ​​with a few reference indicators in the "every tick" mode, and I can say that this version has "more acceptable" perfonmance results than the previous generation T3 family.

In the EA design I'm working on, I might consider giving T3 another chance with this release :)

[msnd47]

Hello to Mladen Rakic

Really in writing meta 4 and meta 5 tools

You are unique and very creative

I use most of your indicators

I demand

if possible

for me

RSI bands.mq5

Take the form of three levels

With levels;

Email 30-50-70

Thank you very much in advance

That you do this for me

I am waiting for your answer

***

[Mladen Rakic]

msnd47:

Hello to Mladen Rakic

Really in writing meta 4 and meta 5 tools

You are unique and very creative

I use most of your indicators

I demand

if possible

for me

RSI bands.mq5

Take the form of three levels

With levels;

Email 30-50-70

Thank you very much in advance

That you do this for me

I am waiting for your answer

***

You demand?

For demands please check here : https://www.mql5.com/en/job

[Andrei Iakovlev]

If 'T3 volume factor' is 1.01 and greater, all plots go off the scale. Is it ok?

[Andrei Iakovlev]

Andrei Iakovlev #:

If 'T3 volume factor' is 1.01 and greater, all plots go off the scale. Is it ok?

This is fixed here: https://www.forexfactory.com/thread/post/14170745#post14170745