Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

⚡️ Make signals only trigger once in lookback windows #43

Closed
Rikj000 opened this issue Jun 5, 2021 · 3 comments
Closed

⚡️ Make signals only trigger once in lookback windows #43

Rikj000 opened this issue Jun 5, 2021 · 3 comments
Assignees
Labels
Feature - Enhancement Update or improvement to existing feature
Milestone

Comments

@Rikj000
Copy link
Owner

Rikj000 commented Jun 5, 2021

The trend_total_signal_needed_candles_lookback_window_value's are based on an idea out of the EmperorBTC Trading Manual.
EmperorBTC

As you can see in the picture a great buy signal was the result of 6 indicators firing rapidly after one another.
To more represent this idea I'd like to move the rolling checks currently done on the total signals, to the individual weighted signals.
Since this should be a more valid implementation of the EmperorBTC idea.

@Rikj000 Rikj000 added Feature - Enhancement Update or improvement to existing feature Planned Planned feature, improvement or bugfix (not being worked on yet) labels Jun 5, 2021
@Rikj000 Rikj000 added this to the v0.12.0 milestone Jun 6, 2021
@Rikj000
Copy link
Owner Author

Rikj000 commented Jun 8, 2021

Perhaps a better implementation (or additional) could be to add a customizable/hyperoptable weighted_signal_cooldown period for individual weighted signals in use.

Reasons behind idea:

  • To prevent signals from firing again for X candles/minutes after they trigger
  • As an attempt to get too many buy signals under control
  • To prevent false re-triggers of signals shortly after the first time they went off

RSI for example usually takes many candles before it goes from 30 back to 70, and then then another rather long amount to go back down from 70 to 30.
So it would be safe to throw in a decent sized cooldown window for each (buy/sell).
To prevent false re-triggers shortly after.
(False re-triggers can be explained by zooming out to bigger candles, then you can often see that the trend indeed still had more to go down or up before reversing again, thus RSI bumps around a few times)
This could also cause missed opportunities due to the same reason though, so I'd try to make it hyperoptable or at least configurable so we can tweak to our own liking

@Rikj000
Copy link
Owner Author

Rikj000 commented Jun 12, 2021

Perhaps a better implementation (or additional) could be to add a customizable/hyperoptable weighted_signal_cooldown period for individual weighted signals in use.

After thinking it over I think it would be better to stick to the first idea instead of this, since false re-triggers also go accompanied with false opposite signals (if buy => sell and if sell => buy).
So this would lead to the cooldown window activating on a false signal and perhaps being blocked on the real signal.

Better would be to stick to the 1st idea where a few different signals in a short lookback window can trigger only once. in the lookback window.

@Rikj000 Rikj000 self-assigned this Jun 12, 2021
@Rikj000 Rikj000 added In Progress This is being worked on and removed Planned Planned feature, improvement or bugfix (not being worked on yet) In Progress This is being worked on labels Jun 12, 2021
@Rikj000
Copy link
Owner Author

Rikj000 commented Jun 13, 2021

HyperOpt still needs to finish to completion but already pushed the code and closing the issue since clear improvements can already be seen 🎉
MGM-FireOnlyOnceInLookback

@Rikj000 Rikj000 closed this as completed Jun 13, 2021
@Rikj000 Rikj000 changed the title Make signals only trigger once in lookback windows ⚡️ Make signals only trigger once in lookback windows Sep 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature - Enhancement Update or improvement to existing feature
Projects
None yet
Development

No branches or pull requests

1 participant