-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
endorspy erroring in nf-core/ender workflow #1083
Comments
Pinging @aidaanva |
Hi @VerbalCant Looking into the nextflow.log that you provided it seems that nf-core/eager does not parse correctly your input files into a tsv file. The names get shorten to only "_L0 "for the initial steps (fastqc, adapter removal) which then when trying to generate the bam files, the file name is further shorten to "". That's why you are seeing the error:
Since no files are produced, endorspy can not be run and I think this is why the workflow showed you this error. My recommendation is that you give your input as a tsv since this is a safer way and ensures that the pipeline extracts the correct sample and library names. You can find documentation as of how set up the tsv for nf-core/eager here: https://nf-co.re/eager/2.5.2/docs/usage/#tsv-input-method Let me know whether using the TSV input method solves the issue and if not I will take another look. |
Hey @aidaanva thanks for the quick reply! I can confirm that using the tsv input method, as described in the docs you linked, resolves this. Closing the issue, and hoping it helps somebody else in the future! |
Check Documentation
I have checked the following places for your error:
- nf-core/eager FAQ/troubleshooting can be found here
Description of the bug
endors.py step is failing in a way that seems to be related to program arguments. The nf-core/eager version in
bin/endors.py
, which is what is being called, is quite a bit different than the current release version of [endors.py(https://github.com/aidaanva/endorS.py), but I don't think that matters. If I can make a guess of what's happening based on the extra space between the-n
and the_flagstat_stats
below, perhaps it's passing an empty value to--name/-n
?. If I look at the code here, it looks like might have an empty/nulllibrary_id
?I do also note the earlier warnings about the _rmdup files, where they're specifying the destination off of root,
/_rmdup.bam
, instead of what I presume should be more like./_rmdup.bam
? I don't have any evidence that they're related.Steps to reproduce
Steps to reproduce the behaviour:
NXF_VER=22.10.6 nextflow run nf-core/eager -profile docker --input '*Momia3_S2_L001_R1_001_merged.fastq.gz' --fasta /references/reference_genomes/hg38.analysisSet.fa --max_memory 60GB --max_cpus 16 --max_time 288.h -config nextflow_custom.config --run_genotyping true --save_reference --genotyping_tool 'freebayes' --run_mtnucratio true --run_sexdeterrmine true --run_nuclear_contamination true --single_end true --mapper bowtie2 -resume
It fails with this error the first time it hits endors.py, which (I can confirm) is the one called from the version in
nf-core/eager/bin
. It fails on subsequent runs with-resume
, and if I clean the directory, remove all subdirectories, and start again from scratch.Expected behaviour
I expected it to proceed through the endorS.py step and move on to the next step of the workflow.
Log files
Have you provided the following extra information/files:
The command used to run the pipeline
The
.nextflow.log
file: nextflow.logThe exact error:
System
Nextflow Installation
Container engine
Additional context
The reads are a PE aDNA run that was merged using (NGmerge) into a single fastq.
I can confirm that the working directory contains the symlink to the _flagstat.stats:
The
.nextflow.log
file: nextflow.logThe text was updated successfully, but these errors were encountered: