Team:UNIPV-Pavia/Parts/Characterization/RebExistingParts
From 2010.igem.org
m |
|||
(7 intermediate revisions not shown) | |||
Line 32: | Line 32: | ||
=Improved Parts: list= | =Improved Parts: list= | ||
- | * [[Team:UNIPV-Pavia/Parts/Characterization/RebExistingParts #BBa_K300002 - Phasin (PhaP) - head domain|BBa_K300002 - Phasin (PhaP) - head domain]] | + | * [[Team:UNIPV-Pavia/Parts/Characterization/RebExistingParts #BBa_K300002 - Phasin (PhaP) - head domain|BBa_K300002 - Phasin (PhaP) - head domain - improvement of BBa_K208001]] |
- | * [[Team:UNIPV-Pavia/Parts/Characterization/RebExistingParts #BBa_K300003 - Phasin (PhaP) - internal domain|BBa_K300003 - Phasin (PhaP) - internal domain]] | + | * [[Team:UNIPV-Pavia/Parts/Characterization/RebExistingParts #BBa_K300003 - Phasin (PhaP) - internal domain|BBa_K300003 - Phasin (PhaP) - internal domain - improvement of BBa_K208001]] |
<br> | <br> | ||
Line 43: | Line 43: | ||
=Phasins= | =Phasins= | ||
- | Polyhydroxyalkanoates (PHAs) are polyoxoesters that are produced by | + | Polyhydroxyalkanoates (PHAs) are polyoxoesters that are produced by several bacteria and that accumulate as intracellular granules. Phasins are proteins that can bind these granules. |
- | + | The following parts are derived from the phaP gene of ''Ralstonia eutropha'', which encodes for a phasin, engineered without the stop codon in order to support protein fusions as a head/internal domain. | |
Phasins can be used as affinity tags for a target protein, which can bind PHA granules allowing this way protein purification. | Phasins can be used as affinity tags for a target protein, which can bind PHA granules allowing this way protein purification. | ||
In literature [Banki MR et al., 2005] it has been shown that affinity tags composed by phasins assembled in tandem can increase the affinity with PHA. | In literature [Banki MR et al., 2005] it has been shown that affinity tags composed by phasins assembled in tandem can increase the affinity with PHA. | ||
+ | |||
+ | The aim of our improvement of phasin already present in the Registry (<partinfo>BBa_K208001</partinfo>) was to provide a head and an internal protein domain useful to build fusion proteins. | ||
==<partinfo>BBa_K300002</partinfo> - Phasin (PhaP) - head domain== | ==<partinfo>BBa_K300002</partinfo> - Phasin (PhaP) - head domain== | ||
Line 128: | Line 130: | ||
===Discussion=== | ===Discussion=== | ||
- | All cell cultures showed a similar growth curve | + | All cell cultures showed a similar growth curve; doubling time was computed as described [[Team:UNIPV-Pavia/Parts/Characterization#Doubling_time_evaluation|here]] in order to have informations about the burden due to the synthesis of such fusion proteins. It's possible to see that all doubling time are very similar; it's possible to assert that the expression of these BioBrick parts doesn't cause abnormal stress to cells. |
- | + | From GFP curve it's possible to appreciate that in <partinfo>BBa_K300086</partinfo> GFP accumulation it's significantly different from that of negative control <partinfo>BBa_B0031</partinfo>. This result shows that the green fluorescent protein assembled downstream of the genetic circuit is correctly folded. | |
The mean protein synthesis rate was also computed over the growth exponential phase, showing an appreciable GFP production rate that is about a half of the positive control. | The mean protein synthesis rate was also computed over the growth exponential phase, showing an appreciable GFP production rate that is about a half of the positive control. | ||
==<partinfo>BBa_K300003</partinfo> - Phasin (PhaP) - internal domain== | ==<partinfo>BBa_K300003</partinfo> - Phasin (PhaP) - internal domain== | ||
- | This part without stop codon and with Prefix and Suffix compatible with RFC23 (Silver Standard) in order to fully support protein fusions as an internal domain. Together with <partinfo>BBa_K300002</partinfo>, enables the construction of synthetic affinity tags | + | This part without stop codon and with Prefix and Suffix compatible with RFC23 (Silver Standard) was built in order to fully support protein fusions as an internal domain. Together with <partinfo>BBa_K300002</partinfo>, enables the construction of synthetic affinity tags containing phasins in tandem, possibly spaced by peptide linkers, as described in [Banki MR et al., 2005]. |
===Construction=== | ===Construction=== | ||
Line 146: | Line 148: | ||
The Suffix sequence is 5'-ACTAGTAGCGGCCGCTGCAG-3' (RFC23 Suffix) | The Suffix sequence is 5'-ACTAGTAGCGGCCGCTGCAG-3' (RFC23 Suffix) | ||
- | For these reasons, a tail domain or an internal domain (compatible with RFC23) can be easily assembled downstream to create protein fusions. | + | For these reasons, a tail domain or an internal domain (compatible with RFC23) can be easily assembled downstream this BiobBrick to create protein fusions. |
- | To obtain this part BioBrick <partinfo>BBa_K208001</partinfo> (provided by iGEM HQ in pSB3K3 in RFC23 standard) was PCR-amplified/mutagenized with primers: | + | To obtain this part, BioBrick <partinfo>BBa_K208001</partinfo> (provided by iGEM HQ in pSB3K3 in RFC23 standard) was PCR-amplified/mutagenized with primers: |
phaPSF: 5'-GCTTCTAGAATGATCCTCACCCCGGAACA-3' | phaPSF: 5'-GCTTCTAGAATGATCCTCACCCCGGAACA-3' | ||
Line 156: | Line 158: | ||
in order to delete the stop codon. | in order to delete the stop codon. | ||
- | The PCR product was ran on a 1% agarose gel, gel-extracted, | + | The PCR product was ran on a 1% agarose gel, gel-extracted, digested with XbaI-SpeI and ligated with <partinfo>pSB1A3</partinfo> (previously cut with XbaI-SpeI and dephosphorylated). |
- | Positive clones were | + | Positive clones were selected through digestion screening/sequencing. |
---- | ---- |
Latest revision as of 03:25, 28 October 2010
|
|||||||||||||||||||||||||||||
|
|