jiva34's BB Stop auto-trader

[laharjaya]

thanx Steve for inviting me ..

[SteveHopwood]

Hi Steve,
for moving average we want to confirm entry with cross of bb stop, and slope of ma...
We are not looking for a close above or below ma, just slope....
it doesn't appear that the bot is consulting with aa.....
http://img198.imageshack.us/img198/6971/oc3.png

Latest update in post 1.

I uploaded the code with AA turned off by default - no idea why. It is turned on now and there is some screen feedback to show if it is turned off.

Sing out if it still does not work, because that means there is a hole in the code. I am fairly sure that it worked in backtesting to check the code.

[SteveHopwood]

Sorry. There was a bloop in the AA code. Fixed now, I think.

Update in post 1.

[jiva34]

Sorry. There was a bloop in the AA code. Fixed now, I think.

Update in post 1.

chomping at the bit here...
to get it going..
the previous upgraded file was still not working, will test this latest upgrade.

[jiva34]

needs something... not opening and closing properly...
http://img841.imageshack.us/img841/2811/oc7.png

[SteveHopwood]

This could easily be me mis-understanding something.

Do me a favour, please, and spell out your trade exit rules in one-syllable words. If you can make them 3-letter words as well, that would be even better.

Hey, tell you what. When the damn thing does work properly, it is awesome. I think we owe you a few drinks.

[jiva34]

This could easily be me mis-understanding something.

Do me a favour, please, and spell out your trade exit rules in one-syllable words. If you can make them 3-letter words as well, that would be even better.

Hey, tell you what. When the damn thing does work properly, it is awesome. I think we owe you a few drinks.

ha ha, noticed you were careful not to say 4 letter words....

Enter long at open 2nd candle after a close above bb stop and aa is up
Enter short at open 2nd candle after a close below bb stop and aa is down

exit long at open 2nd candle after close below bb stop
exit short at open 2nd candle after close above bbstop
(or other options which are available in the shell).

[jiva34]

This could easily be me mis-understanding something.

Do me a favour, please, and spell out your trade exit rules in one-syllable words. If you can make them 3-letter words as well, that would be even better.

Hey, tell you what. When the damn thing does work properly, it is awesome. I think we owe you a few drinks.

ha ha, noticed you were careful not to say 4 letter words....

Enter long at open 2nd candle after a close above bb stop and aa is up
Enter short at open 2nd candle after a close below bb stop and aa is down

exit long at open 2nd candle after close below bb stop
exit short at open 2nd candle after close above bbstop
(or other options which are available in the shell).

I changed the wording a bit since I posted this at first...

[Gamma_gallus]

Regarding the Indi All Averages, I've found somewhere a newer version with 2 new methods (from the same original author), no clue if that could be useful for you, but better to share it.

The 2 new methods are :

// MA_Method=18: TriMAgen - Triangular Moving Average generalized by J.Ehlers
// MA_Method=19: VWMA - Volume Weighted Moving Average

Thx
Gamma

[gaheitman]

Hey Steve,

You've probably already seen this, but I have a couple of observations.

In ReadIndicatorValues() you have a "return" statement after testing that SlowUpTrendSignal > -1, which skips the AllAverages test later.

More importantly, perhaps, the exit criteria doesn't use the AllAverages test, so it is possible that even though you have an opposite cross of BBands, if the AA slope doesn't change you set the direction to "none" and then your test in start() doesn't close the open trade.

Does it make sense to add an option to your standard TrendDetectionModule() for UseAATrendDetection() and then handle like you do with the other trend detection options? I'm not sure the AllAverages test has been proven as well as the others in your template, but it might simplify matters. The faster option is probably to just add an AATrend variable and set that separately, but I'm always trying to think in terms of code reuse.

George