b3aef6de6abdf2356bf7d4a64fd5d857726eea6b
mspeir
  Sun Oct 4 09:57:49 2026 -0700
Regulation FAQ: cis-regulation background and six interpretive questions

Max asked for a short introduction to cis-regulation, and Lou noted that the
page leaned towards listing datasets rather than explaining how to read them.
This covers both.

A new opening question walks through the kinds of evidence the Browser carries
for regulation: open chromatin, histone marks, DNA methylation, transcription
factor binding, conservation and physical contact. It is adapted from Max's
draft, trimmed where it repeated the sections below it. The top of the page now
says when the track list was last checked, and CADD 1.7 goes ahead of
AlphaGenome among the variant scores, since it has been stable for years.

Six questions are new, each one chosen because people keep asking it on the
genome list: why a motif turns up across a whole gene, what a GeneHancer arc
does and does not claim, what the scores and grey shading mean (which differs
from track to track), whether signal heights can be compared (ENCODE4
auto-scales and ENCODE3 does not, which nothing else documents), what an empty
region means, and what to do when your tissue was never assayed.

The three "Which tracks show ..." headings become "How do I find ...", which is
the form the other FAQ pages use. The Single-cell ATAC-seq row leaves the
summary table because singleCellSignalsPeaks is still release alpha and those
links error anywhere but hgwdev; the row is kept in a comment to restore when
the track is released.

refs #24610

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

diff --git src/hg/htdocs/FAQ/FAQregulation.html src/hg/htdocs/FAQ/FAQregulation.html
index 8e06956e0c6..64febc9776f 100755
--- src/hg/htdocs/FAQ/FAQregulation.html
+++ src/hg/htdocs/FAQ/FAQregulation.html
@@ -1,577 +1,817 @@
 <!DOCTYPE html>
 <!--#set var="TITLE" value="Genome Browser FAQ" -->
 <!--#set var="ROOT" value=".." -->
 
 <!-- Relative paths to support mirror sites with non-standard GB docs install -->
 <!--#include virtual="$ROOT/inc/gbPageStart.html" -->
 
 <h1>Frequently Asked Questions: Regulation and cis-regulatory tracks</h1>
 
 <h2>Topics</h2>
 
 <ul>
+<li><a href="#whatEvidence">How do I tell whether a region is
+                            regulatory?</a></li>
 <li><a href="#measuredPredicted">What is the difference between measured and predicted binding
                                  sites?</a></li>
-<li><a href="#whichTfbs">Which tracks show transcription factor binding sites?</a></li>
+<li><a href="#whichTfbs">How do I find transcription factor binding sites?</a></li>
+<li><a href="#motifEverywhere">The JASPAR track shows my factor binding across the whole
+                               gene. Why?</a></li>
 <li><a href="#notFound">I cannot find my transcription factor in any track. Where else can I
                         look?</a></li>
 <li><a href="#encodePortal">How do I display ENCODE data that is not already a track?</a></li>
-<li><a href="#promoters">Which tracks show promoters?</a></li>
-<li><a href="#enhancers">Which tracks show enhancers and other regulatory elements?</a></li>
+<li><a href="#promoters">How do I find the promoter of a gene?</a></li>
+<li><a href="#enhancers">How do I find enhancers and other regulatory elements?</a></li>
+<li><a href="#arcs">What does it mean when GeneHancer draws an arc between an element and a
+                    gene?</a></li>
 <li><a href="#ccres">What are cCREs, and which cCRE track should I use?</a></li>
+<li><a href="#scores">What do the scores and the grey shading in these tracks mean?</a></li>
+<li><a href="#signalHeight">The signal is higher in one region than another. Can I compare
+                            them?</a></li>
+<li><a href="#nothingThere">Nothing is annotated over my region. Does that mean it is not
+                            regulatory?</a></li>
 <li><a href="#cellType">How do I restrict a search to one cell type or tissue?</a></li>
+<li><a href="#noTissue">My tissue is not in the list of cell types. What should I do?</a></li>
 <li><a href="#myGene">I have a gene. How do I find the factors that regulate it?</a></li>
 <li><a href="#variantEffect">I have a variant, not a region. What does it do to
                              regulation?</a></li>
 <li><a href="#otherGenomes">What is available for assemblies other than human and mouse?</a></li>
 <li><a href="#summary">Summary: regulatory tracks by category</a></li>
 </ul>
 <hr>
 <p>
 <a href="index.html">Return to FAQ Table of Contents</a></p>
 
 <p>
 The assembly names after each track are links. They open that track's description page on
-that assembly, which gives the methods, the data version and the citation. Coverage varies a
+that assembly, which gives the methods, the data version, and the citation. Coverage varies a
 lot between assemblies, so check the list before you assume a track exists on the genome you
 work with.</p>
+<p>
+<em>The tracks described here were last checked in October 2026. Projects such as JASPAR and
+ENCODE issue new versions on their own schedules, and we add tracks between checks, so use
+<a href="../cgi-bin/hgTracks?hgt_tSearch=track+search">Track Search</a> if you need to know what
+is on an assembly today.</em></p>
 
-<a name="measuredPredicted"></a>
+<a name="whatEvidence"></a>
 <h2>The basics</h2>
 <p>
 The Genome Browser carries a large number of tracks that annotate regulatory regions. Most of
 them are in the <em>Regulation</em> track group, which you will find below the browser image on
 the <a href="../cgi-bin/hgTracks">main browser page</a>.</p>
 
+<h6>How do I tell whether a region is regulatory?</h6>
+<p>
+This page is about regulation at the level of DNA and chromatin. Mechanisms acting on RNA after
+it has been transcribed are a separate subject and are not covered. None of the tracks below
+observes regulation directly. Each one measures a property that regulatory regions tend to have,
+and the case for any particular region is built by stacking several of them. Almost all of these
+signals differ between cell types, so pick the tissue that matters for your question instead of
+reading a genome-wide summary.</p>
+<ul>
+  <li>
+  <strong>Open chromatin.</strong> A region that is in use generally has to be reachable by the
+  proteins that bind it, and DNase-seq and ATAC-seq report where that is so. Both are in
+  <strong>ENCODE4 Regulation</strong>, organized by tissue, on
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg4">hg38</a> and
+  <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=encode4Reg">mm10</a>. The older ENCODE3
+  <strong>DNase HS</strong> clusters are on
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeRegDnase">hg38</a>.</li>
+  <li>
+  <strong>Histone modifications.</strong> Histones carry chemical marks that differ between
+  element types: H3K4me3 at active promoters, H3K4me1 at enhancers, H3K27ac at both when they
+  are active, and H3K27me3 over Polycomb-repressed genes. The <strong>Layered H3K27Ac</strong>
+  track is the quickest look at the active ones, on
+  <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=wgEncodeRegMarkH3k27ac">hg19</a> and
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeRegMarkH3k27ac">hg38</a>. The
+  <a href="#ccres">cCRE tracks</a> combine accessibility, these marks and CTCF into a single
+  classification, which is usually a better first track to turn on than any one signal.</li>
+  <li>
+  <strong>DNA methylation.</strong> A methylated promoter is usually a silenced one. Many
+  promoters sit in <strong>CpG Islands</strong>, which stay unmethylated in most tissues, on
+  <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=cpgIslandExt">hg19</a>,
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=cpgIslandExt">hg38</a>,
+  <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=cpgIslandExt">mm10</a> and
+  <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=cpgIslandExt">mm39</a>. The <strong>DNA
+  Methylation</strong> collection gathers measurements from several sources and calls hypo- and
+  hypermethylated regions in a range of cell types, on
+  <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=dnaMethylation">hg19</a> and
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=dnaMethylation">hg38</a>.</li>
+  <li>
+  <strong>Transcription factor binding.</strong> The human genome encodes well over a thousand
+  transcription factors. Many recognize nearly the same motif, so a match alone rarely tells you
+  which factor is involved. Most matches are never bound in any cell. For a
+  sense of how unspecific motifs are, paste a random sequence into the scanning tool at
+  <a href="https://jaspar.elixir.no/analysis" target="_blank">JASPAR</a> and count the hits. The
+  <a href="#measuredPredicted">next question</a> covers the distinction this creates, and
+  <a href="#whichTfbs">the section after it</a> lists the tracks.</li>
+  <li>
+  <strong>Conservation and constraint.</strong> Non-coding sequence held steady across species
+  is often regulatory, which is what the <strong>phyloP</strong> and <strong>phastCons</strong>
+  tracks measure, on
+  <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=cons100way">hg19</a> and
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=cons100way">hg38</a>. <strong>Unusually
+  Conserved</strong> picks out the extreme cases, such as sequence identical between human and
+  mouse, on <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=unusualcons">hg38</a>. Sequence that
+  varies little between human genomes is described instead as constrained, and the
+  <strong>Constraint scores</strong> collection measures that, on
+  <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=constraintSuper">hg19</a> and
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=constraintSuper">hg38</a>.</li>
+  <li>
+  <strong>Physical contact.</strong> An enhancer can sit a megabase from the gene it controls,
+  so position on the chromosome says little by itself. <strong>Hi-C and Micro-C</strong> shows
+  which regions touch each other in the folded genome, on
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=hicAndMicroC">hg38</a>. CTCF sites often mark the
+  anchors of those loops and the edges of domains. For linking an element to a
+  candidate gene, see <a href="#myGene">finding the factors that regulate a gene</a>.</li>
+</ul>
+
+<a name="measuredPredicted"></a>
 <h6>What is the difference between measured and predicted binding sites?</h6>
 <p>
 A <em>measured</em> binding site comes from an experiment, usually ChIP-seq, in which one
 protein was pulled down in one cell type under one set of conditions. The site is real in the
 sense that the factor was found there in that experiment. It tells you nothing about other cell
 types, and the experiment has to have been done for your factor and your tissue for the data to
 exist at all.</p>
 <p>
 A <em>predicted</em> binding site comes from scanning the genome sequence for a
 <a href="/goldenPath/help/hgRegMotifHelp.html">motif</a>, the sequence theme a given factor
 prefers, usually stored as a position weight matrix and not a single spelling. Predictions exist
 everywhere in the genome for every
 factor with a known motif, regardless of cell type, and most of them are not bound <em>in
 vivo</em>. A typical transcription factor motif occurs hundreds of thousands of times in the
 human genome, while the factor binds only a few thousand of those positions in any given cell.</p>
 <p>
 Neither kind is better than the other. To find out where a factor was actually found, use a
 measured track. To find out whether some sequence you care about, a variant or a promoter
 fragment, could plausibly be bound, use a predicted track. What you cannot do is cite a
 prediction as evidence that the factor binds there.</p>
 
 <a name="whichTfbs"></a>
 <h2>Transcription factor binding sites</h2>
 
