Fix: update dropped strains file to list accession instead of strain names - #26
Merged
Conversation
victorlin
approved these changes
Feb 12, 2024
victorlin
left a comment
Member
There was a problem hiding this comment.
Wow, this looks like some manual work! I haven't changed these files before. Added some non-blocking suggestions from my perspective.
Rename the file dropped_strains.txt to exclude.txt to better reflect its purpose since it lists accession numbers instead of strain names. This file is a list of sequences to exclude from analysis and gets passed to `augur filter --exclude`.
joverlee521
added a commit
to nextstrain/pathogen-repo-guide
that referenced
this pull request
Feb 13, 2024
Based on conversation in dengue PR nextstrain/dengue#26 (comment)
4 tasks
joverlee521
added a commit
to nextstrain/zika
that referenced
this pull request
Jun 4, 2025
Prompted by previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/zika
that referenced
this pull request
Jun 5, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/zika
that referenced
this pull request
Jun 5, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/zika
that referenced
this pull request
Jun 6, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/mpox
that referenced
this pull request
Jun 25, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/mpox
that referenced
this pull request
Jul 1, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/mpox
that referenced
this pull request
Jul 1, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
joverlee521
added a commit
to nextstrain/mpox
that referenced
this pull request
Jul 2, 2025
Simplify the name of the config files in preparation for support for `nextstrain run`. Also inline with previous discussion on `exclude.txt` in <nextstrain/dengue#26 (comment)>
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.
Description of proposed changes
In the phylogenetic workflow, we initially listed strains slated to be dropped from the build (due to excessive divergence or misclassification) in the config/dropped_strain.txt file, identified by their strain names. Subsequently, we transitioned to using "accession" numbers to identify strains after merging the ingest pipeline (and using ncbi-datasets api) 8ab810f. However, updating the corresponding dropped strain list was missed resulting in these strains not being appropriately dropped from the build.
This commit addresses this issue by adding accession numbers to ensure proper dropping of these records.
Steps to find accessions:
metadata.tsvfile, the associated accession numbers are used.(e.g.
DAK_Ar_510is probably a shorter name forDENV2/COTE_D_IVOIRE/DAKAR510/1980)metadata.tsvfile for those collected in the same year and country, considering potential differences in underscores or hyphens separating the strain name (e.g.DENV1/VIETNAM/BIDV992/2006equivalent toDENV-1/VN/BID-V992/2006).DENV/SPAIN/EEB17/2009led to https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3149010/ which led to accession numberJF260983)Related issue(s)
Checklist
Post Merge rebase and update checklist