# HG changeset patch # User iuc # Date 1466952615 14400 # Node ID 1e74f16adaa19acd83f1b296cebfbcf85e2b84af # Parent ecbdfc775b9a56124e5d805ac048eec8de7b829e planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/jbrowse commit 942848a0ccd21064ad5d9ee237d1442a5ef47664 diff -r ecbdfc775b9a -r 1e74f16adaa1 all_fasta.loc.sample --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/all_fasta.loc.sample Sun Jun 26 10:50:15 2016 -0400 @@ -0,0 +1,18 @@ +#This file lists the locations and dbkeys of all the fasta files +#under the "genome" directory (a directory that contains a directory +#for each build). The script extract_fasta.py will generate the file +#all_fasta.loc. This file has the format (white space characters are +#TAB characters): +# +# +# +#So, all_fasta.loc could look something like this: +# +#apiMel3 apiMel3 Honeybee (Apis mellifera): apiMel3 /path/to/genome/apiMel3/apiMel3.fa +#hg19canon hg19 Human (Homo sapiens): hg19 Canonical /path/to/genome/hg19/hg19canon.fa +#hg19full hg19 Human (Homo sapiens): hg19 Full /path/to/genome/hg19/hg19full.fa +# +#Your all_fasta.loc file should contain an entry for each individual +#fasta file. So there will be multiple fasta files for each build, +#such as with hg19 above. +# diff -r ecbdfc775b9a -r 1e74f16adaa1 tool_data_table_conf.xml.sample --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool_data_table_conf.xml.sample Sun Jun 26 10:50:15 2016 -0400 @@ -0,0 +1,9 @@ + + + + + value, dbkey, name, path + +
+
+