Skip to content

AlleleCall not detecting valid .fna input files (v2.8.5) #218

@EdDjonlagic2

Description

@EdDjonlagic2

Hi,

I’m having trouble running chewBBACA.py AlleleCall (v2.8.5). I’ve tried providing a directory of valid .fna files as input using the -i flag, but I consistently get this error:

'Could not get input files. Please provide a directory with FASTA files or a file with the list of full paths to the FASTA files and ensure that filenames end with one of the following suffixes: ['.fasta', '.fna', '.ffn', '.fa'].'

All of the .fna files:
• Are standard multi-entry FASTA files (CDS predicted from Prokka)
• Are readable and non-empty
• Have correct extensions (.fna)
• Contain hundreds of CDS entries each

I also tried renaming them to .fasta, and using a text file (.txt) with full paths to the .fna files (one per line) and still the same result.

I noticed there were similar issues reported in earlier versions of chewBBACA but I haven’t seen anything specific to v2.8.5. Has something changed in how input files are validated?

Thanks in advance for your help!

—Ed

Metadata

Metadata

Assignees

Labels

Status: In ProgressHas been assigned and is being worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions