Online: | |
Visits: | |
Stories: |
Story Views | |
Now: | |
Last Hour: | |
Last 24 Hours: | |
Total: |
In this post, in continuation of Part 1, I will try to describe the most common problems which occur while testing algorithmic trading strategies in MATLAB when using one’s own groundwork or the code from the automated trading webinars.
Easy-to-use GUI
Let’s start with the fact that there is no graphical interface because if we presume that almost the whole process of testing and analysing trading strategies is standardised (it is 99%), you would like to have the interface which helps you call up the necessary data and start the testing process with one click.
Someone (experienced users of MATLAB, in particular), might argue that the use of ready-made functions is not any worse and actually is even sometimes better and more convenient that the static GUI. It’s possible, but a GUI however has a number of advantages:
Thus, in WFAToolbox, we created a possibility to write any codes for your strategy, using any of MATLAB toolboxes and working with multiple assets for the strategies such as pairs trading, basket trading or triplet arbitrage, etc.; but at the same time this code is easily integrated in the GUI by use of patterns, which are simple enough to apply in the code and they do not limit opportunities.
In order to easily master the patterns of code to create your strategies, not only we created detailed WFAToolbox Documentation, but also WFAToolbox Video Tutorial, which provides an opportunity to a full-scale work with the app in a few minutes.
![]() |
Easy-to-use GUI in WFAToolbox |