# HG changeset patch
# User fubar
# Date 1720929347 0
# Node ID 36b8c6f7601b7449f3a603928e4eef8154b08555
# Parent  9f2709bb1722fdbcadebcd0186f1a3f7d4ec5c71
planemo upload for repository https://github.com/fubar2/microsatbed commit 7ceb6658309a7ababe622b5d92e729e5470e22f0-dirty

diff -r 9f2709bb1722 -r 36b8c6f7601b all_fasta.loc.sample
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/all_fasta.loc.sample	Sun Jul 14 03:55:47 2024 +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):
+#
+#<unique_build_id>	<dbkey>		<display_name>	<file_path>
+#
+#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 9f2709bb1722 -r 36b8c6f7601b test-data/all_fasta.loc
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/test-data/all_fasta.loc	Sun Jul 14 03:55:47 2024 +0000
@@ -0,0 +1,22 @@
+#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.
+#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):
+#
+#<unique_build_id>      <dbkey> <display_name>  <file_path>
+#
+#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.
+#
+hgtest	hgtest	hgtest	${__HERE__}/humsamp.fa
diff -r 9f2709bb1722 -r 36b8c6f7601b tool_data_table_conf.xml.sample
--- a/tool_data_table_conf.xml.sample	Sun Jul 14 02:59:17 2024 +0000
+++ b/tool_data_table_conf.xml.sample	Sun Jul 14 03:55:47 2024 +0000
@@ -2,6 +2,6 @@
     <!-- Locations of all fasta files under genome directory -->
     <table name="all_fasta" comment_char="#">
         <columns>value, dbkey, name, path</columns>
-        <file path="tool-data/all_fasta.loc.sample" />
+        <file path="test-data/all_fasta.loc" />
     </table>
 </tables>
diff -r 9f2709bb1722 -r 36b8c6f7601b tool_data_table_conf.xml.test
--- a/tool_data_table_conf.xml.test	Sun Jul 14 02:59:17 2024 +0000
+++ b/tool_data_table_conf.xml.test	Sun Jul 14 03:55:47 2024 +0000
@@ -1,7 +1,7 @@
 <tables>
     <!-- Locations of dbkeys and len files under genome directory -->
-    <table name="__dbkeys__" comment_char="#" allow_duplicate_entries="False">
+    <table name="all_fasta" comment_char="#">
         <columns>value, dbkey, name, path</columns>
-        <file path="${__HERE__}/tool-data/all_fasta.loc.sample" />
+        <file path="${__HERE__}/test-data/all_fasta.loc" />
     </table>
 </tables>