You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Useful link in my opinion:
Forum on trading, automated trading systems and testing trading strategies
Indicators: volatility_Bar
Igor Makanu, 2020.01.07 15:32
https://www.mql5.com/ru/code/9869
For every action, there is a trace in the present, which of course affects the future. :))))
I suggest in this thread without philosophy, let's just do mathematics, programming, testing, optimisation.
I would answer in another way. If Vasya broke his leg, he will limp in the future. This is an answer to a rhetorical question.
What is interesting here is not so much extrapolation as approximation. The point is that the market has certain, almost immutable regularities. Not everyone can notice them. An impartial formula doesn't care about this human flaw. It will calculate its own maths and draw you a smooth line without "noise". And, depending on the sample, it will allow even the most blind trader to notice these regularities. And they are the safest to make money on.
That's how it is. And forecasting the market is not a thankless business.
Regards, KAE.
It's a pity the branch is closed.
Great ungrateful business.
That's right.
"The fact is that the market has certain, almost unchanging patterns."
Is Fourier64.dll commented out in your code, does it exist in real life? Or did you plan to write it? There are large FFT dll libraries online, with lots of entry points. I'm not going to figure it out. I am interested in the possibility to replace MQL-function MathFourier2() with it.
Is Fourier64.dll commented out in your code, does it exist in real life? Or did you plan to write it? There are large FFT dll libraries online, with lots of entry points. I'm not going to figure it out. I am interested in the possibility to replace MQL-function MathFourier2() with it.
I apologise, it was in Nikolai Semko's code
I apologise, it was in Nikolai Semko's code
It's been a long time. A long time ago. But it seems to do the same thing, only about twice as fast. Since it's written in C++.
Too long and expensive or what else?
Too long and expensive or something else?
maybe he just doesn't know how to play it :-)