Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve MaxDrawDownHyperOptLoss #10221

Merged
merged 2 commits into from
May 20, 2024
Merged

improve MaxDrawDownHyperOptLoss #10221

merged 2 commits into from
May 20, 2024

Conversation

xmatthias
Copy link
Member

Summary

Improve calculation of MaxDrawDownHyperOptLoss.

Replaces #10216
closes #10192

@stash86 would love if you could give this a look / try - i think this improves the calculation - and for me, this yields quite nice results in the optimization.

@xmatthias xmatthias added Enhancement Enhancements to the bot. Get lower priority than bugs by default. Hyperopt Hyperopt related issues and pull requests labels May 19, 2024
@xmatthias xmatthias requested a review from stash86 May 19, 2024 08:12
@coveralls
Copy link

Coverage Status

coverage: 94.683%. remained the same
when pulling 480477d on hyp/profit-drawdown
into acae6e7 on develop.

@stash86
Copy link
Contributor

stash86 commented May 19, 2024

Sure. Gonna check it later

Copy link
Contributor

@stash86 stash86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems good

@xmatthias xmatthias merged commit 1717733 into develop May 20, 2024
33 checks passed
@xmatthias xmatthias deleted the hyp/profit-drawdown branch May 20, 2024 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Enhancements to the bot. Get lower priority than bugs by default. Hyperopt Hyperopt related issues and pull requests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hyperopt loss going wrong way ?
3 participants