Skip to content

Commit

Permalink
Merge pull request #587 from dannon/retab_loc_samples
Browse files Browse the repository at this point in the history
Retab .loc.samples
  • Loading branch information
nturaga committed Aug 11, 2015
2 parents 7baab04 + ee4f077 commit a04147d
Show file tree
Hide file tree
Showing 10 changed files with 28 additions and 28 deletions.
8 changes: 4 additions & 4 deletions tool-data/all_fasta.loc.sample
Expand Up @@ -4,13 +4,13 @@
#all_fasta.loc. This file has the format (white space characters are
#TAB characters):
#
#<unique_build_id> <dbkey> <display_name> <file_path>
#<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
#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,
Expand Down
4 changes: 2 additions & 2 deletions tool-data/faseq.loc.sample
Expand Up @@ -20,7 +20,7 @@
#Your faseq.loc file should include an entry per line for each set of fasta
#sequence files you have stored. For example:
#
#hg18 /depot/data2/galaxy/faseq/hg18
#mm9 /depot/data2/galaxy/faseq/mm9
#hg18 /depot/data2/galaxy/faseq/hg18
#mm9 /depot/data2/galaxy/faseq/mm9
#Arabidopsis /depot/data2/galaxy/faseq/Arabidopsis
#...etc...
2 changes: 1 addition & 1 deletion tool-data/liftOver.loc.sample
Expand Up @@ -8,7 +8,7 @@
#located at /depot/data2/galaxy/anoCar1/liftOver/anoCar1ToGalGal3.over.chain,
#then the liftOver.loc entry would look like this:
#
#anoCar1 galGal3 /depot/data2/galaxy/anoCar1/liftOver/anoCar1ToGalGal3.over.chain
#anoCar1 galGal3 /depot/data2/galaxy/anoCar1/liftOver/anoCar1ToGalGal3.over.chain
#
#and your /depot/data2/galaxy/anoCar1/liftOver directory would
#contain all of your "chain" files (e.g.):
Expand Down
4 changes: 2 additions & 2 deletions tool-data/mosaik_index.loc.sample
Expand Up @@ -5,13 +5,13 @@
#the directories in which those files are stored. The mosaik_index.loc
#file has this format (longer white space is the TAB character):
#
#<unique_build_id> <dbkey> <display_name> <fasta_file_path>
#<unique_build_id> <dbkey> <display_name> <fasta_file_path>
#
#So, for example, if you had hg18 indexed and stored in
#/depot/data2/galaxy/mosaik/hg18/
#then the mosaik_index.loc entry would look like this:
#
#hg18 hg18 hg18 Pretty /depot/data2/galaxy/mosaik/hg18/hg18.fa
#hg18 hg18 hg18 Pretty /depot/data2/galaxy/mosaik/hg18/hg18.fa
#
#and your /depot/data2/galaxy/mosaik/hg18/ directory
#would contain the following files:
Expand Down
6 changes: 3 additions & 3 deletions tool-data/ngs_sim_fasta.loc.sample
Expand Up @@ -4,7 +4,7 @@
#in this directory) that points to the locations of those files. The ngs_sim.loc
#file has this format (white space characters are TAB characters):
#
#<unique_build_id> <dbkey> <display_name> <file_base_path>
#<unique_build_id> <dbkey> <display_name> <file_base_path>
#
#So, for example, if you had hg18chrM.fa in
#/data/path/hg18/seq/,
Expand All @@ -16,5 +16,5 @@
#have stored.
#
#hg18chrM hg18 hg18chrM /data/path/hg18/seq/hg18chrM.fa
#phiX174 phiX phiX174 /data/path/genome/phiX/seq/phiX.fa
#pUC18 pUC18 pUC18 /data/path/genome/pUC18/seq/pUC18.fa
#phiX174 phiX phiX174 /data/path/genome/phiX/seq/phiX.fa
#pUC18 pUC18 pUC18 /data/path/genome/pUC18/seq/pUC18.fa
12 changes: 6 additions & 6 deletions tool-data/perm_base_index.loc.sample
Expand Up @@ -5,23 +5,23 @@
#the directories in which those files are stored. The perm_base_index.loc
#file has this format (longer white space characters are TAB characters):
#
#<build_seed_readlength> <display_name> <file_base>
#<build_seed_readlength> <display_name> <file_base>
#
#Because each PerM index is built with a specific seed and a specific read
#length, this needs to be specified so the user can choose the appropriate
#one. So, for example, if you had phiX indexed with seed F3 and read length
#50, and stored in /depot/data/galaxy/phiX/perm_index/,
#then the perm_base_index.loc entry would look something like this:
#
#phiX_F3_50 phiX: seed=F3, read length=50 /depot/data/galaxy/phiX/perm_index/phiX_base_F3_50.index
#phiX_F3_50 phiX: seed=F3, read length=50 /depot/data/galaxy/phiX/perm_index/phiX_base_F3_50.index
#
#and your /depot/data/galaxy/phiX/perm_index/ directory
#would contain the file phiX_base_F3_50.index:
#
#Your perm_base_index.loc file should include an entry per line for each
#index set you have stored. For example:
#
#phiX_F3_50 phiX: seed=F3, read length=50 /data/galaxy/phiX/perm_index/phiX_base_F3_50.index
#phiX_F4_50 phiX: seed=F4, read length=50 /data/galaxy/phiX/perm_index/phiX_base_F3_50.index
#hg19_F3_50 hg19: seed=F3, read length=50 /data/galaxy/hg19/perm_index/hg19_base_F3_50.index
#hg19_F4_50 hg19: seed=F4, read length=50 /data/galaxy/hg19/perm_index/hg19_base_F3_50.index
#phiX_F3_50 phiX: seed=F3, read length=50 /data/galaxy/phiX/perm_index/phiX_base_F3_50.index
#phiX_F4_50 phiX: seed=F4, read length=50 /data/galaxy/phiX/perm_index/phiX_base_F3_50.index
#hg19_F3_50 hg19: seed=F3, read length=50 /data/galaxy/hg19/perm_index/hg19_base_F3_50.index
#hg19_F4_50 hg19: seed=F4, read length=50 /data/galaxy/hg19/perm_index/hg19_base_F3_50.index
12 changes: 6 additions & 6 deletions tool-data/perm_color_index.loc.sample
Expand Up @@ -5,24 +5,24 @@
#the directories in which those files are stored. The perm_color_index.loc
#file has this format (white space characters are TAB characters):
#
#<build_seed_readlength> <display_name> <file_base>
#<build_seed_readlength> <display_name> <file_base>
#
#Because each PerM index is built with a specific seed and a specific read
#length, this needs to be specified so the user can choose the appropriate
#one. So, for example, if you had phiX indexed with seed F3 and read length
#50, and stored in /depot/data/galaxy/phiX/perm_index/,
#then the perm_color_index.loc entry would look something like this:
#
#phiX_F3_50 phiX: seed=F3, read length=50 /data/galaxy/phiX/perm_index/phiX_color_F3_50.index
#phiX_F3_50 phiX: seed=F3, read length=50 /data/galaxy/phiX/perm_index/phiX_color_F3_50.index
#
#and your /depot/data/galaxy/phiX/perm_index/ directory
#would contain the file phiX_color_F3_50.index:
#
#Your perm_color_index.loc file should include an entry per line for each
#index set you have stored. For example:
#
#phiX_F3_50 phiX: seed=F3, read length=50 /data/galaxy/phiX/perm_index/phiX_color_F3_50.index
#phiX_F4_50 phiX: seed=F4, read length=50 /data/galaxy/phiX/perm_index/phiX_color_F3_50.index
#hg19_F3_50 hg19: seed=F3, read length=50 /data/galaxy/hg19/perm_index/hg19_color_F3_50.index
#hg19_F4_50 hg19: seed=F4, read length=50 /data/galaxy/hg19/perm_index/hg19_color_F3_50.index
#phiX_F3_50 phiX: seed=F3, read length=50 /data/galaxy/phiX/perm_index/phiX_color_F3_50.index
#phiX_F4_50 phiX: seed=F4, read length=50 /data/galaxy/phiX/perm_index/phiX_color_F3_50.index
#hg19_F3_50 hg19: seed=F3, read length=50 /data/galaxy/hg19/perm_index/hg19_color_F3_50.index
#hg19_F4_50 hg19: seed=F4, read length=50 /data/galaxy/hg19/perm_index/hg19_color_F3_50.index
#
4 changes: 2 additions & 2 deletions tool-data/picard_index.loc.sample
Expand Up @@ -5,13 +5,13 @@
#the directories in which those files are stored. The picard_index.loc
#file has this format (longer white space is the TAB character):
#
#<unique_build_id> <dbkey> <display_name> <fasta_file_path>
#<unique_build_id> <dbkey> <display_name> <fasta_file_path>
#
#So, for example, if you had hg18 indexed and stored in
#/depot/data2/galaxy/srma/hg18/,
#then the srma_index.loc entry would look like this:
#
#hg18 hg18 hg18 Pretty /depot/data2/galaxy/picard/hg18/hg18.fa
#hg18 hg18 hg18 Pretty /depot/data2/galaxy/picard/hg18/hg18.fa
#
#and your /depot/data2/galaxy/srma/hg18/ directory
#would contain the following three files:
Expand Down
2 changes: 1 addition & 1 deletion tool-data/regions.loc.sample
Expand Up @@ -8,7 +8,7 @@
#/depot/data2/galaxy/regions/encode_regions_coords_hg16.bed, then the
#regions.loc entry would look like this:
#
#hg16 encode_hg16 ENCODE Regions /depot/data2/galaxy/regions/encode_regions_coords_hg16.bed
#hg16 encode_hg16 ENCODE Regions /depot/data2/galaxy/regions/encode_regions_coords_hg16.bed
#
#and your /depot/data2/galaxy/regions/ directory would
#contain all of your regions files (e.g.):
Expand Down
2 changes: 1 addition & 1 deletion tool-data/srma_index.loc.sample
Expand Up @@ -8,7 +8,7 @@
#the directories in which those files are stored. The srma_index.loc
#file has this format (longer white space is the TAB character):
#
#<unique_build_id> <dbkey> <display_name> <fasta_file_path>
#<unique_build_id> <dbkey> <display_name> <fasta_file_path>
#
#So, for example, if you had hg18 indexed and stored in
#/depot/data2/galaxy/srma/hg18/,
Expand Down

0 comments on commit a04147d

Please sign in to comment.