The goal of ChromoZoom is to make genome browsing as effortless as navigating the world on Google Maps, while retaining the data density and customizability of UCSC's browser.
To achieve this goal, this project stitches images from the UCSC Genome Browser into tiles, and presents these tiles via a dynamic web interface called ChromoZoom.
Although the below steps will most directly guide you toward setting up your own instance of ChromoZoom, the tiles created by the tile stitcher could conceivably power other visualizations.
ChromoZoom is free for academic, nonprofit, and personal use. The source code is licensed under the GNU Affero General Public License v3. In a nutshell, this license means that you are free to copy, redistribute, and modify the source code, but you are expected to provide the source for any code derived from ChromoZoom to anybody that receives the modified code or uses it over a computer network (e.g. as a web application). ChromoZoom is not free for commercial use. For commercial licensing, please contact the Roth laboratory.
ChromoZoom was designed to run in a *NIX environment and has been tested on OS X and Debian Linux. The web interface should work in any recent version of a modern HTML5-capable web browser (apologies to IE users).
To generate tiles
- Ruby ≥1.8.x and rake.
- The curl command line tool for fetching URLs.
- The ImageMagick command line tools. Specifically,
- Several Ruby gems, most easily acquired with a
On Mac OS X with MacPorts, this should be enough to get you started:
$ sudo port install ImageMagick $ sudo port install libxml2 libxslt $ sudo gem install bundler $ cd path/to/this/repo && bundle install
On a Debian, like Ubuntu:
$ sudo apt-get install imagemagick curl $ sudo apt-get install ruby ruby1.8 rake rubygems $ sudo apt-get install libxslt-dev libxml2-dev $ sudo gem install bundler $ which bundle || sudo ln -s /var/lib/gems/1.8/bin/bundle /usr/local/bin/bundle $ cd path/to/this/repo && bundle install
If you are using Homebrew or one of the other Linuxes, Nokogiri's instructions can help you get the right libxml2 and libxslt. Then, you will need to search your package manager for ImageMagick, Ruby, and RubyGems, and
gem install bundler followed by
bundle install should take you the rest of the way.
By default, the tile stitcher will scrape the public UCSC browser and save files directly to the file system. This method has significant limitations that will likely not permit the scraping of most genomes within a reasonable amount of time or disk space. Therefore, we strongly encourage installing all of the components in Recommended Enhancements further down in this README.
To serve the ChromoZoom web interface
- PHP 5.x + Apache (or another webserver that can run PHP scripts)
- libcurl bindings for PHP (included in OS X's default PHP install)
- If you would like to support the full range of custom tracks, you need the following on your
$PATH, which during setup will be symlinked into a new directory in this repo called
Place a checkout of this repo somewhere in your webserver's DOCROOT. Files under
php/ will need to be executable by the webserver. After generating tiles and a JSON configuration for your genome of interest (detailed in Usage), you will access
index.html from a web browser to view the ChromoZoom interface.
All interactions with the tile stitcher are performed via rake. To check that you have all the above requirements,
cd into this repo and run
$ rake check
This will warn you about missing components that are not required, but will fail if the tools needed for tile stitching are not available. If everything checks out, you can get started by simply typing
which will guide you through all the steps of selecting an available genome, creating a configuration for this genome, and grabbing tiles. The typical workflow is as follows (replacing GENOME with the respective name of the UCSC genome database):
- Create a YAML configuration for a genome:
- Edit the YAML configuration to your liking
- Generate tiles according to this configuration:
- Generate the JSON configuration that initializes the web interface:
Once you have tiles and the JSON configuration, ensure your webserver is running and open
index.php in your web browser to see the ChromoZoom interface.
In the first step of the workflow, you create a minimal YAML configuration file for a genome using properties acquired from UCSC. You may want to customize this file, e.g., to include or exclude certain tracks or to change the zoom levels that will be scraped. Two example configurations have been included in this repo at
sacCer3.example.yaml; please read their comments for details on how to customize your own.
Using multiple workers
The third step of the workflow, or
rake tiles[GENOME], is usually the most time-consuming. You can parallelize it by running multiple
rake tiles processes at once; each process will lock the directories it is working on and therefore should be able to avoid trampling work done by others. NOTE: You should only run multiple workers if you have installed a local instance of the UCSC browser as described under Recommended Additions, otherwise you risk running afoul of UCSC's usage limits on their public site.
To launch NUMBER worker processes in a split layout of GNU
screen, you can run
$ rake tiles[GENOME,0,NUMBER]
You will be able to monitor what the processes are doing by their output, and terminate them if necessary by sending SIGINT to each split-screen or with
kill from another terminal. For more information on usage of
screen please check your system's manpage with
None of the following components are strictly necessary for running the ChromoZoom software; however, it is likely that you will need them to have ChromoZoom operate at scale. In the preferable order of installation, they are:
- A local installation of the UCSC browser
- A Tokyo Cabinet for storing and retrieving tile images
- Building the native extension for image processing
Installing a local instance of the UCSC browser
Installing UCSC locally is not for the faint of heart and will likely require a dedicated machine with plenty of disk space. However, it will allow you to scrape tiles much faster than the one hit per 15 seconds allowed by the public UCSC browser and enforced by the tile scraper. If you modify the code to ignore this limit, you risk being banned by the public UCSC browser.
Instructions for creating a mirror of the UCSC browser are available from UCSC. Rsync'ing all the required files may take several days. Once you have verified it is working (e.g., you can load it in a web browser), add the URL for your local install to
ucsc.yaml under the key
For maximum performance, scraping tiles directly from the machine(s) running your local genome browser allows the tile stitcher to call the CGI binaries directly, avoiding the overhead of the network, HTTP, and the Apache server. If you can run the tile stitcher from the same machine(s) that have the kentsrc CGI binaries, set
ucsc.yaml to the directory that contains them (e.g.,
/var/www/website/cgi-bin), then set the
cgi_bin. If you must run the tile stitcher from a different machine, set
local to scrape your local genome browser using HTTP requests to the
One significant modification we made to our local install of UCSC was to increase the maximum pixel width for images, which decreases the frequency of "seams" in genomic features at closer zoom levels. A patch is available in
kentsrc-rothlab.patch. To apply it, first navigate to the root of the kentsrc tree:
$ cd path/to/kentsrc && ls
if you're in the right place, you should see
build java python src. Then,
$ patch -p0 < path/to/this/repo/kentsrc-rothlab.patch $ export ROTHLAB=1 $ cd src && make clean
and re-compile and install the binaries as instructed in
src/product/README.building.source in the Kent source tree. Note that our additions are conditional on the
ROTHLAB environment variable being set when running
make, as included in the above example.
Installing Tokyo Cabinet for tile storage
By default tiles are saved to the filesystem, but this is not recommended for production usage as many of these files will be smaller than a typical 4k filesystem block and therefore as much as 90% of your hard disk may be wasted on empty space. Additionally, there is overhead in creating and traversing directory structures to access the tiles. Tokyo Cabinet is a persistent, fast, and durable hashtable that increases the efficiency of storing and retrieving billions of relatively small key-value pairs. Tokyo Tyrant provides a network interface to this hashtable that simplifies simultaneous usage by multiple processes. ChromoZoom supports saving its scraped tiles directly to a Tokyo Cabinet hashtable (.tch) file, and retrieving them for the web interface.
To support this you must install:
- the Tokyo Cabinet and Tokyo Tyrant binaries somewhere on your
$PATH, along with their respective libraries
- the rufus-tokyo gem (should have been installed by
On OS X, the binaries are available via MacPorts in the
tokyotyrant portfiles, but Tokyo Tyrant appears to have a bug with UNIX domain sockets. Inconveniently, the only fix is to download the Tokyo Tyrant source directly, apply a patch provided in this repo as
ttserver-macosx-socketfix.patch, and install it over the MacPorts binary. So, in total:
$ sudo port install tokyocabinet tokyotyrant $ cd /tmp && curl -O http://fallabs.com/tokyotyrant/tokyotyrant-1.1.41.tar.gz $ tar xvzf tokyotyrant-1.1.41.tar.gz $ cd tokyotyrant-1.1.41 $ patch -p0 < path/to/this/repo/ttserver-macosx-socketfix.patch $ ./configure --prefix=/opt/local && make && sudo make install
If you are on Debian ≥6.0.0 "squeeze" or Ubuntu ≥10.10 "maverick" all binaries should be available as packages, so all you need is:
$ sudo apt-get install tokyocabinet tokyotyrant
The tile stitcher will take care of starting a Tokyo Tyrant instance for each genome that you are scraping. You will find
*.sock UNIX domain sockets appear in
/tmp while these servers are running. However, in a production environment, you may wish to start these servers automatically with init scripts.
Building the native extension for image processing
This enhancement will perhaps only make a difference if you are processing large genomes across many machines and the (very inefficient) image processing performed by the ImageMagick utilities begins to consume a significant fraction of your render time. However, it is very easy to install. You must have
make, and the Ruby development headers to build the extension. If you are are on Mac OS X with MacPorts, you already have all these things. In the unlikely event that you are on Debian and don't have them, you can fix that with:
$ sudo apt-get install build-essential ruby1.8-dev
Once you're ready to proceed, go to the root of this repo and run:
$ rake build_native
and the files under
ext/ will be compiled into a Ruby extension suitable for your platform. If this works, you will no longer see the "native image processing extension" warning when you start the tile stitcher.
Note that the native extension will only run if you have installed Tokyo Cabinet per the directions above.