Note that it is not important that the items be sorted exactly in order - as long
as the items are almost all in order, it will not affect performance.
". Expect to find chrom/chromStart and
chrom/chromEnd. Press show sizes in the push queue and look at
the indexes. Make sure no tables are missing and all return valid values.
Searching
If the track item names are relatively unique, perform a few searches.
If search isn't enabled, make that request to the track sponsor. This isn't
required for the push.
If the track item names are relatively similar (i.e. RNA Genes, TFBS) we don't
want to enable search, it would return too many matches.
Help pages
(This may no longer be relevant as Donna does not maintain them manually
anymore and the table-browser schema link in description page handles much
of this now.)
The User Guide includes track descriptions at
hgTracksHelp.html.
Review the track description for correctness.
Send edit requests to the person who maintains the static page content
(currently Donna).
joinerCheck
Time permitting, ask the track sponsor about applicable rules in all.joiner
for your track and run joinerCheck -identifier -database -keys. You can also
use Bob's runJoiner.csh.
Chromosome coverage
Some tracks don't have data on all chromosomes. To check which ones
do have data:
countPerChrom.csh db table
and/or:
countPerChrom.csh db table histogram
OR:
SELECT DISTINCT chrom FROM encode_UVA_DNARep_0_2;
If a "regular" chrom (not random or haplotype) is missing data, it
should NOT be listed in the trackDb restrictList setting. You you can check
the restrictList in trackDb as follows:
SELECT tableName, restrictList FROM trackDb WHERE tableName like
'encode_UVA_DNARep%';
restrictList (if not blank) should be a comma-separated list of chroms with
data. In trackDb.ra, the chromosomes line specifies the contents that later
becomes restrictList after doing a "make strict" on beta. e.g. chromosomes
chr2, chr4, chr5.
EASY GRAPHICAL WAYS TO CHECK COVERAGE: (1) Import the table into Genome Graphs.
(2) To see a count plus a histogram of chrom coverage, select the table
in the Table Browser, hit the "describe table schema" button, and
click the "values" link for the chrom field.
In addition, you can use the countPerChrom.csh script to get a count of track
items for each chromosome, and checkCoverage.csh, to get a list of the largest
blocks of non-annotated regions (with links) that are not gaps.
Track Settings (hgTrackUi)
Click on the track name or the mini-button to the left of the track (in
hgTracks) to get to the track settings page. Make sure that the track settings
work as expected.
genePredCheck/pslCheck
For gene prediction tracks (with tables in the
genePred format, run genePredCheck
(run the command with no arguments for instructions). For psl tables, run pslCheck.
Table Descriptions
Hit the "view table schema" button (on hgTrackUi, hgc, or hgTables) and make
sure there is a description column present with descriptions of the table
fields. If a track has more than one table, be sure to check for table
descriptions on each of them. The
description column uses the 'tableDescriptions' table to display this
information. This table is built nightly on hgwdev and hgwbeta, and must be
pushed to the RR if it contains descriptions for a new type of table (things
like psl will already be out there).
Background on the tableDescriptions table is
here.
Release Log
Remember that the contents of the "release log" field in the qaPushQ will be
added to the auto-generated release log page.
trackDb and hgFindSpec
Check whether trackDb needs to be pushed to the RR (use table browser on RR).
Check that no rows would get deleted when pushing trackDb. Check whether other
rows get added. If so, update the pushqueue for that, or, temporarily delete
the row, push trackDb, then regenerate it on hgwbeta.
Can use compareTrackDbs.csh hgwbeta hgw1 hg16
Can use compareHgFindSpecs.csh hgwbeta hgw1 hg16
(will create 2 output temp files in current directory per assembly checked)
push request
Ask admins (push-request at soe) for a push of the table (incl trackDb, if needed)
to the RR.
Notify (cc:) the track submitter on the push request, in case they are not on
the browser-qa alias.
Be sure to ask the pushers to 'unexclude' any of the hgnfs1 files that need
to be available for the track to work for the mirror sites.
Validate on the RR
Check your track on the RR. Also check that all default tracks still display.