593033daa676cedf89870baf24143e5ec0015c64 lrnassar Fri May 2 16:11:09 2025 -0700 Adding more prominent mentions of dynseq display to the docs, refs #35616 diff --git src/hg/htdocs/goldenPath/help/bigWig.html src/hg/htdocs/goldenPath/help/bigWig.html index b6960c69d24..2617ebff1b1 100755 --- src/hg/htdocs/goldenPath/help/bigWig.html +++ src/hg/htdocs/goldenPath/help/bigWig.html @@ -1,29 +1,31 @@
The bigWig format is useful for dense, continuous data that will be displayed in the Genome
Browser as a graph. BigWig files are created from wiggle (wig)
type files using the program wigToBigWig
. Alternatively, bigWig files can be created
from bedGraph files, using the program
-bedGraphToBigWig
.
+bedGraphToBigWig
. bigWig also supports dynseq display as described in example 4.
The bigWig files are in an indexed binary format. The main advantage of this format is that only those portions of the file needed to display a particular region are transferred to the Genome Browser server. Because of this, bigWig files have considerably faster display performance than regular wiggle files when working with large data sets. The bigWig file remains on your local web-accessible server (http, https or ftp), not on the UCSC server, and only the portion needed for the currently displayed chromosomal position is locally cached as a "sparse file". If you do not have access to a web-accessible server and need hosting space for your bigWig files, please see the Hosting section of the Track Hub Help documentation.
Wiggle data must be continuous and consist of equally sized elements. If your data is sparse or contains elements of varying sizes, use the bedGraph format instead of the wiggle format. If you have a very large bedGraph data set, you can convert it to the bigWig