You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.
First of all I want to thanks for a great project that I'm experimenting with the last few weeks! I did several simulations (with genetic_backtester recently) that showed big profits using bollinger strategy. So I imported some simulations output into excel that showed upper and lower bollinger bounds as wel. Then I realized that making the bollinger upper/lower bount pct values (Let's assume identical for the moment) > ~3 pct in that dataset would flip them! iow: the lower trigger boundry would lay above the higher boundry.
Of course the simulation proves sanety but I have a hard time understanding the strategy then. Someone understands?
The text was updated successfully, but these errors were encountered:
There is more testing and finetuning to be done with this strategy, issues like these and people taking the time to analyze things that they find are what allow devs to pinpoint issues and write fixes for them. Thank you for bringing this up and I'll be sure to take a look again at this when I have some more free time 👍
First of all I want to thanks for a great project that I'm experimenting with the last few weeks! I did several simulations (with genetic_backtester recently) that showed big profits using bollinger strategy. So I imported some simulations output into excel that showed upper and lower bollinger bounds as wel. Then I realized that making the bollinger upper/lower bount pct values (Let's assume identical for the moment) > ~3 pct in that dataset would flip them! iow: the lower trigger boundry would lay above the higher boundry.
Of course the simulation proves sanety but I have a hard time understanding the strategy then. Someone understands?
The text was updated successfully, but these errors were encountered: