Machine learning in trading: theory, models, practice and algo-trading - page 1732

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
I have been interested in this subject for a long time. I have been messing around with Fourier, wavelets, EMD, SSA. The main problem is latency. All these methods show the past. It is solved by means of forecasting, but it leads to overriding (SSA). If the price is stationary for some time the forecast is good, but how do we know how long the price stays forecasted? The settings in CSSA are quite usual for predicting methods. There is another way to get rid of the delay, it is a phase correction, but because of this indicator has strong deviations after the sharp price movements. I do not think that CSSA hacked all these limitations, they just added a nice visualization of calibration.
You just need to check the method. Just myself I will not do it in life, firstly I will do it fiercely long, I have remembered R, so the dataframe did four hours of unused until I figured it out, there is no one to advise. And what I'll do 100 percent will be a lot of mistakes. And I need to create a script in R, which implements the entire above algorithm and check it in real life. Even if the most difficult parameter TC such as "GUARANTEED" will be 3 out of 5 already can earn.
this is normal practice, don't be sad, just do it
I have been interested in this topic for a long time. I have fiddled a lot with Fourier, wavelets, EMD, SSA. The main problem is the delay. All these methods show the past. It is solved by means of forecasting, but it leads to overrun (SSA). If the price is stationary for some time the forecast is good, but how do we know how long the price stays forecasted? The settings in CSSA are quite usual for predicting methods. There is another way to get rid of the delay, it is a phase correction, but because of this indicator has strong deviations after the sharp price movements. I don't think CSSA hacked all these limitations, they just added a nice visualization of calibration.
this is normal practice, don't be sad, just do it
Conditionally. 1-e 2 parameters hour and minute, then the quality score and cluster number 1, -1 (you can make more)
1 and 2 parameters can be any (indicator value, etc.), there can be more
You have states now, when the indicators are in some values, you know what strategy to apply. And this will persist for years, with luck
That's the shit I wrote based on your glues.
I just put out a better score, but you can combine
on top of that the caterpillar will work (although you don't need it anymore)
I need to make a primitive mall and put it on OOS
We need to make a primitive merchant system and put it on OOS
Everything works. We need to come up with floating time windows. Fixed numbers seem limited.