Difference between revisions of "Team:Chalmers-Gothenburg/ProjectResults"

 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template_All_Teams}}
+
{{Chalmers-Gothenburg}}
 
+
<!-- Declare that you are going to use html code instead of wiki code -->
+
<html>
+
 
+
<!-- Start of CSS-->
+
<style type="text/css">
+
 
+
/* PAGE LAYOUT */
+
 
+
/* Change Background color*/
+
body {
+
background-color: #fff;
+
}
+
 
+
/* Creates a container that will wrap all of the content inside your wiki pages. */
+
#mainContainer { 
+
width: 978px;
+
overflow:hidden;
+
float:left;
+
margin-left:20px;
+
margin-bottom: 10px;
+
background-color: #fff;
+
border-bottom: 14px solid #565656;
+
border-right: 2px solid #565656;
+
border-left: 2px solid #565656;
+
border-top: 2px solid #565656;
+
font-family: "Trebuchet MS", Helvetica, sans-serif;
+
}
+
 
+
/* Creates the container for the menu */
+
#menuContainer  {
+
float:left;
+
width: 134px;
+
padding: 20px 0px;
+
border-top: 14px solid #565656;
+
background-color: #E8E8E9;
+
}
+
 
+
/* Creates the container for the content */
+
#contentContainer {
+
padding-top:20px;
+
padding-right:10px;
+
margin-bottom: 20px;
+
width: 814px;
+
padding-left: 20px;
+
float: left;
+
background-color: #fff;
+
border-top: 14px solid #565656;
+
font-family: "Trebuchet MS", Helvetica, sans-serif;
+
}
+
 
+
/*Set up height place holder for the banner*/
+
#bannerContainer {
+
height:200px;
+
margin:auto;
+
text-align:center;
+
color: #24B694;
+
}
+
 
+
/*VISUAL STYLE (TABLES, FONTS, LINKS, IMAGES, UL) */
+
 
+
/*Change the styling of text for everything inside main container*/
+
#mainContainer p {
+
font-size: 13px;
+
color: #000000;
+
}
+
+
/*This changes the color and font family */
+
#contentContainer h1, h2, h3, h4, h5, h6 {
+
color: #565656;
+
border-bottom: none;
+
font-weight: bold;
+
font-family: "Trebuchet MS", Helvetica, sans-serif;
+
margin-top:10px;
+
}
+
 
+
/*Style of the links - links are different inside the menu */
+
#contentContainer a {
+
font-weight: bold;
+
color: #23b593;
+
}
+
 
+
  /* Styling links on hover- links are different inside the menu */
+
#contentContainer a:hover {
+
color: #59bf92;
+
}
+
 
+
/*Change the styling of tables */
+
        #contentContainer table {
+
    border: 1px solid #565656;
+
    border-collapse: collapse;
+
    width: 90%
+
    margin: auto;
+
    margin-bottom: 15px;
+
    margin-top: 15px;
+
    margin-right: 10px;
+
    margin-left: 10px;
+
    }
+
 
+
/*Change the styling of table cells*/
+
    #contentContainer  td {
+
    padding: 10px;
+
    border: 1px solid #565656;
+
    border-collapse: collapse;
+
    vertical-align: text-top;
+
    }
+
 
+
/*Change the styling of table headers */
+
    #contentContainer th {
+
    background-color: #E8E8E9;
+
    padding: 10px;
+
    border: 1px solid #565656;
+
    border-collapse: collapse;
+
    vertical-align: text-top;
+
    }
+
 
+
 
+
 
+
/*MENU STYLING */
+
 
+
/*Styling for the links in the menu */
+
#menuContainer a {
+
color: #565656;
+
text-decoration:none;
+
font-weight: bold;
+
}
+
 
+
/* Sets the style for lists inside menuContainer  */
+
#menuContainer ul {
+
list-style: none;
+
margin-left:0px;
+
}
+
 
+
/*Styles the list items to become menu buttons */
+
#menuContainer ul li {
+
text-align: center;
+
display: block;
+
width: 100%;
+
height:30px;
+
padding-top:10px;
+
}
+
 
+
/*For the menu buttons, changes the color when hovering*/
+
#menuContainer li:hover {
+
color:  #FFF;
+
background-color: #24B694;
+
}
+
 
+
/*Submenus are not displayed as default*/
+
#menuContainer li ul {
+
display: none;
+
padding-top:15px;
+
margin-left: -19px;
+
}
+
 
