zaskok3: Imagine that you wrote a deliberately floppy TS, knowing full well that it would lose on trends. The only hope was that it would lose less than it earns. But as a result we see that some trends it trades excellently, while some of the flots - on the contrary, it fails. Obviously, its profit is not due to initial flatness. But due to the fact that the logic that you have laid down, you yourself have not fully understood.
For your own sake: before each data processing, zero out all variables which are prescribed in the global level.
zaskok3: Imagine that you deliberately wrote a flat Expert Advisor knowing that it will fail on trends. The only hope was that it would be losing less than earning. But as a result we see that some trends it trades excellently, while some of the flots - on the contrary, it fails. Obviously, its profit is not due to initial flatness. And the reason is that the logic you have laid down, you have not fully understood.
What is this nonsense? How can you lay down what you don't understand, is it possible to insert pieces of different other people's code from several programs into one of your own, and if it compiles - then rejoice and test it? И ... Oh a miracle, it works!
Any sensible developer can justify the work of his program - where and why it opens and closes, because it has some algorithm. The only exception is an Expert Advisor written on the principle of randomness - the generation of a random number, and execution of a trade operation based on it.
Any sane developer can justify the work of his program - where and why it opens and closes, because it has some algorithm. The only exception is an Expert Advisor written on the principle of randomness - the generation of a random number and the execution of a trading operation.
Regularity is an objectively existing, recurring, essential relationship of phenomena. A distinction is made between dynamic (the relationship between preceding and succeeding states of a system) and static (making its way through a mass of contingencies) regularities.
zaskok3: Imagine that you wrote a deliberately floppy TS, knowing full well that it would lose on trends. The only hope was that it would lose less than it earns. But as a result we see that some trends it trades excellently, while some of the flots - on the contrary, it fails. Obviously, its profit is not due to initial flatness. But due to the fact that the logic you've laid down, you yourself have not fully understood.
Ah, now I understand it, because it really looks like someone else's code)) I keep very detailed logs, write all the parameters I'm interested in for each tick, and then look it up in Matlab. It helps
zaskok3: I wrote a random TS and it shows a profit. But I can't understand what patterns it is based on. I need this in order to create a conscious TS based on these regularities and, consequently, to have adequate ideas about refinement.
An accidental TS is when you feel it without understanding what you are doing. For example, let me insert the input parameter here and prooptimize it. And lo and behold, the picture will be completely different. But I cannot understand what this parameter exploits.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Imagine that you wrote a deliberately floppy TS, knowing full well that it would lose on trends. The only hope was that it would lose less than it earns. But as a result we see that some trends it trades excellently, while some of the flots - on the contrary, it fails. Obviously, its profit is not due to initial flatness. But due to the fact that the logic that you have laid down, you yourself have not fully understood.
the last time I watched it
Which side is it on? Left or right?
For your own sake: before each data processing, zero out all the variables that are prescribed in the global level.
Imagine that you deliberately wrote a flat Expert Advisor knowing that it will fail on trends. The only hope was that it would be losing less than earning. But as a result we see that some trends it trades excellently, while some of the flots - on the contrary, it fails. Obviously, its profit is not due to initial flatness. And the reason is that the logic you have laid down, you have not fully understood.
What is this nonsense? How can you lay down what you don't understand, is it possible to insert pieces of different other people's code from several programs into one of your own, and if it compiles - then rejoice and test it? И ... Oh a miracle, it works!
Any sensible developer can justify the work of his program - where and why it opens and closes, because it has some algorithm. The only exception is an Expert Advisor written on the principle of randomness - the generation of a random number, and execution of a trade operation based on it.
Any sane developer can justify the work of his program - where and why it opens and closes, because it has some algorithm. The only exception is an Expert Advisor written on the principle of randomness - the generation of a random number and the execution of a trading operation.
Imagine that you wrote a deliberately floppy TS, knowing full well that it would lose on trends. The only hope was that it would lose less than it earns. But as a result we see that some trends it trades excellently, while some of the flots - on the contrary, it fails. Obviously, its profit is not due to initial flatness. But due to the fact that the logic you've laid down, you yourself have not fully understood.
I keep very detailed logs, write all the parameters of interest for each tick and then look it up in Matlab. It helps
I wrote a random TS and it shows a profit. But I can't understand what patterns it is based on. I need this in order to create a conscious TS based on these regularities and, consequently, to have adequate ideas about refinement.
An accidental TS is when you feel it without understanding what you are doing. For example, let me insert the input parameter here and prooptimize it. And lo and behold, the picture will be completely different. But I cannot understand what this parameter exploits.