Mercurial > repos > galaxyp > custom_pro_db
comparison tool-data/customProDB.loc.sample @ 0:8ccfff69dd57 draft
planemo upload for repository https://github.com/galaxyproteomics/tools-galaxyp/tools/bumbershoot/custom_pro_db commit 4bb5b663989d5f04e8fb74b111456f16d6edaa66
author | galaxyp |
---|---|
date | Tue, 14 Mar 2017 14:14:38 -0400 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:8ccfff69dd57 |
---|---|
1 #This file lists the locations and dbkeys of all the fasta files | |
2 #under the "genome" directory (a directory that contains a directory | |
3 #for each build). The script extract_fasta.py will generate the file | |
4 #all_fasta.loc. This file has the format (white space characters are | |
5 #TAB characters): | |
6 # | |
7 #<unique_build_id> <dbkey> <display_name> <file_path> | |
8 # | |
9 #So, all_fasta.loc could look something like this: | |
10 # | |
11 #apiMel3 apiMel3 Honeybee (Apis mellifera): apiMel3 /path/to/genome/apiMel3/apiMel3.fa | |
12 #hg19canon hg19 Human (Homo sapiens): hg19 Canonical /path/to/genome/hg19/hg19canon.fa | |
13 #hg19full hg19 Human (Homo sapiens): hg19 Full /path/to/genome/hg19/hg19full.fa | |
14 # | |
15 #Your all_fasta.loc file should contain an entry for each individual | |
16 #fasta file. So there will be multiple fasta files for each build, | |
17 #such as with hg19 above. | |
18 # |