-<h6>Which tracks show transcription factor binding sites?</h6>
+<h6>How do I find transcription factor binding sites?</h6>
 <p>
 For human, three tracks cover most needs. All three are in the <em>Regulation</em> group.</p>
 <ul>
   <li>
   <strong>ReMap ChIP-seq</strong> is the broadest collection of <em>measured</em> sites. ReMap
   2022 integrates the public ChIP-seq experiments for transcriptional regulators from GEO,
   ArrayExpress and ENCODE into one atlas, so it covers far more factors and cell types than any
   single project. There are three versions: all peaks per experiment, a non-redundant set that
   merges similar targets, and cis-regulatory modules.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=ReMap">hg19</a>,
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=ReMap">hg38</a>,
   <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=ReMap">mm10</a>,
   <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=ReMap">mm39</a> and
   <a href="../cgi-bin/hgTrackUi?db=dm6&amp;g=ReMap">dm6</a>.</li>
   <li>
   <strong>TF ChIP</strong> has the ENCODE 3 transcription factor ChIP-seq peaks, all processed
   the same way. That matters if you are comparing experiments instead of looking up one
   factor. It covers 340 factors in 129 cell types on hg38, and 338 factors in 130 cell types on
   hg19, where the track is named <em>ENCODE 3 TFBS</em> rather than <em>TF ChIP</em>.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=encTfChipPk">hg19</a> and
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=encTfChipPk">hg38</a>. An older clustered version of
   the
   same data, <em>Txn Factor ChIP</em>, is on
   <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=wgEncodeRegTfbsClusteredV3">hg19</a>.</li>
   <li>
   <strong>JASPAR Transcription Factors</strong> is the <em>predicted</em> set, made by scanning
   the genome with the JASPAR CORE profiles. Scores are scaled from 0 to 1000 and reflect how well
   the sequence matches the profile; the track shows only sites scoring 400 or above by default,
   and you can raise that threshold in the track settings. Clicking a site shows the
   <a href="/goldenPath/help/hgRegMotifHelp.html">motif display</a>, with the sequence logo and the
   matrix behind the score. The track holds several JASPAR releases as separate subtracks, so check
   which one you have turned on before you quote a version. JASPAR 2026 is on
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=jaspar">hg38</a>,
   <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=jaspar">mm39</a>,
   <a href="../cgi-bin/hgTrackUi?db=danRer11&amp;g=jaspar">danRer11</a>,
   <a href="../cgi-bin/hgTrackUi?db=galGal6&amp;g=jaspar">galGal6</a>,
   <a href="../cgi-bin/hgTrackUi?db=dm6&amp;g=jaspar">dm6</a>,
   <a href="../cgi-bin/hgTrackUi?db=ce11&amp;g=jaspar">ce11</a>,
   <a href="../cgi-bin/hgTrackUi?db=ci3&amp;g=jaspar">ci3</a> and
   <a href="../cgi-bin/hgTrackUi?db=sacCer3&amp;g=jaspar">sacCer3</a>. On
   <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=jaspar">hg19</a> and
   <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=jaspar">mm10</a> the newest release is JASPAR
   2024.</li>
 </ul>
 
+<a name="motifEverywhere"></a>
+<h6>The JASPAR track shows my factor binding across the whole gene. Why?</h6>
+<p>
+This is the expected result for a motif search, not a sign that anything has gone wrong. Motifs
+are short and they tolerate mismatches, so a typical one occurs hundreds of thousands of times
+in the human genome, while the factor binds only a few thousand of those places in any given
+cell.</p>
+<p>
+Turning a matrix into a list of hits means picking a threshold, and there is no standard one.
+Two tools working from the same matrix will hand you different sites, because they cut at
+different places and weigh conservation differently. This has been an open problem for as long
+as people have been scanning genomes, so any particular set of predicted sites is best treated as
+one possible answer.</p>
+<p>
+Raising the score cutoff in the track settings will thin the display, but it does not make the
+survivors bound. A more productive approach is to read the motif as the list of places the
+factor <em>could</em> bind, then narrow that list using evidence that it did bind: a ChIP peak
+in a cell type close to yours, open chromatin, or both.</p>
+
 <a name="notFound"></a>
 <h6>I cannot find my transcription factor in any track. Where else can I look?</h6>
 <p>
 First check whether the experiment simply has not been done. ReMap covers the published ChIP-seq
 experiments that were available when it was built, so if your factor is absent from ReMap there
 may be no public ChIP-seq for it in that organism. The
 <a href="https://remap.univ-amu.fr/" target="_blank">ReMap website</a> lets you search by target
 and download the peaks per factor, and that is the quickest way to check.</p>
 <p>
 If the experiment exists but is newer than our tracks, or was done in a cell type we do not
 carry, you will need to load the data yourself as a custom track. The usual sources are:</p>
 <ul>
   <li>
   The <a href="https://www.encodeproject.org/" target="_blank">ENCODE portal</a>, for anything
   produced by ENCODE. This is the easiest case, because the portal will send the data
   straight to our browser for you. See the <a href="#encodePortal">next question</a>.</li>
   <li>
   <a href="https://www.ncbi.nlm.nih.gov/geo/" target="_blank">GEO</a>, for data submitted
   alongside a publication. Many GEO submissions include processed peak files as supplementary
   material, usually BED or narrowPeak, which you can
   <a href="/goldenPath/help/customTrack.html">load as a custom track</a> at
   <a href="../cgi-bin/hgCustom">Add Custom Tracks</a>, after checking that the coordinates
   match the assembly you are using.</li>
   <li>
   <a href="https://www.ncbi.nlm.nih.gov/sra" target="_blank">SRA</a>, for raw sequencing reads.
   The Browser cannot display SRA data. Raw reads have to be aligned and peak-called before there
   is anything to show, which is a job for a sequence analysis pipeline rather than for us.</li>
 </ul>
 
 <a name="encodePortal"></a>
 <h6>How do I display ENCODE data that is not already a track?</h6>
 <p>
 You do not need to download anything or write a custom track by hand. The ENCODE portal will
 open its data in the Genome Browser for you.</p>
 <ol>
   <li>
   Search the <a href="https://www.encodeproject.org/search/?type=Experiment"
   target="_blank">ENCODE portal</a> for what you want, narrowing the results with the filters
   down the left side. <strong>Assay title</strong>, <strong>Target of assay</strong> (the
   factor), <strong>Biosample</strong> (the cell type or tissue) and <strong>Genome
   assembly</strong> are the useful ones.</li>
   <li>
   Click the <strong>Visualize</strong> button above the result list.</li>
   <li>
   Pick your assembly in the panel that opens, then click <strong>UCSC</strong>.</li>
 </ol>
 <p>
 The Browser opens with every experiment in your filtered result set loaded as a track hub, so
 this works just as well for one experiment as for fifty. Restrict the search before you
 visualize, since a broad filter can attach a very large number of tracks at once.</p>
 <p>
 ENCODE also publishes a hub for each individual experiment, which is handy if you are scripting
 or want to keep a link in a session. Substitute the accession into this URL:</p>
 <pre>https://www.encodeproject.org/experiments/ENCSR000AKO/@@hub/hub.txt</pre>
 <p>
 and load it from the <a href="../cgi-bin/hgHubConnect#unlistedHubs">My Hubs</a> tab of the Track
 Hubs page, or by appending it to a browser URL as
 <code>hgTracks?db=hg38&amp;hubUrl=</code> followed by the hub address.</p>
 <!--
 <p>
 If you would rather place a single file yourself, note that ENCODE distributes peaks as bigBed
 and signal as bigWig, both of which the Browser reads directly. Copy the file URL from the portal;
 you do not
 need to download the file. Then paste one custom track line at
 <a href="../cgi-bin/hgCustom">Add Custom Tracks</a>:</p>
 <pre>track type=bigBed name="CTCF K562 peaks" bigDataUrl=https://www.encodeproject.org/files/ENCFF002CEL/@@download/ENCFF002CEL.bigBed</pre>
 <p>
 Full instructions are on the
 <a href="/goldenPath/help/customTrack.html">custom tracks help page</a> and the
 <a href="/goldenPath/help/hgTrackHubHelp.html">track hub help page</a>.</p>
 -->
 <a name="promoters"></a>
 <h2>Promoters, enhancers and other elements</h2>
 
