Ensembl QA: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
(hgwbeta) |
||
(8 intermediate revisions by 4 users not shown) | |||
Line 6: | Line 6: | ||
*All Ensembl builds are documented in the single file: | *All Ensembl builds are documented in the single file: | ||
src/hg/makeDb/doc/makeEnsembl.txt | src/hg/makeDb/doc/makeEnsembl.txt | ||
*If it is the first assembly, however, it will rather be documented in the assembly.txt make document. | |||
/kent/src/hg/makeDb/doc/nameAssembly.txt | |||
*You can find all ensembl gene builds in: | *You can find all ensembl gene builds in: | ||
Line 13: | Line 15: | ||
*To get the links to go to the correct place at Ensembl, you will have to check for the appropriate rows in trackVersion table in hgFixed database | *To get the links to go to the correct place at Ensembl, you will have to check for the appropriate rows in trackVersion table in hgFixed database | ||
**The latest entry in the hgFixed.trackVersion table should have "current" in the dateReference field and the previous entry needs to have the dateReference field updated to whatever month the last Ensembl release was dated. | **The latest entry in the hgFixed.trackVersion table should have "current" in the dateReference field and the previous entry needs to have the dateReference field updated to whatever month the last Ensembl release was dated. | ||
**Before you push the hgFixed.trackVersion table, check (using the compareWholeTable.csh script) that you aren't pushing changes that aren't ready to go out yet. For instance, if there are changes to an unrelated track | **Before you push the hgFixed.trackVersion table '''(2017 NOTE - likely QA should NOT push the entire table as there may be rows in this table that are in development and should not yet be on the rr. Check with an engineer if you have a row that needs to get to the rr)''', check (using the compareWholeTable.csh script) that you aren't pushing changes that aren't ready to go out yet. For instance, if there are changes to an unrelated track, you will need to check with the person who made the changes to see if it is okay to push the changes. If it is not, the timing of the push should be coordinated or the trackVersion table should be edited on hgwbeta to exclude the changes that are not ready to go out. | ||
** Hiram has said to not worry about pushing entries for the COSMIC track in the hgFixed.trackVersion table. The COSMIC track is otto updated on the RR, but the version number updates in hgFixed.trackVersion table aren't automatically pushed to the RR. Hiram said he expects these COSMIC version number updates to be pushed along with the Ensembl Genes updates. (From Hiram's comment in [http://redmine.soe.ucsc.edu/issues/11675#note-74 Redmine #11675 note-74]) | |||
* ''' | |||
* '''Note: You also need to update the [[blastTabs]] if the zebrafish assembly used in hgGene got new Ensembl Genes. Talk to Brooke or Mary if this is case.''' | |||
*Note: See the issue from [http://redmine.soe.ucsc.edu/issues/20393 this RM MLQ] regarding a missing joiner rule. The ensemblToGeneName table should be linked to ensGene. | |||
[[Category:Browser QA tracks]] | [[Category:Browser QA tracks]] | ||
[[Category:Browser QA]] | [[Category:Browser QA]] | ||
[[Category:Browser QA Ensembl]] | [[Category:Browser QA Ensembl]] |
Latest revision as of 23:56, 4 June 2019
There are periodic updates to all Ensembl Genes tracks in all dbs. Here is a list of things to do in addition to the regular QA you would do normally for a track:
- Run qaEnsGenes.csh
- Run it before you push to beta, as it compares dev to beta. You'll lose that comparison if you push too soon.
- All Ensembl builds are documented in the single file:
src/hg/makeDb/doc/makeEnsembl.txt
- If it is the first assembly, however, it will rather be documented in the assembly.txt make document.
/kent/src/hg/makeDb/doc/nameAssembly.txt
- You can find all ensembl gene builds in:
/hive/data/genomes/<db>/bed/ensGene.NN/
- where NN is the ensembl version number.
- To get the links to go to the correct place at Ensembl, you will have to check for the appropriate rows in trackVersion table in hgFixed database
- The latest entry in the hgFixed.trackVersion table should have "current" in the dateReference field and the previous entry needs to have the dateReference field updated to whatever month the last Ensembl release was dated.
- Before you push the hgFixed.trackVersion table (2017 NOTE - likely QA should NOT push the entire table as there may be rows in this table that are in development and should not yet be on the rr. Check with an engineer if you have a row that needs to get to the rr), check (using the compareWholeTable.csh script) that you aren't pushing changes that aren't ready to go out yet. For instance, if there are changes to an unrelated track, you will need to check with the person who made the changes to see if it is okay to push the changes. If it is not, the timing of the push should be coordinated or the trackVersion table should be edited on hgwbeta to exclude the changes that are not ready to go out.
- Hiram has said to not worry about pushing entries for the COSMIC track in the hgFixed.trackVersion table. The COSMIC track is otto updated on the RR, but the version number updates in hgFixed.trackVersion table aren't automatically pushed to the RR. Hiram said he expects these COSMIC version number updates to be pushed along with the Ensembl Genes updates. (From Hiram's comment in Redmine #11675 note-74)
- Note: You also need to update the blastTabs if the zebrafish assembly used in hgGene got new Ensembl Genes. Talk to Brooke or Mary if this is case.
- Note: See the issue from this RM MLQ regarding a missing joiner rule. The ensemblToGeneName table should be linked to ensGene.