Nothing is more frustrating than to have an Expert Advisor yet no corresponding System Tester to backtest the effectiveness of the Expert. Basically, you have to eyeball the entry/exits noted on the chart where the Expert is applied. While a related post referred to cut-n-paste of System to create Expert, thats great when the formulae is not hidden with password protection. Specifically referring to the 5 *FX Experts. How do you create a corresponding System Tester when the Expert Editor reads "Formula is password protected or read-only"? It is impossible to cut-n-paste! Now, I am not asking you to share proprietary info so I can create a system test. But, since it is password protectd AND not included in the original release of Metastock Pro 9.1, it would be nice if could download and add to the program. This would allow the System Tester to compliment the Expert, plus enable multi-timeframe backtesting to see where the (and which) Expert ismost effective.

It is not a plug in or the new FXTA (which I am also thinking about ordering). I know you do have a few plug in teasers in the system test, such as pp::Bollinger Bands (Modified), but I am not referring to them either. What I was referring to were the following 5 Expert Advisors in MS Pro 9.1 *FX - Multiple Time Frame Signals *FX - Multiple Time Frame Trend *FX Keltner System 1 *FX Keltner System 2 *FX Pattern System Within the System Tester, there is no corresponding system to those experts, and you can't create the system because the formulae is pasword protected. Without a system test, you have no trade history, winners, losers etc. You basically have to eyeball the expert's historical plots to see if it is something you want to consider. Using the eyeball method, Ketlner System 2 and Pattern System look 'interesting' but an actual system test would be far more accutate and time efficient.

Hi Doc

What was the outcome of the expert system ?

I would like to be able to backtest these experts as well and agree with the frustration of the previous post, I note this was dated back in 2005, what was the outcome, may I download the system tests?

Regards,

mhal8394@usyd.edu.au

Garp

This means that you need to keep your code within the 1023 character limit of all EST code windows. There are a number of ways to do this. Calling large chunks of code from the Indicator Builder is one way to go, but there any number of tricks that can be used to shorten code for use within the EST. For example, variable names only need to be 1 character long, so take the knife to them. There are 14 letters of the alphabet that can be used as variable names so there's no real reason why a name should be longer than 2 characters. Eliminate all comments. In fact it's a good idea to make whatever changes you can in a text editor before attempting to paste into an EST code window.

Roy