Assembly QA Part 4 RR Steps

This page is currently a draft in progress. For now, use Releasing an assembly instead.

Navigation Menu Home Page Assembly QA Part 1: DEV Steps Assembly QA Part 2: Track Steps Assembly QA Part 3: BETA Steps Assembly QA Part 4: RR Steps Assembly QA Part 5: Post Release Steps

RR: Populate spreadsheet steps

• We need to create a checklist for your RR steps.
• You can add a new tab to track RR steps, or you can pick up where you left off on the same tab as your "dev" and "beta" steps.

To populate the "wiki link" for each step, add this formula to cell A2 (or the row after your last "dev" step) in your new "track checklist" spreadsheet and drag the formula down:

A2 (or the row after your last "beta" step)

=HYPERLINK("http://genomewiki.ucsc.edu/genecats/index.php/Assembly_QA_Part_4_RR_Steps#"&SUBSTITUTE(B2," ", "_"),"link")

IMPORTANT: Drag the formula for "A" down the spreadsheet to populate the other rows.

To populate the "track checklist steps," add this formula to cell B2 ((or the row after your last "dev" step) in your new "track checklist" spreadsheet. Do NOT drag the formula down.

B2

=IMPORTXML("http://genomewiki.ucsc.edu/genecats/index.php/Assembly_QA_Part_4_RR_Steps#", "/html/body/div/div/div/div/div/h4/span/span")

This formula will populate all the rows below it with the wiki section titles. You do no need to drag this formula down.

RR: Push Request: rsync complete database

• Request an rsync of the entire database from mysqlbeta to mysqlrr/euro/asia.
• Request drop of trackDb_public and hgFindSpec_public from mysqlrr/euro/asia
• Request push of trackDb and friends
• See an example push request

RR: Push Downloads

If there are files associated with the track that are to be pushed to hgdownload, check to see that there is a README that makes sense and the files have an md5sum.txt file that goes with them and is correct. Check the file itself to make sure it is not corrupted and that it contains what is expected. If it is a gzipped file, you can do "zcat file.gz | head" and "zcat file.gz | tail" to look at it. Looking at the last part of the file can sometimes catch corruption that can't be seen by only looking at the first part.

Data files destined for hgdownload are organized on hgwdev at:

/usr/local/apache/htdocs-hgdownload/goldenPath/*

and can be viewed in a browser from http://hgdownload-test.cse.ucsc.edu/downloads.html. Non-data files (such as downloads.html) are in the "hgdownload" git repository. See the Static_Page_Protocol for instructions on checking out that repository. Push requests for downloads should look like something like this:

Please push files from here on hgwdev:
    /usr/local/apache/htdocs-hgdownload/goldenPath/$db/file
To here on hgdownload:
    /usr/local/apache/htdocs/goldenPath/$db/file
(in the path, "htdocs-hgdownload" should become "htdocs") 

RR: Push Request: start dump/autodump

• Database rsync should be complete before doing this.
• Request start of dump/autodump for your assembly on rr/euro/asia.

See this example push request.

RR: Check all tracks on the RR

Check your track on the RR. Check that searches work (if not, you probably need to push the hgFindSpec_public table). Also check that all default tracks still display. If you filled in the "Release Log URL" field in the push queue, check the next day to be sure that the link from the release log works as expected.

RRs: Edit downloads.html

Check to see if the downloads files ought to have a link from downloads.html. If so, add the link and push downloads.html (after the files are already pushed!). NOTE: If you are pushing ENCODE tracks, when using a second/third/fourth version of the data there is often a "releaseLatest" directory that has the latest files. Be sure that you are not pushing the entire releaseLatest directory, only the files from there. Be sure to add a helpful sentence in your push-request to tip off the admin about this unusual push.

RR: Push chain/nets for other assemblies

• At the start of the RR steps, you asked for an rsync of your database from beta>rr/euro/asia, so you have already pushed the chain/nets within your database. Now we need to do this for any other databases (aka, other assemblies that your assembly has chain/net alignments to).
• Push trackDb & friends for any other databases
• Push chain/chainLink/net tables for each database.
• See this example push request .

RR: Chain chain/nets tracks for other assemblies

QA chain/nets for the other assemblies.

RR: Write Google Groups announcement

See announcement example.

RR: Write release log text in Redmine & close

🔵 Done with RR steps? Go to Assembly QA Part 5: Post Release Steps