5fd99d465a31d5bd38320ac85ff1969ab9515014 mspeir Wed Sep 23 15:44:06 2026 -0700 Regulation FAQ: correct assembly coverage, add variant effect section, refs #24610 Corrections found by checking the page against our own release announcements, which I should have done before the first commit: - ENCODE4 Regulation is on mm10 as well as hg38. The track symbol differs by assembly (wgEncodeReg4 on hg38, encode4Reg on mm10), so a search by name missed it. - JASPAR 2026 covers hg38, mm39, danRer11, galGal6, dm6, ce11, ci3 and sacCer3. hg19 and mm10 stop at JASPAR 2024. The page had implied all ten were 2026. Also notes that the track holds several releases as subtracks, so the version depends on which one is turned on. - TFBS Conserved is on hg17 as well as hg18 and hg19. - ENCODE4 replaced ENCODE3 as the default in July 2026 and ENCODE3 is kept for archival use. Said in the text and marked in the summary table. - The cell type section described the old subtrack list for the large collections, which now use the faceted interface. - Dropped "composite" and "superTrack", which users should not see. New section on what a single variant does to regulation, covering MPRAVarDB for variants that were actually tested in a reporter assay, and AlphaGenome and PromoterAI for predictions. These live under Phenotype and Disease Associations rather than Regulation, which is worth saying since that is where a reader would otherwise fail to find them. Links to goldenPath/help/hgRegMotifHelp.html from the motif definition and from the JASPAR entry, and the definition now matches the wording there. 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 575f02c1a79..611ee9f2595 100755 --- src/hg/htdocs/FAQ/FAQregulation.html +++ src/hg/htdocs/FAQ/FAQregulation.html @@ -9,30 +9,32 @@ <h2>Topics</h2> <ul> <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="#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="#ccres">What are cCREs, and which cCRE track should I use?</a></li> <li><a href="#cellType">How do I restrict a search to one cell type or tissue?</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 lot between assemblies, so check the list before you assume a track exists on the genome you work with.</p> <a name="measuredPredicted"></a> <h2>The basics</h2> @@ -41,32 +43,34 @@ them are in the <em>Regulation</em> track group, which you will find below the browser image on the <a href="../cgi-bin/hgTracks?db=hg38">main browser page</a>. It is not always obvious which one you want, because these tracks answer quite different questions even when they all look like boxes on the screen.</p> <h6>What is the difference between measured and predicted binding sites?</h6> <p> Nearly every question we get about these tracks comes down to this distinction.</p> <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 motif, a short -pattern that the factor is known to prefer. Predictions exist everywhere in the genome for every +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> <p> For human, three tracks cover most needs. All three are in the <em>Regulation</em> group.</p> @@ -78,47 +82,51 @@ 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&g=ReMap">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=ReMap">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=ReMap">mm10</a>, <a href="../cgi-bin/hgTrackUi?db=mm39&g=ReMap">mm39</a> and <a href="../cgi-bin/hgTrackUi?db=dm6&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&g=encTfChipPk">hg19</a> and <a href="../cgi-bin/hgTrackUi?db=hg38&g=encTfChipPk">hg38</a>. An older clustered version of the - same data is on <a href="../cgi-bin/hgTrackUi?db=hg19&g=wgEncodeRegTfbsClusteredV3">hg19 as - Txn Factor ChIP</a>.</li> + same data, <em>Txn Factor ChIP</em>, is on + <a href="../cgi-bin/hgTrackUi?db=hg19&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. The current track is JASPAR 2026. 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. - Available for <a href="../cgi-bin/hgTrackUi?db=hg19&g=jaspar">hg19</a>, + 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&g=jaspar">hg38</a>, - <a href="../cgi-bin/hgTrackUi?db=mm10&g=jaspar">mm10</a>, <a href="../cgi-bin/hgTrackUi?db=mm39&g=jaspar">mm39</a>, <a href="../cgi-bin/hgTrackUi?db=danRer11&g=jaspar">danRer11</a>, + <a href="../cgi-bin/hgTrackUi?db=galGal6&g=jaspar">galGal6</a>, <a href="../cgi-bin/hgTrackUi?db=dm6&g=jaspar">dm6</a>, <a href="../cgi-bin/hgTrackUi?db=ce11&g=jaspar">ce11</a>, - <a href="../cgi-bin/hgTrackUi?db=galGal6&g=jaspar">galGal6</a>, <a href="../cgi-bin/hgTrackUi?db=ci3&g=jaspar">ci3</a> and - <a href="../cgi-bin/hgTrackUi?db=sacCer3&g=jaspar">sacCer3</a>.</li> + <a href="../cgi-bin/hgTrackUi?db=sacCer3&g=jaspar">sacCer3</a>. On + <a href="../cgi-bin/hgTrackUi?db=hg19&g=jaspar">hg19</a> and + <a href="../cgi-bin/hgTrackUi?db=mm10&g=jaspar">mm10</a> the newest release is JASPAR + 2024.</li> </ul> <p> Two older tracks still come up in questions. <strong>TFBS Conserved</strong> shows predicted sites that are conserved across human, mouse and rat, on <a href="../cgi-bin/hgTrackUi?db=hg17&g=tfbsConsSites">hg17</a>, <a href="../cgi-bin/hgTrackUi?db=hg18&g=tfbsConsSites">hg18</a> and <a href="../cgi-bin/hgTrackUi?db=hg19&g=tfbsConsSites">hg19</a> only; it has not been updated in many years and there is no hg38 version. <strong>ORegAnno</strong> is a curated collection of regulatory elements taken from the literature, so it is small but every entry has a citation, on <a href="../cgi-bin/hgTrackUi?db=hg19&g=oreganno">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=oreganno">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=oreganno">mm10</a> and <a href="../cgi-bin/hgTrackUi?db=dm6&g=oreganno">dm6</a>.</p> @@ -238,71 +246,87 @@ <a href="../cgi-bin/hgTrackUi?db=hg38&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&g=vistaEnhancersBb">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=vistaEnhancersBb">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=vistaEnhancersBb">mm10</a> and <a href="../cgi-bin/hgTrackUi?db=mm39&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&g=refSeqFuncElems">hg38</a> and <a href="../cgi-bin/hgTrackUi?db=mm10&g=refSeqFuncElems">mm10</a>.</li> <li> - <strong>MPRAs</strong> is a collection of massively parallel reporter assay results. These - measure regulatory activity for many sequences at once. + <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&g=mpra">hg38</a>.</li> </ul> <p> -For the chromatin evidence behind the called elements, see -<a href="../cgi-bin/hgTrackUi?db=hg38&g=wgEncodeReg4">ENCODE4 Regulation</a> on hg38, which -carries DNase, ATAC-seq, histone -modification and CTCF signal organized by tissue, and the older ENCODE3 Regulation container on +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&g=wgEncodeReg4">hg38</a> and +<a href="../cgi-bin/hgTrackUi?db=mm10&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&g=wgEncodeReg">hg19</a> and <a href="../cgi-bin/hgTrackUi?db=hg38&g=wgEncodeReg">hg38</a>.</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. The word <em>candidate</em> is doing real work here: these are regions worth testing, not confirmed regulatory elements.</p> <p> -The <a href="../cgi-bin/hgTrackUi?db=hg38&g=cCREs">ENCODE cCREs</a> container on hg38 holds -several versions. The <strong>ENCODE4 -cCREs</strong> registry is the current one and should be your default. The <strong>ENCODE4 Core -Collection</strong> is a smaller, higher-confidence subset. <strong>ENCODE3 cCREs</strong> is the -earlier release, kept 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. <a href="../cgi-bin/hgTrackUi?db=mm10&g=cCREs">Mouse -mm10</a> carries the same three versions.</p> +The <strong>ENCODE cCREs</strong> container on +<a href="../cgi-bin/hgTrackUi?db=hg38&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&g=cCREs">mm10</a> carries the same three versions.</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 composites or superTracks holding many subtracks, one -per cell type or experiment, and they arrive with only a summary view turned on. Click the track -name to open its configuration page, where you will find the list of subtracks and, on the -bigger tracks, 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> +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 +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&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="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> @@ -314,46 +338,89 @@ 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&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 +<a href="../cgi-bin/hgTrackUi?db=hg38&g=predictionScoresSuper">hg38</a>.</p> +<ul> + <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 + <a href="../cgi-bin/hgTrackUi?db=hg38&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&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> -Considerably less, and this is a matter of what data exists rather than what we have loaded. The -large regulatory resources were built for human first and mouse second. JASPAR predictions are -the most widely available, since they only require the genome sequence and a motif, and are -present for zebrafish, fly, worm, chicken, sea squirt and yeast in addition to human and mouse. -ReMap and ORegAnno cover fly. Most of the remaining tracks described on this page are human and -mouse only.</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 and ORegAnno also cover fly. Everything else described on this page is human and mouse +only.</p> <p> -Coverage also differs between assemblies of the same organism. On mouse, mm10 carries most of -the regulatory tracks while mm39 has only JASPAR, ReMap and VISTA, because several of the source -projects have not released mm39 versions. If a track you need is on mm10 but not mm39, the -<a href="../cgi-bin/hgLiftOver">LiftOver</a> tool can convert coordinates between the two, -though you should check the result. Human has the same problem on a smaller scale: a few of -these tracks are still hg19 only, and TFBS Conserved was never rebuilt for hg38.</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 are +still hg19 only, and TFBS Conserved was never rebuilt for hg38.</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> @@ -374,42 +441,42 @@ <td><a href="../cgi-bin/hgTrackUi?db=hg19&g=ReMap">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=ReMap">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=ReMap">mm10</a>, <a href="../cgi-bin/hgTrackUi?db=mm39&g=ReMap">mm39</a>, <a href="../cgi-bin/hgTrackUi?db=dm6&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&g=encTfChipPk">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=encTfChipPk">hg38</a></td> </tr> <tr> <td>JASPAR Transcription Factors</td> - <td>Motif matches from the JASPAR CORE collection</td> + <td>Motif matches from the JASPAR CORE collection; several releases as subtracks</td> <td>Predicted</td> - <td><a href="../cgi-bin/hgTrackUi?db=hg19&g=jaspar">hg19</a>, - <a href="../cgi-bin/hgTrackUi?db=hg38&g=jaspar">hg38</a>, - <a href="../cgi-bin/hgTrackUi?db=mm10&g=jaspar">mm10</a>, + <td>JASPAR 2026 on <a href="../cgi-bin/hgTrackUi?db=hg38&g=jaspar">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm39&g=jaspar">mm39</a>, <a href="../cgi-bin/hgTrackUi?db=danRer11&g=jaspar">danRer11</a>, + <a href="../cgi-bin/hgTrackUi?db=galGal6&g=jaspar">galGal6</a>, <a href="../cgi-bin/hgTrackUi?db=dm6&g=jaspar">dm6</a>, <a href="../cgi-bin/hgTrackUi?db=ce11&g=jaspar">ce11</a>, - <a href="../cgi-bin/hgTrackUi?db=galGal6&g=jaspar">galGal6</a>, <a href="../cgi-bin/hgTrackUi?db=ci3&g=jaspar">ci3</a>, - <a href="../cgi-bin/hgTrackUi?db=sacCer3&g=jaspar">sacCer3</a></td> + <a href="../cgi-bin/hgTrackUi?db=sacCer3&g=jaspar">sacCer3</a>; up to JASPAR 2024 on + <a href="../cgi-bin/hgTrackUi?db=hg19&g=jaspar">hg19</a> and + <a href="../cgi-bin/hgTrackUi?db=mm10&g=jaspar">mm10</a></td> </tr> <tr> <td>TFBS Conserved</td> <td>Conserved motif matches; not updated recently, no hg38 version</td> <td>Predicted</td> <td><a href="../cgi-bin/hgTrackUi?db=hg17&g=tfbsConsSites">hg17</a>, <a href="../cgi-bin/hgTrackUi?db=hg18&g=tfbsConsSites">hg18</a>, <a href="../cgi-bin/hgTrackUi?db=hg19&g=tfbsConsSites">hg19</a></td> </tr> <tr> <td>ORegAnno</td> <td>Regulatory elements curated from the literature</td> <td>Measured, curated</td> <td><a href="../cgi-bin/hgTrackUi?db=hg19&g=oreganno">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=oreganno">hg38</a>, @@ -444,78 +511,102 @@ <td>Mixed, with predicted targets</td> <td><a href="../cgi-bin/hgTrackUi?db=hg19&g=geneHancer">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&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&g=vistaEnhancersBb">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=vistaEnhancersBb">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=vistaEnhancersBb">mm10</a>, <a href="../cgi-bin/hgTrackUi?db=mm39&g=vistaEnhancersBb">mm39</a></td> </tr> <tr> <td>ENCODE cCREs</td> - <td>Candidate elements classified from chromatin signal</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&g=cCREs">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&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&g=refSeqFuncElems">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=refSeqFuncElems">mm10</a></td> </tr> <tr> - <td>MPRAs</td> - <td>Massively parallel reporter assay activity</td> + <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&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</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&g=wgEncodeReg4">hg38</a></td> + <td><a href="../cgi-bin/hgTrackUi?db=hg38&g=wgEncodeReg4">hg38</a>, + <a href="../cgi-bin/hgTrackUi?db=mm10&g=encode4Reg">mm10</a></td> </tr> <tr> <td>ENCODE3 Regulation</td> - <td>DNase, histone marks and transcription signal</td> + <td>DNase, histone marks and transcription signal; archival, replaced by ENCODE4</td> <td>Measured</td> <td><a href="../cgi-bin/hgTrackUi?db=hg19&g=wgEncodeReg">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&g=wgEncodeReg">hg38</a></td> </tr> <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&g=singleCellSignalsPeaks">hg38</a>, <a href="../cgi-bin/hgTrackUi?db=mm10&g=singleCellSignalsPeaks">mm10</a></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&g=gtexGene">hg19</a>, <a href="../cgi-bin/hgTrackUi?db=hg38&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&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&g=mpraVarDb">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&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&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?db=hg38">browser page</a>, or use <a href="../cgi-bin/hgTracks?hgt_tSearch=track+search">Track Search</a>.</p> <!--#include virtual="$ROOT/inc/gbPageEnd.html" -->