Mercurial > repos > bgruening > nanopolish_methylation
changeset 9:5ba6aaa39140 draft
"planemo upload for repository https://github.com/bgruening/galaxytools/tree/master/tools/nanopolish commit dff183f4eb2d3df42917ec4fed0fbdb2ea11e19a"
author | bgruening |
---|---|
date | Fri, 29 May 2020 17:27:52 +0000 |
parents | af4ac35cab87 |
children | db21aa55d799 |
files | test-data/all_fasta.loc test-data/all_fasta.loc.sample tool-data/all_fasta.loc.sample |
diffstat | 3 files changed, 21 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/test-data/all_fasta.loc Fri May 29 17:27:52 2020 +0000 @@ -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/test-data/all_fasta.loc.sample Fri May 29 17:27:52 2020 +0000 @@ -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 May 29 17:27:52 2020 +0000 @@ -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. +# +