-<h6>Which tracks show promoters?</h6>
+<h6>How do I find the promoter of a gene?</h6>
 <p>
-It depends on what you mean by a promoter, and the tracks disagree enough that it matters.</p>
+It depends on what you mean by a promoter, something which the tracks don't always agree on. In
+the loosest sense a promoter is the minimal stretch upstream of the transcription start site
+that will drive expression, but there is no agreed figure for minimal: some authors work with
+2 kb upstream, others with 500 bp or 100 bp, and the right choice depends on the gene and on
+whether you are after broad or tissue-specific expression.</p>
 <ul>
   <li>
   <strong>EPDnew Promoters</strong> has experimentally defined promoters, each with a single,
   precisely mapped transcription start site. Use it when you need a defined, citable promoter
   region and not an approximation. On hg38 there is a companion
   set for non-coding RNA promoters.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=epdNew">hg19</a>,
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=epdNew">hg38</a> and
   <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=epdNew">mm10</a>.</li>
   <li>
   <strong>FANTOM5</strong> maps transcription start sites by CAGE and reports how much each one
   is used across a large panel of tissues and cell types. Use it when you want to know which
   start site is active in which tissue.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=fantom5">hg19</a>,
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=fantom5">hg38</a> and
   <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=fantom5">mm10</a>, and for a few other
   genomes including chicken, dog, rat and rhesus.</li>
   <li>
   The promoter-like cCREs in the <a href="#ccres">ENCODE cCRE tracks</a> are a genome-wide
   classification built from chromatin signal, so they are more inclusive and less precise than
   EPDnew.</li>
   <li>
   If all you need is a fixed window upstream of a gene, do not use a promoter track at all. The
   Table Browser can return the upstream sequence for any gene track, and our download server
   carries prepackaged 1000, 2000 and 5000 bp upstream sequence files for RefSeq genes. See
   <a href="FAQdownloads.html#download18">Obtaining promoter sequence</a>.</li>
 </ul>
 
 <a name="enhancers"></a>
-<h6>Which tracks show enhancers and other regulatory elements?</h6>
+<h6>How do I find enhancers and other regulatory elements?</h6>
 <ul>
   <li>
   <strong>GeneHancer</strong> is the track most users want when they ask about enhancers. It
   marks the elements and also links them to their predicted target genes, drawn as
   interactions.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=geneHancer">hg19</a> and
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=geneHancer">hg38</a>.</li>
   <li>
   <strong>VISTA Enhancers</strong> has elements that were tested one at a time in transgenic
   mouse assays, with the resulting expression pattern recorded. It is the smallest of these
   sets and the best validated.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=vistaEnhancersBb">hg19</a>,
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=vistaEnhancersBb">hg38</a>,
   <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=vistaEnhancersBb">mm10</a>
   and <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=vistaEnhancersBb">mm39</a>.</li>
   <li>
   <strong>RefSeq Functional Elements</strong> is NCBI's curated set of experimentally
   characterized non-coding elements.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=refSeqFuncElems">hg38</a> and
   <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=refSeqFuncElems">mm10</a>.</li>
   <li>
   <strong>MPRAs</strong> is a collection of massively parallel reporter assay results, which
   measure regulatory activity for many sequences at once. The MPRA Base half holds 40,938 tested
   elements; the MPRAVarDB half holds tested variants and is covered under
   <a href="#variantEffect">variant effects</a> below.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=mpra">hg38</a>.</li>
 </ul>
 <p>
 For the chromatin evidence behind the called elements, see <strong>ENCODE4 Regulation</strong>,
 which carries DNase, ATAC-seq, histone modification and CTCF signal organized by tissue, on
 <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg4">hg38</a> and
 <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=encode4Reg">mm10</a>. This replaced <strong>ENCODE3
 Regulation</strong>
 as the default in July 2026; ENCODE3 is kept for archival use and is still on
 <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=wgEncodeReg">hg19</a> and
 <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg">hg38</a>.</p>
 
