Open fanninpm opened 1 year ago
Yeah, Nextclade should call the clades for us and pangolin can be removed for hmpxv.
Code changes to make:
modules/local/bbtools.nf
:
BBMAP_ALIGN
(and BBMAP_INDEX
): find a way to store the index on-disk instead of in-memorymodules/local/ivar.nf
: perhaps tweaking a few parameters related to ivar
and samtools
modules/local/misc.nf
:
DATA_PREP
:--schema-name
argument customizableedirect
to download iVar GFF (if the GFF straight from NCBI gives better iVar results than the GFF from nextclade_data)LINEAGE_EXCEL
: make pangolin input optionalSPIKE_GENE_COVERAGE
: see #10 TRAFFIC_LIGHT_PLOT
: in the future, explain what it representsmodules/local/nextclade.nf
: make name and reference (accession) customizablemodules/local/vadr.nf
: move params.vadr_{mdir,options,reference,trim_options}
out to main.nf
or a subworkflowmain.nf
: implement logic for handling SARS-CoV-2 vs. hMPXV
modules/local/misc.nf
:
DATA_PREP
:make
--schema-name
argument customizablein the future, use
edirect
to download iVar GFF (if the GFF straight from NCBI gives better iVar results than the GFF from nextclade_data)
LINEAGE_EXCEL
: make pangolin input optional
Yeah, the LINEAGE_EXCEL
file would not need to be created, or anything like it, for this initial conversion of taking fastq data and turning it into a consensus fasta.
SPIKE_GENE_COVERAGE
: see GeneralizeSPIKE_GENE_COVERAGE
to cover all genes #10
Can we just ignore edits/improvements to SPIKE_GENE_COVERAGE
process while trying to get to hmpxv conversion?
As discussed today, we should name these primers something like "hMPXV_YSPH".
Most of the current workflow should be compatible with the references for hMPXV. However, pangolin seems to be exclusive to SARS-CoV-2.