>>60589163
when? respond to this too pls >>60589044

I have a pretty good backtesting UI right now I think, here's an example. not all kinks are ironed out yet of course. the backtesting engine generates signals for a given strategy+parameter+asset+timeframe, which are then archived in a database. then I use Jupyter notebooks (with templates and a library of snippets) to explore the signal database and determine ideal filtration, risk config, etc.

I'm not yet doing any ML or anything, just simple TA indicators to stress testing workflows and the UI. the backend is event driven