SHARED private genomes are not recognized by BLAST sometimes

[Sveta-user]

Greetings,
Sharing private genomes with other user(s) is a very useful feature in PATRIC. And it works smoothly by the most part, except with the Blast tool. Blast breaks (sometimes) if at least one genome in a group is a "shared private". Strangely this problem comes and goes: on some days shared genomes are recognized by BLAST, but other times they break Blast (like today)
The regular private genomes work reliably with blast all the time

In the example below I can view shared genome 1597.515, but not blast against it (not today at least ;))

Error creating BLAST FNA database for 1597.515 (owned by [email protected]): No contig sequences found in genome

[olsonanl]

This is a different issue than what we were seeing before; in this genome the contig sequences are tagged with sequence types of plasmid and chromosome, where the blast service is looking for sequence types of contig for building the database.

Have contig blasts been working for you with other genomes? I'll need to look into updating the code to properly pull the contigs.

[Sveta-user]

Interesting... Didn't realize that genome ownership or sharing was not the only issue with blast. Now that you pointed it out, I looked at many genome that work fine with BLAST - and nearly all of them have "contig" as sequence type. But there is one exception: 391904.5 has "chromosome" , but works with blast nonetheless -

While 1597.515 that does NOT work with blast has a "plasmid" and 2 "chromosome" labeled contigs. Can it be that only the presence of a "plasmid" contig breaks blast..?

Thank you for looking into this issue, Bob!

[Sveta-user]