It depends on what you are trying to back test. I went through a phase of back testing everything to pieces and I used Tradestation 2000i to do this. I don't back test any more but I still use the same software which, even though others are telling me is old and limited in use, is still one of the best on the market in my view. It also works with Vista which is a big bonus for a package written back in the last millenium.
Paul
This may not be a useful reply as I'm not yet trading the 'stuff' that I'm developing. I trade UK stocks with play money but I'm in the long process of developing my own system for a different instrument, and I'm some way from going live yet.For all those which backtest their ideas before committing real money to them, can I ask what methods & software you use to perform this?
This may not be a useful reply as I'm not yet trading the 'stuff' that I'm developing. I trade UK stocks with play money but I'm in the long process of developing my own system for a different instrument, and I'm some way from going live yet.
To your question, for system exploration and backtesting I'm writing my own code. It's fairly low level - just plain C with no libraries, APIs or fancy pants like that - and just reads historical intraday data from a .csv file.
The beauty of writing your own code is the freedom it gives you, including possibly the potential to explore things in ways that the standard packages don't support. Then again I haven't used the standard packages, so they might do everything for all I know. Doing it yourself also forces you into the data and the analysis which I feel has benefits of its own. I also just enjoy it.
The downside is the time it takes and the occasional difficulty in implementing your ideas.
Yes, it can take money management, sizing, scaling in/out into account as necessary. Because it's open ended, and works by simulating a trader bar by bar as opposed to applying an equation to whole datasets, it can simulate arbitrary strategies, e.g. reserving Tuesday mornings for long-only trades at reduced exposure except where Monday's high was touched more than once and the previous week was low volatility, and the clocks went back within the last 10 days, and volume/range/close profile of the last 20 bars was x or y, etc., etc. You get the idea.Another more important point though is what elements are you coding in? For instance, are you taking into account money management / position sizing when you backtest and is it designed to test a complete portfolio (of many stocks) rather than on an individual stock by stock basis?
I know of some systems that when backtested on individual stocks can return a specific profit but when applied to a complete portfolio of stocks shows a much lower return.....
It depends on what you are trying to back test. I went through a phase of back testing everything to pieces and I used Tradestation 2000i to do this. I don't back test any more but I still use the same software which, even though others are telling me is old and limited in use, is still one of the best on the market in my view. It also works with Vista which is a big bonus for a package written back in the last millenium.
Paul
Hello All,
For all those which backtest their ideas before committing real money to them, can I ask what methods & software you use to perform this?
Just interested...
Chorlton
I have used and done all of the above. Just avoid optimization, fitting and multivariate systems. These break down really fast in actual trading. Simple ideas are the best.
Alex
ProRealTime is good.
If an idea is not profitable without any optimization then you can be certain that it wont be afterwards regardless of how good the results are made to look. I have seen many offerings time and again, and some that are still commercially available, that are clearly optimized back tested systems that always fail to deliver.
Paul
If you have a moving average cross-over type system and after backtesting the initial idea you decide to change the specific values of the MA's to offer a more favourable result then this is basically curve-fitting to previous data and IMO is what you are referring to above.
However, if your system relies on some form of specific pattern search and you decide after testing that there might be a better alternative this could be classed as optimisation of the overall system. The same logic could be applied to your money management rules such as which TYPE of trailing stop to use. In the search for a more ROBUST set of rules it could be argued that we are optimising.
Hello All,
For all those which backtest their ideas before committing real money to them, can I ask what methods & software you use to perform this?
Just interested...
Chorlton
Chorlton,
I'm using a full programming language called "PowerBasic" www.powerbasic.com for development of my software including trading systems (but for this you need some programing skills). Former i used Metastock which is easy to use and if you search the tool with the best cost/benefit ratio in this area you should try Amibroker www.amibroker.com .
Additionally I use my monte carlo simulation product ( www.zentrader.de/html/monte_carlo_simulator1.html ) for stresstests of conventional backtests and especially for data simulation issues (´= test your system with synthetic data to get a scenario under changed market conditions).
bye,
zentrader
Firstly, Thanks to all who have contributed.....
ZenTrader,
Can you elaborate on the above especially those phrase in BOLD? To get a scenario under CHANGED market conditions sounds interesting.....
Thanks....
Chorlton,
I've written a short paper concerning to this topic on my website:
http://www.zentrader.de/dataSimulation_e.pdf
Only my two cents...
bye,
zentrader