Difference between revisions of "Part:BBa K3365053"

 
Line 3: Line 3:
 
<partinfo>BBa_K3365053 short</partinfo>
 
<partinfo>BBa_K3365053 short</partinfo>
  
This part is used as a reporter for detecting whether dCas9-ωis on-target. We integrated this part downstream of transcription activating unit. If dCas9-ω is binding to target sequence, this part will be activated to express and the cell then emit red fluorescence, allowing us to know that dCas9-ωis on-target. As we plan to put the potential off-target site downstream of this part, we added a terminator to RFP so that the expression of this part can stop before next off-target reporting site.
+
This part is used as a reporter for detecting whether dCas9-ωis on-target. We integrated this part downstream of transcription activating unit. If dCas9-ω is binding to target sequence, this part will be activated to express and the cell then emit red fluorescence, allowing us to know that dCas9-ωis literally on-target. As we plan to put the potential off-target site downstream of this part, we added a terminator to RFP so that the expression of this part can stop before next off-target reporting site.
  
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here

Latest revision as of 12:56, 27 October 2020


RFP with double terminator

This part is used as a reporter for detecting whether dCas9-ωis on-target. We integrated this part downstream of transcription activating unit. If dCas9-ω is binding to target sequence, this part will be activated to express and the cell then emit red fluorescence, allowing us to know that dCas9-ωis literally on-target. As we plan to put the potential off-target site downstream of this part, we added a terminator to RFP so that the expression of this part can stop before next off-target reporting site.

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 700
    Illegal XhoI site found at 691
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal AgeI site found at 555
    Illegal AgeI site found at 667
  • 1000
    COMPATIBLE WITH RFC[1000]