search

Rikj000 / MoniGoMani

Isn't that what we all want? Our money to go many? Well that's what this framework/strategy hopes to do for you! By giving you & HyperOpt a lot of signals to alter the weights from.
https://monigomani.io
GNU General Public License v3.0
1.01k stars 153 forks source link

⚡️ Freqtrade Protections / Market Crash Protection #40

Open denvers opened 3 years ago

denvers commented 3 years ago

When the market crashes the unclogger will keep unclogging profits away. Freqtrade protections should help to prevent this.

Rikj000 commented 3 years ago

Better crash prevention is still needed, but might also be reachable with better configured Freqtrade protections https://www.freqtrade.io/en/latest/plugins/#protections Please report back if you can find a good protection configuration for MGM :slightly_smiling_face: But be sure to use minutes and not candles so it won't interfere with TimeFrame-Zoom And you'll need to append the --enable-protections flag to your BackTest/HyperOpt commands It will add some time to the duration of the tests though, but I think this is truly needed to help us keep our profits during market crashes

Rikj000 commented 3 years ago

Added Protection example to the development branch, however I tested this and I think we can still do better https://github.com/Rikj000/MoniGoMani/commit/9acd555c5971d2b6c9d76fcfcf0dd1188d9a1b79

Rikj000 commented 3 years ago

I haven't found a configuration that I'm happy with yet and testing these takes quite some time.
Please explore these too so we can hopefully find a good setup more quickly!

Rikj000 commented 3 years ago

Since the Drawdown and Cooldown protections activate after X lost trades (sell signals) we should be weary of using these together with the unclogger.
The unclogger has an intended side effect of creating sells at a small loss to hunt for more profitable trades again more quickly.

We could try to:

Rikj000 commented 3 years ago

@3ylo though that protections and the unclogger might be interfering with each other.
Due to this reason I'm currently testing with only a couple of StoplossGuard protections.

Finding good protections already has taken up quite some time, please if you have time, help out in the search for a couple of good ones for MGM :pray:

v-anton commented 3 years ago

@Rikj000 Please let me know if you need any help there. I could run some HO as well :)

Rikj000 commented 3 years ago

@Rikj000 Please let me know if you need any help there. I could run some HO as well :)

Yes that would be truly welcome! So the goal is to look for a couple of good Freqtrade Proctections to go along with MGM.
It's not hard either to look for some, just takes a lot of CPU crunching (which takes time):

Wait and see if improvement happened, then report back here. We'd like to get our drawdown more tight and our losses less overall without cutting down our overall profit (too much).

FYI: 1st HyperOpt Runs are simply without any mgm-config-hyperopt.json present on your device

v-anton commented 3 years ago

@Rikj000 Trying to HO, but for now I have such error: 2021-06-15 11:02:35,710 - freqtrade.resolvers.iresolver - WARNING - Could not import /Users/antonvozghrin/Developer/MoniGoMani/user_data/strategies/MoniGoManiHyperStrategy.py due to 'No module named 'user_data.strategies.MasterMoniGoManiHyperStrategy'' 2021-06-15 11:02:35,710 - freqtrade - ERROR - Impossible to load Strategy 'MoniGoManiHyperStrategy'. This class does not exist or contains Python code errors.

Rikj000 commented 3 years ago

`2021-06-15 11:02:35,710 - freqtrade.resolvers.iresolver - WARNING - Could not import /Users/antonvozghrin/Developer/MoniGoMani/user_data/strategies/MoniGoManiHyperStrategy.py due to 'No module named 'user_data.strategies.MasterMoniGoManiHyperStrategy''

Are you sure you updated to the latest MGM development? Seems your MasterMoniGoManiHyperStrategy file is missing.

v-anton commented 3 years ago
Снимок экрана 2021-06-15 в 11 16 03

Nope, it exists. Rly now sure what's the reason:( Will proceed later a bit

nuaimat commented 3 years ago

i just had the same error few minutes ago, it's related to this issue https://github.com/Rikj000/MoniGoMani/issues/59 the fix for me was: in MasterMoniGoManiHyperStrategy line 21 change: from freqtrade.state import RunMode to from freqtrade.enums import RunMode

Rikj000 commented 3 years ago

@nuaimat and @v-anton if https://github.com/Rikj000/MoniGoMani/issues/59 is the issue you guys are struggling with, then I'm guessing you guys are not on the correct Freqtrade fork + branch + commit anymore? Currently MGM still requires:

After this issue (https://github.com/Rikj000/MoniGoMani/issues/40) is closed I'll update back to the latest Official Freqtrade development, then I will look at issue https://github.com/Rikj000/MoniGoMani/issues/59 and for other breakage/bugs that might have happened with updating. This will be the very last thing done before officially releasing MGM v0.12.0, so please keep using my Freqtrade fork until v0.12.0 has been officially released!

v-anton commented 3 years ago

i just had the same error few minutes ago, it's related to this issue #59 the fix for me was: in MasterMoniGoManiHyperStrategy line 21 change: from freqtrade.state import RunMode to from freqtrade.enums import RunMode

Didn't help :(

Rikj000 commented 3 years ago

i just had the same error few minutes ago, it's related to this issue #59 the fix for me was: in MasterMoniGoManiHyperStrategy line 21 change: from freqtrade.state import RunMode to from freqtrade.enums import RunMode

Didn't help :(

Then please post your new error at issue https://github.com/Rikj000/MoniGoMani/issues/59 and then stick to the version I just mentioned in my previous message until I will work on updating to the latest Official Freqtrade

Rikj000 commented 2 years ago

Linking to issue: https://github.com/Rikj000/MoniGoMani/issues/221