Assembly QA Part 1 DEV Steps

From Genecats
Revision as of 16:47, 2 November 2016 by Cath (talk | contribs)
Jump to navigationJump to search

Welcome to the Assembly QA Part 1: DEV Steps page! 😎

Home: Assembly_Release_QA_Steps
  1. Assembly QA Part 1: DEV Steps
  2. Assembly QA Part 2: BETA Steps
  3. Assembly QA Part 3: RR Steps
  4. 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.

Dev 1.0. Set up a directory in hive

You will need a place to put output during the QA/Release process.

Dev 1.1. Make a directory in your hive:
mkdir /hive/users/userName/assemblies/assemblyName  e.g.:  mkdir /hive/users/cath/assemblies/manPen1
Dev 1.2. Optional: Create an alias to your new dir

Dev 2.0: Claim it in Redmine & PushQ

  1. Find your assembly in the associated Assembly Redmine ticket.
    1. If there is no Redmine for your assembly, you should create one, assign to yourself, and add the engineer as a watcher.
    2. If one exists, read carefully, assign it to yourself. Make sure the engineer is a watcher.
    3. For any issues found in the QA process, report in the Redmine ticket.
  2. Find your assembly in the PushQ
    1. Click on the link in the "Queue ID" column
    2. Click the "lock" button at the top of the page to "unlock" the fields for editing.
    3. Add your name to the "Reviewer" column.
    4. Press the "Submit" button to save your edits.


Dev 3.0. Check chrom sizes

Dev 3.1. List step 1 here
Dev 3.2. List step 2 here

CHRIS V TO EDIT

Ignore this if assembly is the first for a species.
For a new assembly version, compare the chrom sizes from the last assembly to this new assembly version. You are not checking annotations on the reference sequence, you are just checking the number of base pairs per chrom/contig, and making sure that nothing has changed drastically (i.e., millions of base pairs different). Also take a look for general differences, such as chrom labels or number of chrom/contigs.
Output chrom sizes into two files, sort each file by using the command below
Compare the sorted files

Add note about viewing http://genome.ucsc.edu/cgi-bin/hgGateway and clicking on "View Sequences" button - bring up 2 windows side by side 

hgwdev > hgsql -Ne "select chrom, size from chromInfo" $oldDb > oldChromSizes assemblyName (e.g., "panTro4")
hgwdev > hgsql -Ne "select chrom, size from chromInfo" $newDb > newChromSizes assemblyName (e.g., "panTro5")
hgwdev > sdiff -s oldChromSizes newChromSizes

=Dev 4.0. Are associated alignment files (listed in the pushQ) to valid assemblies on the RR?

Dev 4.1. List step 1 here
Dev 4.2. List step 2 here

chain/net/liftOver CATH TO EDIT

Dev.3: Check "minimal browser" criteria: got required tracks?

Visit this page for the required tracks to be considered a minimal browser.



Add this later as a QA step

Assemblies/sequences, from various organizations, are submitted to the mother ship GenBank.
Those assemblies might be included in RefSeq if criteria are met.


The QA check should be to go out to NCBI and double check that the accessionID is correct


RefSeq assemblies:
use accession ID: GCF_000002315.4 (e.g., galGal5)
are delivered with chrMt (if they exisit)
are delivered with NCBI gene predictions
Genbank assemblies:
use accession ID: GCA_000001305.2
delivered without a chrMt.
do not have gene predictions.


For the UCSC Genome Browser, it is preferable to use RefSeq assemblies (in part due to 'more data'). This is a "learn as we go" direction; historically GeneBank was preferred.

Helpful article: Nature, 2012 A beginner's guide to eukaryotic genome annotation








.

.


🔵 Done with DEV steps? Let's go to Assembly QA Part 2: BETA Steps

Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=Assembly_QA_Part_1_DEV_Steps&oldid=3087"