+
/*Submenus are displayed when hovering the menu button */
+
#menuContainer li:hover ul {
+
/*display: inline-block; */
+
display: block;
+
position: absolute;
+
float:right;
+
margin-left: 134px;
+
margin-top:-42px;
+
}
+
 
+
/*Style the submenu buttons*/
+
#menuContainer li ul li{
+
background-color: #59BF92;
+
padding-left:20px;
+
padding-right:20px;
+
height:30px;
+
padding-top:10px;
+
margin-top:-2px;
+
color: #565656;
+
width: 150px;
+
}
+
 
+
/*CLASSES */
+
 
+
/*Clear class for all the pages, adds spacing too*/
+
.clear{
+
clear:both;
+
height: 10px;
+
}
+
 
+
 
+
/* highlight box for special messages */
+
    .highlightBox {
+
        width:500px;
+
        margin:auto;
+
        background-color: #E8E8E9;
+
margin-bottom: 15px;
+
margin-top: 15px;
+
padding: 15px;
+
padding-top: 5px;
+
    }
+
 
+
 
+
</style>
+
<!-- End of CSS -->
+
 
+
 
+
<!-- Start of the template html elements. -->
+
<div id ="mainContainer"><!--The closing tag for mainContainer should be placed at the bottom of each content page.-->
+
 
+
 
+
<div id="bannerContainer">
+
<br><br>
+
<h2> Add a banner to your wiki! </h2>
+
+
<p>You can make the image 980px  by  200px</p>
+
<p> Remember to call the file: "<i>Team_Chalmers-Gothenburg_banner.jpg</i>" </p>
+
</div>
+
 
+
<!-- Start of menu -->
+
<div id="menuContainer">
+
 
+
<!-- This list is your menu, every list item is a menu button and nested listed become submenu buttons -->
+
<ul>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg"><li>HOME</li></a>
+
 
+
 
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Team"><li>TEAM
+
<ul> 
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Students"><li>Students</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Supervisors"><li>Supervisors</li></a> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Attributions"><li>Attributions</li></a>   
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Gallery"><li>Gallery</li></a>
+
+
</ul>
+
 
+
</li></a>
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Project"><li>PROJECT
+
<ul> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Theory"><li>Theory</li></a> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Constructs"><li>Constructs</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Protocols"><li>Protocols</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/OtherApplications"><li>Other applications</li></a>
+
</ul>
+
</li></a>
+
 
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Achievements"><li>ACHIEVEMENTS
+
<ul> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Project Results"><li>Project Results</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/BioBricks"><li>BioBricks</li></a> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Medals"><li>Medals</li></a> 
+
+
</ul>
+
</li></a>
+
 
+
 
+
<a href="#"><li>MODELING
+
            <ul>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Detection"><li>Detection</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Safety Switch"><li>Safety Switch</li></a> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Simulation"><li>Simulation</li></a> 
+
+
</ul>
+
</li></a>
+
+
 
+
 
+
 
+
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Practices"><li>HUMAN PRACTICES
+
<ul>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/iGEMCommunity"><li>iGEM Community</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/NextGeneration"><li>Next Generation</li></a> 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Society"><li>Society</li></a> 
+
+
</ul></a></li>
+
 
+
 
+
 
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Notebook"><li>NOTEBOOK
+
<ul>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Schedule"><li>Schedule</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Attributions"><li>Attributions</li></a>   
+
+
</ul>
+
</li></a>
+
     
+
+
 
+
 
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Safety"><li>SAFETY
+
<ul>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/LabSafety"><li>Lab Safety</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Ethics"><li>Ethics</li></a> 
+
+
</ul>
+
 
+
</li></a>
+
 
+
+
 
+
 
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Entrepreneurship"><li>THANKS
+
 
+
<ul>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Sponsors"><li>Sponsors</li></a>
+
<a href="https://2015.igem.org/Team:Chalmers-Gothenburg/Acknowledgements"><li>Acknowledgements</li></a> 
+
+
</ul>
+
 
+
</li></a>
+
 
+
</ul>
+
</div>
+
<!-- End of menu  -->
+
 
+
<!-- Start of content -->
+
<div id="contentContainer"> <!--The closing tag for contentContainer should be placed at the bottom of each content page.-->
+
</html>
+
 
<h2>Overview</h2>
 
