Assembly Release QA Steps: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFBF1; color: #000;"> | <div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFBF1; color: #000;"> | ||
== Welcome to the '''Assembly Release: QA | == Welcome to the '''Assembly Release: QA Guide''' page! 😀 == | ||
{| class=wikitable width=415 align=right | {| class=wikitable width=415 align=right | ||
| | | | ||
:Home: [[Assembly_Release_QA_Guide]] | :Home: [[Assembly_Release_QA_Guide: Test]] | ||
#[[Assembly QA Part 1: DEV Steps]] | #[[Assembly QA Part 1: DEV Steps]] | ||
#[[Assembly QA Part 2: BETA Steps]] | #[[Assembly QA Part 2: BETA Steps]] | ||
Revision as of 22:42, 19 September 2016
Welcome to the Assembly Release: QA Guide page! 😀
Page created Fall. 2016 by Cath, Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.
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
