Closed gabyrech closed 8 months ago
Hi, thanks for reporting this, we will see if we can reproduce.
Hi, would you be able to update your nextflow version to >=23.04.2
and try to run the workflow again?
Hi, just run it with version 23.04.4
and got the same error... I am attaching the .nextflow.log
file FYI... thanks!
nextflow.log
Hi, thanks for that. I am just trying to recreate the error. Would you mind sharing you sample sheet with me if you are using one?
Sure, here you go: sample_sheets_run1.txt
Hi, great thanks. I was able to recreate your error. We will add a fix to the workflow shortly with handling for Aliases that could be all numbers. Sorry for that! In the mean time the workflow should complete if you were to rename barcode03 alias with a name that included a letter but we will add a fix soon.
Thanks, @sarahjeeeze ! renaming barcode03 to something starting with a letter fixed the issue. Now the workflow finished completely. Thanks!
Operating System
CentOS 7
Other Linux
No response
Workflow Version
v0.5.2
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
$ nextflow run epi2me-labs/wf-clone-validation -revision prerelease -profile singularity --fastq 'fastq/run1' --basecaller_cfg 'dna_r9.4.1_e8_hac@v3.3' --sample_sheet 'sample_sheets/run1.txt' --out_dir 'results_run1'
Workflow Execution - CLI Execution Profile
singularity
What happened?
Running the command above on a ONT run containing 9 barcodes: ..fastq$ tree -L 2 . └── run1 ├── barcode01 ├── barcode02 ├── barcode03 ├── barcode04 ├── barcode05 ├── barcode06 ├── barcode07 ├── barcode08 └── barcode09 Assenblies were generated for all the nine (I do see the 9 *.final.fasta files in the output directory). But then I get the error below during the report generation.
Note: Running similar command on the _testdata worked ok (a.k.a finished all processes):
$ nextflow run epi2me-labs/wf-clone-validation -revision prerelease -profile singularity --fastq 'wf-clone-validation/test_data/test' --out_dir 'wf-clone-validation_output_prerelease_v0.5.2'
Relevant log output
Application activity log entry
No response