Team:UC Davis/Modeling
From 2010.igem.org
(Difference between revisions)
(Prototype team page) |
|||
Line 1: | Line 1: | ||
- | + | {{Team:UC_Davis/Head}} | |
+ | |||
+ | <html> | ||
+ | <head> | ||
+ | </head> | ||
+ | <style type="text/css"> | ||
+ | |||
+ | .projects | ||
+ | { | ||
+ | border: 2px solid #99dd66; | ||
+ | width: 690px; | ||
+ | } | ||
+ | |||
+ | .projects td | ||
+ | { | ||
+ | border: 2px solid #99dd66; | ||
+ | text-align: center; | ||
+ | } | ||
+ | |||
+ | .projectBanner | ||
+ | { | ||
+ | width: 690px; | ||
+ | } | ||
+ | |||
+ | .version{ | ||
+ | font-family: arial; | ||
+ | font-size: 13px; | ||
+ | color: #65983E; | ||
+ | } | ||
+ | |||
+ | </style> | ||
+ | |||
+ | <script src="http://code.jquery.com/jquery-1.4.2.min.js"></script> | ||
+ | <script text="javascript"> | ||
+ | |||
+ | |||
+ | function tabFunction(tab) | ||
+ | { | ||
+ | var crosstalkContent = "<br/><p class='header'>THE PROBLEM</p>In synthetic biology, the issue of crosstalk acts as a substantial barrier against developing fully-controlled biological systems. Much like in the development of electrical systems where crosstalk causes harmful interference and unpredictable behavior, crosstalk prevents us from completely understanding how our biological constructs function, and quite often can affect the efficacy of these systems. As such, it is clear that a method to computationally predict crosstalk in a given biological system would be a valuable scientific resource, and would effectively help minimize the negative effects of crosstalk. This is where our computational tool, CPOTATo, comes in.<br/><br/><div style='text-align: center;'><img src='https://static.igem.org/mediawiki/2010/c/c3/CPPaperScreen1.jpg'></div><br/>Crosstalk can be attributed to several aspects of biological systems, one of which is the interaction between proteins from the synthetic circuit and proteins from the host organism. CPOTATo (Crosstalk Predictive Organism-Targeted Analysis Tool) takes advantage of this fact in an attempt to predict protein combinations that may cause crosstalk in various biological systems.<br/><br/>The primary reason for the crosstalk between proteins is usually the homology between them. Consider the following abstract example: In the chassis' system, Protein A naturally interacts with Protein B; however, Protein C, a protein produced by the synthetic circuit we wish to implant, is very homologous to Protein A. Since Protein A and Protein C are very similar, there is a certain degree of probability that Protein C will interact with Protein B. Therefore, unless Protein C's original purpose was to interact with Protein B, this is an undesirable interaction that may lead to unpredictable crosstalk.<br/><br/><p class='header'>APPROACH</p>CPOTATo executes several consecutive database queries to different existing databases of genomic information in order to infer any instances of crosstalk based on protein-protein relationships. The tool relies on two inputs: the amino acid sequence of the target protein, and the target organism or chassis. We query 3 individual databases in order to obtain the information we need: Interpro, UniprotKB and String.<br/><br/>From the Interpro database, we obtain one or more Interpro entries, each of which consists of a group of proteins homologous to our target protein. We then use these Interpro entries as the query parameter to the UniprotKB database in order to filter out all proteins that are not produced within the chassis. And finally, we query the String database with each of the remaining proteins to obtain the final list of interactions involving each of these homologous proteins and the target protein.<br/><br/><div style='text-align:center'><img src='https://static.igem.org/mediawiki/2010/c/c6/CPPaperScreen2.jpg'></div><p class='header'>SCORES</p>The finalization of the numerical score analysis is still pending. See the Changelog.<br/><br/><p class='header'>Changelog</p><div class='version'>v0.1.0:</div> Queries completed. Some documented cases of crosstalk have been run through the tool, and the results are consistent with what's in the literature. Score system is still in development."; | ||
+ | |||
+ | |||
+ | var pHContent = "<br/><p class='header'>THE PROBLEM</p>Cellular machines are not isolated systems. They have an intimate relationship with their surroundings and must change with varying environmental conditions. To do this, they rely on sensory machinery to trigger internal responses based on external stimuli such as light, chemical concentrations, etc. Sensors have been engineered for the E. coli chassis but one stimulus has been neglected: pH.<br/><br/> Cells thrive in a limited pH range; the optimal range for E. coli being 6-7. If the pH is much different than this, the cell must take action to survive. This needs to be taken into account when designing cellular machines which are reactive to pH changes. A pH sensitive system from another organism would help keep the engineered response independent. This would allow the desired response to be separate from a native stress response. <br/><br/><div style='text-align:center'><img src='https://static.igem.org/mediawiki/2010/a/ac/Mes_photo.jpg'></div><br/><br/><p class='header'>APPROACH</p>In the native host, Agrobacterium tumefaciens, the pH sensing machinery is a two component system consisting of the ChvG and ChvI genes. ChvG is the membrane bound histidine kinase and ChvI is the chromosomal response regulatory gene. The pH sensing machinery is flawlessly intertwined in the vast number of other simultaneously occurring processes. Ideally, it could be transplanted into E. coli without affecting any other pathway, although the possibility of this happening is next to none. We do not know how the construct will behave in it's new environment, but we do expect some unwanted crosstalk caused by differing pH and phosphate levels within the new host.<br/><br/>Four promoters are likely to be activated by the ChvG/ChvI in A. tumefaciens: KatA, ImpA, ChvG, and AopB. We took these sequences and placed them upstream of RFP to measure the extent to which they are activated in E. coli. Another promoter, PhoA from the PhoB/PhoR two component system was also chosen to be tested with the ChvG/ChvI construct since both two-component systems are similar. We expect some activation of the PhoA promoter at high phosphate levels when the PhoB/PhoR system is deactivated."; | ||
+ | |||
+ | var spatialContent = "<br/><p class='header'>MOTIVATION</p>Patterns are everywhere in biology. Some, like zebra stripes, are easy to see, while other patterns like those that appear during animal development may be more subtle. Underneath the expression of these patterns are complex genetic networks that interpret specific cues from the environment and use this data to direct cells, or even populations of cells, to self organize and act.<br/><p class='header'>THE PROJECT</p>Given the importance of pattern generation in biology, we wanted to see if we could construct a synthetic circuit that would allow us to generate patterns in a community of inter-communicating cells in response to a simple stimuli; in our case, this stimuli would be light.<br/><br/>In order to mimic the process by which groups of cells can communicate to ultimately form a pattern, we will be using a lawn of E. Coli cells as our multicellular model system. These cells would be designed to communicate with each other through quorum sensing, and based on the small signaling molecules that each cell \"patch\" produces, the subsequent cell patch will know whether to activate or remain inactive.<br/><br/>In our system, the activated cells would produce colored pigment in order to indicate that they have been activated, and the cells that remain inactive will produce no color. In this way, the lawn of E. Coli cells would produce an oscillatory pattern of active and inactive \"bands\" of color and no color. "; | ||
+ | |||
+ | switch(tab) | ||
+ | { | ||
+ | case 1: | ||
+ | $("#projectContent").fadeOut("slow", function() { document.getElementById("projectContent").innerHTML =spatialContent;}).fadeIn("slow"); | ||
+ | $("#projectBanner").fadeOut("slow", function() { document.getElementById("projectBanner").innerHTML = "<img src='https://static.igem.org/mediawiki/2010/9/9d/SObanner2.jpg' width='689px' height='100px'>";}).fadeIn("slow"); | ||
+ | |||
+ | break; | ||
+ | case 2: | ||
+ | $("#projectContent").fadeOut("slow", function() { document.getElementById("projectContent").innerHTML = pHContent;}).fadeIn("slow"); | ||
+ | $("#projectBanner").fadeOut("slow", function() { document.getElementById("projectBanner").innerHTML = "<img src='https://static.igem.org/mediawiki/2010/a/a8/PhBanner.jpg' width='689px'' height='100px'>";}).fadeIn("slow"); | ||
+ | break; | ||
+ | case 3: | ||
+ | $("#projectContent").fadeOut("slow", function() { document.getElementById("projectContent").innerHTML = crosstalkContent;}).fadeIn("slow"); | ||
+ | $("#projectBanner").fadeOut("slow", function() { document.getElementById("projectBanner").innerHTML = "<img src='https://static.igem.org/mediawiki/2010/b/b1/CrosstalkBanner.jpg' width='689px' height='100px'>";}).fadeIn("slow"); | ||
+ | break; | ||
+ | default: | ||
+ | document.getElementById("projectContent").innerHTML = spatialContent; | ||
+ | break; | ||
+ | } | ||
+ | } | ||
+ | |||
+ | </script> | ||
+ | |||
+ | <body onload="tabFunction()"> | ||
+ | <table class="pikachu"> | ||
+ | <tr> | ||
+ | <td width="685px"> | ||
+ | <table class="projects"> | ||
+ | <tr> | ||
+ | <td width='33%'><a onclick="tabFunction(1)" style="cursor:pointer">Spatial Oscillation</a></td> | ||
+ | <td width='33%'><a onclick="tabFunction(2)" style="cursor:pointer">pH Sensor</a></td> | ||
+ | <td width='33%'><a onclick="tabFunction(3)" style="cursor:pointer">Crosstalk Predictor</a></td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <table width="690px"> | ||
+ | <tr><th><div id="projectBanner"><img src="https://static.igem.org/mediawiki/2010/9/9d/SObanner2.jpg" width="689px"></div></th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td> | ||
+ | <div id="projectContent"> | ||
+ | Spatial Oscillation | ||
+ | </div> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <td> | ||
+ | <table class="pikachu" width="280px"><tr><th><img class="marth" src="/wiki/images/0/00/Sponsors.jpg" width="280px"></th></tr> | ||
+ | <tr> | ||
+ | <td class="kirby" align="center"></html>{{Team:UC_Davis/sponsors}}<html> | ||
+ | </td></tr></table> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | |||
+ | </body> | ||
+ | </html> |
Revision as of 04:28, 12 October 2010
|
|
|