[an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive]

Contact Us

UCSC Genome Bioinformatics Group
UCSC Genomics Institute
University of California, Santa Cruz
1156 High Street, MS: GI
Santa Cruz, CA 95064

Follow GenomeBrowser on Twitter

Genome Browser staff

Browser staff in native habitat.

Genome Browser inquiries

[an error occurred while processing this directive]

This website gwips.ucc.ie is a "mirror" not run by UCSC. Please try to contact the person who manages this mirror with questions.

If you mail the UCSC mailing list, please include this mirror's address http://gwips.ucc.ie with any questions.

Before posting a question, we strongly encourage you to search our mailing list archives, our website, and our wiki for the answer. Please follow our technical support guidelines in your queries. This will give us enough to resolve your issue without requests for more information. PLoS Computational Biology has published a good set of guidelines for seeking online scientific help. When sending us a browser URL, we recommend that you use our Session tool to create a link that fully captures the browser settings. If copy/pasting a URL, be sure to remove the "hgsid=<value>" parameter from any URL you send, as this can cause your personal settings to change unexpectedly. Read more about making links in our documentation.

Search the Genome Browser website:  

Search the Genome Browser Wiki Site:  


We encourage you to search the appropriate archive before contacting us via the mailing list, but we will reply to your message as quickly as we can.
Questions and comments submitted to most of the Genome Browser forums are publicly accessible and searchable. Please do not post confidential information to our public forums.

Mailing list

Subscribe Search Write
Website and data questions
Publicly searchable, interactive discussion forum for questions about the UCSC Genome Browser software, annotation database, genome assemblies, bug reports and release cycles (high volume).

Subscribe Genome archives genome@soe.ucsc.edu
Server and website access problems
Private forum for reporting server errors or other access problems on the UCSC Genome Browser or BLAT servers. Scheduled service interruptions for system maintenance are posted to the genome-announce forum and our Twitter feed.
Please also use this private forum for sensitive data. It is visible only to our staff.

  Private: Not searchable genome-www@soe.ucsc.edu
Mirror and source code questions
Interactive discussion forum for questions about the setup and maintenance of Genome Browser mirrors. Commercial use of the source code and binaries requires a license. Set up a mirror.

Subscribe Genome-mirror archives genome-mirror@soe.ucsc.edu
Genome Browser announcements
Notifications from the Genome Browser project team about new software and data releases, and other items of interest to Genome Browser users (low volume).

Subscribe Genome-announce archives  
Track hub developers mailing List
Track Hub Developers can learn about new Track Hub settings on our software release log or ask to join this collaborative mailing list to receive news about new track hub settings. The list shares updates about new documented settings on the Hub Track Database Definition page.

Ask to join group Track hub developers archives track-hubs@soe.ucsc.edu
Genome Browser Training Program
For information about our newly expanded on-site training program, email our training department or visit our sign-up page.

    ucscgbtraining@soe.ucsc.edu
Comments and suggestions
Private forum for suggesting new tracks, utilities, and other features for the Genome Browser.

    Suggestion Box

Commercial licensing inquiries

Genome Browser: genome-www@soe.ucsc.edu
Private forum for licensing questions. For more information about licensing the Genome Browser software, see the software licensing requirements.

Blat and In-Silico PCR: kent@soe.ucsc.edu
See the Kent Informatics web site for more information.

[an error occurred while processing this directive]