Mercurial > repos > devteam > ncbi_blast_plus
comparison blastdb_p.loc.sample @ 0:d375502056f1 draft
Uploaded
author | devteam |
---|---|
date | Fri, 17 Aug 2012 09:11:43 -0400 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:d375502056f1 |
---|---|
1 #This is a sample file distributed with Galaxy that is used to define a | |
2 #list of protein BLAST databases, using three columns tab separated | |
3 #(longer whitespace are TAB characters): | |
4 # | |
5 #<unique_id> <database_caption> <base_name_path> | |
6 # | |
7 #The captions typically contain spaces and might end with the build date. | |
8 #It is important that the actual database name does not have a space in it, | |
9 #and that the first tab that appears in the line is right before the path. | |
10 # | |
11 #So, for example, if your database is NR and the path to your base name | |
12 #is /data/blastdb/nr, then the blastdb_p.loc entry would look like this: | |
13 # | |
14 #nr NCBI NR (non redundant) /data/blastdb/nr | |
15 # | |
16 #and your /data/blastdb directory would contain all of the files associated | |
17 #with the database, /data/blastdb/nr.*. | |
18 # | |
19 #Your blastdb_p.loc file should include an entry per line for each "base name" | |
20 #you have stored. For example: | |
21 # | |
22 #nr_05Jun2010 NCBI NR (non redundant) 05 Jun 2010 /data/blastdb/05Jun2010/nr | |
23 #nr_15Aug2010 NCBI NR (non redundant) 15 Aug 2010 /data/blastdb/15Aug2010/nr | |
24 #...etc... | |
25 # | |
26 #See also blastdb.loc which is for any nucleotide BLAST database. | |
27 # |