– Personalize your view of GENCODE Genes<\/h3>\n
In addition to choosing which GENCODE Gene tracks to view (e.g. basic gene set, PolyA, pseudogenes), you can now filter and highlight transcripts within the tracks. Try it here<\/a> (click on the “Genes” link).<\/p>\n Use the new trackDb setting, If you need to automatically disconnect your hub, you can use the If you have created your own assembly hub<\/a> you can now set up a BLAT<\/a> server to enable quick mRNA\/DNA and cross-species protein alignments. All you need is a server from which you can run gfServer<\/a>, and the .2bit<\/a> file containing the sequence of your assembly. Read the detailed instructions here<\/a>.<\/p>\n Note that the BLAT and gfServer programs and source code are freely available from the University of California Santa Cruz for academic and non-commercial use. A license<\/a> is required for commercial use.<\/p>\n We released four annotation tracks from human Build 141 of NCBI’s database of short genetic variations, dbSNP<\/a>. This release marks the first set of data available for the newest human assembly, hg38\/GRCh38. Read more<\/a>.<\/p>\n<\/div>\n Since then, NCBI has released the next database update: dbSNP Build 142<\/a>. We have derived another four tracks from this release, which are currently undergoing our rigorous quality assurance process and will be released very soon.<\/p>\n Data from the National Cancer Institute’s (NCI) Clinical Proteomic Tumor Analysis Consortium (CPTAC)<\/a> is now available in the UCSC Genome Browser as a public track hub. This track hub contains peptides that were identified by CPTAC in their deep mass spectrometry-based characterization of the proteome content of breast, colorectal and ovarian cancer biospecimens that were initially sequenced by The Cancer Genome Atlas<\/a> (TCGA).<\/p>\n In addition, we have also released a PeptideAtlas<\/a> track that displays peptide identifications from the PeptideAtlas August 2014 (Build 433) Human build<\/a>. This build, based on 971 samples containing more than 420 million spectra, identified over a million distinct peptides covering more than 15,000 canonical proteins. Read more<\/a>.<\/p>\n We have reduced the frequency of GenBank data updates for assemblies other than human and mouse. The GenBank-based tracks for selected recent assemblies are now updated about once a week rather than daily. The remainder of the 150+ assemblies in the Genome Browser are updated whenever a newer assembly is released and after that, about once a month. The GenBank update schedule for the human and mouse assemblies remains unchanged. Read more<\/a>.<\/p>\n We have added a UniProt<\/a> track to hg19\/GRCh37, and merged the old PFAM<\/a> (Protein Families) track into it. Check it out here<\/a>.<\/p>\n In case you missed the previous blog post<\/a>, we have created an easily installable version of the Genome Browser. You can set it up in just a few minutes on your laptop for private browsing of your own data alongside the native annotation tracks. It\u2019s fine-tuned to work with hg19\/GRCh37, but it works with all other assemblies as well. If you have genomic sequence for other organisms, you can add your own assembly hub. Read more<\/a>.<\/p>\n If you would like to stay informed about our new features and data sets, you are welcome to subscribe to our low-volume announcement mail list: genome-announce@soe.ucsc.edu<\/a><\/p>\n If after reading this blog post you have any public questions, please email genome@soe.ucsc.edu<\/a>. All messages sent to that address are archived on a publicly accessible forum<\/a>. If your question includes sensitive data, you may send it instead to genome-www@soe.ucsc.edu<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" We realize that it is sometimes difficult to keep up with all of the new features and data sets in the Genome Browser. After all, we release new annotation tracks almost daily, and we update our software every three weeks. This post highlights a smattering of the most recent updates. Browser & Track Hub Features – Personalize […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-100","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/posts\/100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/comments?post=100"}],"version-history":[{"count":55,"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/posts\/100\/revisions"}],"predecessor-version":[{"id":950,"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/posts\/100\/revisions\/950"}],"wp:attachment":[{"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/media?parent=100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/categories?post=100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/genome-blog.gi.ucsc.edu\/blog\/wp-json\/wp\/v2\/tags?post=100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}– Display your bigWig data on the other strand in your track hub<\/h3>\n
negateValues on<\/code>, to allow your bigWig data to be displayed on the Crick strand. This setting negates the values in the wiggle file, meaning that positive values become negative and vice versa. This is useful for wiggles representing transcription or other activities on the Crick strand. Note that wiggles with negative values are drawn in the color specified in altColor, <\/em>not color<\/em> as positive values are.<\/p>\n![\"negateValues\"](\"http:\/\/genome.ucsc.edu\/blog\/wp-content\/uploads\/2015\/02\/negateValues-300x139.jpg\")
<\/a><\/p>\n– Disconnect your hub automatically<\/h3>\n
hubClear<\/code> variable in the URL. This is especially helpful for users who are creating hubs dynamically. For example, to disconnect the urlOfHubToClear<\/code> hub, use a URL constructed like so:<\/p>\nhttp:\/\/genome.ucsc.edu\/cgi-bin\/hgTracks?db=hg19&hubClear=http:\/\/urlOfHubToClear<\/code><\/p>\n– Enable BLAT for your assembly hub<\/h3>\n
Annotation Tracks & Assemblies<\/span><\/h1>\n
– dbSNP v141 for hg19\/GRCh37 & hg38\/GRCh38<\/h3>\n
– Proteomics data available for hg19\/GRCh37: PeptideAtlas track & CPTAC data hub<\/h3>\n
– GenBank track updates<\/h3>\n
– UniProt track for hg19\/GRCh37<\/h3>\n
– New assembly browsers:<\/h3>\n
\n
![\"Ebola](\"http:\/\/genome.ucsc.edu\/blog\/wp-content\/uploads\/2015\/02\/ebola-300x185.png\")
<\/a><\/span><\/h1>\nNew Product<\/span><\/h1>\n
– Genome Browser in a Box (GBiB)<\/h3>\n
\n
\n