|
|
| Line 59: |
Line 59: |
| | </div> <!--This is the closing tag for main container --> | | </div> <!--This is the closing tag for main container --> |
| | | | |
| − | <!--
| |
| − | <h4>Before you start: </h4>
| |
| − | <p> Please read the following pages:</p>
| |
| − | <ul>
| |
| − | <li> <a href="https://2015.igem.org/Requirements">Requirements page </a> </li>
| |
| − | <li> <a href="https://2015.igem.org/Wiki_How-To">Wiki Requirements page</a></li>
| |
| − | </ul>
| |
| − |
| |
| − | <div class="highlightBox">
| |
| − | <h4> Styling your wiki </h4>
| |
| − | <p>You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.</p>
| |
| − | <p>While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.</p>
| |
| − | </div>
| |
| − |
| |
| − | <h4> Editing your wiki </h4>
| |
| − | <p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>
| |
| − | <p> <a href="https://2015.igem.org/wiki/index.php?title=Team:IIT_Madras&action=edit"> Click here to edit this page! </a></p>
| |
| − | <p>See tips on how to edit your wiki on the <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template Documentation</a> page.</p>
| |
| − |
| |
| − |
| |
| − | <h4>Templates </h4>
| |
| − | <p> This year we have created templates for teams to use freely. More information on how to use and edit the templates can be found on the
| |
| − | <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template Documentation </a> page.</p>
| |
| − |
| |
| − |
| |
| − | <h4>Tips</h4>
| |
| − | <p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
| |
| − | <ul>
| |
| − | <li>State your accomplishments! Tell people what you have achieved from the start. </li>
| |
| − | <li>Be clear about what you are doing and how you plan to do this.</li>
| |
| − | <li>You have a global audience! Consider the different backgrounds that your users come from.</li>
| |
| − | <li>Make sure information is easy to find; nothing should be more than 3 clicks away. </li>
| |
| − | <li>Avoid using very small fonts and low contrast colors; information should be easy to read. </li>
| |
| − | <li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2015.igem.org/Calendar_of_Events">iGEM 2015 calendar</a> </li>
| |
| − | <li>Have lots of fun! </li>
| |
| − | </ul>
| |
| − |
| |
| − | <h4>Inspiration</h4>
| |
| − | <p> You can also view other team wikis for inspiration! Here are some examples:</p>
| |
| − | <ul>
| |
| − | <li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
| |
| − | <li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
| |
| − | <li> <a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a> </li>
| |
| − | <li> <a href="https://2014.igem.org/Team:Michigan"> 2014 Michigan</a></li>
| |
| − | <li> <a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara </a></li>
| |
| − | <li> <a href="https://2014.igem.org/Team:SCU-China"> 2014 SCU-China </a></li>
| |
| − | </ul>
| |
| − | <h4> Uploading pictures and files </h4>
| |
| − | <p> You can upload your pictures and files to the iGEM 2015 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
| |
| − | When you upload, set the "Destination Filename" to <code>Team:YourOfficialTeamName/NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
| |
| − |
| |
| − | <a href="https://2015.igem.org/Special:Upload">CLICK HERE TO UPLOAD FILES</a>
| |
| − |
| |
| − |
| |
| − | </div></div> <!--These are the closing tags for div id="mainContainer" and div id="contentContainer". The corresponding opening tags appear in the template that is {{included}} at the top of this page.-->
| |
| | </body> | | </body> |
| | </html> | | </html> |
The Problem
Our iGEM project aims to tackle the emerging problem of antibiotic resistance by leveraging
the power of natural selection under selective pressure. It is known that higher exposure
to antibiotics leads to the resistance against that antibiotic in bacterial populations.
Anti microbial peptides are small protein molecules that have been shown to have anti-microbial
activity. They are also also known to exhibit lower tendency to develop antibiotic resistance.
Recently, However, it has also been reported that a prolonged exposure to anti-microbial peptides
could also lead to the emergence of resistance in bacteria
Our Solution
Here, we come up with a solution to this problem. We will synthesize a bacterial system that:
- Senses the cell density of pathogenic bacteria
- Our system releases anti-microbial peptides which kill pathogens, when it has sensed high cell density
- As the population goes down we release a peptide that neutralizes the activity of anti-microbial
peptides, resulting into a stress free environment.The stress-free environment would be favourable to
the wild type compared to the mutants which have developed antibiotic resistance
Consequentially this will lead to a population of predominantly wild type bacteria. Again, as the
population of wild type goes up, the same cycle of steps 1-3 is repeated. After few cycles, the pathogens
should be eliminated.
The system we propose will use an anti microbial peptide Alyteserin, which has bactericidal
effects. Alyteserin has a lethal effect on gram negative bacteria.[Ref. 2] We have designed a
novel short peptide sequence(which shall be called NAly from herein). Molecular Dynamics
simulations of Alyteserin and NAly have been performed under various conditions and conformations,
and we have found that the two peptides interact favourably.
The pathogen of interest, which has to be a gram negative bacterium in this case was chosen to
be E.Coli. We chose E.Coli for its ease of availability in a laboratory setting, but Alyteserin
is a broad antimicrobial peptide and is effective against a wide range of gram negative bacteria
including E.Coli and Salmonella Typhi.
We chose the carrier of the AMP to be Lactococcus Lactis, for several reasons. L.lactis is a
gram positive bacterium. This ensures that the AMP would not have lethal effects on L. lactis
itself. Also, L.lactis is a non-pathogenic bacteria, and will not elicit an inflammatory response
from the human immune system. Developing the genetic circuit for timed release of AMP and its
inhibitory molecule inside L.lactis will provide more scope in the future for developement of a robust
drug delivery system.
