Difference between revisions of "Part:BBa K801100:Sequence, Features, and Subparts"
VolkerMorath (Talk | contribs) (→Extension of the standard compability to RFC10 and RFC25) |
VolkerMorath (Talk | contribs) (→Extension of the standard compability to RFC10 and RFC25) |
||
| Line 36: | Line 36: | ||
==Extension of the standard compability to RFC10 and RFC25== | ==Extension of the standard compability to RFC10 and RFC25== | ||
| − | [http://2012.igem.org/Team:TU_Munich Team TU_Munich 2012] extended the standard compability of the RFP coding device (<partinfo>BBa_J04450</partinfo>) to RFC10 and RFC25 by adding the | + | [http://2012.igem.org/Team:TU_Munich Team TU_Munich 2012] extended the standard compability of the RFP coding device (<partinfo>BBa_J04450</partinfo>) to RFC10 and RFC25 by adding the NgoMIV and AgeI restriction sites into the prefix and suffix of this part. Additionally two AgeI restriction sites that were present in the genrator itself were deletd. This part may be used as a stndard insert for RFC10 as well as RFC25 backbones. This improvement was necessary because when <partinfo>BBa_J04450</partinfo> in inserted into a RFC25 compatible backbone the RFC25 restriction site are lost and the backbone can not be used for inframe proteinfusion as desired in RFC25. |
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 14:31, 21 October 2012
No part name specified with partinfo tag.
| LacI R0010 | B0034 | mRFP1 E1010 | B0015 | |
 |  |  |  |
The colonies are clearly red in color under natural light after about 18 hours. Smaller colonies are visibly red under UV. The RFP part does not contain a degradation tag and the RBS is strong.
- LacI sensitive
- CAP sensitive
This part is commonly used, but can fail if the system contains LacI or CAP protein.
(--Meagan 15:39, 23 July 2009 (UTC))
Pictures
BBa_J04450 visualized under non-UV lightbox
BBa_J04450 visualized under 254nm wavelength UV lightbox
BBa_J04450 Colonies
Usage as a cloning tool
[http://2010.igem.org/Team:Groningen Team Groningen 2010] reports the usage of this part as a cloning tool. When ligating any part, or part assembly, into any standard backbone that contains this part, the non-restricted and single-restricted backbones that self-circularize will produce red colonies on rich media plates (we use TY). These undesired transformants can than be avoided in the screening for the correct construct. With this method, the backbone desired for a new construct does not need to be purified from agarose gel to decrease the amount of undesired tranformants caused by ligation of the original part present in the backbone. The amount of incorrect transformants depends, of course, on the ratio of backbone (mixed with J04450) vs. BioBrick insert, the size of the BioBrick insert, and whether the insert is an assembly of two BioBricks. The images below show two ligations with different efficiencies.
An inefficient assembly ligation of two BioBricks into the pSB1C3 backbone producing many red colonies.
A more efficient, single BioBrick ligation into the pSB1C3 backbone.
Extension of the standard compability to RFC10 and RFC25
[http://2012.igem.org/Team:TU_Munich Team TU_Munich 2012] extended the standard compability of the RFP coding device (BBa_J04450) to RFC10 and RFC25 by adding the NgoMIV and AgeI restriction sites into the prefix and suffix of this part. Additionally two AgeI restriction sites that were present in the genrator itself were deletd. This part may be used as a stndard insert for RFC10 as well as RFC25 backbones. This improvement was necessary because when BBa_J04450 in inserted into a RFC25 compatible backbone the RFC25 restriction site are lost and the backbone can not be used for inframe proteinfusion as desired in RFC25.