+<a name="arcs"></a>
+<h6>What does it mean when GeneHancer draws an arc between an element and a gene?</h6>
+<p>
+It means that somebody has associated the two. It does not mean that the element has been
+shown to regulate the gene.</p>
+<p>
+In <strong>GeneHancer</strong> the higher end of an arc is the element and the lower end is the
+gene it has been linked to. The track pools several kinds of evidence to make those links.
+They include eQTLs, promoter capture Hi-C, correlation between enhancer RNA and gene expression,
+correlation between a transcription factor and a candidate target, and plain proximity. That
+last one is worth remembering, because an arc drawn mostly on distance is making the same
+nearest-gene assumption you were trying to get away from. The track's
+<em>double elite</em> subset keeps only the cases where both the element and the link to the
+gene were supported by more than one source. It is a great deal smaller and worth a look when
+the full set gives you too much.</p>
+<p>
+The arcs also say nothing about the relationship between two genes that share an element. An
+element linked to two genes has been associated with each of them separately, which is not a
+statement that either gene affects the other.</p>
+
 <a name="ccres"></a>
 <h6>What are cCREs, and which cCRE track should I use?</h6>
 <p>
 A candidate cis-regulatory element, or cCRE, is a region that looks regulatory in chromatin
 data. Nobody has shown that it regulates anything. ENCODE built the
 Registry of cCREs by combining DNase accessibility with histone modification and CTCF signal
 across many biosamples, then classifying each region as promoter-like, enhancer-like, CTCF-only
 and so on.</p>
 <p>
 The <strong>ENCODE cCREs</strong> container on
 <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=cCREs">hg38</a> holds several versions. The
 <strong>ENCODE4
 cCREs</strong> registry became the default in July 2026 and is the one to use: 2.3 million human
 and 927,000 mouse elements. The <strong>ENCODE4 Core Collection</strong> is a smaller,
 higher-confidence subset, covering the 170 human and 18 mouse biosamples that were profiled with
 all four core assays. <strong>ENCODE3 cCREs</strong> is the earlier release, kept for archival
 use because a great many published analyses used it and coordinates need to stay reproducible. The
 container also carries per-biosample subtracks, which is how you restrict
 the classification to one cell type. Mouse
 <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=cCREs">mm10</a> carries the same three versions.</p>
 
+<a name="scores"></a>
+<h2>Reading the data</h2>
+
+<h6>What do the scores and the grey shading in these tracks mean?</h6>
+<p>
+It often means signal strength, but not always, and the tracks on this page do not all use it
+the same way. A score from 0 to 1000 drawn as a shade of grey is an old BED convention, dark for
+high. Where a track uses that convention, the number reflects how strong the signal was in the
+experiment behind the item. It is not a probability, and it is not a statement that the element
+does anything.</p>
+<p>
+Beyond that convention, each track uses color for its own purpose. <strong>JASPAR</strong> does
+use it as a score: the shade is the match to the motif profile, scaled to 0 to 1000, and sites
+below 400 are hidden until the threshold is lowered in the track settings.
+<strong>ReMap</strong> does not. It gives every transcription factor a color of its own, so the
+color indicates which factor is shown and says nothing about the quality of the peak.
+<strong>GeneHancer</strong> uses color for two things at once, whether the element is a
+promoter or an enhancer and whether its confidence is high, medium or low. The
+<a href="#ccres">cCRE tracks</a> color by class, promoter-like against enhancer-like against
+CTCF-only, which is unrelated to strength.</p>
+<p>
+The track description page is authoritative in each case, and it is one click from the track
+name.</p>
+
+<a name="signalHeight"></a>
+<h6>The signal is higher in one region than another. Can I compare them?</h6>
+<p>
+Between cell types in one window, yes. That is what the layered tracks are built for: the
+colored traces share a vertical axis, so a taller trace really is a stronger signal.</p>
+<p>
+Between regions, check the scale first. The <strong>ENCODE4</strong> histone and accessibility
+tracks on <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg4">hg38</a> arrive set to
+<em>Auto-scale to data view</em>, which recomputes the vertical range from whatever is on screen.
+The same peak is then drawn at different heights depending on how far out you are zoomed. Two
+screenshots of two places cannot be compared at all. Open the
+track's configuration page, change <em>Data view scaling</em> to use the vertical viewing range,
+and set a range that suits your data. The older <strong>ENCODE3</strong> layered tracks on
+<a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=wgEncodeRegMarkH3k27ac">hg19</a> and
+<a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeRegMarkH3k27ac">hg38</a> come with a fixed
+range instead, so they are already comparable from one place to the next.</p>
+<p>
+Between one track and another, no. The experiments were done by different labs and run through
+different pipelines, so the numbers are not in the same units. A value of 12 in one track and a
+value of 12 in another are not the same quantity, and the display gives no warning of this.</p>
+<p>
+When the comparison matters, it is better to work with the values than with the picture. The
+<a href="../cgi-bin/hgTables">Table Browser</a> and the
+<a href="../cgi-bin/hgIntegrator">Data Integrator</a> will return values for your regions, and
+the track description page says what the units are.</p>
+
+<a name="nothingThere"></a>
+<h6>Nothing is annotated over my region. Does that mean it is not regulatory?</h6>
+<p>
+No. It means these particular experiments did not report anything in that region.
+</p>
+<p>
+The most common reason is that nobody has assayed your cell type. The tracks we
+carry cover only a selective number of cell types or tissues chosen by the
+experimenters, and a region may be a strong enhancer in a tissue that has never
+been profiled. The same goes for the factor. ReMap and the ENCODE ChIP tracks
+together cover a few hundred factors in a few hundred cell types, which is a
+small fraction of the possible combinations. Peak calling also requires a
+cutoff, so a site that is real but weak can fall below it and thus will not
+be annotated.</p>
+<p>
+Annotations that do not depend on a particular experiment make a better test for absence.
+Conservation requires no experiment at all, and the cCREs pool a great many biosamples into one
+classification. If those are also empty over the region, there is more reason to think it is
+may not be a regulatory region.</p>
+
 <a name="cellType"></a>
 <h2>Working with the data</h2>
 
 <h6>How do I restrict a search to one cell type or tissue?</h6>
 <p>
