Assembly Release QA Steps: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
# '''New version for exisiting species:''' Assembly version for a species that already exists as a browser. | # '''New version for exisiting species:''' Assembly version for a species that already exists as a browser. | ||
When a new or updated assembly is ready to QA, the QA team should perform the following steps, outlined in | When a new or updated assembly is ready to QA, the QA team should perform the following steps, outlined in this guide. | ||
#Assembly QA Part 1: DEV Steps | {| class=wikitable width=415 align=right | ||
#Assembly QA Part 2: BETA Steps | | | ||
#Assembly QA Part 3: RR Steps | :Home: [[Assembly_Release_QA_Steps]] | ||
#Assembly QA Part 4: Post Release Steps | #[[Assembly QA Part 1: DEV Steps]] | ||
#[[Assembly QA Part 2: BETA Steps]] | |||
#[[Assembly QA Part 3: RR Steps]] | |||
#[[Assembly QA Part 4: Post Release Steps]] | |||
|} | |||
Revision as of 22:36, 19 September 2016
Welcome to the Assembly Release: QA Steps page! 😀
Page created Fall. 2016 by Cath , Jairo, and ChrisV.
|
For the UCSC Genome Browser QA Team, there are two types of genome assemblies:
- New species: Assembly for a species that is not already exisiting as a browser.
- New version for exisiting species: Assembly version for a species that already exists as a browser.
When a new or updated assembly is ready to QA, the QA team should perform the following steps, outlined in this guide.
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps