Multi Timeframe Indicators - page 18

New comment
 

Forex_Off_Trend Oscillator

One of the most accurate Oscillators to determine trend change i.m.o. is the

Forex_Off_Trend Oscillator. The latest version I received last week is called the ForexTrend_v2 which is a Histogram version. I was very excited about this development, but the new one is not good at all. It repaints terribly, but if we can fix it, it could be a very good adjunct as a MTF-oscillator.

I am attaching both here with a request that you look at it and if you can put it into a MTF format, I would be very glad. The histogram format is excellent so that one can narrow the window and still see at a glance when the direction is changing.

Looking forward to hearing from you guys. Thanks in advance and best wishes.

 

offtrend

looks like basicly the same code to me with histo code and the default SSP number changed. may just wanna call that one histo or something instead of v2 imho.

A little more seperation helps me for quick glances

else

{

ExtHBuffer1=0;

ExtHBuffer2=-1 //<----

and here is some timeframe crap

as usual beware of redrawing problems

//+------------------------------------------------------------------+

//| Copy and Pasted by Lowphat |

//| |

//+------------------------------------------------------------------+

#property copyright " "

#property link " "

#property indicator_separate_window

#property indicator_buffers 2

#property indicator_color1 Lime

#property indicator_color2 Red

#property indicator_maximum 1

#property indicator_minimum -1

extern int TimeFrame=30;

extern int SSP=7;

extern double Kmax=50.6;

double ExtMapBuffer1[];

double ExtMapBuffer2[];

int init()

{

SetIndexStyle(0,DRAW_HISTOGRAM,EMPTY,2);

SetIndexBuffer(0,ExtMapBuffer1);

SetIndexStyle(1,DRAW_HISTOGRAM,EMPTY,2);

SetIndexBuffer(1,ExtMapBuffer2);

switch(TimeFrame)

{

case 1 : string TimeFrameStr="Period_M1"; break;

case 5 : TimeFrameStr="Period_M5"; break;

case 15 : TimeFrameStr="Period_M15"; break;

case 30 : TimeFrameStr="Period_M30"; break;

case 60 : TimeFrameStr="Period_H1"; break;

case 240 : TimeFrameStr="Period_H4"; break;

case 1440 : TimeFrameStr="Period_D1"; break;

case 10080 : TimeFrameStr="Period_W1"; break;

case 43200 : TimeFrameStr="Period_MN1"; break;

default : TimeFrameStr="Current Timeframe";

}

string short_name;

short_name=("FxTrend("+TimeFrame+")");

IndicatorShortName(short_name);

SetIndexLabel(0,short_name);

}

//----

return(0);

int start()

{

datetime TimeArray[];

int i,limit,y=0,counted_bars=IndicatorCounted();

// Plot defined time frame on to current time frame

ArrayCopySeries(TimeArray,MODE_TIME,Symbol(),TimeFrame);

limit=Bars-counted_bars;

limit=Bars-counted_bars;

for(i=0,y=0;i<limit;i++)

{

if (Time<TimeArray[y]) y++;

ExtMapBuffer1=iCustom(NULL,TimeFrame,"ForexTrend Histo",SSP,Kmax,0,y);

ExtMapBuffer2=iCustom(NULL,TimeFrame,"ForexTrend Histo",SSP,Kmax,1,y);

}

return(0);

}
 
lowphat:
looks like basicly the same code to me with histo code and the default SSP number changed. may just wanna call that one histo or something instead of v2 imho.

A little more seperation helps me for quick glances

else

{

ExtHBuffer1=0;

ExtHBuffer2=-1 //<----

and here is some timeframe crap

as usual beware of redrawing problems

//+------------------------------------------------------------------+

//| Copy and Pasted by Lowphat |

//| |

//+------------------------------------------------------------------+

#property copyright " "

#property link " "

#property indicator_separate_window

#property indicator_buffers 2

#property indicator_color1 Lime

#property indicator_color2 Red

#property indicator_maximum 1

#property indicator_minimum -1

extern int TimeFrame=30;

extern int SSP=7;

extern double Kmax=50.6;

double ExtMapBuffer1[];

double ExtMapBuffer2[];

int init()

{

SetIndexStyle(0,DRAW_HISTOGRAM,EMPTY,2);

SetIndexBuffer(0,ExtMapBuffer1);

SetIndexStyle(1,DRAW_HISTOGRAM,EMPTY,2);

SetIndexBuffer(1,ExtMapBuffer2);

switch(TimeFrame)

{

case 1 : string TimeFrameStr="Period_M1"; break;

case 5 : TimeFrameStr="Period_M5"; break;

case 15 : TimeFrameStr="Period_M15"; break;

case 30 : TimeFrameStr="Period_M30"; break;

case 60 : TimeFrameStr="Period_H1"; break;

case 240 : TimeFrameStr="Period_H4"; break;

case 1440 : TimeFrameStr="Period_D1"; break;

case 10080 : TimeFrameStr="Period_W1"; break;

case 43200 : TimeFrameStr="Period_MN1"; break;

default : TimeFrameStr="Current Timeframe";

}

string short_name;

short_name=("FxTrend("+TimeFrame+")");

IndicatorShortName(short_name);

SetIndexLabel(0,short_name);

}

//----

return(0);

int start()

{

datetime TimeArray[];

int i,limit,y=0,counted_bars=IndicatorCounted();

// Plot defined time frame on to current time frame

ArrayCopySeries(TimeArray,MODE_TIME,Symbol(),TimeFrame);

limit=Bars-counted_bars;

limit=Bars-counted_bars;

for(i=0,y=0;i<limit;i++)

{

if (Time<TimeArray[y]) y++;

ExtMapBuffer1=iCustom(NULL,TimeFrame,"ForexTrend Histo",SSP,Kmax,0,y);

ExtMapBuffer2=iCustom(NULL,TimeFrame,"ForexTrend Histo",SSP,Kmax,1,y);

}

return(0);

}

Thanks for your reply Lowphat, but as I am not a programmer, it makes very little sense to me unfortunately. - I agree with your sentiments regarding the V2 = Histogram.

Any further suggestions, please?

 

here ya go bud

i havent had time to test it but i think it should be ok

 
ValeoFX:
One of the most accurate Oscillators to determine trend change i.m.o. is the

Forex_Off_Trend Oscillator

. The latest version I received last week is called the ForexTrend_v2 which is a Histogram version. I was very excited about this development, but the new one is not good at all. It repaints terribly, but if we can fix it, it could be a very good adjunct as a MTF-oscillator.

I am attaching both here with a request that you look at it and if you can put it into a MTF format, I would be very glad. The histogram format is excellent so that one can narrow the window and still see at a glance when the direction is changing.

Looking forward to hearing from you guys. Thanks in advance and best wishes.

Sorry to say so but I don't understand that you can make such a statement. It repaints the past up to 6 bars...and you call this one of the most accurate indicators to determine trend ?!?!....It has even beaten the accuracy of the Yu4rik indicator....

regards..iGoR

Files:
forex2.zip  119 kb
 
iGoR:
Sorry to say so but I don't understand that you can make such a statement. It repaints the past up to 6 bars...and you call this one of the most accurate indicators to determine trend ?!?!....It has even beaten the accuracy of the Yu4rik indicator.... regards..iGoR

Igor, the repainting may be so, however, in realtime it is very accurate. So one cannot backtest it either.

Now regarding your statement that it has "even beaten the accuracy of the Yu4rik", are you saying that it is more accurate than the Yu4rik? Sorry, but I am a little confused here.

 
lowphat:
here ya go bud i havent had time to test it but i think it should be ok

Much appreciated, Lowphat. I will test it diligently and report back to you.

Best wishes.

 

Last few bars are keeping changing color, it can be sure make you lose maney.

 
ValeoFX:
Igor, the repainting may be so, however, in realtime it is very accurate. So one cannot backtest it either. Now regarding your statement that it has "even beaten the accuracy of the Yu4rik", are you saying that it is more accurate than the Yu4rik? Sorry, but I am a little confused here.

In real time it repaints the past up to 6 bars. So that means if you would place this indicator on a day chart it can repaint the past up to 6 days.

In my zip folder you can see what it did in real time. If you have an indicator who repaints the past only with 1 bar it is uselles.

Working with an indicator like that is the same as you say ....I WOULD HAVE go long 6 bars ago (but that is after the facts) and a bit later you would say I WOULD HAVE exited 6 bars ago.

This way you WOULD HAVE a 100% hitrate....

The YU4rik indicator is also uselles because it repaints up to 4 or 5 bars ago. So when I said it has beaten the YU4rik that means it is even more unreliable.

That indicator is like an MA that you would shift back in time (hindsight).

So that indicator is not accurate iit is cr*p.

regards...iGoR

 
iGoR:
In real time it repaints the past up to 6 bars. So that means if you would place this indicator on a day chart it can repaint the past up to 6 days.

In my zip folder you can see what it did in real time. If you have an indicator who repaints the past only with 1 bar it is uselles.

Working with an indicator like that is the same as you say ....I WOULD HAVE go long 6 bars ago (but that is after the facts) and a bit later you would say I WOULD HAVE exited 6 bars ago.

This way you WOULD HAVE a 100% hitrate....

The YU4rik indicator is also uselles because it repaints up to 4 or 5 bars ago. So when I said it has beaten the YU4rik that means it is even more unreliable.

That indicator is like an MA that you would shift back in time (hindsight).

So that indicator is not accurate iit is cr*p.

regards...iGoR

Thanks iGoR for this explanation. Much appreciated.

1...111213141516171819202122232425...1225
New comment
Reason: