Team:SDU-Denmark/labwork/Constructs
From 2012.igem.org
(44 intermediate revisions not shown) | |||
Line 246: | Line 246: | ||
- | <h1>Constructs</h1> | + | <h1>Data page / Constructs</h1> |
<a href="https://static.igem.org/mediawiki/2012/7/77/Giant_Bacteria%21fin%21_.png"><img src="https://static.igem.org/mediawiki/2012/thumb/7/77/Giant_Bacteria%21fin%21_.png/800px-Giant_Bacteria%21fin%21_.png" width="100%"> </a> | <a href="https://static.igem.org/mediawiki/2012/7/77/Giant_Bacteria%21fin%21_.png"><img src="https://static.igem.org/mediawiki/2012/thumb/7/77/Giant_Bacteria%21fin%21_.png/800px-Giant_Bacteria%21fin%21_.png" width="100%"> </a> | ||
</br> | </br> | ||
+ | <h2>Data For Our Favorite New Parts</h2> | ||
</br> | </br> | ||
- | < | + | |
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899011" target="_new"><b>Part:BBa_K899011</b></a> | ||
<p> | <p> | ||
- | + | Our submitted FFT gene in pSB1C3 vector, was characterized in pJET blunt vector. We produced growth curve and inulin staining. From our results we can conclude, that FFT might be able to produce inulin, and is not able to produce any inulin without the presence of 1-kestose sugars produced by the SST enzyme. | |
- | + | </p> | |
- | + | ||
- | </ | + | |
</br> | </br> | ||
- | <h2>Data For Our Favorite | + | <h2>Data For Our Favorite non-characterized composite parts</h2></br> |
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899005" target="_new"><b>Part:BBa_K899005</b></a> | ||
+ | <p> | ||
+ | This is our theoretical composite bio-brick system of SST producing the 1-kestose trisaccharide as mentioned. This brick also includes the toxin-antitoxin system which is comprised of ccdB as a toxin and MazE as antitoxin. | ||
+ | </p> | ||
</br> | </br> | ||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899006" target="_new"><b>Part:BBa_K899006</b></a> | ||
</br> | </br> | ||
+ | <p> | ||
+ | The complementary part to K899005 producing FFT and mazF as a toxin and ccdA as antitoxin | ||
+ | </p> | ||
</br> | </br> | ||
- | <h2>Data For | + | |
- | + | ||
- | + | <h2>Data For Registry entries</h2> | |
</br> | </br> | ||
- | |||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899000" target="_new"><b>Part:BBa_K899000</b></a> | ||
<p> | <p> | ||
+ | This part is the coding sequence for Sucrose:sucrose 1-fructosyltransferase isolated from jerusalem artichoke. | ||
+ | </p> | ||
+ | </br> | ||
- | + | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899001" target="_new"><b>Part:BBa_K899001</b></a> | |
- | + | <p> | |
+ | This part is the coding sequence for Fructan:Fructan 1-Fructosyltransferase isolated from jerusalem artichoke | ||
+ | </p> | ||
</br> | </br> | ||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899002" target="_new"><b>Part:BBa_K899002</b></a> | ||
+ | <p> | ||
+ | Composite part: BBa_K899000(SST) + Reporter system containing a LacL promotor, GFP and two terminators. | ||
+ | </p> | ||
</br> | </br> | ||
- | + | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899003" target="_new"><b>Part:BBa_K899003</b></a> | |
- | < | + | <p> |
+ | Composite part: BBa_K899001(FFT) + Reporter system containing a LacL promotor, GFP and two terminators. | ||
</p> | </p> | ||
- | < | + | </br> |
- | + | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899004" target="_new"><b>Part:BBa_K899004</b></a> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
<p> | <p> | ||
- | + | Composite part of Reporter system to test for transcription of both SST and FFT. Contains LacL promotor, RBS, SST, RBS, FFT RBS, GFP and two terminators | |
+ | </p> | ||
</br> | </br> | ||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899007" target="_new"><b>Part:BBa_K899007</b></a> | ||
+ | <p> | ||
+ | ccdB is a toxin that fits to the ccdA antitoxin | ||
+ | </p> | ||
</br> | </br> | ||
- | < | + | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899008" target="_new"><b>Part:BBa_K899008</b></a> |
+ | <p> | ||
+ | antitoxin ccdA working by inhibitting the toxin ccdB (BBa_K899007) | ||
</p> | </p> | ||
+ | </br> | ||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899009" target="_new"><b>Part:BBa_K899009</b></a> | ||
+ | <p> | ||
+ | Double ribosomal binding site, containing kozak and shine-dalgarno sequence | ||
+ | </p> | ||
+ | </br> | ||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899010" target="_new"><b>Part:BBa_K899010</b></a> | ||
+ | <p> | ||
+ | Shine-dalgarno sequence (AGGAGGT) and a kozak sequence (CACC). | ||
+ | </p> | ||
+ | <a href="http://partsregistry.org/wiki/index.php?title=Part:BBa_K899012" target="_new"><b>Part:BBa_K899012</b></a> | ||
+ | <p> | ||
+ | SST (BBa_K899001) with double RBS (BBa_K899010) | ||
+ | </p> | ||
+ | </br> | ||
- | < | + | <h2>The System</h2> |
+ | <p> | ||
+ | The above picture illustrates our idealized system the way we wanted it to be . It consists of two plasmids with FFT and SST respectively. Both plasmids have a toxin-antitoxin system introduced which works as a form of safety to prevent horizontal gene transfer (read more about it further down the page). The two enzymes, FFT and SST, produce together the non-digestible inulin from sucrose. Along with the two plasmids there is also a sigma-E gene that functions as a regulator gene in our kill-switch system. </br> </br> | ||
+ | The sigma-E is an alternative sigma factor that controls the extracytoplasmic stress response in E. coli. The idea is to have an L-Rhamnose sensitive promoter that expresses this essential gene. </br></br> | ||
+ | The L-Rhamnose would be in the yoghurt with our bacteria and function as a limiting lifetime for the consumed bacteria. L-Rhamnose is a non-digestible sugar which passes through the system and thereby inactivates the sigma-E gene. The consumed bacteria from the yoghurt would inevitably die after a while. | ||
+ | </br> | ||
</br> | </br> | ||
+ | |||
+ | <h2>Killswitch</h2> | ||
<p> | <p> | ||
- | + | During the construction of a killswitch, we stumbled upon a very concerning fact. A normal killswitch inducible by a promoter can be rendered useless in the case of frameshift mutations (and any other mutation, that affects the gene-product). Therefore we chose to construct killswitches with a less likely chance of being frameshifted out of order. </br></br> | |
- | </ | + | <img src="https://static.igem.org/mediawiki/igem.org/9/9f/SDU2012_killS0.png" width="100%"/></br></br> |
+ | In order to make the most effective killswitch we have take several aspects in consideration. As you might observe on the figure above, it is not just a promoter and a death gene, since this would be rendered useless by frameshift mutations or loss of promoter effectivity etc.. The design of our killswitch aims to produce a reliable killswitch that decreases the risk of misfunction. This is very important because the introduction of GMO in humans requires utter carefulness and security, should something go wrong.</br></br> | ||
- | + | Our killswitch consists of a constitutive promoter, 3 structural genes in a polycistronic system whereas 2 of them are translationally coupled with 1 bp frameshift. The frameshift-coupled genes are mazF and yafO which is both toxic to the bacteria. MazE is located after another shine-dalgarno sequence and is therefore not affected by frameshifts in the mazF-yafO region.</br> | |
+ | The point of the frameshifted translational coupling between mazF and yafO is, that the yafO not will be translated if the frameshift does not occur. Should a frameshift occur in the mazF toxin the yafO will be expressed, killing the cell. Does a mutation in mazE occur the cell will die because mazE is the antitoxin of mazF. Should the genes be untranscribed at any point, the mazE should be degraded faster than the mazF killing the cell. | ||
+ | The sequences have been codon optimized, in order to remove any stop codons potentially terminating translation before the ribosome reaches the yafO toxin.</br></br> | ||
+ | |||
+ | After developing this idea we found, that ribosomes can jump up to 10 bp back and forth from a stop-codon, therefore this frameshift system will not work in practice. Though it is subject for further development, since moving the toxin’s an appropriate distance from the stop codon would solve that problem. We have not been able to find attempts on this in the literature so it would be an interesting subject to investigate further. Since we don’t have the time to investigate this idea, we instead propose another idea for a safety mechanism that will help controlling the bacteria of our culture.</br></br> | ||
+ | |||
+ | <b>Safety mechanism targeting sigma-E:</b></br> | ||
+ | |||
+ | This construct will contain an L-rhamnose promoter that is activated by L-rhamnose. This promoter will then transcribe the sigma-E factor which should be deleted from the genome of our chassi bacteria. This factor is a life-essential part of the bacteria, hence killing it, if it should remain untranslated. Also it would be necessary to delete the toxin-antitoxin of hicAB since it is shown that hicA is capable of keeping the cell alive upon lac of sigma-E [<a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2631989/" target="_new">jørgensen et al</a>]. The reason for putting the sigma-E under control of the rhamnose promoter is, that by adding rhamnose to our product (fx yoghurt), the bacteria will only be alive as long as the rhamnose is present, and when the rhamnose i removed from the gut the bacteria will die.</br></br> | ||
+ | |||
+ | <b>Optimizing the sequence</b></br> | ||
+ | The RNA code optimized<br> | ||
+ | <span style="background-color:red">Red markings indicates silent mutations</span></br> | ||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/igem.org/2/29/SDU2012_killS1.png" width="100%"/></br></br> | ||
+ | |||
+ | <b>Translational overview</b></br> | ||
+ | <span style="background-color:green">start</span></br> | ||
+ | <span style="background-color:red">stop</span></br> | ||
+ | <span style="background-color:brown">Inserted AA (gly)</span></br> | ||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/igem.org/8/83/SDU2012_killS2.png" width="100%"/></br></br> | ||
+ | |||
+ | Should a frameshift occur, the sequence would look like this (notice the F in the beginning is the insertion of 1 bp). The weakness of the killswitch is, that if the frameshift occurs in the start codon the ribosome will terminate translation before it gets to the coding sequence of yafO.</br> | ||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/igem.org/d/d7/SDU2012_killS3.png" width="100%"/></br></br> | ||
+ | |||
+ | deletion of 1 bp /2 bp insertion</br> | ||
+ | |||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/igem.org/d/d9/SDU2012_killS4.png" width="100%"/></br></br> | ||
+ | </br></br> | ||
+ | <h2>Construct flowchart</h2> | ||
+ | <p> | ||
+ | This flowchart shows our proposed workflow for constructing our desired final construct. See partsregistry for further details regarding the individual parts. (see further up on this page for the relevant links.) | ||
+ | </br></br> | ||
+ | <a href="https://static.igem.org/mediawiki/2012/8/8e/Design_plan_%28final%29.gif"> <img src="https://static.igem.org/mediawiki/2012/thumb/8/8e/Design_plan_%28final%29.gif/800px-Design_plan_%28final%29.gif" width="100%" TARGET="_new" /> | ||
+ | </a> | ||
<!-- //////////// Anchor used to scroll to PORTFOLIO //////////// --> | <!-- //////////// Anchor used to scroll to PORTFOLIO //////////// --> | ||
Latest revision as of 03:41, 27 September 2012
Data page / Constructs
Data For Our Favorite New Parts
Part:BBa_K899011Our submitted FFT gene in pSB1C3 vector, was characterized in pJET blunt vector. We produced growth curve and inulin staining. From our results we can conclude, that FFT might be able to produce inulin, and is not able to produce any inulin without the presence of 1-kestose sugars produced by the SST enzyme.
Data For Our Favorite non-characterized composite parts
Part:BBa_K899005This is our theoretical composite bio-brick system of SST producing the 1-kestose trisaccharide as mentioned. This brick also includes the toxin-antitoxin system which is comprised of ccdB as a toxin and MazE as antitoxin.
Part:BBa_K899006The complementary part to K899005 producing FFT and mazF as a toxin and ccdA as antitoxin
Data For Registry entries
Part:BBa_K899000This part is the coding sequence for Sucrose:sucrose 1-fructosyltransferase isolated from jerusalem artichoke.
Part:BBa_K899001This part is the coding sequence for Fructan:Fructan 1-Fructosyltransferase isolated from jerusalem artichoke
Part:BBa_K899002Composite part: BBa_K899000(SST) + Reporter system containing a LacL promotor, GFP and two terminators.
Part:BBa_K899003Composite part: BBa_K899001(FFT) + Reporter system containing a LacL promotor, GFP and two terminators.
Part:BBa_K899004Composite part of Reporter system to test for transcription of both SST and FFT. Contains LacL promotor, RBS, SST, RBS, FFT RBS, GFP and two terminators
Part:BBa_K899007ccdB is a toxin that fits to the ccdA antitoxin
Part:BBa_K899008antitoxin ccdA working by inhibitting the toxin ccdB (BBa_K899007)
Part:BBa_K899009Double ribosomal binding site, containing kozak and shine-dalgarno sequence
Part:BBa_K899010Shine-dalgarno sequence (AGGAGGT) and a kozak sequence (CACC).
Part:BBa_K899012SST (BBa_K899001) with double RBS (BBa_K899010)
The System
The above picture illustrates our idealized system the way we wanted it to be . It consists of two plasmids with FFT and SST respectively. Both plasmids have a toxin-antitoxin system introduced which works as a form of safety to prevent horizontal gene transfer (read more about it further down the page). The two enzymes, FFT and SST, produce together the non-digestible inulin from sucrose. Along with the two plasmids there is also a sigma-E gene that functions as a regulator gene in our kill-switch system. The sigma-E is an alternative sigma factor that controls the extracytoplasmic stress response in E. coli. The idea is to have an L-Rhamnose sensitive promoter that expresses this essential gene. The L-Rhamnose would be in the yoghurt with our bacteria and function as a limiting lifetime for the consumed bacteria. L-Rhamnose is a non-digestible sugar which passes through the system and thereby inactivates the sigma-E gene. The consumed bacteria from the yoghurt would inevitably die after a while.
Killswitch
During the construction of a killswitch, we stumbled upon a very concerning fact. A normal killswitch inducible by a promoter can be rendered useless in the case of frameshift mutations (and any other mutation, that affects the gene-product). Therefore we chose to construct killswitches with a less likely chance of being frameshifted out of order.
In order to make the most effective killswitch we have take several aspects in consideration. As you might observe on the figure above, it is not just a promoter and a death gene, since this would be rendered useless by frameshift mutations or loss of promoter effectivity etc.. The design of our killswitch aims to produce a reliable killswitch that decreases the risk of misfunction. This is very important because the introduction of GMO in humans requires utter carefulness and security, should something go wrong.
Our killswitch consists of a constitutive promoter, 3 structural genes in a polycistronic system whereas 2 of them are translationally coupled with 1 bp frameshift. The frameshift-coupled genes are mazF and yafO which is both toxic to the bacteria. MazE is located after another shine-dalgarno sequence and is therefore not affected by frameshifts in the mazF-yafO region.
The point of the frameshifted translational coupling between mazF and yafO is, that the yafO not will be translated if the frameshift does not occur. Should a frameshift occur in the mazF toxin the yafO will be expressed, killing the cell. Does a mutation in mazE occur the cell will die because mazE is the antitoxin of mazF. Should the genes be untranscribed at any point, the mazE should be degraded faster than the mazF killing the cell.
The sequences have been codon optimized, in order to remove any stop codons potentially terminating translation before the ribosome reaches the yafO toxin.
After developing this idea we found, that ribosomes can jump up to 10 bp back and forth from a stop-codon, therefore this frameshift system will not work in practice. Though it is subject for further development, since moving the toxin’s an appropriate distance from the stop codon would solve that problem. We have not been able to find attempts on this in the literature so it would be an interesting subject to investigate further. Since we don’t have the time to investigate this idea, we instead propose another idea for a safety mechanism that will help controlling the bacteria of our culture.
Safety mechanism targeting sigma-E:
This construct will contain an L-rhamnose promoter that is activated by L-rhamnose. This promoter will then transcribe the sigma-E factor which should be deleted from the genome of our chassi bacteria. This factor is a life-essential part of the bacteria, hence killing it, if it should remain untranslated. Also it would be necessary to delete the toxin-antitoxin of hicAB since it is shown that hicA is capable of keeping the cell alive upon lac of sigma-E [jørgensen et al]. The reason for putting the sigma-E under control of the rhamnose promoter is, that by adding rhamnose to our product (fx yoghurt), the bacteria will only be alive as long as the rhamnose is present, and when the rhamnose i removed from the gut the bacteria will die.
Optimizing the sequence
The RNA code optimized
Red markings indicates silent mutations
Translational overview
start
stop
Inserted AA (gly)
Should a frameshift occur, the sequence would look like this (notice the F in the beginning is the insertion of 1 bp). The weakness of the killswitch is, that if the frameshift occurs in the start codon the ribosome will terminate translation before it gets to the coding sequence of yafO.
deletion of 1 bp /2 bp insertion
Construct flowchart
This flowchart shows our proposed workflow for constructing our desired final construct. See partsregistry for further details regarding the individual parts. (see further up on this page for the relevant links.)