# HG changeset patch
# User bgruening
# Date 1560531871 14400
# Node ID cf069dea4554ad5de59231e91a46015ae25fabb6
# Parent  ec4ac1a63682fd1576501e3dfd38ba6ee33522c2
planemo upload for repository https://github.com/bgruening/galaxytools/tree/master/tools/nanopolish commit 4478b7f7e16d56ff6c1ffa24ded1fc106f2379c6-dirty

diff -r ec4ac1a63682 -r cf069dea4554 test-data/all_fasta.loc
--- a/test-data/all_fasta.loc	Fri Jun 14 08:36:58 2019 -0400
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-draft	draft	draft	${__HERE__}/draft.fa
\ No newline at end of file
diff -r ec4ac1a63682 -r cf069dea4554 test-data/all_fasta.loc.test
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/test-data/all_fasta.loc.test	Fri Jun 14 13:04:31 2019 -0400
@@ -0,0 +1,1 @@
+draft	draft	draft	${__HERE__}/draft.fa
\ No newline at end of file
diff -r ec4ac1a63682 -r cf069dea4554 tool-data/all_fasta.loc.sample
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tool-data/all_fasta.loc.sample	Fri Jun 14 13:04:31 2019 -0400
@@ -0,0 +1,19 @@
+#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.
+#
+