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
1k stars 152 forks source link

✨ Implement individual Configurable HyperOptable Weighted Signals #237

Open Rikj000 opened 2 years ago

Rikj000 commented 2 years ago

In the current MoniGoMani implementation we are limited to only being able to adjust the search space for all weighted signals at once.

The idea here would be to make the search spaces for individual weighted signals easily configurable in MoniGoManiHyperStrategy.py.

:black_square_button: Each weighted signal should have following settings:

So it will align with the new protection_spaces format.

:black_square_button: Then we can just use following settings from mgm-config as default values, if no specific ones are added in MoniGoManiHyperStrategy.py:

:black_square_button: Finally we should re-work the documentation for this

@raftersvk is currently working on this on his separation-of-signals-into-triggers-and-guards branch,
and it was already showing promising results!

Early POC example: early_example

Rikj000 commented 2 years ago

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

raftersvk commented 2 years ago

Before continuing with my work, one question: Do you really want to get rid of the following mgm-config values?

So far I kept them as default values if None were given on the individual signal. Both are valid concepts, just let me know what you prefer.

Rikj000 commented 2 years ago

Do you really want to get rid of the following mgm-config values?

  • min_weighted_signal_value
  • max_weighted_signal_value
  • search_threshold_weighted_signal_values

So far I kept them as default values if None were given on the individual signal.

That's a good idea, to keep them as default values! :smile:

raftersvk commented 2 years ago

check this #247