Assembly Release QA Steps

Welcome to the Assembly Release: QA Guide 😀

Home: Assembly_Release_QA_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

Page created Fall. 2016 by Cath, Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.

When a developer is ready for a new assembly to be released, the QA team (usually an individual of) will QA and release the assembly. This wiki section exists as a guide for the assembly QA and release process.

CHANGE HAPPENS.
As time goes on, please update this section as things change!

For the UCSC Genome Browser QA Team, there are two types of genome assemblies:

1. New species: Assembly for a species that is not already exisiting as a browser.
2. 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.

While genbank and refseq assemblies can be claimed to be 'identical' that just means they use the same sequence. The names for everything are different, aptMan1 has contig names of the format NW_013982187v1 which is a RefSeq identifier. galGal5 is a RefSeq assembly GCF_000002315.4 It does have the chrM/NC_001323.1 RefSeq assemblies often are delivered with chrMt, although not always (sometimes none exists). Genbank assemblies are almost always delivered *without* a chrMt RefSeq assemblies are delivered with NCBI gene predictions, Genbank assemblies do *not* have gene predictions. Hence, whenever possible it is preferable to use RefSeq assemblies since they have that extra stuff. This is a recent innovation at UCSC, we (==I) always used to use GenBank assemblies because I was under the mistaken impression that somehow that was the gold standard 'official' assembly. Not true at all. Live and learn, however slowly.

🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps