Difference between revisions of "Part:BBa K792012"

Line 18: Line 18:
  
  
{| style="width:100%" rowspan="2"
+
{| style="width:100%"
 
|-
 
|-
| style="background: red" rowspan="2" | '''Important note: '''
+
| style="background: red" | '''Important note: '''
 
| style="background: #D8D8D8" rowspan="2" | this part has been submitted to the registry using a direct synthesis DNA sample, so it does not contain scars from ''BB assembly standard''.
 
| style="background: #D8D8D8" rowspan="2" | this part has been submitted to the registry using a direct synthesis DNA sample, so it does not contain scars from ''BB assembly standard''.
 
|}
 
|}
  
{| style="width:100%" rowspan="2"
+
{| style="width:100%"  
 
|-
 
|-
 
| style="background: yellow" rowspan="2" | '''See also: '''
 
| style="background: yellow" rowspan="2" | '''See also: '''
| style="background: #D8D8D8" rowspan="2" | * Another similar '''''Trp-export and enhanced import''''' composite device [[Part:BBa_K792010]].
+
| style="background: #D8D8D8" | Another '''''Trp-export and enhanced import''''' composite device [[Part:BBa_K792010]].
 +
|-
 +
| style="background: #D8D8D8" | Similar design '''''His-export and enhanced import''''' composite device [[Part:BBa_K792011]].
 
|}
 
|}
  
{| style="width:100%; background: #CEE3F6" rowspan="2"
+
{| style="width:100%; background: #CEE3F6"
 
|-  
 
|-  
 
|The device was originally designed and built to be used in [http://2012.igem.org/Team:Buenos_Aires iGEM BsAs 2012 project] to implement a ''cross-feeding'' regulatory system between two different yeast strains with specific auxotrophy. [http://2012.igem.org/Team:Buenos_Aires Visit our wiki] to read details about the designing process and implementation details. Also feel free to contact us for any question regarding this part.
 
|The device was originally designed and built to be used in [http://2012.igem.org/Team:Buenos_Aires iGEM BsAs 2012 project] to implement a ''cross-feeding'' regulatory system between two different yeast strains with specific auxotrophy. [http://2012.igem.org/Team:Buenos_Aires Visit our wiki] to read details about the designing process and implementation details. Also feel free to contact us for any question regarding this part.

Revision as of 16:03, 25 September 2012

Yeast exportable Trp-rich peptide w/enhanced import (2)

This composite device produces and exports a Tryptophan rich peptide, that is import enhanced (thanks to a trojan peptide). This device is intended to be used with Yeast chassis, so it is composed by subparts designed also to be use in yeast.


The high level structure of the device is:

  • BamHI restriction site (introduced by device designers just to use this biobrick with an specific yeast vector - this is not essential for the device purpose)
  • Kozak consensus sequence for initiation of translation
  • Signal peptide that targets the product of the gene for secretion
  • Trojan peptide, to increase internalization in target cell (Polyarginine)
  • Payload: this is the exported Tryptophan rich domain of the protein (a custom designed peptide that we called PolyWb)


The device's sequence has inherited HindIII restriction site from the parts it's made of.


Important note: this part has been submitted to the registry using a direct synthesis DNA sample, so it does not contain scars from BB assembly standard.
See also: Another Trp-export and enhanced import composite device Part:BBa_K792010.
Similar design His-export and enhanced import composite device Part:BBa_K792011.
The device was originally designed and built to be used in [http://2012.igem.org/Team:Buenos_Aires iGEM BsAs 2012 project] to implement a cross-feeding regulatory system between two different yeast strains with specific auxotrophy. [http://2012.igem.org/Team:Buenos_Aires Visit our wiki] to read details about the designing process and implementation details. Also feel free to contact us for any question regarding this part. Igem.bsas.png


Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BamHI site found at 1
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]