Difference between revisions of "Team:Evry Paris-Saclay/Description"

Line 17: Line 17:
 
An engineering-ready specific communication system like ours could also be useful within the framework of distributed biological computing. Instead of implementing complex molecular circuits in one cell, it would enable bioengineers to implement simpler circuits in multiple cells of a consortium and integrate circuit outputs later. This would make building large-scale circuits easier to implement, more modular and less noisy, while reducing the expression burden on individual cells (<i>Macía et al., 2012 Trends Biotechnol 30, 342-349</i>). In practical terms, the envisioned bacterial communication system would have numerous benefits, some of them relevant to the fields of biomedicine (Kim et al., 2018, bioRxiv 308734), bioengineering and bioremediation (<i>Macia & Sole, 2014, PLoS ONE 9, e81248</i>). It would also enable new ways of engineering multicellular biomaterials, such as biofilms or tissue architectures (<i>Macia & Sole, 2014, PLoS ONE 9, e81248</i>).
 
An engineering-ready specific communication system like ours could also be useful within the framework of distributed biological computing. Instead of implementing complex molecular circuits in one cell, it would enable bioengineers to implement simpler circuits in multiple cells of a consortium and integrate circuit outputs later. This would make building large-scale circuits easier to implement, more modular and less noisy, while reducing the expression burden on individual cells (<i>Macía et al., 2012 Trends Biotechnol 30, 342-349</i>). In practical terms, the envisioned bacterial communication system would have numerous benefits, some of them relevant to the fields of biomedicine (Kim et al., 2018, bioRxiv 308734), bioengineering and bioremediation (<i>Macia & Sole, 2014, PLoS ONE 9, e81248</i>). It would also enable new ways of engineering multicellular biomaterials, such as biofilms or tissue architectures (<i>Macia & Sole, 2014, PLoS ONE 9, e81248</i>).
 
</p>
 
</p>
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
+
<br />
<p>___________________________________________________________________________________________________________</p>
+
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
 
+
</div>
+
 
+
 
+
 
+
<div class="column two_thirds_size">
+
<h3>What should this page contain?</h3>
+
<ul>
+
<li> A clear and concise description of your project.</li>
+
<li>A detailed explanation of why your team chose to work on this particular project.</li>
+
<li>References and sources to document your research.</li>
+
<li>Use illustrations and other visual resources to explain your project.</li>
+
</ul>
+
</div>
+
 
+
<div class="column third_size" >
+
<div class="highlight decoration_A_full">
+
<h3>Inspiration</h3>
+
<p>See how other teams have described and presented their projects: </p>
+
 
+
<ul>
+
<li><a href="https://2016.igem.org/Team:Imperial_College/Description">2016 Imperial College</a></li>
+
<li><a href="https://2016.igem.org/Team:Wageningen_UR/Description">2016 Wageningen UR</a></li>
+
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> 2014 UC Davis</a></li>
+
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">2014 SYSU Software</a></li>
+
</ul>
+
</div>
+
</div>
+
 
+
 
+
 
+
 
+
<div class="column two_thirds_size" >
+
<h3>Advice on writing your Project Description</h3>
+
 
+
<p>
+
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be concise, accurate, and unambiguous in your achievements.
+
</p>
+
 
+
</div>
+
 
+
<div class="column third_size">
+
<h3>References</h3>
+
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you thought about your project and what works inspired you.</p>
+
 
+
</div>
+
 
+
 
+
 
+
 
+
 
+
  
 
</html>
 
</html>

Revision as of 19:52, 29 June 2018


TO CONTACT US
Genopole Campus 1, Batiment 6, 91030 Evry Cedex, France
+33 7 69 96 68 31
igemevry@gmail.com

© Copyright 2018
Design & Developpement by
IGEM EVRY GENOPOLE

Description

Our project aims to build a synthetic intercellular communication system. In natural ecosystems, there already exist several mechanisms which bacteria utilize to interact among themselves for latency, reproduction, or survival. Bacteria can produce signaling molecules that are sensed by others of their species, or even of other species, to trigger a molecular response. These communication systems can be engineered to regulate and automatize industrial bioprocesses. An important feature that would help achieve this goal is the orthogonality of the signaling molecules. The more specific the send-sense system is, the more efficiently the response of the targeted microorganism can be engineered.

We find the recently described phage communication system to be a good candidate for synthetic cell-cell interaction (Zohar et al., 2017 Nature 541, 488-493). The system uses a secreted peptide called “arbitrium” to control phage-mediated bacterial lysis. The principal genes in charge of this regulated lysis have been validated in phage Phi3T and B. subtilis. However, to our knowledge there are 17 orthologous genes that encode similar peptides and their receptors, which have not yet been characterized. A key part of our project goals is to characterize a library of these different arbitrium peptides and their receptors for orthogonality. This will help identify unique peptide-receptor pairs that do not exhibit cross-talk for future use in engineering of unambiguous cell-cell communication. Additionally, we will test and expand the use of the peptide-based communication system from Bacillus to E. coli, a more widely used model bacterium. This will benefit many academic and industrial projects by enabling multiple parallel channels of communication between cells.

The newly validate communication system will be also be integrated into a co-culture of two different species of bacteria. Co-culturing more than one microorganism has been used as a strategy for mainly industrial process. It has been shown that the engineered co-culture displays robustness, tolerance for toxic metabolic waste and resistance to stress conditions (Goers et al., 2014, J R Soc Interface 11, 20140065). Moreover, engineered co-cultures can be used for many other applications such as biocatalysis or bioremediation, bioproduction of high-valued compound with metabolic engineering, complex protein expression, among others.

An engineering-ready specific communication system like ours could also be useful within the framework of distributed biological computing. Instead of implementing complex molecular circuits in one cell, it would enable bioengineers to implement simpler circuits in multiple cells of a consortium and integrate circuit outputs later. This would make building large-scale circuits easier to implement, more modular and less noisy, while reducing the expression burden on individual cells (Macía et al., 2012 Trends Biotechnol 30, 342-349). In practical terms, the envisioned bacterial communication system would have numerous benefits, some of them relevant to the fields of biomedicine (Kim et al., 2018, bioRxiv 308734), bioengineering and bioremediation (Macia & Sole, 2014, PLoS ONE 9, e81248). It would also enable new ways of engineering multicellular biomaterials, such as biofilms or tissue architectures (Macia & Sole, 2014, PLoS ONE 9, e81248).