Difference between revisions of "Part:BBa K4491009"

Line 12: Line 12:
  
 
{| style="color:black" cellpadding="6" cellspacing="1" border="2" align="right"
 
{| style="color:black" cellpadding="6" cellspacing="1" border="2" align="right"
! colspan="2" style="background:#FFBF00;"|DT54
+
! colspan="2" style="background:#FFBF00;"|MegaT
 
|-
 
|-
 
|'''Function'''
 
|'''Function'''
Line 39: Line 39:
 
|}
 
|}
  
<!-- Add more about the biology of this part here
+
 
 
===Usage and Biology===
 
===Usage and Biology===
  
<!-- -->
+
 
 
<span class='h3bb'>Sequence and Features</span>
 
<span class='h3bb'>Sequence and Features</span>
 
<partinfo>BBa_K4491009 SequenceAndFeatures</partinfo>
 
<partinfo>BBa_K4491009 SequenceAndFeatures</partinfo>
 
 
<!-- Uncomment this to enable Functional Parameter display
 
===Functional Parameters===
 
<partinfo>BBa_K4491009 parameters</partinfo>
 
<!-- -->
 

Revision as of 02:13, 12 October 2022


MegaT

The part MegaT is composed of RBS B0032, mVenus and L3S2P21 terminator. The purpose of the part is to show the relative amount of a CDS. In our project, we hope to use a reporter protein to visualise the amount of feedback species X we have in the circuit. To avoid tagging the reporter protein directly onto X, we have decided to put in an RBS and a reporter (mVenus) right after X to visualise the amount of X. We are implementing JUMP assembly. However, JUMP assembly requires us to clone in 4 parts (usually the promoter, RBS, CDS and terminator) at the same time and does not allow polycistronic assemblies as is the case we have in our main project. Therefore, we need a way to design an operon to allow polycistronic assembly.


MegaT
Function Reporter
Use in Bacteria
Chassis Tested E. coli
Abstraction Hierarchy Part
Related Device
RFC standard RFC10 & RFC12 & RFC21 & RFC23 & RFC25 & RFC1000 compatible
Backbone pJUMP18-Uac
Submitted by Cambridge iGEM 2022


Usage and Biology

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
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]