Mercurial > repos > bgruening > nanopolish_eventalign
changeset 4:cf069dea4554 draft
planemo upload for repository https://github.com/bgruening/galaxytools/tree/master/tools/nanopolish commit 4478b7f7e16d56ff6c1ffa24ded1fc106f2379c6-dirty
| author | bgruening |
|---|---|
| date | Fri, 14 Jun 2019 13:04:31 -0400 |
| parents | ec4ac1a63682 |
| children | c63b6a7c7b7e |
| files | test-data/all_fasta.loc test-data/all_fasta.loc.test tool-data/all_fasta.loc.sample |
| diffstat | 3 files changed, 20 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- 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
--- /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
--- /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. +# +