Replies: 2 comments · 1 reply
-
|
This is a strong concept — the gap between I ran a backtest and I understand which of my strategies is actually best is real. A few thoughts:
Whether or not it becomes a formal contribution to this repo, it sounds like a project worth finishing. The "orchestration + persistence + comparison" layer is exactly what's missing from most backtesting workflows. |
Beta Was this translation helpful? Give feedback.
-
Right, in fact, comparing strategies based solely on returns is only an important first step; the real challenge lies in identifying a portfolio of different strategies that, when combined, produce a return curve that is as smooth (balanced) as possible. |
Beta Was this translation helpful? Give feedback.
-
|
A GUI like that would lower the barrier to entry for backtesting and would therefore be very welcome! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I would like to ask for your opinion regarding a potential contribution related to Backtesting.py.
As part of my master’s thesis, I developed an early prototype of a GUI application that uses Backtesting.py as its backtesting engine (without modifying its core).
The GUI allows users to:
The application is written entirely in Python and uses a client-server architecture. Backtesting.py remains the computational engine, while the application provides orchestration, persistence, and a graphical interface layer on top.
The project is still in a prototype stage and would require further work to become robust enough for practical use. Before investing more time into development, I would like to ask whether you see any value in this kind of application within the Backtesting.py ecosystem.
Thank you for your time and for maintaining Backtesting.py.
Example screenshot of the prototype:
Beta Was this translation helpful? Give feedback.
All reactions