# HG changeset patch # User iuc # Date 1678707229 0 # Node ID 67832417fba21de5ce04ffaffe89d5f9a56cc8da # Parent 1919ba3fa175b51ebfdc7491e7a2afce1d87b3bf planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/pbmm2 commit 037e03be14baed6dbb55af7830dc0e61d1a48862 diff -r 1919ba3fa175 -r 67832417fba2 tool-data/all_fasta.loc.sample --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool-data/all_fasta.loc.sample Mon Mar 13 11:33:49 2023 +0000 @@ -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 1919ba3fa175 -r 67832417fba2 tool_data_table_conf.xml.sample --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool_data_table_conf.xml.sample Mon Mar 13 11:33:49 2023 +0000 @@ -0,0 +1,6 @@ + + + value, dbkey, name, path + +
+
\ No newline at end of file