Difference between revisions of "Part:BBa K145210"

 
 
Line 1: Line 1:
 
 
__NOTOC__
 
__NOTOC__
 
<partinfo>BBa_K145210 short</partinfo>
 
<partinfo>BBa_K145210 short</partinfo>
  
MEMORY This device should start in the stable OFF state with P22 c2 (LVA+) being actively produced and repressing the synthesis of 434 cI (LVA+). A switch to the ON state can then be made by increasing the PoPs from the OmpF promoter which guides transcription of the 434 cI (LVA-) coding region. This pulse of 434 cI repressor (if long enough) can effectively shut down P22 c2 transcription and make the device switch to the permanent ON state in which cI 434 is continuously produced, even if transcription from the OmpF promoter slows down again.
+
MEMORY This device should start in the stable OFF state with P22 c2 (LVA+) being actively produced and repressing the synthesis of 434 cI (LVA+). A switch to the ON state can then be made by increasing the PoPs from the TetR promoter which guides transcription of the 434 cI (LVA-) coding region. This pulse of 434 cI repressor (if long enough) can effectively shut down P22 c2 transcription and make the device switch to the permanent ON state in which cI 434 is continuously produced, even if transcription from the TetR promoter slows down again.
  
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here

Latest revision as of 11:18, 25 August 2008

MEMORY

MEMORY This device should start in the stable OFF state with P22 c2 (LVA+) being actively produced and repressing the synthesis of 434 cI (LVA+). A switch to the ON state can then be made by increasing the PoPs from the TetR promoter which guides transcription of the 434 cI (LVA-) coding region. This pulse of 434 cI repressor (if long enough) can effectively shut down P22 c2 transcription and make the device switch to the permanent ON state in which cI 434 is continuously produced, even if transcription from the TetR promoter slows down again.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BglII site found at 1630
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    INCOMPATIBLE WITH RFC[1000]
    Illegal SapI site found at 2018