-Most of the large regulatory tracks are collections holding many separate tracks, one per cell
-type or experiment, and they arrive with only a summary view turned on. Click the track name to
+Most of the large regulatory tracks are collections holding many separate tracks, often with
+one per cell type or experiment. By default, these collections often only have a summary view
+turned on. Click the track name to
 open its configuration page, where you will find the list and, on the bigger collections,
 filters. ReMap, for instance, lets you filter by transcription factor directly in the track
 settings, so you can show one factor across all its experiments.</p>
 <p>
 The largest collections use a different configuration page. Where there are hundreds or
 thousands of individual experiments, as in the per-experiment tracks of
 <strong>ENCODE4 Regulation</strong> on
 <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg4">hg38</a>, the page shows facets down the
 left side and a
 paginated table on the right: tick the tissue, assay or biosample you want and the table narrows
 to the matching experiments. This is usually a faster way to reach one cell type than reading a
 long list.</p>
 <p>
 To find a track rather than configure one, the
 <a href="../cgi-bin/hgTracks?hgt_tSearch=track+search">Track Search</a> page searches track
 names and descriptions across the whole assembly, which is usually faster than reading through
 the track groups.</p>
 
+<a name="noTissue"></a>
+<h6>My tissue is not in the list of cell types. What should I do?</h6>
+<p>
+One solution may be to choose the closest available cell type, and state that choice in any
+write-up. For example, treating a cell line as a stand-in for primary cells is a judgment made by
+the person reading the data, not something the data supports on its own.</p>
+<p>
+Before you settle for a substitute, check whether the experiment exists somewhere we do not
+carry it. The <a href="https://www.encodeproject.org/" target="_blank">ENCODE portal</a> holds
+far more biosamples than we turn into tracks. It will open any of them in the Browser for you;
+see <a href="#encodePortal">displaying ENCODE data</a> above. You can also search the
+<a href="../cgi-bin/hgHubConnect">public hubs</a> list, as some may contain more
+tissue-specific regulatory data than what's available natively in the Browser.</p>
+<p>
+If nothing close exists, consider the annotations that were never specific to one cell type.
+The cCREs pool many biosamples into a single classification, and conservation does not depend on
+any experiment. Neither one describes your tissue. Neither one silently describes a different
+tissue either, which is the risk that comes with a poorly matched proxy.</p>
+
 <a name="myGene"></a>
 <h6>I have a gene. How do I find the factors that regulate it?</h6>
 <p>
 No single track answers this, so you have to work outward from the gene.</p>
 <ol>
   <li>
   Navigate to the gene and zoom out far enough to include the surrounding non-coding sequence.
   Regulatory elements are often tens or hundreds of kilobases away, and the nearest gene to an
   element is frequently not its target.</li>
   <li>
   Turn on GeneHancer. Its interaction arcs will show which elements have been linked to your
   gene, including distant ones, which narrows the search from the whole neighborhood to a
   handful of regions.</li>
   <li>
   Turn on ReMap or TF ChIP and look at which factors have peaks in those regions. This gives you
   factors that were measured at that position in some cell type.</li>
   <li>
   Check whether any of those cell types are relevant to your biology. A peak in K562 says little
   about neurons.</li>
   <li>
   If you need candidates in a cell type nobody has assayed, fall back to JASPAR predictions
   within the GeneHancer elements, and treat the result as hypotheses to test.</li>
 </ol>
 <p>
 To do this systematically, the
 <a href="../cgi-bin/hgIntegrator">Data Integrator</a> will intersect two or more tracks and
 return a table, and the <a href="../cgi-bin/hgTables">Table Browser</a> will do the same for a
 region or for a list of genes.</p>
 
 <a name="variantEffect"></a>
 <h6>I have a variant, not a region. What does it do to regulation?</h6>
 <p>
 This is a different question from the rest of this page. Everything above annotates regions and
 tells you what is where; the tracks here take one base change and tell you what it does. The
 same measured and predicted distinction applies, so start with the one track that is
 measured.</p>
 <p>
 <strong>MPRAVarDB</strong> holds 239,028 variants that were put
 through a reporter assay and scored for allelic effect, drawn from 18 MPRA studies covering more
 than 30 cell lines and more than 30 diseases or traits. The variants come from GWAS and eQTL
 fine-mapping, from saturation mutagenesis of 20 disease-associated regulatory elements, and from
 smaller focused screens, so the coverage is concentrated on loci people have already had reason
 to care about. Items are colored by significance, dark red for FDR below 0.05. If your variant
 is in here, you have an experimental answer and not a guess. It lives in the
 <strong>MPRAs</strong> collection, alongside MPRA Base, which tests whole elements.
 Available for <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=mpraVarDb">hg38</a>.</p>
 <p>
 Most variants will not be in it, since 239,028 tested positions is a very small part of the