<h2>Overview</h2>
<p>• Assembled and integrated two different safety switches, based on TPK2 overexpression or mRFP expression induced at low ATP levels, into CEN.PK2.</p>
+
<p>• Assembled and integrated two different safety switches, based on <i>TPK2</i> overexpression or <i>mRFP</i> expression induced at low ATP levels, into CEN.PK2.</p>
 
<p>• SS TPK2 shows reduced growth rate after OD-measurement but no change in viability compared to wild type.</p>
 
<p>• SS TPK2 shows reduced growth rate after OD-measurement but no change in viability compared to wild type.</p>
<p>• mRFP measurements show that connection of pTEF1 to pSUC2 maintains the ATP repression mechanism of pSUC2, while achieving higher expression at low ATP levels.</p>  
+
<p>• Fluorescent measurements show that connection of pTEF1 to pSUC2 maintains the ATP repression mechanism of pSUC2, while achieving higher expression at low ATP levels.</p>  
<p>• Successfully constructed and integrated the system to detect the P-factor from S.pombe into CEN.PK2.</p>
+
<p>• Successfully constructed and integrated the system to detect the P-factor from <i>S.pombe</i> into CEN.PK2.</p>
<p>• Fluorescent cells in DAS</p>
+
<p>• Fluorescent cells in the Detection System</p>
<p>• Amplified all parts of the PUR system, but obtained vector-only clones after Gibson and transformation into E.coli</p>
+
<p>• Amplified all parts of the DNA repair system, but obtained vector-only clones after Gibson and transformation into E.coli</p>
  
<h3>DAS</h3>
+
<h3>Detection system</h3>
<p>The system without the amplification through dCAS9-VP64 (construct 4) was successfully assembled and integrated into S.cerevisiae CEN.PK2. The genomic integration was verified with colony PCR and sequencing. The detection system was initially intended to be integrated into IMFD-70, but as several transformations failed the strain was changed to CEN.PK2 instead.</p>
+
<p>The system without the amplification through dCAS9-VP64 (construct 4) was successfully assembled and integrated into <i>S.cerevisiae</i> CEN.PK2. The genomic integration was verified with colony PCR and sequencing. The detection system was initially intended to be integrated into IMFD-70, but as several transformations failed the strain was changed to CEN.PK2 instead.</p>
  
 
<p>The construction of the application systems (construct 2 and 3) was unsuccessful. The fragments of the constructs was individually amplified with PCR, see figure 1, but only clones with empty vectors were obtained after Gibson assembly and transformation into E.coli.</p>
 
<p>The construction of the application systems (construct 2 and 3) was unsuccessful. The fragments of the constructs was individually amplified with PCR, see figure 1, but only clones with empty vectors were obtained after Gibson assembly and transformation into E.coli.</p>
Line 357: Line 36:
 
<p>[[File:ChalmersGothenburgWt0.jpg|500px]]
 
<p>[[File:ChalmersGothenburgWt0.jpg|500px]]
 
<br><b>Figure 7. WT without P-factor. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.</b></p>
 
<br><b>Figure 7. WT without P-factor. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.</b></p>
<p>Only the C4 samples containing the highest amount of P-factor showed a few fluorescent cells, which is promising for our concept. The weak signal can be explained by the fact that constructs containing the amplification system through dCas9-vp64 could not be completed. This forces the detection system to rely on the weak promoter pFUS1 <b>[1]</b> to express mRFP. This can result in a weak fluorescent signal when the P-factor is detected.</p>
+
<p>Only the C4 samples containing the highest amount of P-factor showed a few fluorescent cells, which is promising for our concept. The weak signal can be explained by the fact that constructs containing the amplification system through dCas9-vp64 could not be completed. This forces the detection system to rely on the presumably weak promoter pFUS1 to express <i>mRFP</i>. This can result in a weak fluorescent signal when the P-factor is detected.</p>
<h3>PUR</h3>
+
 
 +
 
 +
 
 +
 
 +
<h3>DNA Repair System</h3>
 +
 
 +
<p>The PUR genes were successfully amplified through PCR, see figure 8, but only clones with empty vectors were obtained after Gibson assembly and transformation into E.coli.  One of the problems could have been the size of the constructs, which was around 11-12 kbp, as only chemical transformation into E.coli was used.  Although, it is not certain that electroporation would have solved the problem, as the chemical transformation yielded only very few colonies, all of them containing empty vectors.</p>
 +
 
 +
<p>[[File:ChalmersGothenburgResultsPurFragments.jpeg|300px]]
 +
