# HG changeset patch
# User cpt
# Date 1690046142 0
# Node ID c62acc3e4bf69fd145ef22d4237c6b365c9fb9a7
# Parent 9c03867832fc083552df66d68fbe2fc1147da1e3
planemo upload commit 852ac96ca53a2ffa0947e6df5e24671866b642f5
diff -r 9c03867832fc -r c62acc3e4bf6 all_fasta.loc.sample
--- a/all_fasta.loc.sample Sat Jul 22 17:13:37 2023 +0000
+++ b/all_fasta.loc.sample Sat Jul 22 17:15:42 2023 +0000
@@ -1,8 +1,18 @@
-
-
-
-
- value, dbkey, name, path
-
-
-
\ No newline at end of file
+#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.
+#
\ No newline at end of file
diff -r 9c03867832fc -r c62acc3e4bf6 tool_data_table_conf.xml.sample
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/tool_data_table_conf.xml.sample Sat Jul 22 17:15:42 2023 +0000
@@ -0,0 +1,8 @@
+
+
+
+
+ value, dbkey, name, path
+
+
+
\ No newline at end of file