genomicsITER / NanoCLUST

NanoCLUST is an analysis pipeline for UMAP-based classification of amplicon-based full-length 16S rRNA nanopore reads
MIT License
106 stars 49 forks source link

No such variable: barcode #48

Open Socotr opened 3 years ago

Socotr commented 3 years ago

Hello, I've been trying to test the pipeline with one of my samples (fastq file) but every time I tried this error kept appearing (no matter if I use conda or docker ) :

ERROR ~ No such variable: barcode -- Check script 'main.nf' at line: 202 or see '.nextflow.log' file for more details.

Run Name : high_torvalds Reads : /home/nutrigenomics/bioinfo_soco/barcodes_4run_vsearch/barcode12.fastq Max Resources : 128 GB memory, 16 cpus, 10d time per job Output dir : ./results Launch dir : /home/nutrigenomics/NanoCLUST-master/ Working dir : /home/nutrigenomics/NanoCLUST-master/work Script dir : /home/nutrigenomics/NanoCLUST-master User : nutrigenomics Config Profile : conda Config Description: Minimal test dataset to check pipeline function ---------------------------------------------------- ERROR ~ No such variable: barcode -- Check script 'main.nf' at line: 202 or see '.nextflow.log' file for more details

The input file is a fastq file after nanopore sequencing. I would appreciate your response

Aline-Git commented 9 months ago

Hello, I have the same error message while runing the test (with nextflow 18.10.1) : nextflow run main.nf -profile test,docker

Here is the output :


NanoCLUST v1.0dev

Run Name : goofy_bassi Reads : /home/cluster/programs/NanoCLUST/test_datasets/mock4_run3bc08_5000.fastq Max Resources : 128 GB memory, 16 cpus, 10d time per job Container : docker - [:] Output dir : ./results Launch dir : /home/cluster/programs/NanoCLUST Working dir : /home/cluster/programs/NanoCLUST/work Script dir : /home/cluster/programs/NanoCLUST User : cluster Config Profile : test,docker Config Description: Minimal test dataset to check pipeline function

ERROR ~ No such variable: barcode

-- Check script 'main.nf' at line: 202 or see '.nextflow.log' file for more details


Any clue on where the error comes from would be appreciated.