Define arbitrary number of MAPseq databases in config#77
Open
timrozday-mgnify wants to merge 11 commits intomainfrom
Open
Define arbitrary number of MAPseq databases in config#77timrozday-mgnify wants to merge 11 commits intomainfrom
timrozday-mgnify wants to merge 11 commits intomainfrom
Conversation
…inal test snapshot
…is run, and update file sizes where the tsv headers have been fixed.
Contributor
Author
|
|
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
1 participant
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.
Changed the way MAPseq databases are defined (used for assigning taxonomy to reads and to ASVs). They are now defined in the config params and an arbitrary number can be described and they will all be used. The details are in the new README.md.
There are a few very slight differences in the test snapshots. These are to do with "SILVA-SSU" in the TSV header instead of "SSU". "SILVA-SSU" is preferable, so this is feature! Also, I removed the nf-prov output bco.json from the file-lines and file-size snapshots because it is highly variable with full-length paths in it.
A parallel PR for pipelines-nextflow-configs is in the works...