<br><b>Figure 8. 1kb ladder, RecJ, RecA, RecQ, RecD2, SSB, PprA and 1kb ladder.</b></p>
  
<p>The PUR genes were successfully amplified through PCR, see figure 8, but only clones with empty vectors were obtained after Gibson assembly and transformation into E.coli.</p>
+
<p>We cannot tell if this system will work in the same way in a yeast model as it does in <i>D. radiodurans</i>. We did not have enough time to evaluate optimizations, such as additional enzymes needed, as a lot of time was spend on trial and error in the construction of the current DNA repair system. We laid our focus on the other two systems
 +
</p>
  
 
<p>[[File:ChalmersGothenburgResultsPurFragments.jpeg|300px]]
 
<p>[[File:ChalmersGothenburgResultsPurFragments.jpeg|300px]]
Line 368: Line 57:
 
<h3>Safety switch</h3>
 
<h3>Safety switch</h3>
  
<p>All three variants of the safety switch (pTEF1-pSUC2-TPK2, pTEF1-pSUC2-mRFP and pSUC2-mRFP) was successfully integrated into the genome of S.cerevisiae CEN.PK2 and verified by colony PCR and sequencing.</p>
+
<p>All three variants of the safety switch (pTEF1-pSUC2-TPK2, pTEF1-pSUC2-<i>mRFP</i> and pSUC2-<i>mRFP</i>) was successfully integrated into the genome of <i>S.cerevisiae</i> CEN.PK2 and verified by colony PCR and sequencing.</p>
  
 
<h4>SS TPK2</h4>
 
<h4>SS TPK2</h4>
  
<p>The results for continuous OD-measurement of the wild type S.cerevisiae CEN.PK2 (WT) and CEN.PK2 with integrated safety switch (SS) in YPD are shown in figure 8.</p>
+
<p>The results for continuous OD-measurement of the wild type <i>S.cerevisiae</i> CEN.PK2 (WT) and CEN.PK2 with integrated safety switch (SS) in YPD are shown in figure 8.</p>
  
 
<p>[[File:ChalmersGothenburgSsTpk2.jpg|500px]]
 
<p>[[File:ChalmersGothenburgSsTpk2.jpg|500px]]
Line 384: Line 73:
 
<h4>SS mRFP</h4>
 
<h4>SS mRFP</h4>
  
<p>Expression of <i>mRFP</i> (monomeric Red Fluorescent Protein) was used to analyze expression levels of the safety switch. To evaluate the effect of connecting pTEF1 to pSUC, two different versions were made: pTEF1-pSUC2-mRFP and pSUC2-mRFP. Both constructs were integrated into the genome of S.cerevisiae CEN.PK2. The fluorescence of the clone with integrated pTEF1-pSUC2-<i>mRFP</i> (TEFSUC) and the clone with pSUC2-<i>mRFP</i> (SUC) was compared with wild type CEN.PK2 (WT).</p>
+
<p>Expression of <i>mRFP</i> (monomeric Red Fluorescent Protein) was used to analyze expression levels of the safety switch. To evaluate the effect of connecting pTEF1 to pSUC2, two different versions were made: pTEF1-pSUC2-<i>mRFP</i> and pSUC2-<i>mRFP</i>. Both constructs were integrated into the genome of <i>S.cerevisiae</i> CEN.PK2. The fluorescence of the clone with integrated pTEF1-pSUC2-<i>mRFP</i> (TEFSUC) and the clone with pSUC2-<i>mRFP</i> (SUC) was compared with wild type CEN.PK2 (WT).</p>
 
<p>The first sample of TEFSUC, SUC and WT was cultivated for 2 hours in YPD. The results from fluorescent microscopy are shown in figure 11-14.</p>
 
<p>The first sample of TEFSUC, SUC and WT was cultivated for 2 hours in YPD. The results from fluorescent microscopy are shown in figure 11-14.</p>
  
Line 407: Line 96:
 
<br><b>Figure 18. WT sample 2 cultivated for 6 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.</b></p>
 
<br><b>Figure 18. WT sample 2 cultivated for 6 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.</b></p>
  
<p>Now there is a clear difference between TEFSUC and SUC. TEFSUC gives several highly fluorescent cells while SUC only shows slightly higher fluorescent compared to WT. This indicates that the repression of pSUC2 is reduced which allows expression of mRFP through the high expression promoter pTEF1. </p>
+
<p>Now there is a clear difference between TEFSUC and SUC. TEFSUC gives several highly fluorescent cells while SUC only shows slightly higher fluorescent compared to WT. This indicates that the repression of pSUC2 is reduced which allows expression of <i>mRFP</i> through the high expression promoter pTEF1. </p>
 
