b7d562f6d2b90c3755c508c1a5b98c67648bf5b9 brianlee Tue Nov 17 14:16:52 2020 -0800 Working with Gerardo to resolve a git merge on bigLolly.html and adding some and punctuation changes after running htmlCheck validate on the page refs #26481 diff --git src/hg/htdocs/goldenPath/help/bigLolly.html src/hg/htdocs/goldenPath/help/bigLolly.html index 9e7980c..531fd30 100755 --- src/hg/htdocs/goldenPath/help/bigLolly.html +++ src/hg/htdocs/goldenPath/help/bigLolly.html @@ -36,104 +36,94 @@

In this example, you will create a bigLolly custom track using an existing bigBed file, located on the UCSC Genome Browser http server. By default the score field is used to define the lollipop height. This file contains data for the hg38 assembly.

To create a custom track using this bigBed file:

  1. Construct a track line that references the file:

    track type=bigLolly name="bigLolly Example One" description="A bigLolly file" bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigBedExample3.bb visibility=full
  2. Paste the track line into the custom track management page for the human assembly hg38 (Dec. 2013).
  3. Click the "submit" button.
  4. - Go to chr21:17,030,007-17,055,589 to see the data. + Go to chr21:17,030,007-17,055,589 to see the data.

Custom tracks can also be loaded via one URL line. This link loads the same bigLolly.bb track and sets additional display parameters in the URL:

-
http://genome.ucsc.edu/cgi-bin/hgTracks?ignoreCookie=1&db=hg38&position=chr21:17,002,145-17,159,243&hgct_customText=track%20type=bigLolly%20name=Example %20bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigBedExample3.bb %20visibility=full
+
http://genome.ucsc.edu/cgi-bin/hgTracks?ignoreCookie=1&db=hg38&position=chr21:17,002,145-17,159,243&hgct_customText=track%20type=bigLolly%20name=Example %20bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigBedExample3.bb %20visibility=full

Example #2

In this example, you will create your own bigBed file to display as a bigLolly from an bed file, using an extra field to define the height of the lollipops.

  1. Save this bed file to your computer.
  2. - Save the autoSql files bigLollyExample2.as and + Save the autoSql files bigLollyExample2.as to your computer.
  3. Download the bedToBigBed utility.
  4. Save the hg38.chrom.sizes text file to your computer. This file contains the chrom.sizes for the human hg38 assembly.
  5. Use the bedToBigBed utility to create a bigBed file from your sorted BED file, using the bigLollyExample2.bed file and chrom.sizes files created above.

    -
    bedToBigBed -as=bigLollyExample2.as -type=bed9+1 bigLollyExample2.bed hg38.chrom.sizes bigLollyExample2.bb
    +
    bedToBigBed -as=bigLollyExample2.as -type=bed9+1 bigLollyExample2.bed hg38.chrom.sizes bigLollyExample2.bb
  6. Move the newly created bigBed file (bigLollyExample2.bb) to a web-accessible http, https, or ftp location. At this point you should have a URL to your data, such as "https://institution.edu/bigLollyExample2.bb", and the file should be accessible outside of your institution/hosting providers network. For more information on where to host your data, please see the Hosting section of the Track Hub Help documentation.

    -<<<<<<< Updated upstream -
    track type=bigLolly name="bigLolly Example Two" description="A second bigLolly file" bigDataUrl=http://hgwdev.gi.ucsc.edu/goldenPath/help/examples/bigLollyExample2.bb lollyField=pValueLog visibility=full
  7. -
  8. - Go to chr21:15,593,670-15,632,442 to see the data. -=======
    track type=bigLolly name="bigLolly Example Two" description="A second bigLolly file" bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigLollyExample2.bb lollyField=pValueLog visibility=full
  9. ->>>>>>> Stashed changes -
  • + Go to chr21:15,593,670-15,632,442 to see the data.
  • +

    Example #3

    In this example, you will create your own bigBed file to display as a bigLolly from an bed file with the size of the lollipop defined by an extra field, and the height defined by the score field. We'll also turn off the lollipop stems and add some labels and lines on the y axis.

    1. Save this bed file to your computer.
    2. Save the autoSql files bigLollyExample3.as - to your computer + to your computer.
    3. Download the bedToBigBed utility.
    4. Save the hg38.chrom.sizes text file to your computer. This file contains the chrom.sizes for the human hg38 assembly.
    5. Use the bedToBigBed utility to create a bigBed file from your sorted BED file, using the bigLollyExample3.bed file and chrom.sizes files created above.

      bedToBigBed -as=bigLollyExample3.as -type=bed9+1 bigLollyExample3.bed hg38.chrom.sizes bigLollyExample3.bb
      -

      +

    6. Move the newly created bigBed file (bigLollyExample3.bb) to a web-accessible http, https, or ftp location. At this point you should have a URL to your data, such as "https://institution.edu/bigLollyExample3.bb", and the file should be accessible outside of your institution/hosting providers network. For more information on where to host your data, please see the Hosting section of the Track Hub Help documentation.

      -<<<<<<< Updated upstream -
      track type=bigLolly name="bigLolly Example Three" description="A third bigLolly file" bigDataUrl=http://hgwdev.gi.ucsc.edu/goldenPath/help/examples/bigLollyExample3.bb lollySizeField=lollySize visibility=full yAxisLabel.0="0 on 30,30,190 0" yAxisLabel.1="5 on 30,30,190 5" lollyNoStems=on lollyMaxSize=10 yAxisNumLabels=off
    7. -=======
      track type=bigLolly name="bigLolly Example Three" description="A third bigLolly file" bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigLollyExample3.bb lollySizeField=lollySize visibility=full yAxisLabel.0="0 on 30,30,190 0" yAxisLabel.1="5 on 30,30,190 5" lollyNoStems=on
      -
    ->>>>>>> Stashed changes
  • - Go to chr21:25,891,755-25,891,870 to see the data. + Go to chr21:25,891,755-25,891,870 to see the data.
  • Sharing your data with others

    If you would like to share your bigLolly data track with a colleague, learn how to create a URL by looking at Example 6 on this page.

    Extracting data from the bigLolly format

    Because the bigLolly files are an extension of bigBed files, which are indexed binary files, it can be difficult to extract data from them. UCSC has developed the following programs to assist in working with bigBed formats, available from the binary utilities directory.