(→General part design using RFC[10] & RFC[25]) |
(→General part design using RFC[10] & RFC[25]) |
||
Line 7: | Line 7: | ||
=General part design using RFC[10] & RFC[25]= | =General part design using RFC[10] & RFC[25]= | ||
− | All BioBricks were assembled according to the RFC[10] or RFC[25] standard. For all basic parts the RFC[10] standard was used. Because the RFC[10] scar | + | All of our BioBricks were assembled according to the RFC[10] or RFC[25] standard. For all basic parts the RFC[10] standard was used. Because the RFC[10] scar codes for a stop codon this assembly standard does not allow the generation of fusion proteins. Therefore all fusion proteins were assembled by RFC[25] standard. Thus all RFC[10] and RFC[25] digestion sites were eliminated from the BioBricks either directly when planing the genesynthesis or by quick-change PCR. |
+ | |||
+ | --!Only one of the BioBricks which we supply for the community could not be freed from all digestion sites, because one part of the BioBrick!-- | ||
=Featured parts= | =Featured parts= |
Revision as of 21:57, 12 October 2016
biotINK project overview
General part design using RFC[10] & RFC[25]
All of our BioBricks were assembled according to the RFC[10] or RFC[25] standard. For all basic parts the RFC[10] standard was used. Because the RFC[10] scar codes for a stop codon this assembly standard does not allow the generation of fusion proteins. Therefore all fusion proteins were assembled by RFC[25] standard. Thus all RFC[10] and RFC[25] digestion sites were eliminated from the BioBricks either directly when planing the genesynthesis or by quick-change PCR.
--!Only one of the BioBricks which we supply for the community could not be freed from all digestion sites, because one part of the BioBrick!--
Featured parts
Parts we improved
- Kill-switch from Freiburg/Slovenia
- Improved the characterization of TetR construct
- Improved the chracterization of CMV-Signal_Peptide constructs
Impressions from the packaging
<groupparts>iGEM2016 LMU-TUM_Munich</groupparts>