-genome. Two prediction tracks fill the gap by scoring every possible substitution, and neither
-is in the <em>Regulation</em> group: look under <em>Phenotype and Disease Associations</em>, in
-the <strong>Deleteriousness Predictions</strong> collection on
+genome. Three prediction tracks fill the gap by scoring every possible substitution. None of
+them is in the <em>Regulation</em> group; all three are under <em>Phenotype and Disease
+Associations</em>, the last two inside the <strong>Deleteriousness Predictions</strong>
+collection on
 <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=predictionScoresSuper">hg38</a>.</p>
 <ul>
+  <li>
+  <strong>CADD</strong> is the oldest and most widely used of the three, and the one a reader is
+  most likely to be asked for. It weights more than a hundred annotations, conservation and
+  regulatory signal among them, into a single score per substitution, trained by contrasting
+  variants that survived selection against simulated ones. Scores are PHRED scaled, so 10 marks
+  the top 10 percent of substitutions genome-wide, 20 the top 1 percent and 30 the top 0.1
+  percent. It was built to rank deleteriousness in general and not regulatory effect in
+  particular, so on a non-coding base treat a high score as a reason to look closer. Version 1.7
+  is available for <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=caddSuper1_7">hg19</a> and
+  <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=caddSuper1_7">hg38</a>, with version 1.6 kept
+  alongside it.</li>
   <li>
   <strong>AlphaGenome</strong> gives the AlphaGenome Variant Impact score from Google DeepMind,
   which folds together predicted effects on expression, splicing, chromatin accessibility and
   transcription factor binding across hundreds of cell types, plus AlphaMissense for changes
   that alter protein. It is precomputed for every possible single-base substitution in the
   genome, about 8.8 billion of them, with one track per alternate allele. Scores are PHRED
-  scaled, so 10 marks the top 10 percent of substitutions genome-wide, 20 the top 1 percent and
-  30 the top 0.1 percent. Unusually for a score of this kind it covers non-coding bases as well
-  as coding ones, which is what makes it useful here. Available for
+  scaled on the same convention as CADD. It is aimed squarely at regulatory consequence, which
+  is what makes it useful here, but it is new enough that there is little independent
+  benchmarking of it yet. Available for
   <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=alphaGenome">hg38</a>.</li>
   <li>
   <strong>PromoterAI</strong>, from Illumina, scores every possible single-base substitution in
   proximal promoter regions. Narrower than AlphaGenome and aimed squarely at promoter variants.
   Available for <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=promoterAi">hg38</a>.</li>
 </ul>
 <p>
 A high score from either says a model thinks the change is disruptive, not that anyone has
 measured it. Where a variant appears in both MPRAVarDB and a prediction track, the measurement
 is the better evidence.</p>
 
 <a name="otherGenomes"></a>
 <h6>What is available for assemblies other than human and mouse?</h6>
 <p>
 Much less. The limit is usually the data itself: these resources were built for human first, and
 most never went further than mouse. JASPAR is the main exception, since it needs only the genome
 sequence and a motif, so it covers zebrafish, fly, worm, chicken, sea squirt and yeast as well.
 ReMap also covers fly. Everything else described on this page is human and mouse
 only.</p>
 <p>
 Mouse is split awkwardly between its own assemblies. mm10 carries most of these tracks and mm39
 has only JASPAR, ReMap and VISTA, because several of the source projects never released mm39
 versions. If you need something that is on mm10 but not mm39,
 <a href="../cgi-bin/hgLiftOver">LiftOver</a> will convert the coordinates, though check the
 result before trusting it. Human has a milder version of the same problem: a few tracks, such
 as the older clustered Txn Factor ChIP, are still hg19 only.</p>
 <p>
 For assemblies not hosted at UCSC, or for tracks we do not carry, check the
 <a href="../cgi-bin/hgHubConnect">public hubs</a> list, where other groups publish data through
 our browser.</p>
 
 <a name="summary"></a>
 <h2>Summary: regulatory tracks by category</h2>
 <p>
 Each assembly name below links to that track's description page on that assembly. A few tracks
 appear on additional genomes not listed here; use
 <a href="../cgi-bin/hgTracks?hgt_tSearch=track+search">Track Search</a> to check a genome that is
 not shown.</p>
 <table class="stdTbl">
   <thead style="text-align: left">
     <tr>
       <th>Track</th>
       <th>What it is</th>
       <th>Measured or predicted</th>
       <th>Assemblies</th>
     </tr>
   </thead>
   <tbody>
     <tr>
       <td colspan="4"><em>Transcription factor binding</em></td>
     </tr>
     <tr>
       <td>ReMap ChIP-seq</td>
       <td>Public ChIP-seq for transcriptional regulators, integrated</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=ReMap">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=ReMap">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=ReMap">mm10</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=ReMap">mm39</a>,
       <a href="../cgi-bin/hgTrackUi?db=dm6&amp;g=ReMap">dm6</a></td>
     </tr>
     <tr>
       <td>TF ChIP (ENCODE 3 TFBS on hg19)</td>
       <td>ENCODE 3 TF ChIP-seq peaks, around 340 factors in about 130 cell types</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=encTfChipPk">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=encTfChipPk">hg38</a></td>
     </tr>
     <tr>
       <td>JASPAR Transcription Factors</td>
       <td>Motif matches from the JASPAR CORE collection; several releases as subtracks</td>
       <td>Predicted</td>
       <td>JASPAR 2026 on <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=jaspar">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=jaspar">mm39</a>,
       <a href="../cgi-bin/hgTrackUi?db=danRer11&amp;g=jaspar">danRer11</a>,
           <a href="../cgi-bin/hgTrackUi?db=galGal6&amp;g=jaspar">galGal6</a>,
           <a href="../cgi-bin/hgTrackUi?db=dm6&amp;g=jaspar">dm6</a>,
           <a href="../cgi-bin/hgTrackUi?db=ce11&amp;g=jaspar">ce11</a>,
           <a href="../cgi-bin/hgTrackUi?db=ci3&amp;g=jaspar">ci3</a>,
           <a href="../cgi-bin/hgTrackUi?db=sacCer3&amp;g=jaspar">sacCer3</a>; up to JASPAR 2024 on
           <a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=jaspar">hg19</a> and
           <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=jaspar">mm10</a></td>
     </tr>
     <tr>
       <td colspan="4"><em>Promoters and transcription start sites</em></td>
     </tr>
     <tr>
       <td>EPDnew Promoters</td>
       <td>Experimentally defined promoters with mapped start sites</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=epdNew">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=epdNew">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=epdNew">mm10</a></td>
     </tr>
     <tr>
       <td>FANTOM5</td>
       <td>CAGE transcription start sites and their usage per tissue</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=fantom5">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=fantom5">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=fantom5">mm10</a></td>
     </tr>
     <tr>
       <td colspan="4"><em>Enhancers and candidate elements</em></td>
     </tr>
     <tr>
       <td>GeneHancer</td>
       <td>Regulatory elements linked to predicted target genes</td>
       <td>Mixed, with predicted targets</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=geneHancer">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=geneHancer">hg38</a></td>
     </tr>
     <tr>
       <td>VISTA Enhancers</td>
       <td>Elements tested individually in transgenic mouse assays</td>
       <td>Measured, validated</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=vistaEnhancersBb">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=vistaEnhancersBb">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=vistaEnhancersBb">mm10</a>,
           <a href="../cgi-bin/hgTrackUi?db=mm39&amp;g=vistaEnhancersBb">mm39</a></td>
     </tr>
     <tr>
       <td>ENCODE cCREs</td>
       <td>Candidate elements classified from chromatin signal; ENCODE4 is the default</td>
       <td>Predicted from measured signal</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=cCREs">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=cCREs">mm10</a></td>
     </tr>
     <tr>
       <td>RefSeq Functional Elements</td>
       <td>NCBI curated non-coding functional elements</td>
       <td>Measured, curated</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=refSeqFuncElems">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=refSeqFuncElems">mm10</a></td>
     </tr>
     <tr>
       <td>MPRAs (MPRA Base)</td>
       <td>Reporter assay activity for 40,938 tested regulatory elements</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=mpra">hg38</a></td>
     </tr>
     <tr>
       <td colspan="4"><em>Chromatin and expression context</em></td>
     </tr>
     <tr>
       <td>ENCODE4 Regulation</td>
       <td>DNase, ATAC, histone marks and CTCF by tissue; the current default</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg4">hg38</a>,
       <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=encode4Reg">mm10</a></td>
     </tr>
     <tr>
       <td>ENCODE3 Regulation</td>
       <td>DNase, histone marks and transcription signal; archival, replaced by ENCODE4</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=wgEncodeReg">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=wgEncodeReg">hg38</a></td>
     </tr>
