/tool-data/regions.loc.sample

https://bitbucket.org/cistrome/cistrome-harvard/ · Unknown · 24 lines · 24 code · 0 blank · 0 comment · 0 complexity · 3a87802b1f0a9edbfe20b5f1ec22bab7 MD5 · raw file 

    

  1. #This is a sample file distributed with Galaxy that is used by some
    2. 

  2. #ENCODE tools.  The regions.loc file has this format (white space 
    3. 

  3. #characters are TAB characters):
    4. 

  4. #
    5. 

  5. #<build>	<uid>	<region_description>	<file_path>
    6. 

  6. #
    7. 

  7. #So, for example, if you had ENCODE Regions for build hg16 stored in 
    8. 

  8. #/depot/data2/galaxy/regions/encode_regions_coords_hg16.bed, then the
    9. 

  9. #regions.loc entry would look like this:
    10. 

  10. #
    11. 

  11. #hg16	encode_hg16		ENCODE Regions	/depot/data2/galaxy/regions/encode_regions_coords_hg16.bed
    12. 

  12. #
    13. 

  13. #and your /depot/data2/galaxy/regions/ directory would 
    14. 

  14. #contain all of your regions files (e.g.):
    15. 

  15. #
    16. 

  16. #-rw-r--r--   1 dan  g2cache 1367 2006-03-14 13:55 encode_regions_coords_hg16.bed
    17. 

  17. #-rw-r--r--   1 dan  g2cache 1367 2006-03-14 13:53 encode_regions_coords_hg17.bed
    18. 

  18. #...etc...
    19. 

  19. #
    20. 

  20. #Your regions.loc file should include an entry per line for each region 
    21. 

  21. #file you have stored.  For example:
    22. 

  22. #
    23. 

  23. #hg16	encode_hg16	ENCODE Regions	/depot/data2/galaxy/regions/encode_regions_coords_hg16.bed 
    24. 

  24. #hg17	encode_hg17	ENCODE Regions	/depot/data2/galaxy/regions/encode_regions_coords_hg17.bed
    25.