Difference between revisions of "Part:pSB1C5"
m |
m |
||
Line 2: | Line 2: | ||
__NOTOC__ | __NOTOC__ | ||
<partinfo>pSB1C5 short</partinfo> | <partinfo>pSB1C5 short</partinfo> | ||
+ | |||
+ | <i>Currently in draft</i> | ||
pSB1C5 is derived from pSB1C3, without its BioBrick prefix and suffix. As such, it is expected to function similarly. pSB1C5's main purpose is as an onboarded plasmid backbone, where new flanking sequences, including novel MCSes, can be added without the requirement to address BioBrick RFC10 or include its prefix and suffix. | pSB1C5 is derived from pSB1C3, without its BioBrick prefix and suffix. As such, it is expected to function similarly. pSB1C5's main purpose is as an onboarded plasmid backbone, where new flanking sequences, including novel MCSes, can be added without the requirement to address BioBrick RFC10 or include its prefix and suffix. | ||
+ | |||
+ | |||
<!-- Add more about the biology of this part here | <!-- Add more about the biology of this part here |
Latest revision as of 20:31, 10 December 2021
High-copy chloramphenicol resistant plasmid without an MCS
Currently in draft
pSB1C5 is derived from pSB1C3, without its BioBrick prefix and suffix. As such, it is expected to function similarly. pSB1C5's main purpose is as an onboarded plasmid backbone, where new flanking sequences, including novel MCSes, can be added without the requirement to address BioBrick RFC10 or include its prefix and suffix.
Sequence and Features
Assembly Compatibility:
- 10INCOMPATIBLE WITH RFC[10]Plasmid lacks a prefix.
Plasmid lacks a suffix. - 12INCOMPATIBLE WITH RFC[12]Plasmid lacks a prefix.
Plasmid lacks a suffix. - 21INCOMPATIBLE WITH RFC[21]Plasmid lacks a prefix.
Plasmid lacks a suffix.
Illegal XhoI site found at 1012
Illegal XhoI site found at 1904 - 23INCOMPATIBLE WITH RFC[23]Plasmid lacks a prefix.
Plasmid lacks a suffix. - 25INCOMPATIBLE WITH RFC[25]Plasmid lacks a prefix.
Plasmid lacks a suffix. - 1000INCOMPATIBLE WITH RFC[1000]Plasmid lacks a prefix.
Plasmid lacks a suffix.