Mercurial > repos > crs4 > blat

comparison tool-data/lastz_seqs.loc.sample @ 2:6265acc179ff draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Uploaded
author crs4
date Mon, 04 Nov 2013 06:35:53 -0500
parents
children
comparison
equal deleted inserted replaced
1:c4ad58c4bc7d 2:6265acc179ff
1 #This is a sample file distributed with Galaxy that enables tools
2 #to use a directory of 2bit genome files for use with Lastz. You will
3 #need to supply these files and then create a lastz_seqs.loc file
4 #similar to this one (store it in this directory) that points to
5 #the directories in which those files are stored. The lastz_seqs.loc
6 #file has this format (white space characters are TAB characters):
7 #
8 #<unique_build_id> <display_name> <file_path>
9 #
10 #So, for example, if your lastz_seqs.loc began like this:
11 #
12 #hg18 Human (Homo sapiens): hg18 /depot/data2/galaxy/twobit/hg18.2bit
13 #hg19 Human (Homo sapiens): hg19 /depot/data2/galaxy/twobit/hg19.2bit
14 #mm9 Mouse (Mus musculus): mm9 /depot/data2/galaxy/twobit/mm9.2bit
15 #
16 #then your /depot/data2/galaxy/twobit/ directory
17 #would need to contain the following 2bit files:
18 #
19 #-rw-r--r-- 1 james universe 830134 2005-09-13 10:12 hg18.2bit
20 #-rw-r--r-- 1 james universe 527388 2005-09-13 10:12 hg19.2bit
21 #-rw-r--r-- 1 james universe 269808 2005-09-13 10:12 mm9.2bit
22 #
23 #Your lastz_seqs.loc file should include an entry per line for
24 #each file you have stored that you want to be available. Note that
25 #your files should all have the extension '2bit'.
26 #
27 #Note that for backwards compatibility with workflows, the unique ID of
28 #an entry must be the path that was in the original loc file, because that
29 #is the value stored in the workflow for that parameter.
30 #