Difference between revisions of "Team:Cardiff Wales/Results"

m
 
(43 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Cardiff_Wales}}
 
{{Cardiff_Wales}}
 
<html>
 
<html>
 +
<style>
 +
hr{
 +
width:80%;
 +
}
 +
div{
 +
padding:20px 0px;
 +
}
 +
#d{
 +
clear:both;
 +
}
 +
</style>
  
  
−
<div class="column full_size" >
+
<!-- hr & br doesnt need a / clause>
 +
<!--Start of my work-->
  
−
<p>Here you can describe the results of your project and your future plans. </p>
 
  
−
<h5>What should this page contain?</h5>
+
<img width=100% src="https://static.igem.org/mediawiki/2016/d/d1/T--Cardiff_Wales--Achievements.png"/>
−
<ul>
+
−
<li> Clearly and objectively describe the results of your work.</li>
+
−
<li> Future plans for the project </li>
+
−
<li> Considerations for replicating the experiments </li>
+
−
</ul>
+
  
−
</div>
+
<h1>Results</h1>
 +
<br>
  
−
<div class="column half_size" >
 
  
 +
<h1>Projects</h1>
 +
<hr>
  
−
<h5> Project Achievements </h5>
 
  
−
<p>You can also include a list of bullet points (and links) of the successes and failures you have had over your summer. It is a quick reference page for the judges to see what you achieved during your summer.</p>
 
  
−
<ul>
+
<div style="float:left; margin:0;width:50%;">
−
<li>A list of linked bullet points of the successful results during your project</li>
+
<h2> Cas-Find </h2>
−
<li>A list of linked bullet points of the unsuccessful results during your project. This is about being scientifically honest. If you worked on an area for a long time with no success, tell us so we know where you put your effort.</li>
+
<hr>
 +
<h3> Cas-Found </h3>
 +
<ul>
 +
  <li>IPTG inducible CRISPR-Cas9 guide RNA targeted to rRNA Reverse</li>
 +
  <li>Investigated viable systems for future investigation</li>
 
</ul>
 
</ul>
 +
<br>
 +
<h3> Can't-Find </h3>
 +
<ul>
 +
  <li>Use of vector (pET16B) with non-expected insert doomed 1/3 of our potential constructs</li>
 +
  <li>Failure to clone Cas-LucC/N & into E.Coli</li>
 +
  <li>As a result we have been unable to study the viablity of our proposed diagnostic tool</li>
  
 +
</ul>
 
</div>
 
</div>
  
 +
<div style="float:left; margin:0; width:50%;">
 +
<h2>FUEL Project</h2>
 +
<hr>
 +
<h3> Fuel Up </h3>
 +
<ul>
 +
  <li>We have successfully cloned and sequenced our arabinose-inducible pBAD:mKeima and pBAD:Lux Operon:mKeima constructs</li>
 +
<li>We have demonstrated that the LuxOperon portion of LUXoperon:mKeima of the fusion construct is functional</li>
  
−
<div class="column half_size" >
 
−
 
−
<h5>Inspiration</h5>
 
−
<p>See how other teams presented their results.</p>
 
−
<ul>
 
−
<li><a href="https://2014.igem.org/Team:TU_Darmstadt/Results/Pathway">2014 TU Darmstadt </a></li>
 
−
<li><a href="https://2014.igem.org/Team:Imperial/Results">2014 Imperial </a></li>
 
−
<li><a href="https://2014.igem.org/Team:Paris_Bettencourt/Results">2014 Paris Bettencourt </a></li>
 
 
</ul>
 
</ul>
 +
<br>
 +
<h3> Running on Empty </h3>
 +
<ul>
 +
<li>We have been unable to show a red light output from the mKeima constructs </li>
 +
<li>We have therefore been unable to observe any red shifting of the light output generated by the Lux Operon</li>
  
−
<!--Start of my work-->
+
 
 +
</ul>
  
 
</div>
 
</div>
  
−
<div id="column1" style="float:left; margin:0;width:50%;">
+
<p>The inaugural year of Cardiff iGEM has been an excellent learning experience. There is no doubt that next year we will be in a much stronger position to succeed in all aspects of the our project. We have already set the wheels in motion for a Cardiff_Wales iGEM 2017.
 +
<br><br>
 +
<p> <i>Therefore what did we specifically learn from this years iGEM project?</i>
 +
<li> We would likely use the different pSB1C3 antibiotic resistance variants instead of the three distinct plasmids we chose to use (pSB1C3, pET16B, pCOLA-DUET). This would improve the control of copy number and help maintain uniform expression of our constructs. We were unaware of the different pSB1C3 variants due to our focus on cloning biobricks into the registry-compliant chloramphenicol resistant pSB1C3.</li>
 +
<li> A number of our primers did not work as predicted and meant that we often couldn't inspect our transformed cultures without using direct sequencing. Next time we will set more time and resources to checking all our primers work appropriately, although within the time-scale of a ten-week project this can be challenging as by the time you realise there is a problem, the project has significantly progressed.</li>
 +
