SNP Track QA

Starting with snp132, the SNP track was split into 4 tracks, announced here. Angie gave a presentation (video) on the big changes made starting with snp132. If you have any general questions about SNPs this is a good resource: http://www.ncbi.nlm.nih.gov/bookshelf/br.fcgi?book=helpsnpfaq.

In addition to the SNP-specific checks on this page, be sure to follow the new track checklist, too.

MySQL tables

• If possible, compare to old SNP tables for this species. Look for big jumps in the number of different func types of SNPs as well as the number and type of exceptions. Here's an example:

mysql> SELECT COUNT(DISTINCT (func)) FROM snp146;

• Look for SNPs that may have been erroneously dropped between the old and new versions. You can get a list of all new and dropped rsIDs by comapring the name column of the two tables. For example:

$ hgsql -Ne "SELECT name FROM snp146" | sort -u > snp146.names
$ hgsql -Ne "SELECT name FROM snp144" | sort -u > snp144.names
$ diff snp144.names snp146.names > snp144.snp146.diffs

• Check that func types in snp### table are documented in the html, both in the methods and in the check boxes. If there are new func types, make sure they are displayed correctly in the browser.

• Check that the weights column in snp### are only 1,2 or 3.
• Look at the snp###ExceptionDesc table:
  • Make sure the exception messages show up on hgc pages
  • Make sure the descriptions make sense
  • spot-check the counts. You can also compare these exceptions to those from the previous SNP release. To do so, you can use some commands like:

$ hgsql -Ne "select exception, count from snp146ExceptionDesc" hg19 | sort > hg19.snp146ExceptionDesc.counts
$ hgsql -Ne "select exception, count from snp144ExceptionDesc" hg19 | sort > hg19.snp144ExceptionDesc.counts
$ join -j 1 hg19.snp144ExceptionDesc.counts hg19.snp146ExceptionDesc.counts

The output of these commands will be a three column file, where column 1 is the exception name, column 2 is the count of that exception from the old SNP track, and column 3 is the count from the new SNP track. For example:

AlleleFreqSumNot1           1842     1752
DuplicateObserved           591680   390122
FlankMismatchGenomeEqual    182246   222451

Settings

• Make sure that there are no values in the snp### table that are not represented in the tracks filter controls.
  • Note that the controls in the cgi are hard coded, so you may find that controls exist for values not present in the snp### table.
  • Here's an example (repeat 4x where $field is class, valid, func, molType):

mysql> SELECT DISTINCT($field) FROM 'snp###';  

• Try some table browser queries that use the checkboxes on the filter page.
• Try turning on selected gene tracks on track controls page, make sure results show up

 in the "UCSC's predicted function relative to selected gene tracks:" section.

• Try the various color options.

Details

• Be sure to include a SNP with chimera and ls-snp links in your testing. To find such a SNP, pick any of the SNPs in the lsSnpPdb table (snpId column), go to that SNPs details page and then check the links under "Mappings to PDB protein structures".
• Make sure the tracks "turn off" when viewing large regions (these tables are too large to load for large regions).
• Pay special attention to the PAR regions and haplotype chromosomes. We shouldn't necessarily exclude snps that map to more than one position from sets that are uniquely mapped.

Description

• Note that most of the description is the same on all 4 snp tracks -- this is kept in one file (snp132.shared.html for snp132) that is included in the other html with a line like:

 <!--#insert file="sharedText.html"-->

• Make sure the source files listed are correct and exist at NCBI.
• Make sure that "Interpreting and Configuring the Graphical Display" section mentions all func types that you can select in TrackUi.

Ask Admins to "myisampack" Tables

As the SNP tables grow and grow, we have started to ask the admins to "myisampack" the tables before release to reduce their final size. After the tables are looking good on Dev (or Beta if that's where you've done your QA), then you can send a request to the cluster admins requesting that they "myisampack" the tables on Dev. You can also cc the engineer in charge of these tables on this email as well. Here's an example email:

Hello Cluster Admin,

Can you myisampack the following tables on hgwdev:

hg19.snp146
hg19.snp146CodingDbSnp
hg19.snp146Common
hg19.snp146ExceptionDesc
hg19.snp146Flagged
hg19.snp146Mult
hg19.snp146OrthoPt4Pa2Rm3
hg19.snp146Seq

Thanks!

Note that if you've pushed the tables from Dev to Beta for QA, you will need to re-push the tables to Beta after the admins have "myismapack" the tables.

snp###.fa files

These files will be located in /gbdb/$db/snp/. Be sure to request the push of these files from hgwdev to hgnfs1/genome-euro well in advance of the release. These files can be upwards of 33GB (and will likely keep growing!), and it can take 12 hours to transfer that much data from UCSC to genome-euro.

Downloads

If this is a human assembly, make sure there are downloads for "Masked FASTA Files (human assemblies only)" (/usr/local/apache/htdocs-hgdownload/goldenPath/hg19/snp###Mask). Check hat the FASTA files are actually masked with snps. Look for some lines with y, w, m, etc. Can use a command like:

  zcat chr1.subst.fa.gz | head -300 | grep -i [^atgcn]

AT RELEASE BE SURE TO:

• Make the old SNP track (if any) hidden by default, and check to see if any old SNP tracks should be dropped from the RR.
• Announce the release on genome-announce.
• When you push the snp-masked downloads, add a link to downloads.html.