Mercurial > repos > devteam > megablast_wrapper

comparison tool-data/blastdb.loc.sample @ 0:fb0d744e32fa draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Imported from capsule None
author devteam
date Mon, 19 May 2014 10:59:45 -0400
parents
children
comparison
equal deleted inserted replaced
-1:000000000000 0:fb0d744e32fa
1 #This is a sample file distributed with Galaxy that is used to define a
2 #list of nucleotide 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 release date.
8 #It is important that the actual database name does not have a space in it.
9 #
10 #So, for example, if your database is nt and the path to your base name
11 #is /galaxy/data/blastdb/nt/DDmmmYYYY/nt, then the blastdb.loc entry
12 #could look like this:
13 #
14 #02dec2009 nt 02-Dec-2009 /galaxy/data/blastdb/nt/02dec2009/nt
15 #
16 #A /galaxy/data/blastdb/nt/02dec2009 directory would contain all of
17 #the "nt" blast indexes from ftp://ftp.ncbi.nlm.nih.gov/blast/db/nt* (e.g.):
18 #
19 #-rw-r--r-- 1 wychung galaxy 23437408 2008-04-09 11:26 nt.chunk.00.nhr
20 #-rw-r--r-- 1 wychung galaxy 3689920 2008-04-09 11:26 nt.chunk.00.nin
21 #-rw-r--r-- 1 wychung galaxy 251215198 2008-04-09 11:26 nt.chunk.00.nsq
22 #...etc...
23 #
24 #The blastdb.loc file should include one entry per line for each database.
25 #
26 #See also blastdb_p.loc, used for protein BLAST database.
27 #
28 #Note that for backwards compatibility with workflows, the <unique_id> of
29 #an entry must be the path that was in the original loc file.
30 #The metadata <unique_id> is the value stored in workflows for "database".
31 #