Difference between revisions of "Help:BioBrick Prefix and Suffix"

(→‎BioBrick Suffix)
(→‎BioBrick Suffix)
Line 29: Line 29:
  
 
==BioBrick Suffix==
 
==BioBrick Suffix==
−
Similarly, the standard BioBrick prefix depends on the part that preceeds it (<FONT COLOR="#BABABA">part in grey</FONT>, <FONT COLOR="#CC00FF">PstI</FONT>,<FONT COLOR="#FF5333"> SpeI</FONT>).
+
Similarly, the standard BioBrick prefix depends on the part that preceeds it (<FONT COLOR="#BABABA">part in grey</FONT>, <FONT COLOR="#CC00FF">PstI</FONT>,<FONT COLOR="#FF5333"> SpeI</FONT>). For help locating the transcription initiation site in your promoter part, try [http://www.fruitfly.org/seq_tools/promoter.html promoter prediction.]
 
{|width='85%' style='border:1px solid gray; margin-left:2em'
 
{|width='85%' style='border:1px solid gray; margin-left:2em'
 
|width='45%'|
 
|width='45%'|
 
The standard BioBrick suffix for most parts:
 
The standard BioBrick suffix for most parts:
 
|width='55% 'valign='top'|
 
|width='55% 'valign='top'|
−
'''<span style='font-family:monospace;font-size:175%;padding-left:1em'><FONT COLOR="#BABABA">...ac</FONT>t<FONT COLOR="#FF5333">actagt</FONT>agcggccg<FONT COLOR="#CC00FF">ctgcag</FONT></span>'''
+
'''<span style='font-family:monospace;font-size:175%;padding-left:1em'><FONT COLOR="#BABABA">...AC</FONT>t<FONT COLOR="#FF5333">actagt</FONT>agcggccg<FONT COLOR="#CC00FF">ctgcag</FONT></span>'''
 +
|-
 +
|width='45%'|
 +
For promoter parts, the transcriptional initiation site (in green) is placed 2 bp upstream of the SpeI site:
 +
|width='55%'|
 +
'''<span style='font-family:monospace;font-size:175%;padding-left:1em'><FONT COLOR="#BABABA">...CA</FONT><FONT COLOR="#00FF7F">c</FONT>t<FONT COLOR="#FF5333">actagt</FONT>agcggccg<FONT COLOR="#CC00FF">ctgcag</FONT></span>'''
 
|}
 
|}
  

Revision as of 16:42, 22 August 2006

Partinps.png

For more information about how the prefix and suffix were determined and the special case of coding regions, see Assembly:RBS-CDS_issues.

Part Sequence

The DNA sequence for parts in the Registry starts with the first base of the part itself and ends with its last base. For example, a protein coding sequence is like this "ATG----------TAATAA". The sequence in the Registry does not include any bases of the BioBrick Prefix or Suffix.

Plasmids (see below) and primers or tags that explicitly specify prefix or suffix bases are exceptions to this rule.


BioBrick Prefix

The standard BioBrick prefix depends on the part that follows it (part in grey, EcoRI, XbaI).

If the following part is a coding sequence or any other part that starts "ATG", the BioBrick prefix is:

gaattcgcggccgcttctagATG...

Otherwise, the BioBrick prefix is:

gaattcgcggccgcttctagagCA...

BioBrick Suffix

Similarly, the standard BioBrick prefix depends on the part that preceeds it (part in grey, PstI, SpeI). For help locating the transcription initiation site in your promoter part, try [http://www.fruitfly.org/seq_tools/promoter.html promoter prediction.]

The standard BioBrick suffix for most parts:

...ACtactagtagcggccgctgcag

For promoter parts, the transcriptional initiation site (in green) is placed 2 bp upstream of the SpeI site:

...CActactagtagcggccgctgcag

BioBrick Scar

When BioBricks with these prefix and suffix sequencees are assembled, there is a "scar" between these parts.

If the second part starts "AT", the scar is:

tactag

Otherwise, the scar is:

tactagag


Plasmid Sequences

Since plasmids are circular pieces of DNA, the specification of the "first" base is arbitrary. Furthermore, plasmids often hold BioBrick parts, leading to a question of how the plasmid itself is defined.

In the Registry, we define the plasmid as starting with the first base of the suffix and ending with the last base of the BioBrick prefix. That definition keeps the plasmid continuous and breaks it where parts will be inserted.