e5759993329b6e609e9ab825991a90283e714088
mspeir
Wed Sep 9 11:17:57 2026 -0700
Help pages: fix broken internal links and restore anchors people still cite, refs #38062
Three groups of anchor problems on the help and FAQ pages.
Broken internal links, five pages: posters.html listed a 2022 section that
does not exist (no 2022 posters), api.html listed REST and JSON separately
after the two sections were merged, docker.html pointed at a #UsrAcct section
that is not on that page, FAQgenes.html had a capitalized #ncbiRefSeq where
the anchor is #ncbiRefseq, and the genomes.txt settings rows in
trackDbHub.v3.html carried no anchors so its own "genome" link missed.
Retired anchors that are still cited in twenty years of answers on the genome
list. Content moved to its own page and the old anchor was deleted rather than
left behind, so the citations land at the top of the page. Reattached seven
numeric FAQformat anchors to the Topics entry linking to each format's page.
BED, PSL, GFF and GTF were removed from the custom track page in 2012 and
never added back to its list of supported formats; added them with the old
anchors, which fixes customTrack.html and hgTracksHelp.html together since
both include customTrackText.html. Also restored #lines there, and #Session
on hgTrackHubHelp.html and #link4 on FAQlink.html.
Section anchors on six pages that had none, so a support answer can link to
one part of them: bam.html, hic.html, bedgraph.html, ftp.html, net.html and
trackDbIndexBb.html. Skipped quickLiftChain.html, oligoMatch.html and
cutters.html, which are track description fragments included into the details
page rather than standalone pages.
Co-Authored-By: Claude Opus 5 (1M context)
The bedGraph format allows display of continuous-valued data in track format. This display type is
useful for probability scores and transcriptome data. This track type is similar to the wiggle
(WIG) format, but unlike the wiggle format, data exported
in the bedGraph format are preserved in their original state. This can be seen on export using the
table browser. For more details on data compression in wiggle tracks see the notes section of the
wiggle track description page. If you have a very large
data set and you would like to keep it on your own server, you should use the
bigWig data format. In fact, an attempt to load a bedGraph custom track over 50,000,000 lines
will result in an error message, but can be addressed by turning the bedGraph into a bigWig (see
Example 3). Note that bedGraph files cannot easily be converted to
wiggle files; converting bedGraph to bigWig and using
The bedGraph format is line-oriented. BedGraph data are preceded by a
track definition line, which adds a number of options for
controlling the default display of this track.
Following the track definition line are the track data in four column BED format:
All options are placed in a single line separated by spaces:
Note: if you copy/paste the above example, you must remove the line breaks.
The track type is REQUIRED, and must be bedGraph:
The remaining values are OPTIONAL. The wiggle
documentation contains details on these options. A functional description of these options can be
seen in the track configuration description.
(Custom tracks do not have interactive configuration options.)
+
BedGraph track data values can be integer or real, positive or negative values. The
chromosome coordinates are zero-based, half-open.
This means that the first chromosome position is 0, and the last position in a chromosome
of length N would be N - 1. The positions listed in the input data must be in
numerical order, and only the specified positions will be graphed. bedGraph format has four
columns of data: BedGraph Track Format
bigWigToWig will return the
original bedGraph file.General Structure
+
chromA chromStartA chromEndA dataValueA
chromB chromStartB chromEndB dataValueBParameters for bedGraph track definition lines
track type=bedGraph name=track_label description=center_label
visibility=display_mode color=r,g,b altColor=r,g,b
priority=priority autoScale=on|off alwaysZero=on|off gridDefault=on|off
maxHeightPixels=max:default:min graphType=bar|points viewLimits=lower:upper
yLineMark=real-value yLineOnOff=on|off
windowingFunction=maximum|mean|minimum smoothingWindow=off|2-16type=bedGraphData Values
chrom chromStart chromEnd dataValue
This example specifies 9 separate data points in three tracks on chr19 in the region 49,302,001 to 49,304,701. To view this example as a custom track in the Genome Browser, copy the text and paste it into the browser annotation track text box.
browser position chr19:49302001-49304701
browser hide all
browser pack refGene encodeRegions
browser full altGraph
# 300 base wide bar graph, autoScale is on by default == graphing
# limits will dynamically change to always show full range of data
# in viewing window, priority = 20 positions this as the second graph
# Note, zero-relative, half-open coordinate system in use for bedGraph format
track type=bedGraph name="BedGraph Format" description="BedGraph format" visibility=full color=200,100,0 altColor=0,100,200 priority=20
chr19 49302000 49302300 -1.0