Closed wolfgangrumpf closed 4 years ago
Hi there,
Can you try removing the space between the '>' char and the 'NODE' names and let me know if that works?
Thanks, Paul
Hi, I'm getting the same error and my fasta file doesn't have a space in the name. Any ideas why this would fail?
Hi, can you send me an example FASTA file that causes the issue please? Thanks
I'm trying with this file:
and getting this error:
classify: malformed fasta file - expected header char > not found 0 sequences (0.00 Mbp) processed in 0.006s (0.0 Kseq/m, 0.00 Mbp/m). 0 sequences classified (-nan%) 0 sequences unclassified (-nan%)
thanks
Hi there,
I can't see anything wrong with that FASTA file. I'm afraid I do not understand why you are experiencing errors. What is the full command you are using?
I'm using this comand: ./FindFungi-0.23.3.sh output_contigs.txt P752101
Ah, I see. The pipeline is designed for FASTQ files. You can convert your FASTA to FASTQ with tools such as this one: https://code.google.com/archive/p/fasta-to-fastq/. (NOTE: the additional information used to buff out the FASTA to FASTQ conversion will not mean anything)
I found a FASTA that doesn't seem to play well with FindFungi. The directory structure is created, but Kraken seems to fail for some reason with this error:
Loading database... complete. classify: malformed fasta file - expected header char > not found 0 sequences (0.00 Mbp) processed in 0.008s (0.0 Kseq/m, 0.00 Mbp/m). 0 sequences classified (-nan%) 0 sequences unclassified (-nan%)
The input file does have the > character - here's some sample sequences:
Any ideas why this would fail?