Changing json names to show strain name #9
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
…ble to look at the different segment trees via tanglegrams. Currently, with accession number being the main ID, it is not possible to do so. This commit excludes duplicated sequences and then changes the node.name for in the auspice json from genbank acession number to strain name, allowing for the creation of tanglegrams
genehack
approved these changes
Aug 20, 2024
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.
related to issue #7
A temporary fix to manually remove duplicates and change the name displayed in the auspice json from accession to strain name. This allows for the visualization of the tanglegrams to investigate recombination.
This might be replaced by nextstrain/pathogen-repo-guide#59 (comment) in future.
Example tanglegram:
https://nextstrain.org/staging/oropouche/L:staging/oropouche/M