-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Wolfgang Maier
committed
Nov 11, 2017
1 parent
99cc35e
commit b36048c
Showing
1 changed file
with
18 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
#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. | ||
# |