Discussion of article "The Implementation of Automatic Analysis of the Elliott Waves in MQL5"
Roman,
You have a great chance to use your development for good - namely, to collect statistics of price movement after the moment of detection of this or that wave - 1,2, .... A, B, and so on. I can guess, of course, what the result is likely to be.... but what the hell is going on, maybe there really is a practical sense in marking the waves?
Huge RESPECT!
What a job done....e mine.... Well done!!!
I wanted to see the work of the Expert Advisor according to this article, but no results so far: after starting, the terminal loads the processor at 100% and it is difficult to understand how long to wait, I think it is necessary to display the progress of TF analysis
SUS: after removing the Expert Advisor from the chart, the objects created by the Expert Advisor remain.
What a job done....you're mine.... Well done!!!
I wish it was as useful...
I wonder how many times the C wave was redrawn, around 1 May 84? and in other places. and other waves... and other waves...
IgorM:
SUS: after deleting an Expert Advisor from the chart, objects created by the Expert Advisor remain
In some cases this is normal, perhaps the author intended it that way...
I wanted to see the work of the Expert Advisor according to this article, but no results so far: after launching, the terminal loads the processor at 100% and it is difficult to understand how long to wait, I think there is a need for indication of the progress of TF analysis.
I confirm, there is a certain problem with chart analysis. The Expert Advisor starts to consume CPU resources, I had a CPU load from 60 to 100 percent, and it is "unknown" what, how much and how the Expert Advisor analyses.
As a result, after 25-30 minutes of such work, I removed the Expert Advisor.
One conclusion is that the idea itself is interesting, but the code requires additional work and optimisation of algorithms.
I also suggest the author to reconsider the issue related to the rendering of buttons, so much they interfere in the upper part (covering either the symbol data or the name of the Expert Advisor).
I suggest either moving the buttons to the bottom corner or moving them slightly away from the upper border.
- www.mql5.com
I wrote this article to show the algorithm first of all. Therefore, to keep the article more or less understandable, I removed optimisation, work with the tree of waves, etc. from the code, i.e. the program is deprived of everything that is specified in point 8. "Ways to improve the programme". So, the programme is not useful in trading now. And there is no sense in creating an Expert Advisor based on it.
As for the objects after removing the Expert Advisor from the chart - they should be removed.
I will soon post a variant with optimisation, it analyses hourly and four-hour charts in a couple of minutes. But there is a new problem - more than 5000 vertex labels are created, and this process is longer than the analysis itself.
I wrote this article to show the algorithm first of all. Therefore, to keep the article more or less understandable, I removed optimisation, work with the tree of waves, etc. from the code, i.e. the program is deprived of everything that is specified in point 8. "Ways to improve the programme". So, the programme is not useful in trading now. And there is no sense in creating an Expert Advisor based on it.
As for the objects after removing the Expert Advisor from the chart - they should be removed.
I will soon post a variant with optimisation, it analyses hourly and four-hour charts in a couple of minutes. But there is a new problem - more than 5000 vertex labels are created, and this process is longer than the analysis itself.
What about the analysis (my first post)? You will do an invaluable service to the whole trading community, I am serious.
If you still think about it and have any questions, feel free to contact me.
I would like to draw your attention to the fact that Wave Theory at this point in time is fundamentally divided into two branches - classical and modern. The first one - in the unchanged strict Elliottian form, the second one, including Neely's version, Wozny 's versions, as well as Frost and Prechter , etc., etc. should be referred to the daughter branches. Accordingly, in order to understand and properly use something subsidiary, you must first study the origins. Only after studying the origins will you realise whether it makes sense to consider child branches. If such a sense is found, it becomes much easier to understand the current of thoughts of the developers of child branches, and the use in practice becomes more effective.
I haven't understood from your article which one you prefer, and this is very important in practical application.
In your article, when describing wave models, you made many inaccuracies from the position of classical and modern Wave Analysis. I will not list all the inaccuracies, there are many of them, but as an example...... 1.Describing the wave model "CLINE", you did not take into account a very important circumstance that the 5th wave always exceeds the top of the 3rd wave.
2. You have not taken into account an important property (specificity of waves) in the "CONverging" and "Diverging" wedge.
3. When describing zig-zags, you clearly state.....
In Wave Analysis there are rules (as an example - the 2nd wave does not go beyond the base of the 1st wave, etc.), and there is an expression.... as arule, i.e. often, but not necessarily,
so, in a zig-zag, wave C may not go beyond the beginning of wave B (truncation), and the top of waveA has nothing to do with it (terminology VA), etc. If there are inaccuracies in the code, and . I think you understand.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
New article The Implementation of Automatic Analysis of the Elliott Waves in MQL5 is published:
Author: Roman Martynyuk