Incorrect GFF location with sequence that is 100% CRISPR #4

Closed
fangly opened this Issue Jul 18, 2014 · 2 comments

Comments

Projects
None yet
3 participants
Contributor

fangly commented Jul 18, 2014

Miriam Shiffman has reported a problem when running Prokka. With Minced 0.1.5, I could trace back the problem to a contig that is covered at 100% by CRISPRs.

minced -gff troublesomeContig.fa results.gff

troublesomeContig.fa is:

707_L1_merged_contig_534811
GTCGCCCCTCACGCAGGGGCGTGAGTTGAAATGGTTCCTTAGCCATCACGCACCCACCTC
CGCAACATGTCGCCCCTCACGCAGGGGCGTGGGTTGAAATTTAACTTGCGTTTCCAGCAT
CACCGGTTTCTGCGCGTCGCCCCTCACGCAGGGGCGTGAGTTGAAATGGCCTGCGGGGAG
GTGATGCCGCATGATCGTAAGCAGTCGCCCCTCACGCAGGGGCGTGAGTTGAAATTGCTC
GCGAACATGCGCCGCCTGTAAATACTCCCGGTCGCCACTCACGCAGGGGCGTGAGTTGAA
AT

results.gff is:

gff-version 3

707_L1_merged_contig_534811 minced:0.1.5 CRISPR 1 303 5 . . ID=CRISPR1

The contig is 302 bp long, but the reported end of the CRISPR region is 303 (i.e. beyond the end of the contig). This is what causes trouble in Prokka. I cannot investigate further and dig in the code at the moment. It will have to wait until next week (or until Connor fixes this :)

Florent

Owner

ctSkennerton commented Jul 19, 2014

Fixed in version 0.1.6

tseemann referenced this issue in tseemann/prokka Jul 26, 2014

Closed

Exception: Bad end parameter #21

This resolves my bug too:
Victorian-Bioinformatics-Consortium/prokka#21
I've updated my version and requirements:
tseemann/prokka@e4dfd70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment