I probably need to disagree. Let's take a profiling architecture in python to set up a simple deep learning model and test it using financial time series. There are tons of modules where one plugs in a pandas dataframe and out comes the accuracy of the train and validation data set. Out comes the result. Job done. Not quite, I would argue. Unless the researcher has actually understood what is going on under the hood and why nothing really has been learned. The result without context is quite meaningless I would argue. I am not suggesting to reinvent what keras or tensorflow already offer, so I am with you on the issue of reusing modules. But I strongly suggest to write and create the overall architecture yourself. Because training a network is much more than just plugging data into a framework. It's thinking of what data to use, feature extraction/engineering, data cleansing and preprocessing, choice of hyper parameters, how to normalize the data, the design of the core layers, what to measure and optimize for, how to interpret results,... All that can only be understood properly by doing it oneself. With keras or scikit learn or other packages of course but nonetheless a self-defined and implemented testing framework.
Once a model has been validated in the initial profiling stage can the researcher move on to a more robust testing framework and backtest.
Once a model has been validated in the initial profiling stage can the researcher move on to a more robust testing framework and backtest.
But in this case you can find python frameworks on github to accomplish the task. Really, the goal should be to first find something already built that satisfies your requirements. And if something does not fully satisfy your requirements, can you build an integration with it to get you over the finish line. Rolling your own solution should be a last resort. I have seen plenty of would be algo traders spend years attempting to build their own platform resulting in them never doing any algo trading.