I've added the support for Nextclade to identify differences between the input sequences and reference sequences used by Nextstrain as well as reports potential sequence quality issues in the input sequence. It also describes the clades which are defined by specific signature mutations as defined by Nextstrain.
Why
This will give the information if the clades are groups of related sequences that share a common ancestor and uses the phylogenetic context to assign clades.
How
I've added the NextcladeJS to the conda dependency in the environment.yml files for both Illumina and Nanopore workflows.
process nextclade is added to the /modules/typing.nf and also the process included in the workflows/illuminaNcov.nf and workflows/articNcovNanopore.nf.
Testing
I've tested the process nextclade with a full run of the pipeline in the local machine as well as NGP server for both Illumina and Nanopore test data and both are working fine.
@sylvinite
What
I've added the support for Nextclade to identify differences between the input sequences and reference sequences used by Nextstrain as well as reports potential sequence quality issues in the input sequence. It also describes the clades which are defined by specific signature mutations as defined by Nextstrain.
Why
This will give the information if the clades are groups of related sequences that share a common ancestor and uses the phylogenetic context to assign clades.
How
I've added the NextcladeJS to the conda dependency in the environment.yml files for both Illumina and Nanopore workflows. process nextclade is added to the /modules/typing.nf and also the process included in the workflows/illuminaNcov.nf and workflows/articNcovNanopore.nf.
Testing
I've tested the process nextclade with a full run of the pipeline in the local machine as well as NGP server for both Illumina and Nanopore test data and both are working fine. @sylvinite