<p>Another fluorescence measurement was performed on the same sample after 23 hours of cultivation.  
 
<p>Another fluorescence measurement was performed on the same sample after 23 hours of cultivation.  
 
The results from fluorescent microscopy are shown in figure 19-22.</p>
 
The results from fluorescent microscopy are shown in figure 19-22.</p>

Latest revision as of 01:46, 19 September 2015

Overview

• Assembled and integrated two different safety switches, based on TPK2 overexpression or mRFP expression induced at low ATP levels, into CEN.PK2.

• SS TPK2 shows reduced growth rate after OD-measurement but no change in viability compared to wild type.

• Fluorescent measurements show that connection of pTEF1 to pSUC2 maintains the ATP repression mechanism of pSUC2, while achieving higher expression at low ATP levels.

• Successfully constructed and integrated the system to detect the P-factor from S.pombe into CEN.PK2.

• Fluorescent cells in the Detection System

• Amplified all parts of the DNA repair system, but obtained vector-only clones after Gibson and transformation into E.coli

Detection system

The system without the amplification through dCAS9-VP64 (construct 4) was successfully assembled and integrated into S.cerevisiae CEN.PK2. The genomic integration was verified with colony PCR and sequencing. The detection system was initially intended to be integrated into IMFD-70, but as several transformations failed the strain was changed to CEN.PK2 instead.

The construction of the application systems (construct 2 and 3) was unsuccessful. The fragments of the constructs was individually amplified with PCR, see figure 1, but only clones with empty vectors were obtained after Gibson assembly and transformation into E.coli.

Construct 1 was successfully assembled and transformed into E.coli, see figure 2, but the construct is not functional without construct 2 and 3. Because of this limitation, no further steps were taken with construct 1.

ChalmersGothenburgDCas92.jpg

Figure 1.Well 1: 1kb ladder. Well 2 and 3: unpurified dCas9-Vp64. Well 4: purified dCas9-Vp64. Expected length: 4335 bp.

Construct 1 was successfully assembled and transformed into E.coli, see figure 2, but the construct is not functional without construct 2 and 3. Because of this limitation, no further steps were taken with construct 1.

ChalmersGothenburgVerifyC1.jpeg

Figure 2. Construct 1 digested with MfeI. Expected fragments: 214, 2656 and 5926 bp.

Detection test

The fluorescent microscopy pictures from the detection test with CEN.PK2 containing construct 4 (C4) are shown in figure 3-6. Samples were made with different amounts of concentrated P-factor and compared with wild type CEN.PK2 (WT).

ChalmersGothenburgRfpPositive.jpg
Figure 3. Positive control. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgC4230.jpg
Figure 4. C4 with 230 µl concentrated P-factor. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgC40.jpg
Figure 5. C4 without P-factor. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgWt230.jpg
Figure 6. WT with 230 µl concentrated P-factor. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgWt0.jpg
Figure 7. WT without P-factor. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

Only the C4 samples containing the highest amount of P-factor showed a few fluorescent cells, which is promising for our concept. The weak signal can be explained by the fact that constructs containing the amplification system through dCas9-vp64 could not be completed. This forces the detection system to rely on the presumably weak promoter pFUS1 to express mRFP. This can result in a weak fluorescent signal when the P-factor is detected.



DNA Repair System

The PUR genes were successfully amplified through PCR, see figure 8, but only clones with empty vectors were obtained after Gibson assembly and transformation into E.coli. One of the problems could have been the size of the constructs, which was around 11-12 kbp, as only chemical transformation into E.coli was used. Although, it is not certain that electroporation would have solved the problem, as the chemical transformation yielded only very few colonies, all of them containing empty vectors.

ChalmersGothenburgResultsPurFragments.jpeg
Figure 8. 1kb ladder, RecJ, RecA, RecQ, RecD2, SSB, PprA and 1kb ladder.

We cannot tell if this system will work in the same way in a yeast model as it does in D. radiodurans. We did not have enough time to evaluate optimizations, such as additional enzymes needed, as a lot of time was spend on trial and error in the construction of the current DNA repair system. We laid our focus on the other two systems

ChalmersGothenburgResultsPurFragments.jpeg
Figure 8. 1kb ladder, RecJ, RecA, RecQ, RecD2, SSB, PprA and 1kb ladder.


