4031d6e765e1de6a6a612249f5bc9bdca2358eba jnavarr5 Tue Feb 3 15:53:31 2026 -0800 Announcing the Visible Tracks and Hub Space features. refs #36290 and #36609 diff --git src/hg/htdocs/goldenPath/newsarch.html src/hg/htdocs/goldenPath/newsarch.html index 9727d4bfe3c..0f993cc5b00 100755 --- src/hg/htdocs/goldenPath/newsarch.html +++ src/hg/htdocs/goldenPath/newsarch.html @@ -52,103 +52,109 @@ <p>You can sign-up to get these announcements via our <a target=_blank href="https://groups.google.com/a/soe.ucsc.edu/g/genome-announce?hl=en">Genome-announce</a> email list. We send around one short announcement email every two weeks.</p> <p>Smaller software changes are not announced here. A summary of the three-weekly release changes can be found <a target=_blank href="https://genecats.gi.ucsc.edu/builds/versions.html">here</a>. For the full list of our daily code changes head to our <a href="https://github.com/ucscGenomeBrowser/kent/commits/master" target=_blank>GitHub page</a>. Lastly, see our <a href="credits.html" target="_blank"> credits page</a> for acknowledgments of the data we host.</p> <!-- ============= 2025 archived news ============= --> <a name="2026"></a> -<!-- -<a name="020326"></a> +<a name="020326a"></a> <h2>Feb. 03, 2026 New "Visible Tracks" group feature</h2> <p> We are excited to announce a new improvement to the UCSC Genome Browser: the <b>Visible Tracks</b> group. The Genome Browser now includes a dynamic track group that automatically displays all currently visible tracks in one convenient location. This means you no longer need to hunt through multiple track categories to adjust tracks you've already turned on. </p> <div class="text-center"> -<img src="/images/newsArchImages/visibleTracks.png" width='65%'> +<img src="/images/newsArchImages/visibleTracks.png" width='55%'> </div> <p> Previously, managing visible tracks required navigating back to their original categories — whether that was Genes and Gene Predictions, Conservation, Variation, or any other group. Now, all your active tracks appear together in the <b>Visible Tracks</b> group, making it faster and easier to adjust display modes for visible tracks. </p> <p> -We would like to thank Chris Lee and Jairo Navarro Gonzalez for their work on creating and testing -the feature.</p> ---> +The "Visible Tracks" will only appear when there are more than 32 tracks available for a +genome assembly. +</p> +<p> +We would like to thank Chris Lee and Jairo Navarro Gonzalez for the release of this feature.</p> -<!-- -<a name="020326"></a> +<a name="020326b"></a> <h2>Feb. 03, 2026 Hub Space: Host Your Track Hubs Directly on the Genome Browser</h2> <p> We are excited to introduce <a href="/cgi-bin/hgHubConnect#hubUpload">Hub Space</a>, a new hosting service that allows users to upload and visualize track hub files directly on the UCSC Genome Browser without relying on third-party hosting services such as Dropbox, Google Drive, or AWS. </p> +<div class="text-center"> +<img src="/images/newsArchImages/HubSpace.png" width='65%'> +</div> + <p> <b>Hub Space Features:</b><br> Each account is allocated 10 GB of storage space. While we strive to maintain uninterrupted access, please maintain your own backups. Data persistence over the long term is not guaranteed. To request additional storage space, please <a href="/contacts.html">contact us</a>. </p> <p> <b>How to Use Hub Space:</b><br> There are two primary ways to upload your files: </p> <ol> <li> <b>Single file upload:</b> Upload individual binary-indexed files (bigBed, bigWig, BAM, VCF, and other supported formats) for immediate visualization. </li> <li> <b>Complete hub upload:</b> Upload an entire track hub along with all supporting files (hub.txt, bigWig, bigBed, etc.) to visualize the hub. </li> </ol> <p> If a hub.txt file is not provided when uploading data files, one is automatically generated. The generated hub.txt file is configured with the <a href="/goldenPath/help/trackDb/trackDbHub.html#useOneFile">useOneFile</a> trackDb setting, and -as a result, each hub is limited to a single genome assembly. Editing the generated hub.txt file is -not yet supported. To customize the hub configuration or data display, replace the generated hub.txt -file with your own version after uploading the data files. +as a result, each hub is limited to a single genome assembly. Editing the generated hub.txt file +directly on the UCSC Genome Browser is not yet supported. To customize the hub configuration or +data display, replace the generated hub.txt file with your own hub.txt file. </p> <p> To get started with Hub Space, visit the <a href="/cgi-bin/hgHubConnect#hubUpload">Track Data Hubs page</a> and -click on the "Hub Space" section. We would love to hear your feedback on this new feature. +click on the "Hub Space" tab. We would love to hear your feedback on this new feature. Please <a href="/contacts.html">contact us</a> and let us know what you think! </p> ---> + +<p> +We would like to thank Chris Lee and Jairo Navarro Gonzalez for the release of this feature.</p> <a name="011526"></a> <h2>Jan. 15, 2026 New ENCODE cCREs track available for human (hg38)</h2> <p> We are proud to announce a new <a href="/cgi-bin/hgTrackUi?db=hg38&c=chr7&g=cCREs&position=default" target="_blank"> ENCODE Registry of cCREs (candidate Cis-Regulatory Elements)</a> container track for the hg38/GRCh38 genome as described in <a target="_blank" href="https://www.nature.com/articles/s41586-025-09909-9">Moore et al., <em>Nature</em> 2026</a>. This container contains candidate Cis-Regulatory Elements (cCREs) generated by the ENCODE Consortium during Phase 4 (ENCODE4) and Phase 3 (ENCODE3). The previous "ENCODE3 cCREs" track is retained for archival purposes. The tracks include both integrated (biosample-agnostic) and biosample-specific annotations derived from core epigenomic assays.</p> <div class="text-left">