iGEM 2016 NYUSH Description
Vibrio harveyi, a bacterium non-pathogenic to humans, is a primary pathogen for marine animals, including shrimps, lobsters, seahorses, sharks, and sea bass. It can cause eye-lesions, gastro-enteritis, vasculitis, and luminous vibriosis in these animals and in particular, has been a great threat to the shrimp industry. The main goal of our project is to detect the pathogenic bacterium Vibrio harveyi and design a potential antimicrobial agent for it. To do so, we are going to engineer E.coli to manufacture nitric oxide (NO) which is known to have certain antimicrobial effects.
As a first step, we are going to engineer E. coli to detect the presence of the pathogenic bacterium Vibrio harveyi. This means that we are going to use a mutant E. coli strain with a silenced LuxS gene so that this E. coli cannot synthesize its own quorum sensing molecule Autoinducer-2 (AI-2) but is still capable of detecting the AI-2 secreted by the marine pathogen Vibrio harveyi.
We will then further engineer E. coli so that it has a pathway for synthesizing NO by inserting a bacterial Nitric Oxide Synthase (bNOS) gene from Bacillus subtilis into a vector that is then to be transformed into the E. coli. The expression of this gene will be regulated by T7 promoter which is in turn regulated by T7RPol, which is under the control of lsr promoter.
Lsr genes in E. coli are induced once the repressor LsrR is de-repressed. The signalling molecules AI-2, once phosphorylated, de-represses the LsrR repressor. Thus, this means that when the E. coli detects AI-2 from V. harveyi, there is an uptake of AI-2 molecules that are then phosphorylated to phospho-AI-2. These then activate the lsr promoter, which then initiates the synthesis of T7RPol. T7RPol activates the T7 promoter and this initiates the transcription of bNOS. Once transcribed and translated into NOS, NO, an antimicrobial agent for Vibrio harveyi, will be produced.
Before you start:
Please read the following pages:
Styling your wiki
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.
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.
Wiki template information
We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the Pages for awards link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!
Editing your wiki
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!
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:
- State your accomplishments! Tell people what you have achieved from the start.
- Be clear about what you are doing and how you plan to do this.
- You have a global audience! Consider the different backgrounds that your users come from.
- Make sure information is easy to find; nothing should be more than 3 clicks away.
- Avoid using very small fonts and low contrast colors; information should be easy to read.
- 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 iGEM 2016 calendar
- Have lots of fun!
You can also view other team wikis for inspiration! Here are some examples:
Uploading pictures and files
You can upload your pictures and files to the iGEM 2016 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.
When you upload, set the "Destination Filename" to
T--YourOfficialTeamName--NameOfFile.jpg. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)