Download ChromHMM tracks H3K27ac marks (as BED file) from Roadmap
2
2
Entering edit mode
9.5 years ago
komal.rathi ★ 4.1k

I can easily view the chromHMM tracks for Roadmap project but not able to download the bed files from the UCSC genome browser. I want the bed files for H3K27ac marks for a couple of tissues like Heart Left Ventricle, Fetal Heart etc. I am attaching a screenshot of the browser with Heart Left Ventricle chromHMM track. Also, this is the link for the same at UCSC Genome Browser just in case the screenshot does not upload. The track is second from top and names chromHMM tracks from Roadmap.

< image not found >

Does anyone know how to download these tracks as bed files?

BED UCSC-Genome-Browser H3k27ac Roadmap ChromHMM • 6.4k views
ADD COMMENT
1
Entering edit mode
9.5 years ago
komal.rathi ★ 4.1k

I had emailed Ting Wang (of the Roadmap Epigenomics Project) and he promptly replied back addressing my question. Here is the answer to this question, in his own words:

All the original chromHMM tracks are here for you to download: https://sites.google.com/site/anshulkundaje/projects/epigenomeroadmap

All Roadmap/ENCODE data are available through the WashU EpiGenome Browser (http://epigenomegateway.wustl.edu/). If you right-click on any track and select "information", you will usually see a url for data source.

ADD COMMENT
1
Entering edit mode
9.5 years ago
Denise CS ★ 5.2k

Hi, this track hub is hosted at WashU. If you click on the track itself on the UCSC genome browser you will be taking to http://goo.gl/X9pVFg. At the bottom of it, there is Ting Wang's email address for further contact. Perhaps they would be able to help downloading the bed files?

Brian Lee (UCSC Genome Bioinformatics Group) has addressed a similar question on the UCSC genome browser discussion list (https://groups.google.com/a/soe.ucsc.edu/forum/#!topic/genome/yIyZZKyfLrU). This is an extract of his answer that could be useful to you:

To access the files you are seeing displayed in the browser, you can navigate their public hub's directories and find the trackDb file that points via "bigDataUrl" statements to the location of each file displayed. Below are some short scripts you can put on the command line that will pull out those statements and create links via the relative location of the defined files. First obtains the URLs of all the files, followed by just the .bigBed and .bb files, however, not filtered for only the ChromHMM track.

curl -silent http://vizhub.wustl.edu/VizHub/hg19/trackDb_dli_edacc8_new4.txt | grep bigDataUrl | sed -e 's#^.*bigDataUrl # http://vizhub.wustl.edu/VizHub/hg19/#'
curl -silent http://vizhub.wustl.edu/VizHub/hg19/trackDb_dli_edacc8_new4.txt | grep bigDataUrl | sed -e 's#^.*bigDataUrl #http://vizhub.wustl.edu/VizHub/hg19/#' | grep 'bb\|bigBed'

These are the binary bigBed files that can be turned into bed files with the bigBedToBed utility located in the appropriate directory here: http://hgdownload.soe.ucsc.edu/admin/exe/

Another approach is to use our Table Browser. With the hub data displayed in the browser, click the top "Tools" button and navigate to the Table Browser and then set the group to "Roadmap Epigenomics Data Complete Collection at Wash U VizHub" and then select the "Roadmap ChromHMM" track at the very bottom of tracks. You could then choose each table and get the output from each track individually as bed files.

I suggest investigating the resources for accessing this externally hosted data (Public Track Hubs are not created or maintained by UCSC). You may also be interested in these tutorials about accessing Roadmap Epigenomics Data: http://www.genome.gov/27555330

ADD COMMENT
0
Entering edit mode

I looked at this discussion before posting the question here actually. I tried searching for the URLs (bigDataUrl) for the files that I need, couldn't find any. Also emailed Ting Wang a couple of hours back. Waiting for his reply. Thanks anyway!

ADD REPLY

Login before adding your answer.

Traffic: 1719 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6