Difference between revisions of "Help:Assembly/Scars"

(Created page with "{{CSS/DNA_Table}} Scars are a byproduct of assembling samples of DNA parts together. Assembly systems that follow an assembly standard (BioBrick RFC10, iGEM Type IIS, etc.) c...")
(No difference)

Revision as of 20:51, 15 August 2019

Scars are a byproduct of assembling samples of DNA parts together. Assembly systems that follow an assembly standard (BioBrick RFC10, iGEM Type IIS, etc.) create predictable scars between assembled parts. Some assembly systems can result in "scar-less" assembly (Synthesis, Gibson, "bespoke" Type IIS).


When two BioBrick part samples are assembled together to create a new BioBrick composite part, a scar forms between the subparts with the cohesive ends left by XbaI and SpeI digestion ligating together.


Function

Generally, scars do not provide or code for a function, like a promoter, ribosome binding site, or terminator, so they are not considered a basic part. However, they may still serve a purpose within a composite part through intentional design. Most often, this may be as a small spacer or linker region.

As an example, the 6bp scar formed when assembling BioBrick samples of the BBa_B0034 (RBS) and BBa_E1010 (CDS) results in more optimal spacing thn


Specifying Scars

The composite part editor on the "Edit sequence and features" page allows users to specify scars inbetween your subparts.


Example

Normally scars do not provide a function, but can serve purposes. As an example the BioBrick


Here we have four Registry parts that we will use in the design of our composite part device, an RFP generator.

These parts are compatible with both BioBrick RFC10 and iGEM Type IIS RFC1000. They do not have recognition sites for restriction enzymes that are used in either assembly standard.