Entering edit mode
2.9 years ago
Komalharini
•
0
I am trying to figure out what are the database names supported by blast+ 2.12.0 version remote command. Specifically, I want to get 16S and 18S database names.
The options I have tried so far are:
- 16S_ribosomal_RNA
- rRNA_typestrains
- 16S ribosomal RNA (Bacteria and Archaea type strains)
- 16SMicrobial
- rRNA/ITS
But it is not working... I searched for a documentation/question on this... nothing is available... Even on FTP the name is 16S_ribosomal_RNA... but the database name is not being recognized
For all of the above the same error is generated- "BLAST Database error: '16S_ribosomal_RNA' not found on NCBI servers"
Interesting observation (i.e. no info on which db are supported for remote blast). You should email blast helpdesk to get an authoritative answer and then post that here. Remote search may only support
nt,nr,pbdaa and swissprot
databases.Maybe:
This list does not fully work. As noted by OP (and tested by me) 16S_ribosomal_RNA (several other names at top of list, 16S, 18S, ITS, LSU, SSU) simply generate an error that the
database was not found on NCBI servers
.Of ones tested
nt, nr, pdbnt, pdbaa, refseq_protein and swissprot
work.Is there any update on this issue?
Im trying to use the human_genome database with the remote option but I still get:
BLAST Database error: 'human_genome' not found on NCBI servers.
Update:
Interestingly, typing
GPIPE/9606/current/ref_top_level
instead ofhuman_genome
works for me:One "problem" here is that I receive this error message:
Error: [blastn] Failed to fetch sequences in batch mode
In practice, though, all individual fastas of my multi-fasta query seem to be normally fetched and are included in the blast output.
edit: Just to clarify, I don't know if this solution is appropriate for end users, and I don't urge anyone to apply it. It's just an interesting observation.
I just wanted to pipe in to mention that I'm also getting the
Error: [blastn] Failed to fetch sequences in batch mode
message. I'm running a similar local blast query using-db GPIPE/9669/102/ref_top_level
(I'm BLASTn-ing against the ferret GPIPE accessions in a way advised by one of the NCBI employees when I reached out asking about GPIPE). Just like you, I seem to be getting the desired output hits, but I wanted to "second" your report about getting that message in case it's useful to anyone in the future who finds this thread.Interesting. So blast support actually told you to use this type of PATH for database for remote blast?
How did you figure out
GPIPE/9606/current/ref_top_level
path? It may be something NCBI has for internal use and may not be intended to be used by us.In web-BLAST, I searched a query sequence against refseq_genomes database while limiting results to Homo sapiens. I found the
GPIPE/9606/current/ref_top_level
path in the Database field of the results page:Just to clarify, I don't know if this solution is appropriate for end users, and I don't urge anyone to apply it, but I've had some trouble finding a better/faster alternative.
The following approach seems more appropriate,
though it's significantly slower and I still get this same error: