We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@AngieHinrichs, there seems to be a second XEC branch on recent usher trees derived via KP.3 plus multiple flip-flops.
It eventually result in same mutations as XEC and starts attracting XEC seqs. Both XEC.2 seqs and XEC+Orf1a:A599T seqs are attracted.
This needs fix.
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/hgPhyloPlace/subtreeAuspice96_genome_test_3d266_cb7590.json?label=id:node_5762563
The text was updated successfully, but these errors were encountered:
And all XEC.2 sequences are placed on it and not identified as XEC.2.
Sorry, something went wrong.
Thanks for reporting that! Should be fixed in tomorrow's build (2025-01-24).
No branches or pull requests
@AngieHinrichs, there seems to be a second XEC branch on recent usher trees derived via KP.3 plus multiple flip-flops.
It eventually result in same mutations as XEC and starts attracting XEC seqs. Both XEC.2 seqs and XEC+Orf1a:A599T seqs are attracted.
This needs fix.
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/hgPhyloPlace/subtreeAuspice96_genome_test_3d266_cb7590.json?label=id:node_5762563
The text was updated successfully, but these errors were encountered: