Just to be clear, since your reply to my post referred to a 'mechanical algorithm,' and I'm not sure exactly how you define that. My system is based upon a homemade, custom kNN algorithm. An ensemble of over 32 of them (currently). Their outputs are feed into a homemade simple NN. The NN is trained with the help of an evolutionary algorithm--Excel Solver. My Excel VBA code ties it all together. It's simple. But it's also very complex.
I've had several breakthroughs. I overcame the curse of dimensionality problem--for example. Etc. etc.
https://en.wikipedia.org/wiki/Curse_of_dimensionality
The system has many different aspects to it. It grew over time by me solving one problem at a time. I doubt I could have sat down in the beginning and dreamt up what I ultimately created. In a way, by using logic and common sense; it kind of was telling me how to build it--as I built it.
I can get even greater performance by running the algo on a more powerful computer (by increasing the size of the ensemble). I'm currently running it on a 2014 cheap Best Buy laptop. It takes 2-3 hours to create a forecast. The forecast applies to the following day. It forecasts one day at a time, per day.
I've read papers too. Mainly to see if anyone had discovered what I've discovered about ML. I'll also concluded it is real easy for the results of papers to be 'massaged.' (I recall a recent news story about papers being 'made up.') A few did probably inspire some of the concepts I use. I'm not certain.
My concepts can be used generally, and not just for financial time series.
Imo, it's less about what you're using; and more about how you do it. The first problem to overcome is: how to present the financial time series problem to an algorithm--the inputs.
Before building my own, I tried:
GMDH Shell
Eureqa
Weka
and some others.
I'll eventually get around to coding my system in Python, but if I use any of the ML libraries, it'll be in a very unique way, and not as they are intended to be used. My intent would be to take advantage of Cython eventually...for the speed. More speed: more inputs. More inputs (for my system) the better.
Whenever you get your deep learning system up and running, my challenge will still be on the table.
I've had several breakthroughs. I overcame the curse of dimensionality problem--for example. Etc. etc.
https://en.wikipedia.org/wiki/Curse_of_dimensionality
The system has many different aspects to it. It grew over time by me solving one problem at a time. I doubt I could have sat down in the beginning and dreamt up what I ultimately created. In a way, by using logic and common sense; it kind of was telling me how to build it--as I built it.
I can get even greater performance by running the algo on a more powerful computer (by increasing the size of the ensemble). I'm currently running it on a 2014 cheap Best Buy laptop. It takes 2-3 hours to create a forecast. The forecast applies to the following day. It forecasts one day at a time, per day.
I've read papers too. Mainly to see if anyone had discovered what I've discovered about ML. I'll also concluded it is real easy for the results of papers to be 'massaged.' (I recall a recent news story about papers being 'made up.') A few did probably inspire some of the concepts I use. I'm not certain.
My concepts can be used generally, and not just for financial time series.
Imo, it's less about what you're using; and more about how you do it. The first problem to overcome is: how to present the financial time series problem to an algorithm--the inputs.
Before building my own, I tried:
GMDH Shell
Eureqa
Weka
and some others.
I'll eventually get around to coding my system in Python, but if I use any of the ML libraries, it'll be in a very unique way, and not as they are intended to be used. My intent would be to take advantage of Cython eventually...for the speed. More speed: more inputs. More inputs (for my system) the better.
Whenever you get your deep learning system up and running, my challenge will still be on the table.

I am no expert here; just sharing some thoughts/issues that I have come across when I looked into this area; some of what I write here is the advice that I got from some deep learning experts who happen to be my colleagues at the company I work for.
One particular thing that I have noticed when I scratched this area is that open source software such as Theano/keras or tensorflow or torch have good CNN models, but lack/not upto-date in many RNN/RBM models that are currently being churned out at universities. RNN/RBMs have LSTM (Long-Short Term Memory) that support time series models; CNNs don’t for that matter. At one point, my colleagues advised me to simply ignore the open source packages for latest RNNs and start reading papers and use CUDA programming; Nvidia’s latest cuDNN supports RNNs. The other problem with LSTM models is that they are not as parallel as CNNs and so processing not so parallel neural networks can get time consuming. There is so much research going on in deep learning that one has to just keep reading all the papers coming out of the universities full-time (forget trading). Training RNNs is VERY hard; don't underestimate this; most of today's research focus is around ways to simplify training. As you see, once we get into the details, deep learning can get complicated and time consuming; unless you absolutely know what you are after, you can quickly get bogged down in a wild goose chase.
To be fair, there are a number of simple mechanical strategies that can be developed by hand; deep learning is always there for more complicated scenarios. Every approach can be designed by either traditional (mechanical algo) approach or a deep learning... it’s a matter of how complicated the mechanical algo gets for a required accuracy; guess that’s the deciding factor. Deep learning is always superior, but is it worth the effort for a good enough accuracy? At the end of the day, we are after ROI/PNL, so its just a matter of ones perception of where the alpha is given the resources/time/priorities we have at hand. I struggling to stop myself from jumping into this field, I have some low hanging fruits first![]()