You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A couple of months ago we had a slack thread about how NFCORE_FUNCSCAN:FUNCSCAN:GUNZIP_PYRODIGAL_FNA gets confused with meta.id and gz file path if sample names are repeated along full path to fasta file.
The topic is discussed here on slack.
Fix: Changing sample names solves the problem.
ERROR ~ Error executing process > 'NFCORE_FUNCSCAN:FUNCSCAN:GUNZIP_PYRODIGAL_FNA ([GCA_001438805.1.fna.gz, GCA_001438805.1_ASM143880v1_genomic.fna.gz])'
Caused by:
Missing output file(s) `GCA_001438805.1.fna GCA_001438805.1_ASM143880v1_genomic.fna.gz` expected by process `NFCORE_FUNCSCAN:FUNCSCAN:GUNZIP_PYRODIGAL_FNA ([GCA_001438805.1.fna.gz, GCA_001438805.1_ASM143880v1_genomic.fna.gz])`
Command executed:
# Not calling gunzip itself because it creates files
# with the original group ownership rather than the
# default one for that user / the work directory
gzip \
-cd \
\
GCA_001438805.1.fna.gz GCA_001438805.1_ASM143880v1_genomic.fna.gz \
> GCA_001438805.1.fna GCA_001438805.1_ASM143880v1_genomic.fna.gz
cat <<-END_VERSIONS > versions.yml
"NFCORE_FUNCSCAN:FUNCSCAN:GUNZIP_PYRODIGAL_FNA":
gunzip: $(echo $(gunzip --version 2>&1) | sed 's/^.*(gzip) //; s/ Copyright.*$//')
END_VERSIONS
Command exit status:
0
Command output:
(empty)
Work dir:
/home/test/.work/e1/6e71e01659781bea8f6deb48144838
Tip: when you have fixed the problem you can continue the execution adding the option `-resume` to the run command line
-- Check '.nextflow.log' file for details
ERROR ~ Failed to invoke `workflow.onComplete` event handler
-- Check script '/home/.nextflow/assets/nf-core/funcscan/./workflows/funcscan.nf' at line: 314 or see '.nextflow.log' file for more details
Look again, Im' even more confused. I think the issue is coming further upstream, but I'm not sure where at the moment.
I have a suspion there is a faulty join function that is somehow merging the original FASTAs with some processed onat asome point. Then all downstream modules are for some reason get recieving both FASTAs rather than one.
That said, why cahnging the name would affect that I have no idea.
Description of the bug
A couple of months ago we had a slack thread about how
NFCORE_FUNCSCAN:FUNCSCAN:GUNZIP_PYRODIGAL_FNA
gets confused with meta.id and gz file path if sample names are repeated along full path to fasta file.The topic is discussed here on slack.
Fix: Changing sample names solves the problem.
The input file which resulted in this error was:
changing the input file to the following fixed the issue:
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: