I assume your comment is related to the model, not to the trading trainer, since the trading trainer has nothing to do with one-day price action.
Yes, that's why this statistical model is good to improve understanding price action trading through the days the system fails to predict only.
However, I am speaking about
daily chart price action, not one day price action. I am unsure if we are on the same row.
More important even is that predicting the 2-days smoothed price direction is not always telling you actually where price will go, because the 2-day sma and the 1-day price can move in opposite directions. However, the 2-day moving average is quite an ambitious target, since its variablity is also very high. For the daily price I have not worked on a system for it. I wish I had time enough to write in code a price action model that takes into account all the price chart setup, the market dynamics, the traders sentiment, news, other securities information, etc.
The model innacuracy, those 25% of the predictions may tell something.
- Why has it failed since, which factors made the most probable forecast to be wrong?
- Why was price at the opposite side of the balance point?
- How many times does it fail consecutively. This is interesting, the system never failed three consecutive bars virtually (maybe it could fail three times one time over one thousand).
- It usually failed only one bars and the next the prediction was always right also 70-80% of the times, I do not remember exactly. So, if you are tracking a few thousand securities, you may detect which predictions failed two times consecutively and bet that next bar's prediction is right almost without doubt.
- What happened those days that the model failed? For instance, I performed some basic statistical analysis and found out that the average variability of price the days that the model failed was about 5 times lower than the days the model was accurate. So, this means that for very low price change (short bars), the immediate price change is much more uncertain than for bars with regular or high price variability. It also tells that if you ignore very small bars you are likely to perform good entries.
There are certain programming languages like Python or R that are especially appropriate for mathematical and statistical analysis. You can perform advanced analytics with a few lines, the analytical methods are already implemented so you only have to understand them, you can easily use GPU and distributed computing, etc.
When I was fine-tuning the model I found that most of the papers published were not actually providing the details of the development done by the authors; that's also why I decided to write a short but practical article and what it is most important, with source code and the data set used.
Regards.