Difference between revisions of "Part:BBa K1045011"

 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
<partinfo>BBa_K1045011 short</partinfo>
+
<partinfo>BBa_K1045011 short</partinfo><br/ >
[[Part:BBa_K1045011|BBa_K1045011]] encodes for a weak promoter based on [[Part:BBa_J23117|BBa_J23117]] promoter from the well characterized Anderson promoter collection. Yet, the promoter in [[Part:BBa_K1045011|BBa_K1045011]] is inverted, i.e. the prefix is located at position -1. Additionally, [[Part:BBa_K1045011|BBa_K1045011]] harbors extra bases in front of the promoter sequence. These extra bases might allow the cloning of a vector from which two genes can be expressed into diverging direction: You could place [[Part:BBa_K1045011|BBa_K1045011]] in front of other promoters oriented in the usual way. The extra bases were added to prevent that the binding of the RNA polymerase to the usual promoter influences the binding of the RNA polymerase to the inverse promoter in [[Part:BBa_K1045011|BBa_K1045011]]. (for an example see [[Part:BBa_K1045017|BBa_K1045017]], a screening system for compounds similar to c-di-AMP).
+
[[Part:BBa_K1045011|BBa_K1045011]] encodes for a weak promoter based on [[Part:BBa_J23117|BBa_J23117]] promoter from the well characterized Anderson promoter collection. Yet, the promoter in [[Part:BBa_K1045011|BBa_K1045011]] is inverted. We improved the inverted promoter [[Part:BBa_J23117|BBa_J23117]] by adding additional base pairs upstream of the inverted promoter region. These additional base pairs will allow cloning of this promoter directly in front of another promoter oriented in the opposite direction. This way, a vector with two different expression units oriented in diverging directions can be created. The extra bases might prevent that the binding of the RNA polymerase to the usual promoter influences the binding of the RNA polymerase to the inverse promoter in [[Part:BBa_K1045011|BBa_K1045011]] (for an example see [[Part:BBa_K1045017|BBa_K1045017]], a detection system for c-di-AMP).
 +
 
 +
'''Why this part is improved: '''
 +
 
 +
1. [[Part:BBa_J23117|BBa_J23117]] was inverted (pre- and suffix switched).
 +
 
 +
2. [[Part:BBa_K1045011|BBa_K1045011]] has additional bases in front of its promoter region. These bases allow to clone this promoter in front of a promoter oriented in the other direction.
 +
 
 +
3. Since the sequence is just inverted between the pre- and suffix, this promoter can be used with other inverted biobricks (for example: [[Part:BBa_K1045001|BBa_K1045001]]).  
  
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here

Latest revision as of 10:59, 27 October 2013

Promoter reverse
BBa_K1045011 encodes for a weak promoter based on BBa_J23117 promoter from the well characterized Anderson promoter collection. Yet, the promoter in BBa_K1045011 is inverted. We improved the inverted promoter BBa_J23117 by adding additional base pairs upstream of the inverted promoter region. These additional base pairs will allow cloning of this promoter directly in front of another promoter oriented in the opposite direction. This way, a vector with two different expression units oriented in diverging directions can be created. The extra bases might prevent that the binding of the RNA polymerase to the usual promoter influences the binding of the RNA polymerase to the inverse promoter in BBa_K1045011 (for an example see BBa_K1045017, a detection system for c-di-AMP).

Why this part is improved:

1. BBa_J23117 was inverted (pre- and suffix switched).

2. BBa_K1045011 has additional bases in front of its promoter region. These bases allow to clone this promoter in front of a promoter oriented in the other direction.

3. Since the sequence is just inverted between the pre- and suffix, this promoter can be used with other inverted biobricks (for example: BBa_K1045001).

Sequence and Features


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