Closed d4straub closed 1 year ago
To address the first error, one could use Nextflow as a macro language instead of using R's file.exists("")
and place the conditional processing in a Nextflow block before the R script.
Example pseudocode, assuming a Nextflow variable otu_table
that contains the path to an otu table:
script:
read_otu_table = otu_table.exists() ? "otu_table <- read_otu_table('${otu_table}') : ""
...
"""
$read_otu_table
"""
Thanks for the idea, I fixed it in the draft PR above on nextflow level by making the output optional and therefore output an empty channel in case of fasta file input. Works so far.
Description of the bug
nextflow run nf-core/ampliseq -r dev -profile test_fasta,singularity --outdir results_fasta -resume --max_len_asv 265
fails with:Additionally, when using
nextflow run nf-core/ampliseq -r dev -profile test_fasta,singularity --outdir results_fasta -resume --vsearch_cluster
VSEARCH doesnt cluster anything, the process simply doesnt run, but no error.Also, with the following settings the pipeline doesnt classify (no error!):
nextflow run nf-core/ampliseq -r dev -profile test_fasta,singularity --outdir results_fasta -resume --filter_ssu bac
nextflow run nf-core/ampliseq -r dev -profile test_fasta,singularity --outdir results_fasta -resume --filter_codons
Command used and terminal output
No response
Relevant files
No response
System information
current dev, but
nextflow run nf-core/ampliseq -r dev -profile test_fasta,singularity --outdir results_fasta -resume --filter_ssu bac
nextflow run nf-core/ampliseq -r dev -profile test_fasta,singularity --outdir results_fasta -resume --filter_codons
should also not work as expected with version 2.6.1 (but not tested).