#This is a sample file distributed with Galaxy that enables tools
#to use a directory of fasta and 2bit genome files for use with CREST. You will
#need to supply these files and then create a crest.loc file
#similar to this one (store it in this directory) that points to
#the directories in which those files are stored. The crest.loc
#file has this format (white space characters are TAB characters):
#
#<unique_build_id>   <display_name>   <fasta_path>	<2bit_path>
#
#So, for example, if your crest.loc began like this:
#
#hg19	Human (Homo sapiens): hg19	/depot/data2/galaxy/twobit/hg19.fa	/depot/data2/galaxy/twobit/hg19.2bit
#mm9	Mouse (Mus musculus): mm9	/depot/data2/galaxy/twobit/mm9.fa	/depot/data2/galaxy/twobit/mm9.2bit
#
#then your /depot/data2/galaxy/twobit/ directory
#would need to contain the following fasta and 2bit files:
#
#-rw-r--r--  1 james    universe 527388 2005-09-13 10:12 hg19.2bit
#-rw-r--r--  1 james    universe 527388 2005-09-13 10:12 hg19.fa
#-rw-r--r--  1 james    universe 269808 2005-09-13 10:12 mm9.2bit
#-rw-r--r--  1 james    universe 269808 2005-09-13 10:12 mm9.fa
#
#Your crest.loc file should include an entry per line for 
#each file you have stored that you want to be available. Note that 
#your files should all have the extension '2bit'.
#
#Note that for backwards compatibility with workflows, the unique ID of
#an entry must be the path that was in the original loc file, because that
#is the value stored in the workflow for that parameter. 
#
#hg18	Human (Homo sapiens): hg18	/depot/data2/galaxy/twobit/hg19.fa	/depot/data2/galaxy/twobit/hg19.2bit