The faceted composite interface on the ENCODE4 +DNase/ATAC/Histone/CTCF (Indiv.) track. Facets on the left filter the 6,353 subtracks, +and the table lists those that match.
+You can sign-up to get these announcements via our Genome-announce email list. We send around one short announcement email every two weeks.
Smaller software changes are not announced here. A summary of the three-weekly release changes can be found here. For the full list of our daily code changes head to our GitHub page. Lastly, see our credits page for acknowledgments of the data we host.
+ ++We are pleased to announce +faceted composites, a new +interface for composite tracks that hold very large numbers of subtracks. The standard +composite works well for somewhere between 20 and 50 subtracks, but it becomes unwieldy +once the count runs into the hundreds to thousands. A faceted composite is an alternative +display for those cases: facets along the left side filter the collection while a +paginated table on the right lists the subtracks that match, letting users narrow +thousands of entries down to the handful relevant to their work. The individual-experiment +tracks in the ENCODE4 Regulation collection, announced in July 2026, +already use this interface. Faceted composites are configured entirely through trackDb +settings, so any hub developer can build one. +
+ +The faceted composite interface on the ENCODE4 +DNase/ATAC/Histone/CTCF (Indiv.) track. Facets on the left filter the 6,353 subtracks, +and the table lists those that match.
++A faceted composite otherwise behaves like an ordinary composite, with two differences: +
+metaDataUrl setting
+Adding compositeTrack faceted to a composite stanza turns on the interface. A
+primaryKey setting names the column of that file which identifies each
+subtrack, and subtracks are named <parent>_<primaryKey value> to
+tie each one to its metadata row. Because there are no views, the subtracks of a single
+faceted composite can mix data types, such as signal and peak files, in one container.
+
+Underscore prefixes on the field names in the metadata file control where each field +shows up: +
+ +| Field name in the metadata file | Facet on the page | +Search box in the table |
|---|---|---|
tissue | yes | yes |
_date | no | yes |
__count | no | no |
+Two optional settings extend the interface: +
+dataTypes – groups several files per sample, so a single row of
+ the subtrack table can turn on a signal track and a peak track togethersubtrackUrls – turns metadata values into links, which is useful
+ for accession numbers or protocol identifiers+Our new Faceted Composite +Tracks documentation page walks through building one, with an +example hub that can be loaded directly into the browser. The complete +reference for each setting lives in our +trackDb +documentation, and our Hub +Basics page is a good starting point if you are new to building hubs. +
+ ++We would like to thank Andrew Smith at the University of Southern California, who +contributed the original implementation of this interface, and Jonathan Casper, who +developed it into the version released at the UCSC Genome Browser. We also thank +Lou Nassar, Gerardo Perez, Clay Fischer, Brian Raney, Max Haeussler, and Jairo +Navarro for testing, feedback, and documentation. +
+We are pleased to announce the release of two new proteome-wide missense variant effect prediction tracks for hg38: popEVE and EVE. Both are deep generative models that predict variant pathogenicity by learning patterns of natural sequence variation across species, without relying on clinical labels.
EVE (Evolutionary model of Variant Effect) is a deep generative model that predicts the pathogenicity of missense variants by learning patterns of