UCSC Genome Bioinformatics

Quick Start Guide to Assembly Hubs

Assembly Hubs allow researchers to create Track Data Hubs on assemblies that are not in the UCSC Browser. By including the underlying reference sequence in UCSC twoBit format, as well as data tracks, researchers can browse and annotate any genome. For more information please refer to the Assembly Hub Wiki. Below is also a section about starting GBiB Assembly Hubs.

    STEP 1: In a publicly-accessible directory, copy this Arabidopsis thaliana plant assembly hub, which includes an araTha1.2bit file, using the following wget command:

    wget -r --no-parent --reject "index.html*" -nH --cut-dirs=3 http://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubAssembly/plantAraTha1/

      Alternatively, if you do not have wget installed, you can curl these files individually. Perform the curl -O option in the location you wish to copy the files: curl -O http://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubAssembly/plantAraTha1/hub.txt

      If you use curl, be sure to recreate the structure with matching araTha1 and araTha1/bbi directories. Double check you have all the files by looking here: http://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubAssembly/plantAraTha1/

    STEP 2: Paste your hub.txt link (http://yourURL/hub.txt) into the My Hubs tab of the Track Data Hubs page, click the "Add Hub" button, and then click the "Genome Browser" link from the top bar.

    STEP 3: Congratulations! Your assembly hub should display!

      If you are having problems, be sure all your files and the directories are publicly-accessible. You may also wish to reset the browser occastionally to clear all existing data. For hubs to work, your server must also accept byte-ranges. You can check using the following command to verify "Accept-Ranges: bytes" displays: curl -I http://yourURL/hub.txt

    Now that you have the assembly hub copied from above, you can copy the directory and start to edit some of the documents like genomes.txt, groups.txt, and trackDb.txt to understand how they work. Refer to the Assembly Hub Wiki to understand how to build a twoBit file for your own original fasta files. Read more about trackDb settings in the definition document.

    This assembly hub is a an abbreviated version of a larger plant assembly Public Hub. You can explore the larger hub structure here.

    Please note that the Browser waits 300 seconds before checking for any changes to these files. When editing hub.txt, genomes.txt, trackDb.txt, and related hub files shorten this delay by adding udcTimeout=1 to your URL. For more information, please see the Debugging and Updating Track Hubs section of the Track Hub User Guide. Also, for more detailed instructions on setting up a regular hub, please see the Setting Up Your Own Track Hub section of the Track Hub User Guide.

Setting up Blat for an Assembly Hub

Setting up an Assembly Hub on GBiB with Blat included

Resources:


Starting Blat for an Assembly Hub

From the location of yourAssembly.2bit file, http://yourURL/yourAssembly/yourAssembly.2bit, you can start two gfServers, specifing a port for the assembly hub to access amino acid sequence, 17777 -trans, or DNA sequence, 17779, in this example:

    gfServer start localhost 17777 -trans -mask yourAssembly.2bit &
    gfServer start localhost 17779 -stepSize=5 yourAssembly.2bit &
Then you can edit the genomes.txt file of your assembly hub to include two lines in the stanza referring to yourAssembly, that would have matching port numbers:
    transBlat yourLab.yourInstitution.edu 17777
    blat yourLab.yourInstitution.edu 17779
See an example genomes.txt with commented out lines here, and please note capital B in transBlat. For more information, see the "Adding BLAT servers" section of the Assembly Hub Wiki. The Source Downloads page offers access to utilities with pre-compiled binaries such as gfServer found in a blat/ directory for your machine type here and further blat documentation here. Please note that because the -mask option in the above 17777 -trans gfServer option will mask all lower-case sequence from being matched, you may not wish to include it. See the above blat links and gfServer usage statement for more information.

If you are having trouble with your blat servers connecting to the browser it may help to know that some institutions have firewalls that will prevent the browser from sending multiple inquiries, in which case you may need to request your admins add this IP range as exceptions that are not limited: 128.114.119.* That will cover the U.S. genome.ucsc.edu site. In case you may wish the requests to work from our European Mirror genome-euro.ucsc.edu site, you would want to include 129.70.40.120 also to the exception list.


Starting a Blat enabled Assembly Hub on GBiB

Install GBiB

SSH into your GBiB

    2. With your GBiB operational, use your computer's terminal program to ssh into your GBiB: ssh browser@localhost -p 1235, using browser for the password.

Wget example hub

    3. Navigate to the GBiB's folders directory: cd /folders

    Then use sudo to wget this assembly hub:

      sudo wget -r --no-parent --reject "index.html*" -nH --cut-dirs=3 http://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubAssembly/plantAraTha1/

Enable blat lines in genomes.txt

    4. Navigate to the genomes.txt file of this assembly hub: cd /folders/hubExamples/hubAssembly/plantAraTha1/

    Edit the currently commented-out blat lines with sudo vi genomes.txt. Use "x" when the cursor is over the # at the start of the line to remove it and :w! to save the changes and :q to quit.

      blat localhost 17779
      transBlat localhost 17777
Start gfServers on your assembly hub

    5. Change directories to the 2bit file: cd /folders/hubExamples/hubAssembly/plantAraTha1/araTha1

    Run the two gfServer commands to start the blat servers:

      gfServer start localhost 17777 -trans -mask araTha1.2bit &
      gfServer start localhost 17779 -stepSize=5 araTha1.2bit &

Load hub and use blat