+<!-- Single-cell ATAC-seq (track singleCellSignalsPeaks, hg38 and mm10) is still
+     "release alpha" in trackDb, so these links error on the RR. Restore this row when the
+     track is released:
     <tr>
       <td>Single-cell ATAC-seq</td>
       <td>Accessibility peaks and signal from Cell Browser datasets</td>
       <td>Measured</td>
-      <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=singleCellSignalsPeaks">hg38</a>,
-      <a href="../cgi-bin/hgTrackUi?db=mm10&amp;g=singleCellSignalsPeaks">mm10</a></td>
+      <td>hg38, mm10</td>
     </tr>
+-->
     <tr>
       <td>GTEx Gene</td>
       <td>Gene expression across 53 tissues</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=gtexGene">hg19</a>,
       <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=gtexGene">hg38</a></td>
     </tr>
     <tr>
       <td>GTEx cis-eQTLs</td>
       <td>Variants associated with expression of nearby genes</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=gtexEqtlHighConf">hg38</a></td>
     </tr>
     <tr>
       <td colspan="4"><em>Effect of a single variant</em></td>
     </tr>
     <tr>
       <td>MPRAVarDB</td>
       <td>239,028 variants tested for allelic effect in reporter assays</td>
       <td>Measured</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=mpraVarDb">hg38</a></td>
     </tr>
+    <tr>
+      <td>CADD 1.7</td>
+      <td>Deleteriousness score for every single-base substitution, coding and non-coding;
+          under Phenotype and Disease Associations</td>
+      <td>Predicted</td>
+      <td><a href="../cgi-bin/hgTrackUi?db=hg19&amp;g=caddSuper1_7">hg19</a>,
+      <a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=caddSuper1_7">hg38</a></td>
+    </tr>
     <tr>
       <td>AlphaGenome</td>
       <td>Variant Impact score for every single-base substitution, coding and non-coding;
           under Phenotype and Disease Associations</td>
       <td>Predicted</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=alphaGenome">hg38</a></td>
     </tr>
     <tr>
       <td>PromoterAI</td>
       <td>Score for every single-base substitution in proximal promoters; under Phenotype and
           Disease Associations</td>
       <td>Predicted</td>
       <td><a href="../cgi-bin/hgTrackUi?db=hg38&amp;g=promoterAi">hg38</a></td>
     </tr>
   </tbody>
 </table>
 
 <p>
 For the full set of tracks on any assembly, open the <em>Regulation</em> group on the
 <a href="../cgi-bin/hgTracks">browser page</a>, or use
 <a href="../cgi-bin/hgTracks?hgt_tSearch=track+search">Track Search</a>.</p>
 
 <!--#include virtual="$ROOT/inc/gbPageEnd.html" -->