Steve:
 
I agree with you. ApplyStop() helps in coding stop exits though sometimes it is a bit difficult to figure out what's going on.
For stop entries, AmiBroker is lacking high level functions to do so, though you can probably accomplish what you want in low level array manipulation.
It would be nice to have BuyAtStop(), SellAtStop() etc.
 
I am planning to write a front end to run Trading Recipes systems with AmiBroker as the back end. So far running single system seems to be doable. Running multiple system simulation seems to be more involved.
 
- Mark H. 
 
----- Original Message -----
From: scourt2000
Sent: Sunday, October 08, 2006 7:56 AM
Subject: [amibroker] Re: Ed Seykota's TSP: Support and Resistance


Thanks so much Mark for contributing that code. You're so right.
Amibroker can do just about anything at a lower level, but if that
elegant function, ApplyStop(), can't do the job, you're probably in
for a world of hurt to get things just right.

I think what would help is if Tomasz would code up how each ApplyStop
() option looks when fully coded at the low level of looping through
the trading signals. Using coding templates/patterns like these are
a big help.

Steve

__._,_.___

Please note that this group is for discussion between users only.

To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com

For other support material please check also:
http://www.amibroker.com/support.html






SPONSORED LINKS
Software support Small business finance Business finance online
Business finance training Business finance course

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to