<li> When we started our lab work, the whole team was involved. This has the effect of making the work a bit fractured and disjointed, not to mention complicating the management of samples. In discussion with other teams it became apparent that it was more routine to have only a few members designated to lab duties. We therefore decided to reduce the number of us in the lab, and split off into two groups with each one focusing on a project each. This is something we look to do from the start in 2017.</li>
 +
<li> We didn't start our FUEL project until after half of our lab time was up, this really restricted the amount of time we could devote to it. Next time we would aim to split into two lab groups that start at the same together but work independently, which again would improve the management of lab work. </li>
 +
 
 +
 
 +
<div id=d>
 +
 
 +
<div style="float:left; margin:0; width:50%;">
 +
 
 +
 
  
−
<p> hi </p>
 
  
 
</div>
 
</div>
 +
<div style="float:left; margin:0; width:50%;">
  
  
−
<div id="column2" style="float:left; margin:0; width:50%;">
 
  
−
<p> hi </p>
+
</div>
 +
<div id=d>  
  
 +
<h1>Collaborations </h1>
 +
<hr>
 
</div>
 
</div>
  
−
<style>  
+
<li> Provided <a href="https://2016.igem.org/Team:Oxford" target="_blank">Oxford </a> with FLIM analysis of their copper chelators.  </li>
 +
<li> We have quantified ATP production from cells transformed with <a href="https://2016.igem.org/Team:WashU_StLouis" target="_blank">Washington's</a> phosphoenolpyruvate kinase (PCK) and phosphoglycerate kinase (PGK) constructs </li>
 +
<br>
 +
<p>Unfortunately we were unable to practically collaborate with <a href="https://2016.igem.org/Team:Paris_Saclay" target="_blank">Saclay</a> due to failures in our related dCas9. In future years we aim to increase our number of collaborations. We dedicated most of our lab time to cloning our own constructs, which meant there wasn't much time, or manpower left for collaborations. </p>
 +
<!--end of my work-->
 +
 
  
−
div {background-color: light blue}
 
  
−
</style>
 
  
 
</html>
 
</html>

Latest revision as of 03:24, 3 December 2016

MENU ▤

Results


Projects

Cas-Find

Cas-Found

  • IPTG inducible CRISPR-Cas9 guide RNA targeted to rRNA Reverse
  • Investigated viable systems for future investigation

Can't-Find

  • Use of vector (pET16B) with non-expected insert doomed 1/3 of our potential constructs
  • Failure to clone Cas-LucC/N & into E.Coli
  • As a result we have been unable to study the viablity of our proposed diagnostic tool

FUEL Project

Fuel Up

  • We have successfully cloned and sequenced our arabinose-inducible pBAD:mKeima and pBAD:Lux Operon:mKeima constructs
  • We have demonstrated that the LuxOperon portion of LUXoperon:mKeima of the fusion construct is functional

Running on Empty

  • We have been unable to show a red light output from the mKeima constructs
  • We have therefore been unable to observe any red shifting of the light output generated by the Lux Operon

The inaugural year of Cardiff iGEM has been an excellent learning experience. There is no doubt that next year we will be in a much stronger position to succeed in all aspects of the our project. We have already set the wheels in motion for a Cardiff_Wales iGEM 2017.

Therefore what did we specifically learn from this years iGEM project?

  • We would likely use the different pSB1C3 antibiotic resistance variants instead of the three distinct plasmids we chose to use (pSB1C3, pET16B, pCOLA-DUET). This would improve the control of copy number and help maintain uniform expression of our constructs. We were unaware of the different pSB1C3 variants due to our focus on cloning biobricks into the registry-compliant chloramphenicol resistant pSB1C3.
  • A number of our primers did not work as predicted and meant that we often couldn't inspect our transformed cultures without using direct sequencing. Next time we will set more time and resources to checking all our primers work appropriately, although within the time-scale of a ten-week project this can be challenging as by the time you realise there is a problem, the project has significantly progressed.
  • When we started our lab work, the whole team was involved. This has the effect of making the work a bit fractured and disjointed, not to mention complicating the management of samples. In discussion with other teams it became apparent that it was more routine to have only a few members designated to lab duties. We therefore decided to reduce the number of us in the lab, and split off into two groups with each one focusing on a project each. This is something we look to do from the start in 2017.
  • We didn't start our FUEL project until after half of our lab time was up, this really restricted the amount of time we could devote to it. Next time we would aim to split into two lab groups that start at the same together but work independently, which again would improve the management of lab work.

    • Collaborations

  • Provided Oxford with FLIM analysis of their copper chelators.
  • We have quantified ATP production from cells transformed with Washington's phosphoenolpyruvate kinase (PCK) and phosphoglycerate kinase (PGK) constructs

    • Unfortunately we were unable to practically collaborate with Saclay due to failures in our related dCas9. In future years we aim to increase our number of collaborations. We dedicated most of our lab time to cloning our own constructs, which meant there wasn't much time, or manpower left for collaborations.