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

mgm-hurry - Implement custom search space values #240

Open
Rikj000 opened this issue Jan 17, 2022 · 0 comments
Open

mgm-hurry - Implement custom search space values #240

Rikj000 opened this issue Jan 17, 2022 · 0 comments
Labels
Feature - New New feature or pull request Planned Planned feature, improvement or bugfix (not being worked on yet)
Milestone

Comments

@Rikj000
Copy link
Owner

Rikj000 commented Jan 17, 2022

With MoniGoMani growing in size, I think it can be beneficial / give us more control if we implement custom search space values.

For example:

  • Add an unclogger unclogger space for mgm-hurry
  • Which will allow us to specify if we seek to optimize the unclogger by passing
  • Or if we simply wish use it without optimization during our HyperOpt process.

In the underlying code not much has to change, the unclogger just will stay inside the freqtrade sell space,
but it would be nicer/more clear to the users like that I think. While also giving us more control over our HyperOpts.

I'm already thinking about following new mgm-hurry specific optimizable search spaces:

  • unclogger
  • weighted_triggers
  • weighted_guards
  • (Or without @raftersvk's changes simply weighted_signals)
  • weighted_crosses (To be implemented)
@Rikj000 Rikj000 added Feature - New New feature or pull request Planned Planned feature, improvement or bugfix (not being worked on yet) labels Jan 17, 2022
@Rikj000 Rikj000 added this to Planned in MoniGoMani - Global Development Progress via automation Jan 17, 2022
@Rikj000 Rikj000 added this to the v1.0.0 milestone Jan 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature - New New feature or pull request Planned Planned feature, improvement or bugfix (not being worked on yet)
Development

No branches or pull requests

1 participant