Mercurial > repos > galaxyp > custom_pro_db_annotation_data_manager
comparison tool-data/customProDB.loc.sample @ 0:45755942ae7b 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:11:55 -0400 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:45755942ae7b |
|---|---|
| 1 #This file lists the locations and dbkeys of all the fasta files | |
| 2 #under the "customProDB" directory (a subdirectory of a genome build). | |
| 3 #This file has the format (white space characters are TAB characters): | |
| 4 # | |
| 5 #<unique_build_id> <dbkey> <display_name> <path to annotation files> | |
| 6 # | |
| 7 #So, all_fasta.loc could look something like this: | |
| 8 # | |
| 9 #apiMel3 apiMel3 Honeybee (Apis mellifera): apiMel3 /path/to/genome/apiMel3 | |
| 10 #hg19canon hg19 Human (Homo sapiens): hg19 Canonical /path/to/genome/hg19 | |
| 11 #hg19full hg19 Human (Homo sapiens): hg19 Full /path/to/genome/hg19full | |
| 12 # | |
| 13 #Your customProDB.loc file should contain an entry for each individual | |
| 14 #fasta file. So there will be multiple fasta files for each build, | |
| 15 #such as with hg19 above. | |
| 16 # |