Mercurial > repos > galaxyp > custom_pro_db_annotation_data_manager
view tool-data/customProDB.loc.sample @ 4:b42974daa659 draft
planemo upload for repository https://github.com/galaxyproteomics/tools-galaxyp/tools/bumbershoot/data_manager_customProDB commit 141369f97aa2804d2bbfd9ed620ea2a5574994c2-dirty
author | galaxyp |
---|---|
date | Thu, 28 Jan 2016 18:46:50 -0500 |
parents | 4c77cf5a2977 |
children | a0ca66b32792 |
line wrap: on
line source
#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. #