An unhijacked helper for Evaluator's SAFT trading system

[Anonymous]

Hi Steve,

Thank you very much for another very interesting EA.

I have been following SAFT with great interest at FF. He has recently produced a template incorporating 21 LWMA to the OBV indicator and I have found this works just as well as drawing trendlines for the OBV which is very subjective and different traders draw trendlines differently.

By using the 21 LWMA applied to the OBV, one more variable is removed and makes any future performance of the EA more easily assessed. But, I am not sure if this lends itself to coding.

Once again, thanks for your untiring efforts.

Best regards,
Peter

[SteveHopwood]

Thanks Peter. Someone else mentioned this earlier, but I forgot about it. Sounds like a good idea to me. Our helper ea needs some tlc, so I shall look at it this week.

[fx800]

Thanks Peter. Someone else mentioned this earlier, but I forgot about it. Sounds like a good idea to me. Out helper ea needs some tlc, so I shall look at it this week.

Hi Steve,

Fantastic ! Can't wait to test out the ea when it is ready !

With the summer doldrums soon out of the way, I think SAFT should perform well manually. I would suggest trading from Frankfurt open to London close to get sufficient momentum to drive price action.

A buy above 50 SMA/sell below 50 SMA filter out an occasional good trade but helps to filter out many more bad entries.


Best regards,
Peter

[SteveHopwood]

Thanks Peter. Someone else mentioned this earlier, but I forgot about it. Sounds like a good idea to me. Out helper ea needs some tlc, so I shall look at it this week.

Hi Steve,

Fantastic ! Can't wait to test out the ea when it is ready !

With the summer doldrums soon out of the way, I think SAFT should perform well manually. I would suggest trading from Frankfurt open to London close to get sufficient momentum to drive price action.

A buy above 50 SMA/sell below 50 SMA filter out an occasional good trade but helps to filter out many more bad entries.


Best regards,
Peter

Thanks again Peter. V 1d is in post 1.

I have replaced the OBV trendline with the moving average. There is a problem with this, in that I have not found a way to code calls to the Moving Average indi in such a way that it will return the MA of the OBV indi. Instead, I have replaced the lwma on my OBV with a simple ma, and hand-coded the mo calculation. The result of this calculation appears to be out by a few points, so anybody with more accurate code, please sing out.

Also added the chart 50 ma - fully configurable in the inputs window. Disable it by setting MaPeriod to zero.

[fx800]

Thanks Peter. Someone else mentioned this earlier, but I forgot about it. Sounds like a good idea to me. Out helper ea needs some tlc, so I shall look at it this week.

Hi Steve,

Fantastic ! Can't wait to test out the ea when it is ready !

With the summer doldrums soon out of the way, I think SAFT should perform well manually. I would suggest trading from Frankfurt open to London close to get sufficient momentum to drive price action.

A buy above 50 SMA/sell below 50 SMA filter out an occasional good trade but helps to filter out many more bad entries.


Best regards,
Peter

Thanks again Peter. V 1d is in post 1.

I have replaced the OBV trendline with the moving average. There is a problem with this, in that I have not found a way to code calls to the Moving Average indi in such a way that it will return the MA of the OBV indi. Instead, I have replaced the lwma on my OBV with a simple ma, and hand-coded the mo calculation. The result of this calculation appears to be out by a few points, so anybody with more accurate code, please sing out.

Also added the chart 50 ma - fully configurable in the inputs window. Disable it by setting MaPeriod to zero.

Hi Steve,

GREAT ! I was not expecting the new version so quickly. Will put it to the test tomorrow.

LHDT on FF coded a SAFT EA using 21 LWMA of OBV http://www.forexfactory.com/showthread. ... 44&page=11 post # 160 However, he has not shared his code yet. We have many brilliant coders in your forum, I am sure one of them will contribute.

Best regards,
Peter

[fx800]

Regarding the 50 MA filter, I am using LHDT's settings of 50 SMA shift 0 close, rather than Evaluator's 50 EMA shift 2 typical price used in his template.

Peter

[NeoTrader]

hi Steve,

I have replaced the OBV trendline with the moving average. There is a problem with this, in that I have not found a way to code calls to the Moving Average indi in such a way that it will return the MA of the OBV indi. Instead, I have replaced the lwma on my OBV with a simple ma, and hand-coded the mo calculation. The result of this calculation appears to be out by a few points, so anybody with more accurate code, please sing out.

The following is not a tested code...i just put it together...to show you the concept...this should work...to combine your obv with an MA.

If you have any question feel free to ask here or via PM.

Code: Select all

double obvArray[];
double maCurrent;

ArrayResize(obvArray, MAPeriod + 1);
ArraySetAsSeries(obvArray, true );

for ( j = 0; j <= MAPeriod + 1; j++ ) {
obvArray[j] = iCustom (your call to get the obv, use j for the shift )

// will give you the current MA value for the obv
maCurrent = iMAOnArray( obvArray, 0, MAPeriod, 0, MAMode, 0 ); 
}

hope this helps.

happy trading,

NeoTrader

[MickyMouse]

Thanks Peter. Someone else mentioned this earlier, but I forgot about it. Sounds like a good idea to me. Out helper ea needs some tlc, so I shall look at it this week.


I have replaced the OBV trendline with the moving average. There is a problem with this, in that I have not found a way to code calls to the Moving Average indi in such a way that it will return the MA of the OBV indi. Instead, I have replaced the lwma on my OBV with a simple ma, and hand-coded the mo calculation. The result of this calculation appears to be out by a few points, so anybody with more accurate code, please sing out.

Also added the chart 50 ma - fully configurable in the inputs window. Disable it by setting MaPeriod to zero.

attached you have obv with ma included. first buffer is obv, second is the moving average. cheers.

[fx800]

This is really exciting. MickyMouse and NeoTrader, thank you very much for your contributions.

Cheers,
Peter

[fx800]

Hi MickyMouse

Your OBV_MA indi draws only part of 21 LWMA (top)

The bottom indi is produced by dragging moving average onto the obv window.

Cheers,
Peter