Difference between revisions of "Part:BBa K3040005"

Line 2: Line 2:
 
<partinfo>BBa_K3040013 short</partinfo>
 
<partinfo>BBa_K3040013 short</partinfo>
  
 +
===Description===
 
It is pointed out by the previous iGEM team, UPF CRG Barcelona_2018 iGEM, that the native promoter pFadBA has great leakage and is a weak promoter that isn’t ideal enough for our system. Therefore, to enhance the sensitivity and reduce the leakage of the promoter pFadBA for making it more suitable for our system, we modified the native promoter pFadBA with a mutant in its consensus sequence of -10 and -35 region.
 
It is pointed out by the previous iGEM team, UPF CRG Barcelona_2018 iGEM, that the native promoter pFadBA has great leakage and is a weak promoter that isn’t ideal enough for our system. Therefore, to enhance the sensitivity and reduce the leakage of the promoter pFadBA for making it more suitable for our system, we modified the native promoter pFadBA with a mutant in its consensus sequence of -10 and -35 region.
 
According to the previous research [1], there is improvement in expression for pFadBA with consensus sequence.
 
According to the previous research [1], there is improvement in expression for pFadBA with consensus sequence.

Revision as of 11:29, 20 October 2019

Native pFadD promoter regulating downstream RFP

Description

It is pointed out by the previous iGEM team, UPF CRG Barcelona_2018 iGEM, that the native promoter pFadBA has great leakage and is a weak promoter that isn’t ideal enough for our system. Therefore, to enhance the sensitivity and reduce the leakage of the promoter pFadBA for making it more suitable for our system, we modified the native promoter pFadBA with a mutant in its consensus sequence of -10 and -35 region. According to the previous research [1], there is improvement in expression for pFadBA with consensus sequence.


Sequence and Features


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