|
0
|
1 #This is a sample file distributed with Galaxy that enables tools
|
|
|
2 #to use a directory vcf file for covacs sequences data files. You will need
|
|
|
3 #to create these data files and then create a vcf_loc.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 vcf_loc.loc
|
|
|
6 #file has this format (longer white space characters are TAB characters):
|
|
|
7 #
|
|
|
8 #<unique_id> <display_name> <file_path>
|
|
|
9 #
|
|
|
10 #So, for example, if you had vcf file stored in
|
|
|
11 #/export/resource/,
|
|
|
12 #then the covacs_vcf.loc entry would look like this:
|
|
|
13 #
|
|
|
14 #hapmap hapmap /export/resource/hapmap.vcf
|
|
|
15 #
|
|
|
16 #and your /export/resource directory
|
|
|
17 #would contain hapmap.vcf.
|
|
|
18 #
|
|
|
19 #
|
|
|
20 #Your covacs_vcf.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.
|
|
|
23 #Note that for backwards compatibility with workflows, the unique ID of
|
|
|
24 #an entry must be the path that was in the original loc file, because that
|
|
|
25 #is the value stored in the workflow for that parameter.
|
|
|
26 #
|
|
9
|
27 #hapmap hapmap /export/resources/hapmap.vcf
|
|
|
28 #1000G 1000G /export/resources/1000G.vcf
|
|
0
|
29
|
