SNP Track QA

Starting with snp132, the SNP track was split into 4 tracks, announced here. 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.
• 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 exceptionDesc table: spot-check the counts, make sure the exception messages show up on hgc pages, make sure the descriptions make sense. Ideally, this table would be visible in the Table Browser when the track is selected, but it isn't right now. See Redmine #3606 for current status of this problem.

settings

• Make sure that all settings that you can select for are present in mysql tables and vice versa.
• 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, look in the lsSnpPdb, and then check the links under "Mappings to PDB protein structures" on the track details page.
• 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
• Make sure the source files listed are correct and exist at NCBI.
• Make sure that methods section mentions all func types that you can select in trackUi.

downloads

If this is a human assembly, make sure there are downloads for "Masked FASTA Files (human assemblies only)" 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]

genome graphs

Check with Galt to make sure that the current snp track will be used in genome graphs. (rsID is one of the accepted genome graphs formats. When rsIDs are entered, their positions are looked up in the snp table. Galt said in April 2011 that currently: "It starts looking for snp134, then snp133, ... down to about snp125. The first one it finds that exists in the db is returned and used for resolving user symbols that might be rsIds."

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.