250615a9c51e8402340f9d982aab1d4e87a12152
gperez2
  Mon Feb 13 09:18:51 2023 -0800
Adding bigLolly doc link to page, ref #30585

diff --git src/hg/htdocs/goldenPath/help/wiggle.html src/hg/htdocs/goldenPath/help/wiggle.html
index 56e4a7f..d248022 100755
--- src/hg/htdocs/goldenPath/help/wiggle.html
+++ src/hg/htdocs/goldenPath/help/wiggle.html
@@ -5,31 +5,31 @@
 <!-- Relative paths to support mirror sites with non-standard GB docs install -->
 <!--#include virtual="$ROOT/inc/gbPageStart.html" -->
 
 <h1>Wiggle Track ASCII Text Format (.wig)</h1> 
 <p>
 <p>Wiggle files and its bedgraph variant allow you to plot quantitative data as either shades of
 color (dense mode) or bars of varying height (full and pack mode) on the
 genome. Both are text files that are easy to create, but need to be converted for actual use by the
 genome browser.</p>
 
 <p>The <a href="bedgraph.html">bedGraph</a> format is a very similar format for
 <a href="#sparse">sparse</a> data or data that contains elements of
 varying size. bedGraph can also be converted to compressed/indexed binary bigWig files.
 If you have other data to show in addition to the quantitative data, e.g. data you
 want to show on mouseover or when the user clicks the feature (like GWAS data),
-you should have a look at bigBed files with the "lollipop" type (contact us for more info).
+you should have a look at the <a href="bigLolly.html">bigLolly</a> format.
 For a list of all possible formats for graphing, see the following 
 <a href="http://genomewiki.ucsc.edu/index.php/Selecting_a_graphing_track_data_format" 
 target="_blank">wiki page</a>.</p>
 <p>Text files in wiggle format can be uploaded as custom tracks as-is to UCSC 
 where they are compressed and stored for some time. But we recommand that you convert them 
 on your own computer to the binary bigWig storage format. You then copy bigWig files onto
 your own webserver and they are referenced in custom tracks or track hubs via their URL.</p>
 
 <p>
 Unlike bigWig binar files, wiggle ASCII text files can be uploaded as custom tracks onto our server.
 After the upload, wiggle data is compressed and stored
 internally in 128 unique bins. This compression means that there is a minor
 loss of precision when data is exported from a wiggle track 
 (<em>i.e.</em>, with output format &quot;data points&quot; or &quot;bed format&quot; within the 
 Table Browser). For custom tracks, use the <a href='bedgraph.html'>bedGraph</a>