LouiseAlmer (Talk | contribs) |
LouiseAlmer (Talk | contribs) |
||
Line 84: | Line 84: | ||
This scoring system resulted in a large number of the promoters in the final promoter library being compatible with some of the most widely used Type IIs standards, as seen under the design considerations sections on the pages of their respective parts. | This scoring system resulted in a large number of the promoters in the final promoter library being compatible with some of the most widely used Type IIs standards, as seen under the design considerations sections on the pages of their respective parts. | ||
</p> | </p> | ||
− | + | <style type="text/css"> | |
+ | .tg {border-collapse:collapse;border-spacing:0;border:none;} | ||
+ | .tg td{font-family:Arial, sans-serif;font-size:14px;padding:10px 5px;border-style:solid;border-width:0px;overflow:hidden;word-break:normal;} | ||
+ | .tg th{font-family:Arial, sans-serif;font-size:14px;font-weight:normal;padding:10px 5px;border-style:solid;border-width:0px;overflow:hidden;word-break:normal;} | ||
+ | .tg .tg-il2e{font-weight:bold;background-color:#09314f;color:#ffffff;text-align:left;vertical-align:top} | ||
+ | .tg .tg-kftd{background-color:#efefef;text-align:left;vertical-align:top} | ||
+ | .tg .tg-0lax{text-align:left;vertical-align:top} | ||
+ | </style> | ||
+ | <table class="tg"> | ||
+ | <tr> | ||
+ | <th class="tg-il2e">Enzyme/Cloning system</th> | ||
+ | <th class="tg-il2e">Score</th> | ||
+ | <th class="tg-il2e">Justification</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td class="tg-0lax">SwaI enzyme</td> | ||
+ | <td class="tg-0lax">2</td> | ||
+ | <td class="tg-0lax">SwaI domestication can be used for linearisation of vectors for genomic integration. This is something we have considered working on in the near future</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td class="tg-kftd">MoClo</td> | ||
+ | <td class="tg-kftd">1.5</td> | ||
+ | <td class="tg-kftd">MoClo (level 0) is ****</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td class="tg-0lax">Mobius</td> | ||
+ | <td class="tg-0lax">1</td> | ||
+ | <td class="tg-0lax"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td class="tg-kftd">GoldenBraid</td> | ||
+ | <td class="tg-kftd">0.3</td> | ||
+ | <td class="tg-kftd"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td class="tg-0lax">Chi</td> | ||
+ | <td class="tg-0lax">0.2</td> | ||
+ | <td class="tg-0lax"></td> | ||
+ | </tr> | ||
+ | </table> | ||
</div> | </div> | ||
Line 103: | Line 142: | ||
<h2>More text soon</h2> | <h2>More text soon</h2> | ||
− | <p> | + | <p>For comparison, we have analysed a range of 15 different native promoters from <i>Aspergillus</i> spp. genes that our model has based the synthetic promoters upon. For 8 of those native promoters, we found one or more Type IIs sites from either BsaI or SapI, making these native promoters incompatible with the RFC[1000] standard. Domestication of these native promoters is not trivial, as disruption of any transcription factor binding sites when changing the nucleotide sequence of the promoter. By including domestication of the synthetic promoters in the design from the very beginning, we are producing the best performing promoters that are still compatible with the different assembly standards. |
+ | <br><br> | ||
+ | We have also designed the software to produce promoters that are easily synthesizable by <i>de novo</i> synthesis. This was done by creating some design rules with the algorithm that would keep the global GC% content of the promoters within a certain threshold (For the LEAP promoters, the threshold was set at between 25% and 65% GC content), as well as prevent the promoters from having A/T or G/C homopolymers. This threshold can be changed depending on the constraints of the specific situation. | ||
+ | <br><br> | ||
+ | |||
Revision as of 13:33, 21 October 2019
Promoter Design
Promoter design considerations
Our software was designed to produce promoters that would be compatible with a large range of cloning systems and be easy to de novo synthesize.
We have designed the LEAP promoters not just to be compatible with the new iGEM Type IIs RFC[1000] standard, but with a range of other assembly standards as well. The domestication of promoters was done by making a prioritized list of standards to be compatible with. Using this prioritized list, the scoring system seen in table 01 was implemented into the software used to design the promoters.
This scoring system resulted in a large number of the promoters in the final promoter library being compatible with some of the most widely used Type IIs standards, as seen under the design considerations sections on the pages of their respective parts.
Enzyme/Cloning system | Score | Justification |
---|---|---|
SwaI enzyme | 2 | SwaI domestication can be used for linearisation of vectors for genomic integration. This is something we have considered working on in the near future |
MoClo | 1.5 | MoClo (level 0) is **** |
Mobius | 1 | |
GoldenBraid | 0.3 | |
Chi | 0.2 |
More text soon
For comparison, we have analysed a range of 15 different native promoters from Aspergillus spp. genes that our model has based the synthetic promoters upon. For 8 of those native promoters, we found one or more Type IIs sites from either BsaI or SapI, making these native promoters incompatible with the RFC[1000] standard. Domestication of these native promoters is not trivial, as disruption of any transcription factor binding sites when changing the nucleotide sequence of the promoter. By including domestication of the synthetic promoters in the design from the very beginning, we are producing the best performing promoters that are still compatible with the different assembly standards.
We have also designed the software to produce promoters that are easily synthesizable by de novo synthesis. This was done by creating some design rules with the algorithm that would keep the global GC% content of the promoters within a certain threshold (For the LEAP promoters, the threshold was set at between 25% and 65% GC content), as well as prevent the promoters from having A/T or G/C homopolymers. This threshold can be changed depending on the constraints of the specific situation.
Sources here will also come soon