5
|
1 #This is a sample file distributed with Galaxy that enables tools
|
|
2 #to use a directory of MuTect2 indexed sequences data files. You will need
|
|
3 #to create these data files and then create a mutect2_indexes.loc file
|
|
4 #similar to this one (store it in this directory) that points to
|
|
5 #the directories in which those files are stored. The mutect2_indexes.loc
|
|
6 #file has this format (longer white space characters are TAB characters):
|
|
7 #
|
|
8 #<unique_build_id> <dbkey> <display_name> <file_path>
|
|
9 #
|
|
10 #So, for example, if you had phiX indexed stored in
|
|
11 #/depot/data2/galaxy/phiX/base/,
|
|
12 #then the bwa_index.loc entry would look like this:
|
|
13 #
|
|
14 #phiX174 phiX phiX Pretty /depot/data2/galaxy/phiX/base/phiX.fa
|
|
15 #
|
|
16 #and your /depot/data2/galaxy/phiX/base/ directory
|
|
17 #would contain phiX.dict, phiX.fa.fai files.
|
|
18 #
|
|
19 #
|
|
20 #Your mutect2_indexes.loc file should include an entry per line for each
|
|
21 #index set you have stored. The "file" in the path does not actually
|
|
22 #exist, but it is the prefix for the actual index files. For example:
|
|
23 #
|
|
24 #phiX174 phiX phiX174 /depot/data2/galaxy/phiX/base/phiX.fa
|
|
25 #hg18canon hg18 hg18 Canonical /depot/data2/galaxy/hg18/base/hg18canon.fa
|
|
26 #hg18full hg18 hg18 Full /depot/data2/galaxy/hg18/base/hg18full.fa
|
|
27 #/orig/path/hg19.fa hg19 hg19 /depot/data2/galaxy/hg19/base/hg19.fa
|
|
28 #...etc...
|
|
29 #
|
|
30 #Note that for backwards compatibility with workflows, the unique ID of
|
|
31 #an entry must be the path that was in the original loc file, because that
|
|
32 #is the value stored in the workflow for that parameter. That is why the
|
|
33 #hg19 entry above looks odd. New genomes can be better-looking.
|
|
34 #
|
|
35 hg38 hg38 hg38_GDC /export/gatkhg38pl/GRCh38.d1.vd1.fa
|