Virginia Tech/Project

From 2007.igem.org

< Virginia Tech(Difference between revisions)
m
 
(31 intermediate revisions not shown)
Line 1: Line 1:
-
== '''Virginia Tech iGEM 2007''' ==
+
<html><center></html><!--first table: Title and Navigation-->
 +
{| cellspacing="0px" border="0" style="color: #000000; background-color: #FFFFFF;"
-
[https://2007.igem.org/VirginiaTech/Acknowledgements Acknowledgments]
+
<!--first cell of the table: Title-->
 +
| style="padding: 0px; background-color: #FFFFFF;" |
-
[[VirginiaTech/Acknowledgements]]
+
[[Image:Title_project.JPG]]
-
[[VirginiaTech/Project Description]]
+
|}
-
[[VirginiaTech/Team Members]]
+
<!--second table: Navigation-->
 +
{| cellspacing="0px" border="0" style="width: 800px; color: #000000; background-color: #FFFFFF;"
-
[[VirginiaTech/Progress Reports]]
+
<!--first cell of second table: Home-->
 +
| style="padding: 0px; width=50px; background-color: #FFFFFF;" |
-
[[VirginiaTech/Journal Club]]
+
<html><a href="https://2007.igem.org/Virginia_Tech">
 +
<img src="https://static.igem.org/mediawiki/2007/e/ea/Button_home.JPG"/></a></html>[[Image:Dot1.JPG]]
 +
 
 +
<!-- second cell of the second table: The Project-->
 +
| style="background-color: #FFFFFF;" |
 +
 
 +
<html><a href="https://2007.igem.org/Virginia_Tech/Project">
 +
<img src="https://static.igem.org/mediawiki/2007/0/04/Button_project.JPG"/></a></html>[[Image:Dot1.JPG]]
 +
 
 +
<!--third cell of second table: Our Team-->
 +
| style="padding: 0px; width=50px; background-color: #FFFFFF;" |
 +
 
 +
<html><a href="https://2007.igem.org/Virginia_Tech/Team">
 +
<img src="https://static.igem.org/mediawiki/2007/2/2e/Button_team.JPG"/></a></html>[[Image:Dot1.JPG]]
 +
 
 +
<!--fourth cell of second table: Progress-->
 +
| style="padding: 0px; width=50px; background-color: #FFFFFF;" |
 +
 
 +
<html><a href="https://2007.igem.org/Virginia_Tech/Updates">
 +
<img src="https://static.igem.org/mediawiki/2007/3/3b/Button_progress.JPG"/></a></html>[[Image:Dot1.JPG]]
 +
 
 +
<!--fifth cell of second table: Journal Club-->
 +
| style="padding: 0px; width=50px; background-color: #FFFFFF;" |
 +
 
 +
<html><a href="https://2007.igem.org/Virginia_Tech/JC">
 +
<img src="https://static.igem.org/mediawiki/2007/d/d5/Button_jc.JPG"/></a></html>[[Image:Dot1.JPG]]
 +
 
 +
<!--sixth cell of second table: Contributions and Contact-->
 +
| style="padding: 0px; width=50px; background-color: #FFFFFF;" |
 +
 
 +
<html><a href="https://2007.igem.org/Virginia_Tech/Contributions">
 +
<img src="https://static.igem.org/mediawiki/2007/6/69/Button_contribute.JPG"/></a></html><html><a href="mailto:igem@vt.edu"></a></html>
 +
 
 +
|}<html></center></html>
 +
 
 +
<!--third table: Content-->
 +
{| cellspacing="0px" border="0" style="width: 800px; color: #000000; background-color: #FFFFFF;"
 +
 
 +
<!--first cell of the third table: Space-->
 +
| style="width: 100px; background-color: #FFFFFF;" |
 +
 
 +
<!--second cell of the third table: Content-->
 +
| style="padding: 20px; background-color: #FFFFFF;" |
 +
<h3>The original plan for our project was to model the dynamics of the spread of an epidemic within a population. We hoped to make a multi-scale model of epidemic spread and test it in a model population...</h3>
 +
 
 +
[[Image:Airplane.JPG|300px|right]]
 +
Using modern air travel, it is possible to travel around the world, often several times, within the time it takes for a viral infection to show symptoms. This complicates the early detection of epidemics, making it even more important to predict whether an infection will become an epidemic as early as possible. If an infection is "treated" on a worldwide scale early enough, an epidemic could be prevented. Since transportation and communications technology has changed so rapidly in recent years, research needs to be done to find new ways of combating epidemics.
 +
 
 +
With this problem in mind, we set out to revolutionize an approach to modeling epidemics. We wanted our model to be testable, which is vital to verify its accuracy. Therefore, we would not be reliant on historical records like many epidemiological approaches do. These records can be imprecise or inaccurate, and we knew we could get more accurate data from our testable system. We also wanted to make more use of stochastic modeling, using equations that take random variations into account. The event of an infection either becoming an epidemic or dying out in its early stages is a highly random event influenced greatly by small fluctuations among individuals.
 +
 
 +
<h3>A Multi-scale Model</h3>
 +
[[Image:Model_.25moi.JPG|thumb|right|'''Figure 1. Second Scale of the Multi-scale Model.''' E. coli concentration vs. time for the infection with 1 virus per every 4 E. coli cells. The red curve is output from our model and the blue curve is experimental data.]]
 +
The model we built is multi-scale, specifically covering the growth of the host, and the spread of the phage within an isolated subpopulation. We also envisioned a third layer, the spread of the phage between artificially connected subpopulations. Integrating these levels of modeling to produce varying high-level population epidemic behavior by changing low-level parameters is one of the key aspects of our project. Building an understanding of high-level dynamics from the very lowest level of organization will allow us to more accurately predict the epidemiological outcome.
 +
 
 +
<h3>Testing the Model</h3>
 +
[[Image:Red_green.JPG|thumb|left|'''Figure 2. The Reporter Plasmid at Work.''' A strain of ''E. coli'' carrying the reporter plasmid that has been infected with lambda phage. The red cell is lysogenic and the green cell is lytic.]]
 +
An important part of modeling is testing the model to see if it works in real life. To do this, we needed a model host and pathogen system. We decided to use ''E. coli'' and bacteriophage λ (lambda phage) since as a system they are well-studied and cheap and easy to work with. Lambda phage is also interesting because it can either immediately kill the host cell or it can insert its DNA and lie dormant. The decision to stay dormant (lysogeny) or to kill immediately (lysis) added a degree of flexibility to our model that allowed us to check the model robustness for slightly different phage. As part of the project we designed a reporter plasmid to generate florescent proteins and indicate the virus’ decision. This plasmid, along with the use of a phage modified to be florescent, we hoped, would allow us to determine how the population would act and verify our models.
 +
 
 +
 
 +
<center>'''To learn more about our project and progress, see our [[Virginia_Tech/Updates|progress]] page.'''</center>
 +
 
 +
|}<html></center></html>

Latest revision as of 15:12, 26 October 2007

Title project.JPG

Dot1.JPG

Dot1.JPG

Dot1.JPG

Dot1.JPG

Dot1.JPG

The original plan for our project was to model the dynamics of the spread of an epidemic within a population. We hoped to make a multi-scale model of epidemic spread and test it in a model population...

Airplane.JPG

Using modern air travel, it is possible to travel around the world, often several times, within the time it takes for a viral infection to show symptoms. This complicates the early detection of epidemics, making it even more important to predict whether an infection will become an epidemic as early as possible. If an infection is "treated" on a worldwide scale early enough, an epidemic could be prevented. Since transportation and communications technology has changed so rapidly in recent years, research needs to be done to find new ways of combating epidemics.

With this problem in mind, we set out to revolutionize an approach to modeling epidemics. We wanted our model to be testable, which is vital to verify its accuracy. Therefore, we would not be reliant on historical records like many epidemiological approaches do. These records can be imprecise or inaccurate, and we knew we could get more accurate data from our testable system. We also wanted to make more use of stochastic modeling, using equations that take random variations into account. The event of an infection either becoming an epidemic or dying out in its early stages is a highly random event influenced greatly by small fluctuations among individuals.

A Multi-scale Model

Figure 1. Second Scale of the Multi-scale Model. E. coli concentration vs. time for the infection with 1 virus per every 4 E. coli cells. The red curve is output from our model and the blue curve is experimental data.

The model we built is multi-scale, specifically covering the growth of the host, and the spread of the phage within an isolated subpopulation. We also envisioned a third layer, the spread of the phage between artificially connected subpopulations. Integrating these levels of modeling to produce varying high-level population epidemic behavior by changing low-level parameters is one of the key aspects of our project. Building an understanding of high-level dynamics from the very lowest level of organization will allow us to more accurately predict the epidemiological outcome.

Testing the Model

Figure 2. The Reporter Plasmid at Work. A strain of E. coli carrying the reporter plasmid that has been infected with lambda phage. The red cell is lysogenic and the green cell is lytic.

An important part of modeling is testing the model to see if it works in real life. To do this, we needed a model host and pathogen system. We decided to use E. coli and bacteriophage λ (lambda phage) since as a system they are well-studied and cheap and easy to work with. Lambda phage is also interesting because it can either immediately kill the host cell or it can insert its DNA and lie dormant. The decision to stay dormant (lysogeny) or to kill immediately (lysis) added a degree of flexibility to our model that allowed us to check the model robustness for slightly different phage. As part of the project we designed a reporter plasmid to generate florescent proteins and indicate the virus’ decision. This plasmid, along with the use of a phage modified to be florescent, we hoped, would allow us to determine how the population would act and verify our models.


To learn more about our project and progress, see our progress page.