use stochastic polytomy resolution #1069
Merged
Conversation
This file contains 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
|
Now that the docker container has augur 22.0.1, I could finally test this. The trial open run is here: https://nextstrain.org/staging/ncov/open/trial/stochastic-resolve/global/all-time (and the other resolutions). Generally, I think this is a big improvement, in particular for recent builds with large polytomies. The
and with stochastic resolution would look like this
(the difference is even starker for |
|
Comparing live tree and the trial run I think this is a huge improvement and fits with coalescent expectation for tree structure. Thanks @rneher! |
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.
Stochastic polytomy resolution is faster and leads to more typical trees. The previous (still default in treetime) mode resulted in caterpillar like trees.