When pharokka is run on a set of contigs, then having duplicate fasta ids is an issue that crashes the run. However, it only crashes towards the end of the run when the .gff file is converted to genbank. It should of course be on the user to make sure that the input fasta files don't contain duplicate IDs, but it would be more user friendly to have pharokka do a check for them in the beginning of the run and exit if it finds a duplicate ID. This way, the user loses a lot less time if there is a mistake in the file.
Description
When pharokka is run on a set of contigs, then having duplicate fasta ids is an issue that crashes the run. However, it only crashes towards the end of the run when the .gff file is converted to genbank. It should of course be on the user to make sure that the input fasta files don't contain duplicate IDs, but it would be more user friendly to have pharokka do a check for them in the beginning of the run and exit if it finds a duplicate ID. This way, the user loses a lot less time if there is a mistake in the file.
What I Did
This was in the log:
Unfortunately, I don't have the error message from the stdout anymore, but it did say it crashed because of duplicate fasta IDs.
Great tool!