Difference between revisions of "Part:BBa K523003"
| Line 8: | Line 8: | ||
There are two extra bases at the end which, when combined with the T at the start of the standard RFC10 suffix, code for a glycine. | There are two extra bases at the end which, when combined with the T at the start of the standard RFC10 suffix, code for a glycine. | ||
| − | The effect of both of these features is to provide an in-frame BglII site at the start, and an in-frame SpeI site at the end (from the standard suffix). These features are necessary for Edinburgh 2011's BioSandwich assembly protocol. | + | The effect of both of these features is to provide an in-frame BglII site at the start, and an in-frame SpeI site at the end (from the standard suffix). These features are necessary for producing fusion proteins with Edinburgh 2011's BioSandwich assembly protocol (RFC 81). |
<!-- Add more about the biology of this part here | <!-- Add more about the biology of this part here | ||
Revision as of 20:13, 18 September 2011
malS for BioSandwich
This is a version of BBa_K523001 but with no RBS and no stop codon.
There are four extra bases at the end which (together with the standard RFC10 prefix) generate a BglII site.
There are two extra bases at the end which, when combined with the T at the start of the standard RFC10 suffix, code for a glycine.
The effect of both of these features is to provide an in-frame BglII site at the start, and an in-frame SpeI site at the end (from the standard suffix). These features are necessary for producing fusion proteins with Edinburgh 2011's BioSandwich assembly protocol (RFC 81).
Sequence and Features
Assembly Compatibility:
- 10COMPATIBLE WITH RFC[10]
- 12INCOMPATIBLE WITH RFC[12]Illegal NheI site found at 1204
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25INCOMPATIBLE WITH RFC[25]Illegal AgeI site found at 340
Illegal AgeI site found at 1505 - 1000COMPATIBLE WITH RFC[1000]