Safety switch

All three variants of the safety switch (pTEF1-pSUC2-TPK2, pTEF1-pSUC2-mRFP and pSUC2-mRFP) was successfully integrated into the genome of S.cerevisiae CEN.PK2 and verified by colony PCR and sequencing.

SS TPK2

The results for continuous OD-measurement of the wild type S.cerevisiae CEN.PK2 (WT) and CEN.PK2 with integrated safety switch (SS) in YPD are shown in figure 8.

ChalmersGothenburgSsTpk2.jpg
Figure 8. Growth curve of Wild type CEN.PK2 (WT) and recombinant CEN.PK2 with the safety switch (SS).

The measurements indicates that both WT and SS grow initially at the same rate but after ~6 hours, as energy (glucose) levels starts to decline, SS continues to grow at a reduced rate. This is not ideally as the safety switch is supposed to kill the cells, instead of just reduce its growth rate.

To check if the reduced growth rate was caused by reduced viability of the cells, a drop test was performed after 48 h cultivation in YPD. 10 µL of serially diluted cell suspension was spotted on an YPD plate and incubated overnight. The OD-measurement after 48 hours cultivation is shown in figure 9 and the drop test in figure 10.

ChalmersGothenburg48hgrowth.jpg ChalmersGothenburgResultsDropTest1.jpeg


Figure 9. OD600 after 48 hours cultivation. Figure 10. Drop test of WT (above) and SS (below). Serially diluted to OD 0.1, 0.05, 0.01 and 0.001

There is no clear difference in viability between WT and SS which indicates that overexpression if TPK2 in this system causes reduced growth rate but no obvious change in viability. A solution for this insufficient safety switch could be to change the TPK2 to a more harmful gene.

SS mRFP

Expression of mRFP (monomeric Red Fluorescent Protein) was used to analyze expression levels of the safety switch. To evaluate the effect of connecting pTEF1 to pSUC2, two different versions were made: pTEF1-pSUC2-mRFP and pSUC2-mRFP. Both constructs were integrated into the genome of S.cerevisiae CEN.PK2. The fluorescence of the clone with integrated pTEF1-pSUC2-mRFP (TEFSUC) and the clone with pSUC2-mRFP (SUC) was compared with wild type CEN.PK2 (WT).

The first sample of TEFSUC, SUC and WT was cultivated for 2 hours in YPD. The results from fluorescent microscopy are shown in figure 11-14.

ChalmersGothenburgRfpPositive.jpg
Figure 11. Positive control. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgTefSuc2h.jpg
Figure 12. TEFSUC sample 1 cultivated for 2 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgSuc2h.jpg
Figure 13. SUC sample 1 cultivated for 2 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgWt2h.jpg
Figure 14. WT sample 1 cultivated for 2 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

3 hours of cultivation in YPD (after overnight preculture) gives no visible RFP fluorescence. A reason for this could be that 2 hours is not enough to give a significant drop in energy levels to relieve the repression of pSUC2.

A new sample of TEFSUC, SUC and WT was cultivated for 6 hours in YPD. The results from fluorescent microscopy are shown in figure 15-18.

ChalmersGothenburgRfpPositive.jpg
Figure 15. Positive control. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgTefSuc6h.jpg
Figure 16. TEFSUC sample 2 cultivated for 6 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgSuc6h.jpg
Figure 17. SUC sample 2 cultivated for 6 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgWt6h.jpg
Figure 18. WT sample 2 cultivated for 6 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

Now there is a clear difference between TEFSUC and SUC. TEFSUC gives several highly fluorescent cells while SUC only shows slightly higher fluorescent compared to WT. This indicates that the repression of pSUC2 is reduced which allows expression of mRFP through the high expression promoter pTEF1.

Another fluorescence measurement was performed on the same sample after 23 hours of cultivation. The results from fluorescent microscopy are shown in figure 19-22.

ChalmersGothenburgRfpPositive.jpg
Figure 19. Positive control. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgTefSuc23h.jpg
Figure 20. TEFSUC sample 2 cultivated for 23 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgSuc23h.jpg
Figure 21. SUC sample 2 cultivated for 23 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

ChalmersGothenburgWt23h.jpg
Figure 22. WT sample 2 cultivated for 23 hours. Left: overlay channels (bright field, RFP and GFP). Right: RFP channel.

This demonstrates that the concept of this safety switch could work, but the lethal gene has to be changed to a more potent one to be classified as a functional safety switch