GRC Patch Release

The GRC Patch Release track is different from other tracks in that you are technically also releasing the patch assembly to the RR, though nobody will ever actually see the assembly (ie. it will not be visible from hgGateway). The release of the patch assembly is what allows the links in the hgc page to display the DNA from the patched assembly. Note that in the making of an assembly, there are many tables and files that are automatically created that are not necessary for this track to function, thus we only push certain parts, not the whole assembly.

These are the extra steps you will need to take in addition to the normal Checklist steps for pushing to beta of tables and associated files. The examples below assume you will be on hg19, some push request emails are for mm10.

Stage the track on beta

1. Make the patch database on beta:

hgwbeta> hgsql
hgwbeta> create database hg19Patch#;

2. Push the chromInfo table to mysqlbeta

hgwdev> sudo mypush hg19Patch# chromInfo mysqlbeta

3. Add the necessary lines to hgcentralbeta.dbDb

hgwdev> hgsql -Ne 'select * from dbDb where name like "hg19Patch#"'  hgcentraltest > dbDbHg19Patch

• The above My SQL command will create the file dbDbHg19Patch (-N strips column names, -e executes commands and then quits).
• From the same directory you ran that command you need to edit it, for example hgwbeta> emacs dbDbHg19Patch.
• Change the active column to be 0 rather than 1, this will prevent the database from showing on hgGateway.

  mysql> select * from dbDb where name like "hg19Patch10"\G
  *************************** 1. row ***************************
         name: hg19Patch10
  description: Sep. 2012 (GRCh37.p10/hg19Patch10)
      nibPath: /gbdb/hg19Patch10
     organism: Grch37.p10
   defaultPos: chr1_jh636052:3604121-3614120
       active: 1
     orderKey: 145
       genome: GRCh37.p10
     scientificName: Homo sapiens
     htmlPath: /gbdb/hg19Patch10/html/description.html
     hgNearOk: 0
       hgPbOk: 0
   sourceName: GRCh37 Patch 10 Genome Reference Consortium Human Reference 37
        taxId: 9606
 >>This is just showing you what information is contained in hg19Patch10

Change the 6th column "active:" for the created file dbDbHg19Patch from "1" to 0:

 hg19Patch10	Sep. 2012 (GRCh37.p10/hg19Patch10)	/gbdb/hg19Patch10	Grch37.p10	chr1_jh636052:3604121-3614120	1	
 hg19Patch10	Sep. 2012 (GRCh37.p10/hg19Patch10)	/gbdb/hg19Patch10	Grch37.p10	chr1_jh636052:3604121-3614120	0	
>>Scroll to the right to see change from 1 -> 0, make this change before uploading to hgcentralbeta.

Save the change (AND KEEP the changed file dbDbHg19Patch for RR Release) and use the below command to upload the edited file to hgcentralbeta database into table dbDb:

hgwbeta> hgsql -e "load data local infile 'dbDbHg19Patch' into table dbDb" hgcentralbeta

4. Add the necessary lines to hgcentralbeta.genomeClade

hgwdev> hgsql -Ne 'select * from genomeClade where genome like "GRCh37.p#"' hgcentraltest > genomeCladeHg19Patch

Running the above command on dev will pull GRCh37.p10 information for example and create the file genomeCladeHg19Patch (If you were not on hg19, then GRCh37.p# would be different).

hgwbeta> hgsql -e "load data local infile 'genomeCladeHg19Patch' into table genomeClade" hgcentralbeta

Run the above from the same directory on beta to upload the information to hgcentralbeta database into table genomeClade (AND KEEP the temporary file genomeCladeHg19Patch for RR Release).

5. Edit lines in trackDb/human/hg19/trackDb.ra

include altSeqComposite#old.ra alpha,public  <== remove beta, you will later remove public
include altSeqComposite#new.ra alpha,beta  <== add beta to new patch so it shows in beta, you will later add public

6. Ask for push of /gbdb/hg19Patch#/hg19Patch#.2bit and /gbdb/hg19/hg19Patch#/* (which should contain the assembly in .fa file format) from hgwdev to hgnfs1.

Greetings, Pushers.
Please push the following files:
  
/gbdb/mm10/mm10Patch1/*
/gbdb/mm10Patch1/mm10Patch1.2bit
  
from hgwdev --> hgnfs1
Reason: Files accompany mm10 GRC Patch Release track (redmine #8909)

7. Follow Checklist steps for pushing to beta to move track tables to mysqlbeta either individually or creating a list of tables with a text editor and using bigPush.csh (skip already done gbdb push).

sudo mypush $db $table mysqlbeta

or, for a list of tables:

bigPush.csh $db $tableListFile

8. Do a make beta of your database on hgwbeta

hgwbeta> make beta DBS=hg19

Push the track to the RR

IMPORTANT!! do this before pushing any of the other tables or files

1. Ask the admins to rsync the hg19Patch# database to the RR from mysqlbeta. Add a reminder line to update euroNode, as rsyncs are unscripted updates.

 Greetings, Pushers.
 Please rsync the following database, and please include the euroNode: 
  
 mm10Patch1
  
 mysqlbeta --> mysqlrr
 Reason: Accompanies mm10 GRC Patch Release track (redmine #8909)

2. Add the necessary lines to hgcentral.dbDb, using the same dbDbHg19Patch file that you used to load the lines into hgcentralbeta.dbDb

hgwdev> hgsql -h genome-centdb -e "load data local infile 'dbDbHg19Patch' into table dbDb" hgcentral

3. Add the necessary lines to hgcentral.genomeClade, using the same genomeCladeHg19Patch file that you used to load the lines into hgcentralbeta.genomeClade

hgwdev> hgsql -h genome-centdb -e "load data local infile 'genomeCladeHg19Patch' into table genomeClade" hgcentral

4. Change trackDb.ra to include public for the new patch and remove public for the old patch, mentioned in steps above, and on hgwbeta> make public $db NOTE: if you make public before requesting the rsync, you'll need to let admins know you don't want to push created _public files, so best to wait.

5. Do a regular push request of tables and trackDb and friends to release to the RR.