Week 27th June - 3rd July
Week 4th - 10th July
Week 11th - 17th July
Week 18th -24th July
This week we designed the strategy for cloning all the proteins that we want to test in the pCOLA vector, and at the same time make everything compatible with the phytobrick format.
The table of proteins that we are working on is the following:
How to clone using the pDUET – Golden Gate adapted plasmids
The first thing that you have to do it to codon optimise your sequence for E. coli. For that we used the IDT’s Codon Optimisation Tool (https://eu.idtdna.com/CodonOpt).
After doing the codon optimisation we checked if our sequence had any recognition site for the BpiI, BsaI and BsmBI. Those enzymes are widely used in the Phytobricks and there can therefore be no recognition size outside of the purposely designed (https://2016.igem.org/Resources/Plant_Synthetic_Biology/PhytoBricks). Correct the recognition sites using a codon usage table.
Attach the following to your optimised sequence:
To the 5’- attach a BsaI recognition site that will allow you to fit the part in the Phytobrick. The sequence must be as follows, to be able to fit in the already defined iGEM parts:
In order to be able to get a singe primer for amplifying all the different CDS after synthesis, we need to add a tail before the BsaI site that will allow us to create a universal primer.
We call this structure with the NNNNN + the BsaI site 5’ the extremity A (this will make sense later on, we promise).
When adding the extremity A to the sequence take into account that the extremity ends with a start codon, therefore eliminate the one from your CDS to get it in frame.
To the 3’- attach the His-tag and a BsaI recognition site. This will allow us to purify the protein and also fit the part in the Phytobrick.
Once again, take into account the fact that the sequence must be as follows to fit in the Phytobrick. If not designed like this the BsaI recognition site will continue to exist in our sequence after cloning and that could be a problem.
Before the BsaI 3’ recognition site, add a His-tag. Do not forget removing the STOP codon from the CDS to allow for fusion with the His-tag. This two together will create what we call the extremity C (once again, will make sense!).
The extremities A and C will permit us to clone the entire CDS + His-tag in our plasmid. Nonetheless, we might not want to clone the His-tag in the iGEM Phytobricks. In order to clone the CDS without the his-tag we will design some specific primers.
The common primers FW and RV will allow us to amplify all our CDS with the His-tag and directly clone them in our desired vector. They will also allow cloning the entire part in the Phytobricks.
The common primer FW and the CDS-specific RV will allow to clone only the CDS without the His-tag into the Phytobricks, and will also allow to attach a CBD to our proteins.
Example of primers (ignore the sequence of BsaI that has been added to the CDS sequence, it is only there because it is easier to design the primers like that in the software, they will not exist in the synthesised DNA, they will be present as TAILS. Take the STOP codons always into account!
Until here, a short resume of what has to have been done:
- Codon optimise
- Check for restriction enzymes and correct (BpiI, BsaI and BsmBI)
- Attach the 5’ extremity (A) and delete ATG
- Attach the 3’ extremity (C) and delete the STOP codon
- Design primers that are specific
Next, we need to design our CDB and attach to it the BsaI sites to clone it in the vector, Phytobricks and attach it to our CDS.
To the 5’- attach a BsaI recognition site that will allow you to fit the part in the Phytobrick with our gene in frame. The sequence must be as follows, to be able to fit in the already defined iGEM parts.
T
To the 3’- attach the His-tag and a BsaI recognition site as before. This will allow us to purify the protein and also fit the part in the Phytobrick.
Ordering of primers for golden gate and Gibson assembly
We also ordered the following primers for carrying out our strategy:
Name Sequence Scale Purification
FNS_1 GTAGTAGCTGCTATATGGTCTCAA 24 Standard desalting
FNS_2 CGATGGTCTCAAAGCTCAGT 20 Standard desalting
FNS_4 CGATGGTCTCAGGCTGAGGCTGAAGCACGGCGA 33 Standard desalting
FNS_6 CGATGGTCTCAGGCTGAGGGAGAATTCAAGAAGTTCTTAAACCA 44 Standard desalting
FNS_8 CGATGGTCTCAGGCTGACTGAATAATATCCATCGGGCG 38 Standard desalting
FNS_10 CGATGGTCTCAGGCTGAAGAGTCAAATTCAATTTTTACACCACCG 45 Standard desalting
FNS_12 CGATGGTCTCAGGCTGACTGACACAGACCGTCAATCCA 38 Standard desalting
FNS_14 CGATGGTCTCAGGCTGAAGTCAAAACAGTCATAAAACGTTCATTC 45 Standard desalting
FNS_15 GCTGACGACCGAGTCTCCGCA 21 Standard desalting
FNS_16 TACCGAAGATAGCTCATGTTATATCCCGC 29 Standard desalting
FNS_17 TTGCTCAGCGGTGGCAGCAG 20 Standard desalting
FNS_18 ATCGTATTGTACACGGCCGCAT 22 Standard desalting
FNS_19 TCGGAATCGCAGACCGATACCAGGA 25 Standard desalting
FNS_20 ATTTATGCCTCTTCCGACCATCAAGC 26 Standard desalting
FNS_21 ATGTTCGTCAGGGGGGCG 18 Standard desalting
FNS_22 TTGGGGAACTGCTTAACCTGGTAACT 26 Standard desalting
FNS_23 GTGAAAAGAAAAACCACCCTGGCG 24 Standard desalting
FNS_24 GTAATTCAGCTCCGCCATCGCC 22 Standard desalting
FNS_25 GACGCGCCGAGACAGAACTT 20 Standard desalting
FNS_26 CATGTTAGTCATGCCCCGCG 20 Standard desalting
Week 25th -31th July