Difference between revisions of "Part:BBa K404300"
VolkerMorath (Talk | contribs) |
VolkerMorath (Talk | contribs) |
||
Line 9: | Line 9: | ||
<br> | <br> | ||
This part is a peptide linker, it can be used to connect two protein parts / domains and add additional space between them. This can be necessary to avoid interactions between the different parts when fusion proteins are created. The SEG linker was created to connect our protein domains to a fusion construct. | This part is a peptide linker, it can be used to connect two protein parts / domains and add additional space between them. This can be necessary to avoid interactions between the different parts when fusion proteins are created. The SEG linker was created to connect our protein domains to a fusion construct. | ||
− | + | ||
===Usage and Biology=== | ===Usage and Biology=== | ||
− | + | ||
<span class='h3bb'>Sequence and Features</span> | <span class='h3bb'>Sequence and Features</span> | ||
<partinfo>BBa_K404300 SequenceAndFeatures</partinfo> | <partinfo>BBa_K404300 SequenceAndFeatures</partinfo> | ||
− | + | ||
===Functional Parameters=== | ===Functional Parameters=== | ||
<partinfo>BBa_K404300 parameters</partinfo> | <partinfo>BBa_K404300 parameters</partinfo> |
Latest revision as of 19:29, 5 August 2013
SEG-Linker
Amino acid sequence:
GGSGGGSEGGGSEGGGSEGGGSEGGGSEGGGSGGGS
This part is a peptide linker, it can be used to connect two protein parts / domains and add additional space between them. This can be necessary to avoid interactions between the different parts when fusion proteins are created. The SEG linker was created to connect our protein domains to a fusion construct.
Usage and Biology
Sequence and Features
Assembly Compatibility:
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25COMPATIBLE WITH RFC[25]
- 1000COMPATIBLE WITH RFC[1000]
Functional Parameters
Parameters for BioBrick BBa_K404300 automatically created by the BioBrick-AutoAnnotator version 1.0 | ||||||||||||||||||||||||||||||||||||||||||||||
Nucleotide sequence in RFC 25, so ATGGCCGGC and ACCGGT were added (in italics) to the 5' and 3' ends: (underlined part encodes the protein) ATGGCCGGCGGTGGTTCT ... GGCGGTAGCACCGGT ORF from -8 to 114 (excluding stop-codon) | ||||||||||||||||||||||||||||||||||||||||||||||
Amino acid sequence: (RFC25 scars in shown in bold, other sequence features underlined; both given below)
| ||||||||||||||||||||||||||||||||||||||||||||||
Sequence features: (with their position in the amino acid sequence, also underlined or shown bold above) | ||||||||||||||||||||||||||||||||||||||||||||||
Amino acid composition:
| ||||||||||||||||||||||||||||||||||||||||||||||
Amino acid counting
| Biochemical parameters
| |||||||||||||||||||||||||||||||||||||||||||||
Codon usage
| ||||||||||||||||||||||||||||||||||||||||||||||
The BioBrick-AutoAnnotator was created by TU-Munich 2013 iGEM team. For more information please see the documentation. If you have any questions, comments or suggestions, please email us at igem@wzw.tum.de. |