Mercurial > repos > iuc > jvarkit_wgscoverageplotter
diff tool-data/all_fasta.loc.sample @ 2:70efe7b19018 draft
"planemo upload for repository https://github.com/galaxyproject/iuc/tree/master/tools/jvarkit commit dd0745115487da9c9e9f51c7049619263a055b8e"
| author | iuc |
|---|---|
| date | Thu, 11 Feb 2021 10:32:04 +0000 |
| parents | |
| children |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool-data/all_fasta.loc.sample Thu Feb 11 10:32:04 2021 +0000 @@ -0,0 +1,20 @@ +#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 +#sars-cov-2 SARS-CoV-2 SARS-CoV-2 (MN908947.3) /depot/data/MN908947_3_Wuhan-Hu-1.fasta +# +#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