Jan 01, 2020

Public workspaceSequence Analysis of a Plasmid

DOI
dx.doi.org/10.17504/protocols.io.43ngyme
Sequence Analysis of a Plasmid
  • 1Addgene
Addgene The Nonprofit Plasmid Repository
Open access
DOI: dx.doi.org/10.17504/protocols.io.43ngyme
External link: https://www.addgene.org/protocols/sequence-analysis/
Protocol Citation: Addgene The Nonprofit Plasmid Repository 2020. Sequence Analysis of a Plasmid. protocols.io https://dx.doi.org/10.17504/protocols.io.43ngyme
License: This is an open access protocol distributed under the terms of the Creative Commons Attribution License,  which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited
Protocol status: Working
We use this protocol and it's working
Created: July 02, 2019
Last Modified: August 17, 2020
Protocol Integer ID: 25422
Abstract
This protocol is for sequence analysis of a plasmid. To see the full abstract and additional resources, please visit https://www.addgene.org/protocols/sequence-analysis/.


Sample data

A good sequencing reaction will produce between 300-900 base pairs of useable sequence. You should receive your sequencing results as a trace file (.ab1) which graphically depicts the sequence as a series of colored peaks corresponding to one of the four nucleotide bases. This is an example of a trace file from a high-quality portion of a sequencing reaction:

Sequence near the beginning or end of a sequencing reaction is often unreliable. Although your sequencing results may indicate bases at specific locations, by looking at the trace file, you will see that these base calls are unreliable. This is an example of a trace file from a portion of a sequencing reaction with high background:

Guidelines
Tips and FAQs

  • My sequence doesn’t match Addgene’s sequencing result, what should I do? Check your trace file first; the apparent mismatch/mutation may be the result of a mis-called peak in the trace file. If the mutation is not an artifact, please email help@addgene.org with the sequence, trace file, and primer used.


  • How can I tell if a peak is mis-called? Open the trace file and use the search feature in the program to locate the incorrect sequence. Look at the peaks in the area and make sure they are justifiable peaks. For instance, in the trace file below, you can see that just after base 70 there are multiple peaks in the same location. Looking at the trace file will give you more information than simply looking at the bases provided by your sequencing provider.

  • My sequence has “N”s in it- what does that mean? “N” is the letter used to denote that the position could be any of the 4 bases. Check the trace file and see if you can manually call the correct base at the position. Sometimes an “N” is the result of an erroneous insertion by the sequencing reaction.