Fix drawdown behavior#297
Merged
twiecki merged 3 commits intoquantopian:masterfrom May 11, 2016
brdsio:master
Merged
Conversation
Contributor
|
Thanks @flaviodrt! Still some PEP8 issues that should be easy to fix: (you can use flake8 to check and autopep8 to autofix) |
Contributor
Author
|
Hi @twiecki! Sorry for that. |
Contributor
|
Thanks. Some of the failures seem unrelated and are probably due to pandas 0.18.1. However, these two are related: |
Contributor
Author
|
I think that were related to pandas 0.18.1 because the other tests in previous commits before my changes were failing too. |
Contributor
|
Yep, that looks great. Thanks for the fix! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drawdown function does not work properly.
If one series had a drawdown from 2 to 1 and a drawdown from 10 to 6, pyfolio was considering the second one as the higher drawdown, but in fact the first drawdown was -50% and the second one was -40%.
This commit resolves this issue: #179
I added the tests for the both cases.