Difference between revisions of "20.109(F09): Mod 2 Day 3 Tools for system engineering"
From Course Wiki
(→Finding an RBS) |
MAXINE JONAS (Talk | contribs) m (20 revisions: Transfer 20.109(F09) to HostGator) |
||
(One intermediate revision by one user not shown) | |||
Line 4: | Line 4: | ||
==Introduction== | ==Introduction== | ||
[[Image:EvolutionBiolSystem.png|thumb|left]]Biological systems are not static. Thus they can be engineered to account for changing environmental conditions, as we've seen through our examination of two component regulatory systems. In addition, they can be engineered to account for changes that occur as the cells replicate and divide over time. Indeed, evolution of biological systems away from an original specification can be viewed as a curse (it's not like computer scientists have to worry that their software programs change functions when they relaunch them!) or a blessing (evolution can find a solution we didn't ever dream of). Here we'll take the rosy view and try to harness genetic variability to improve the bacterial photography system. In particular we'll screen a library of changes in the Cph8 gene to find ones that either increase the kinasing activity of the sensor when the cells are growing in the dark OR increase the phosphatase activity of the sensor when the cells are growing in the light. The first class of mutants (we'll call them K+) should make the "dark" color of the photographs more dark by increasing the amount of phosphorylated OmpR that stimulates LacZ transcription. The second class of mutants (we'll call these P+) should make the "light" color of the photographs lighter by decreasing the cell's levels of phosphorylated OmpR, thereby decreasing LacZ transcription. | [[Image:EvolutionBiolSystem.png|thumb|left]]Biological systems are not static. Thus they can be engineered to account for changing environmental conditions, as we've seen through our examination of two component regulatory systems. In addition, they can be engineered to account for changes that occur as the cells replicate and divide over time. Indeed, evolution of biological systems away from an original specification can be viewed as a curse (it's not like computer scientists have to worry that their software programs change functions when they relaunch them!) or a blessing (evolution can find a solution we didn't ever dream of). Here we'll take the rosy view and try to harness genetic variability to improve the bacterial photography system. In particular we'll screen a library of changes in the Cph8 gene to find ones that either increase the kinasing activity of the sensor when the cells are growing in the dark OR increase the phosphatase activity of the sensor when the cells are growing in the light. The first class of mutants (we'll call them K+) should make the "dark" color of the photographs more dark by increasing the amount of phosphorylated OmpR that stimulates LacZ transcription. The second class of mutants (we'll call these P+) should make the "light" color of the photographs lighter by decreasing the cell's levels of phosphorylated OmpR, thereby decreasing LacZ transcription. | ||
− | The region of the Cph8 protein to focus on for this purpose has been defined through traditional scientific studies of EnvZ, for example the work from Tom Silhavy's lab( [ | + | The region of the Cph8 protein to focus on for this purpose has been defined through traditional scientific studies of EnvZ, for example the work from Tom Silhavy's lab( [http://openwetware.org/wiki/PMID:_9721293 ] and [[Media:K+P- JBact98.pdf|pdf]] here). We've also been guided by the expertise of MIT's [http://web.mit.edu/biology/www/facultyareas/facresearch/laub.html Mike Laub,] whose lab studies the specificity and rewiring of two component regulatory systems. From these sources, a span of 5 contiguous amino acids can be identified as relevant for shifting the balance of EnvZ to greater kinasing or greater phosphatasing activity. These five residues in EnvZ are Alanine at amino acid 239 ("A239") through Histidine at amino acid 243 ("H243"), where mutations in the flanking residues (A239 and H243) have been shown to enhance the phosphatase activity of EnvZ and mutations in the internal residues (G240 V241 S242) enhance the kinase activity of EnvZ. The amino acid changes that modify the enzymatic activities are indicated on the figure below. Two important notes about these mutations though: First, the balance of kinase to phosphatase activities have been affected by the changes, but the mutations do not shift the reactions to fully "on" or fully "off." Second, the fusion protein of Cph1 to EnvZ, called Cph8, changes the numbering of the residues, as shown in the figure below. It's hoped, however, that the local environment of the region is similar to the natural EnvZ protein. [[Image:EnvZ,Cph8 align.png]]<br> |
To complement the genetic approach for solving biological engineering puzzles, we'll also consider two other approaches in synthetic biology. The first is a [http://www.partsregistry.org/Main_Page Registry of Standard Biological Parts,] essentially a community resource that has some ready-made and useful genetic elements that can be assembled into synthetic biological devices systems. The second approach is to model biological systems, in this case we'll recapitulate the genetic structure of the bacterial photography system using electronic components, making explicit some of the benefits and limitations of such an approach. | To complement the genetic approach for solving biological engineering puzzles, we'll also consider two other approaches in synthetic biology. The first is a [http://www.partsregistry.org/Main_Page Registry of Standard Biological Parts,] essentially a community resource that has some ready-made and useful genetic elements that can be assembled into synthetic biological devices systems. The second approach is to model biological systems, in this case we'll recapitulate the genetic structure of the bacterial photography system using electronic components, making explicit some of the benefits and limitations of such an approach. | ||
Line 24: | Line 24: | ||
#Hold the pulse button until you hear a beep. | #Hold the pulse button until you hear a beep. | ||
#'''Quickly''' remove the cuvette from the holder and '''immediately''' add the 0.5 ml volume of "SOC" media to the cells. Delaying this addition by even 1 minute has been seen to decrease transformation by 3 fold. | #'''Quickly''' remove the cuvette from the holder and '''immediately''' add the 0.5 ml volume of "SOC" media to the cells. Delaying this addition by even 1 minute has been seen to decrease transformation by 3 fold. | ||
− | # Transfer the cells and the media back to an eppendorf tube and place the tubes on the nutator in the | + | # Transfer the cells and the media back to an eppendorf tube and place the tubes on the nutator in the 37 incubator for 1 hour. During this incubation you can work on Parts 2 and 3 of today's protocols. |
− | # Spread 10 ul + 50 ul sterile water on one LB+Cam+Amp petri dishes. Plate 50 ul of the electroporation mix on another LB+Cam+Amp petri dish. One of these two dilutions should have single, well-isolated colonies to examine next time. Incubate the plates at | + | # Spread 10 ul + 50 ul sterile water on one LB+Cam+Amp petri dishes. Plate 50 ul of the electroporation mix on another LB+Cam+Amp petri dish. One of these two dilutions should have single, well-isolated colonies to examine next time. Incubate the plates at 37 in the light or the dark (depending on the mutant you're looking for) until next time. |
===Part 2: Registry of Standard Biological Parts=== | ===Part 2: Registry of Standard Biological Parts=== | ||
Line 35: | Line 35: | ||
The analogy of the DNA as computer code is not perfect. We have to set aside the presumption of an intelligent agent responsible for writing the initial program as well as accept that natural events will change the code over time (evolution leading to genetic variation--the very thing we're trying to harness in the first part of today's lab). And no good tools exist for systematically debugging the genetic code. | The analogy of the DNA as computer code is not perfect. We have to set aside the presumption of an intelligent agent responsible for writing the initial program as well as accept that natural events will change the code over time (evolution leading to genetic variation--the very thing we're trying to harness in the first part of today's lab). And no good tools exist for systematically debugging the genetic code. | ||
− | What would make genetic code easier to write? One idea is to make it a more | + | What would make genetic code easier to write? One idea is to make it a more |