Composite

Part:BBa_K3365014

Designed by: JUNYAN LI   Group: iGEM20_SJTU-BioX-Shanghai   (2020-10-23)
Revision as of 14:11, 27 October 2020 by Gyaxxxxxx (Talk | contribs)


pBAD/araC upstream of RFP with inhibition unit containing target

To facilitate measurements, we use the RFP as a reporter protein, which can be exchange to other reporters according to the users’ needs. The RFP gene sequence (BBa_K3365052) is located directly downstream of BBa_K3365006 (Target sequence downstream of pBAD/araC) followed by BBa_B0015 (rrnBT1-T7TE). The transcription of the RFP gene is under the control of the inducible pBAD/araC promoter designed to carry PAM and target sequence downstream of pBAD. In our part, the “target” is the target sequence for PDCD1 CRISPR gene editing in one clinical trial, which can be identified and bound by the complex of dCas9 and corresponding sgRNA.


AraC upstream of RFP with inhibition unit containing target.png
Figure.1 Gene circuit


Usage and Biology

This part is used to expression of RFP protein regulated by the signal of arabinose and the on-target or not of dCas9. The pBAD is regulated by the AraC protein, which is both a positive and a negative regulator. The binding of dCas9 to any position within the region between the promotor and RBS might prevent transcription. Therefore, the uninduced transcriptional level of RFP is very low. In the presence of arabinose, transcription from the pBAD promoter is turned on and there will be a relatively strong fluorescence expression. In the presence of both arabinose and the complex of dCas9 and sgRNA, the complex might bind to the target sequence and the transcription is partially inhibited because of the block of RNAP. So, a relatively weak fluorescence expression of bacteria indicates a dCas9 with higher on-target rate that effectively inhibits the expression of reporter gene.

Results

The inducible pBAD/araC promoter (BBa_K3365013) is amplified with the primer F1/R1 to add restriction cutting sites, target sequence and part of the RBS sequence (BBa_K3365002). The RFP with double terminator is amplified with the primer F2/R2 to add restriction cutting sites and part of the RBS sequence (BBa_K3365002). The above PCR products are ligated through overlap PCR with the primer F1/R2 to get the fragment with suitable restriction sites and the product can be ligated into its backbone pUC57 by enzymic digestion and connection. The eletrophoretic profile of the overlap PCR (F1/R2) and colony PCR (M13 fwd/ M13 rev) product and the sequencing result reveal the successful construction of the fragment and the plasmid, named pIn-RTr.

F1: 5’-CGAGCTCTTATGACAACTTGACGGCTACATCATTCAC-3’

R1: 5’-TTCTTAAAGGCAGTTGTGTGACACGGAAGCGGATGGAGAAACAGTAGAGAGTTGCG-3’

F2: 5’-TTCCGTGTCACACAACTGCCTTTAAGAAGGAGATATACATATGGCGAGTAGCGAAGACG-3’

R2: 5’-GGAATTCCCGCCCTAGGTATAAACGCAGAAAG-3’

M13 fwd: 5’-GTAAAACGACGGCCAGT-3’

M13 rev: 5’-GTCATAGCTGTTTCCTG-3’


Eletrophoretic profile of the overlap PCR result.png
Figure.2 Eletrophoretic profile of the overlap PCR result


Eletrophoretic profile of Colony PCR product.png
Figure.3 Eletrophoretic profile of Colony PCR product

To verify the inhibition effect of pdCas9 on pIn-RTr, we set up six culturing system (as shown in the table below) and used microplate spectrophotometer to examine fluorescence intensity. L-arabinose was added to induced the expression of RFP.

Table 014.png

The results are shown below, from which we could see 64.39 times of fluorescence/OD600 difference between transform group (without the expression of dCas9) and co-transform group (with the expression of dCas9), indicating our transcription inhibition system did work.


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 1913
    Illegal XhoI site found at 1922
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal AgeI site found at 979
    Illegal AgeI site found at 1789
    Illegal AgeI site found at 1901
  • 1000
    INCOMPATIBLE WITH RFC[1000]
    Illegal SapI site found at 961


[edit]
Categories
Parameters
None