Replies: 2 comments 6 replies
-
I really like the idea of having a backtest engine that is affiliated with the library, though I would build it as an entirely separate project because a) it's a better architectural design pattern to separate responsibilities, and 2) indicator users won't always want our backtest engine bundled with the indicators. Some ideas and basic design parameters I've been considering:
My biggest concerns are about modularity and whether we can maintain a finite scope of it and have it still be useful. For example, once you have signals, how much analysis and presentation would you want ... charts ... live trading, etc? It can grow into a full algo trading system if not careful, which is something I'd like to avoid (for this proposed module). |
Beta Was this translation helpful? Give feedback.
-
I was just freshening up my thinking on backtests and all of the overfitting and problems to avoid. It can be a real misleading mess if not careful. What I’m reading: |
Beta Was this translation helpful? Give feedback.
-
It would be nice to have a backtest module
Beta Was this translation helpful? Give feedback.
All reactions