Muhammad wrote:
>> âTraders Studio allow programmers to make there own codes to run on portfolios and calculate any thing they want. None of the currently available softwares provide such power.â
Iâm a programmer and a user of TS2000i and TraderStudio doesnât meet my requirements.
I couldnât find any description of features or performance characteristics on their web page. They just have tutorials. I donât want to watch, âclick thisâ or âpoint your mouse hereâ and try to deduce what I would be buying. I want to know what their optimization engine is, what objective functions are available, what built-in indicators are available, what there new hybrid language looks like, how fast is the optimization engine? Etc.
As a programmer it was easy to write my own platform for portfolio testing and I was confident that it was going to what I wanted because of the software development process I went through to develop it: Requirements analysis, Design, Development, Integration and Test. For example my requirement was to test with intraday and tick data. The implementation details for this are trivial if that requirement was there at the beginning.
If I were developing a product I would make a major effort to understand the needs of my customers. If one looks at the total number of users backtesting only EOD verse intraday, EOD only is in the minority. A larger customer base uses intraday data. And as I said intraday testing is such a trivial implementation detail if you specify and design for it from the beginning. The difference is that a bar of EOD data has only a date field while intraday has date and time. Adding that field after the fact as to be rippled though all of design and code. One would have to change everything that touches a bar of data from the data feed interface, to the database, to the charting package to the backtesting engine, etc.
Another import user requirement is speed. TS2000i code is interpreted and some traders have strategies that take hours to optimize. Imagine doing that for a portfolio of 25 stocks. Interpreted code runs at least 10 times slower than compiled code. So my platform had a performance requirement for speed. I wanted to optimize, test and data mine large portfolios and I knew that I had to have speed to do that. Initially a portfolio the size of the NDX, but my requirement had no limitations on the size of the portfolio. The obvious design choice was for compiled code not interpreted code like in TS2000i. Its interesting Iâve only come across one commercial backtesting product that compiles strategies â someone had done their homework.
>> âTraders Studio allow programmers to make there own codes to run on portfolios and calculate any thing they want. None of the currently available softwares provide such power.â
Iâm a programmer and a user of TS2000i and TraderStudio doesnât meet my requirements.
I couldnât find any description of features or performance characteristics on their web page. They just have tutorials. I donât want to watch, âclick thisâ or âpoint your mouse hereâ and try to deduce what I would be buying. I want to know what their optimization engine is, what objective functions are available, what built-in indicators are available, what there new hybrid language looks like, how fast is the optimization engine? Etc.
As a programmer it was easy to write my own platform for portfolio testing and I was confident that it was going to what I wanted because of the software development process I went through to develop it: Requirements analysis, Design, Development, Integration and Test. For example my requirement was to test with intraday and tick data. The implementation details for this are trivial if that requirement was there at the beginning.
If I were developing a product I would make a major effort to understand the needs of my customers. If one looks at the total number of users backtesting only EOD verse intraday, EOD only is in the minority. A larger customer base uses intraday data. And as I said intraday testing is such a trivial implementation detail if you specify and design for it from the beginning. The difference is that a bar of EOD data has only a date field while intraday has date and time. Adding that field after the fact as to be rippled though all of design and code. One would have to change everything that touches a bar of data from the data feed interface, to the database, to the charting package to the backtesting engine, etc.
Another import user requirement is speed. TS2000i code is interpreted and some traders have strategies that take hours to optimize. Imagine doing that for a portfolio of 25 stocks. Interpreted code runs at least 10 times slower than compiled code. So my platform had a performance requirement for speed. I wanted to optimize, test and data mine large portfolios and I knew that I had to have speed to do that. Initially a portfolio the size of the NDX, but my requirement had no limitations on the size of the portfolio. The obvious design choice was for compiled code not interpreted code like in TS2000i. Its interesting Iâve only come across one commercial backtesting product that compiles strategies â someone had done their homework.
