(3 intermediate revisions by 2 users not shown) | |||
Line 33: | Line 33: | ||
This forced us not to think about a specific real world problem but to tackle a technical lock common to all these projects realisations: functionalising cellulose. | This forced us not to think about a specific real world problem but to tackle a technical lock common to all these projects realisations: functionalising cellulose. | ||
</p> | </p> | ||
− | <p>Each | + | <p>Each question could have been addressed using a dedicated physico-chemical or even synthetic biology solutions. However, we considered this an awkward way to solve such a generic problem and we decided to search for a generic and more elegant solution. This is how Cerberus has been brought to life: instead of one construction for each question, we brainstormed creating a solution for all the questions in depth.</p> |
− | <p>In the specifications, the most important features we sought for were | + | <p>In the specifications, the most important features we sought for were genericity and versatility. We found rapidly what molecules should be grafted to cellulose, but they were of a very different nature to be associated through a common property: graphene, antibiotics, carbon nano-tubes, fluorescent proteins or chemicals, paramagnetic beads, etc.</p> |
<h2 class="heavy">Emergence of the Cerberus Platform</h2><hr/> | <h2 class="heavy">Emergence of the Cerberus Platform</h2><hr/> | ||
− | <p>It soon appeared that there were three main properties important for us: (i) to bind cellulose, (ii) to bind organic compounds, (iii) to bind inorganic molecules. This is how we designed a three-headed protein where each head | + | <p>It soon appeared that there were three main properties important for us: (i) to bind cellulose, (ii) to bind organic compounds, (iii) to bind inorganic molecules. This is how we designed a three-headed protein where each head responds to one of these specific questions (and how we chose Cerberus as a name for it!).</p> |
<div class="center"> | <div class="center"> | ||
<img src="https://static.igem.org/mediawiki/2018/d/d1/T--Toulouse-INSA-UPS--ProdDesign--Youn--Fig2.png" style="width:80%; heigth:auto" alt=""/> | <img src="https://static.igem.org/mediawiki/2018/d/d1/T--Toulouse-INSA-UPS--ProdDesign--Youn--Fig2.png" style="width:80%; heigth:auto" alt=""/> | ||
</div> | </div> | ||
− | <p>The cellulose head was the | + | <p>The cellulose head was the easiest to design. Cellulose Binding Domains have already been successfully used by fellow iGEMers (for example, Imperial 2014 or INSA Lyon 2016). This required a little sequence optimization but it was easy.</p> |
− | <p>The next head was the streptavidin domain. Here we had to choose between the classic tetrameric streptavidin and a monomeric streptavidin unsuccessfully used by iGEM UGent Belgium 2016. We tried both. We also added a TEV protease site to add the possibility | + | <p>The next head was the streptavidin domain. Here we had to choose between the classic tetrameric streptavidin and a monomeric streptavidin unsuccessfully used by iGEM UGent Belgium 2016. We tried both. We also added a TEV protease site to add the possibility of releasing the molecule associated with streptavidin.</p> |
<p>The last head was the trickiest. To bind non organic molecules to a protein, we had to search in state-of-the-art synthetic biology concepts, at the interface with chemistry. We ended up with choosing unnatural amino acid incorporation in the Cerberus platform and the use of click chemistry to create covalent bond between inorganic or semi-inorganic compounds and our protein.</p> | <p>The last head was the trickiest. To bind non organic molecules to a protein, we had to search in state-of-the-art synthetic biology concepts, at the interface with chemistry. We ended up with choosing unnatural amino acid incorporation in the Cerberus platform and the use of click chemistry to create covalent bond between inorganic or semi-inorganic compounds and our protein.</p> | ||
<h2 class="heavy">Advantages of the Cerberus Design</h2> | <h2 class="heavy">Advantages of the Cerberus Design</h2> | ||
<hr/> | <hr/> | ||
− | <p>We could have created a specific protein for each of the applications. However, this would have required | + | <p>We could have created a specific protein for each of the applications. However, this would have required analyzing the stability and feasibility of each of them, independently. In contrast, Cerberus is designed with strong stability of its heads but flexibility of the linkers to associate them, which allow compatibility even with complex molecules such as graphene. Besides, there are endless possibilities to modulate the Cerberus structure, for example by replacing one head by another or changing the CBM3a domain by a different domain with another type of affinity. DBCO-DBCO or DBCO-Biotin compounds could also allow the linkage of Cerberus-associated molecules together. So in our opinion, Cerberus could be the basis of many other developments, well beyond cellulose functionalisation.</p> |
<h2 class="heavy">Ensuring the Project Success</h2> | <h2 class="heavy">Ensuring the Project Success</h2> | ||
<hr/> | <hr/> | ||
− | <p>All iGEM teams have great ideas and concepts, but the competition is a big challenge in a very short | + | <p>All iGEM teams have great ideas and concepts, but the competition is a big challenge in a very short period of time. We were lucky to succeed in demonstrating the Cerberus efficiency (see Demonstrate), but this is not only about luck. Here are the reasons which had improved our chances to do well. </p> |
<ol> | <ol> | ||
− | <li><strong>Modelling.</strong> Cerberus was trickier to design than | + | <li><strong>Modelling.</strong> Cerberus was trickier to design than we had expected. We had no idea about the reactivity and conformational problem that could issue from the unnatural amino acid. The Cerberus linkers that bind the domains altogether could have easily destabilized the whole protein too. Modelling was therefore a great way to assess <i>in silico </i>that we were going in the right direction (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Model">Model section</a> ).</li> |
− | <li><strong>Human Practices.</strong> These were central for us. Downstream of the project, the interaction with the public and society | + | <li><strong>Human Practices.</strong> These were central for us. Downstream of the project, the interaction with the public and society reassured us of the importance of what we were trying to achieve. Upstream of the project, the IHP helped us a lot for the project fine tuning and feasibility (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Human_Practices">Human Practices section</a>).</li> |
<li><strong>Division of the project in modules.</strong> This is classically done by iGEM teams and this is indeed a crucial point to ensure that the whole project is not stuck because of one of its aspects (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Design">Design section</a>).</li> | <li><strong>Division of the project in modules.</strong> This is classically done by iGEM teams and this is indeed a crucial point to ensure that the whole project is not stuck because of one of its aspects (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Design">Design section</a>).</li> | ||
− | <li><strong>Multiplying the strategies.</strong> We chose for example to try both tetrameric and monomeric streptavidin. Likewise, we tried both production by <i>E. coli </i>and by the yeast <i>P. pastoris</i>. So yes, this is extra work to do, but | + | <li><strong>Multiplying the strategies.</strong> We chose for example to try both tetrameric and monomeric streptavidin. Likewise, we tried both production by <i>E. coli </i>and by the yeast <i>P. pastoris</i>. So yes, this is extra work to do, but finally, tetrameric streptavidin never worked in our hands, and <i>P. pastoris</i> production was disappointing too. Therefore, we could have easily failed the whole project without this multiplication of strategies (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Results">Results section</a>).</li> |
<li><strong>Multiplying the assays.</strong> We had choices to make about what functions we wanted to graft on cellulose. We tried several of them. Some succeeded rapidly (fluorescence, magnetism), some still need improvements (antibiotic), and some took too long to be completed (graphene, carbon nanotubes). Multiplying the assays improved our chances to succeed in a very short and required schedule (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Demonstrate">Demonstrate section</a> ).</li> | <li><strong>Multiplying the assays.</strong> We had choices to make about what functions we wanted to graft on cellulose. We tried several of them. Some succeeded rapidly (fluorescence, magnetism), some still need improvements (antibiotic), and some took too long to be completed (graphene, carbon nanotubes). Multiplying the assays improved our chances to succeed in a very short and required schedule (see the <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Demonstrate">Demonstrate section</a> ).</li> | ||
</ol> | </ol> | ||
Line 61: | Line 61: | ||
<h2 class="heavy">Rupture Technology and Lifecycle</h2> | <h2 class="heavy">Rupture Technology and Lifecycle</h2> | ||
<hr/> | <hr/> | ||
− | <p>We thoroughly investigated the many consequences of Cerberus for the environment, the manufacturer and the end user’s everyday life through our ethical analysis (see <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Human_Practices">IHP section</a>) and Entrepreneurship efforts (see <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Entrepreneurship">Entrepreneurship section</a>). These were essential but difficult exercises since the possibilities and applications issued from Cerberus are so large and hard to anticipate. Nevertheless, it | + | <p>We thoroughly investigated the many consequences of Cerberus for the environment, the manufacturer and the end user’s everyday life through our ethical analysis (see <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Human_Practices">IHP section</a>) and Entrepreneurship efforts (see <a href="https://2018.igem.org/Team:Toulouse-INSA-UPS/Entrepreneurship">Entrepreneurship section</a>). These were essential but difficult exercises since the possibilities and applications issued from Cerberus are so large and hard to anticipate. Nevertheless, it reassured us in both the innovations made possible by Cerberus and the improvement it will be for groundbreaking processes. It opens up so many possibilities that everyone is excited about what it could bring to each of us in a future which is now envisigable.</p> |
Line 70: | Line 70: | ||
<div id="NAV_ICON_BAR" class="nav-left-col sticky-bottom d-none d-xl-block"> | <div id="NAV_ICON_BAR" class="nav-left-col sticky-bottom d-none d-xl-block"> | ||
<ul class="nav justify-content-center"> | <ul class="nav justify-content-center"> | ||
− | + | ||
− | + | <li class="nav-item"> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
<!--Anchor to TOP--> | <!--Anchor to TOP--> | ||
<a class="nav-link ico" href="#TOP"> | <a class="nav-link ico" href="#TOP"> | ||
Line 82: | Line 77: | ||
</a> | </a> | ||
</li> | </li> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</ul> | </ul> | ||
</div> | </div> |
Latest revision as of 21:14, 17 October 2018
PRODUCT DESIGN
Our Problematic(s!)
A specificity of our project is that we did not start its construction from a single problematic but we actually started from a multiplicity of problems. For example:
- How to produce band aids with antibiotics?
- How to produce paper on which we can print electronic circuit boards?
- How to create new fluorescent fabrics?
- How to create packaging exhaling the smell of the food inside?
- How to manufacture feminine protection preventing toxic shock syndrom?
and so on
This forced us not to think about a specific real world problem but to tackle a technical lock common to all these projects realisations: functionalising cellulose.
Each question could have been addressed using a dedicated physico-chemical or even synthetic biology solutions. However, we considered this an awkward way to solve such a generic problem and we decided to search for a generic and more elegant solution. This is how Cerberus has been brought to life: instead of one construction for each question, we brainstormed creating a solution for all the questions in depth.
In the specifications, the most important features we sought for were genericity and versatility. We found rapidly what molecules should be grafted to cellulose, but they were of a very different nature to be associated through a common property: graphene, antibiotics, carbon nano-tubes, fluorescent proteins or chemicals, paramagnetic beads, etc.
Emergence of the Cerberus Platform
It soon appeared that there were three main properties important for us: (i) to bind cellulose, (ii) to bind organic compounds, (iii) to bind inorganic molecules. This is how we designed a three-headed protein where each head responds to one of these specific questions (and how we chose Cerberus as a name for it!).
The cellulose head was the easiest to design. Cellulose Binding Domains have already been successfully used by fellow iGEMers (for example, Imperial 2014 or INSA Lyon 2016). This required a little sequence optimization but it was easy.
The next head was the streptavidin domain. Here we had to choose between the classic tetrameric streptavidin and a monomeric streptavidin unsuccessfully used by iGEM UGent Belgium 2016. We tried both. We also added a TEV protease site to add the possibility of releasing the molecule associated with streptavidin.
The last head was the trickiest. To bind non organic molecules to a protein, we had to search in state-of-the-art synthetic biology concepts, at the interface with chemistry. We ended up with choosing unnatural amino acid incorporation in the Cerberus platform and the use of click chemistry to create covalent bond between inorganic or semi-inorganic compounds and our protein.
Advantages of the Cerberus Design
We could have created a specific protein for each of the applications. However, this would have required analyzing the stability and feasibility of each of them, independently. In contrast, Cerberus is designed with strong stability of its heads but flexibility of the linkers to associate them, which allow compatibility even with complex molecules such as graphene. Besides, there are endless possibilities to modulate the Cerberus structure, for example by replacing one head by another or changing the CBM3a domain by a different domain with another type of affinity. DBCO-DBCO or DBCO-Biotin compounds could also allow the linkage of Cerberus-associated molecules together. So in our opinion, Cerberus could be the basis of many other developments, well beyond cellulose functionalisation.
Ensuring the Project Success
All iGEM teams have great ideas and concepts, but the competition is a big challenge in a very short period of time. We were lucky to succeed in demonstrating the Cerberus efficiency (see Demonstrate), but this is not only about luck. Here are the reasons which had improved our chances to do well.
- Modelling. Cerberus was trickier to design than we had expected. We had no idea about the reactivity and conformational problem that could issue from the unnatural amino acid. The Cerberus linkers that bind the domains altogether could have easily destabilized the whole protein too. Modelling was therefore a great way to assess in silico that we were going in the right direction (see the Model section ).
- Human Practices. These were central for us. Downstream of the project, the interaction with the public and society reassured us of the importance of what we were trying to achieve. Upstream of the project, the IHP helped us a lot for the project fine tuning and feasibility (see the Human Practices section).
- Division of the project in modules. This is classically done by iGEM teams and this is indeed a crucial point to ensure that the whole project is not stuck because of one of its aspects (see the Design section).
- Multiplying the strategies. We chose for example to try both tetrameric and monomeric streptavidin. Likewise, we tried both production by E. coli and by the yeast P. pastoris. So yes, this is extra work to do, but finally, tetrameric streptavidin never worked in our hands, and P. pastoris production was disappointing too. Therefore, we could have easily failed the whole project without this multiplication of strategies (see the Results section).
- Multiplying the assays. We had choices to make about what functions we wanted to graft on cellulose. We tried several of them. Some succeeded rapidly (fluorescence, magnetism), some still need improvements (antibiotic), and some took too long to be completed (graphene, carbon nanotubes). Multiplying the assays improved our chances to succeed in a very short and required schedule (see the Demonstrate section ).
Rupture Technology and Lifecycle
We thoroughly investigated the many consequences of Cerberus for the environment, the manufacturer and the end user’s everyday life through our ethical analysis (see IHP section) and Entrepreneurship efforts (see Entrepreneurship section). These were essential but difficult exercises since the possibilities and applications issued from Cerberus are so large and hard to anticipate. Nevertheless, it reassured us in both the innovations made possible by Cerberus and the improvement it will be for groundbreaking processes. It opens up so many possibilities that everyone is excited about what it could bring to each of us in a future which is now envisigable.
No dogs were harmed over the course of this iGEM project.
The whole Toulouse INSA-UPS team wants to thank our sponsors, especially:
And many more. For futher information about our sponsors, please consult our Sponsors page.
The content provided on this website is the fruit of the work of the Toulouse INSA-UPS iGEM Team. As a deliverable for the iGEM Competition, it falls under the Creative Commons Attribution 4.0. Thus, all content on this wiki is available under the Creative Commons Attribution 4.0 license (or any later version). For futher information, please consult the official website of Creative Commons.
This website was designed with Bootstrap (4.1.3). Bootstrap is a front-end library of component for html, css and javascript. It relies on both Popper and jQuery. For further information, please consult the official website of Bootstrap.