Calgary/evoGEM introduction
From 2007.igem.org
Line 1: | Line 1: | ||
<html> | <html> | ||
+ | <!-- | ||
+ | evoGEM Introduction | ||
+ | This page introduces the evoGEM project, provides some background on evolutionary computing and suggests why this project is significant | ||
+ | --> | ||
<head> | <head> | ||
+ | <!-- | ||
+ | Cascading Style Sheet (CSS) component | ||
+ | in plain html style sheets are completely independent of the HTML page but are included in this page to simplify design within a wiki script environment. | ||
+ | This section describes the layout, colors and images displayed on the page | ||
+ | --> | ||
<style> | <style> | ||
Line 65: | Line 74: | ||
</head> | </head> | ||
<body> | <body> | ||
+ | |||
+ | <!-- | ||
+ | evoGEM Title | ||
+ | The title and and top level navigation links | ||
+ | --> | ||
<table class="header"> | <table class="header"> | ||
<tr> | <tr> | ||
Line 72: | Line 86: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | <!-- | ||
+ | evoGEM main menu | ||
+ | The navigation menu for the evoGEM section of the site | ||
+ | --> | ||
<table class="links" > | <table class="links" > | ||
<tr> | <tr> | ||
Line 95: | Line 113: | ||
</p> | </p> | ||
<p><b>Our Goals For EvoGEM</b></p> | <p><b>Our Goals For EvoGEM</b></p> | ||
- | <p> | + | <p> The main goal for this project will be to develop EvoGEM |
- | The main goal for this project will be to develop EvoGEM | + | to use evolutionary design,effecient mutation operators on |
- | to use evolutionary design,effecient mutation operators on | + | these circuits and an effecient fitness function that can solve |
- | these circuits and an effecient fitness function that can solve | + | the relatively simple problem of synthesizing a requested |
- | the relatively simple problem of synthesizing a requested | + | molecule considering the existing iGEM bio-bricks. The problem |
- | molecule considering the existing iGEM bio-bricks. The problem | + | can be easy or more challenging depending on whether or |
- | can be easy or more challenging depending on whether or | + | not the molecule is the result of a pathway. The system |
- | not the molecule is the result of a pathway. The system | + | would be designed to solve both possibilities. </p> |
- | would be designed to solve both possibilities. | + | |
- | </p> | + | |
<p><b>Why This Could Be Important</b></p> | <p><b>Why This Could Be Important</b></p> | ||
- | <p> | + | <p> It is important to notice that with such a problem being |
- | It is important to notice that with such a problem being | + | investigated, it is easy for a human to find a solution if |
- | investigated, it is easy for a human to find a solution if | + | given a small number of components and a simple prededefined |
- | given a small number of components and a simple prededefined | + | behavior that is guaranteed to lie in a certain permutation of |
- | behavior that is guaranteed to lie in a certain permutation of | + | these components. However, as the number of available bio- |
- | these components. However, as the number of available bio- | + | bricks increases, and the potential grows, it becomes harder |
- | bricks increases, and the potential grows, it becomes harder | + | and harder to think of several different designs that would |
- | and harder to think of several different designs that would | + | work. With thousands of bio-bricks in the iGEM registry |
- | work. With thousands of bio-bricks in the iGEM registry | + | disposal the possibilities are endless, but such a vast number |
- | disposal the possibilities are endless, but such a vast number | + | is impossible for people to consider and the advantage of |
- | is impossible for people to consider and the advantage of | + | automating this process is self-evident. </p> |
- | automating this process is self-evident. | + | |
- | </p> | + | |
</body> | </body> | ||
- | |||
- | |||
- | |||
</html> | </html> |
Revision as of 06:58, 19 December 2007
Introduction to EvoGEM | Project Design | Final Results of EvoGEM |
Some Background...
Evolutionary design has been a tool that was used for many accomplishments. In this project the power of evolutionary programming is harnessed to produce viable genetic circuits. That is, strings of DNA that, like a program encoded in a cell, dictate a novel behavior for a bacterium. The application developed, EvoGEM, will be built upon in an attempt to create a more powerful tool that would capture the behavior that can fountain from a swarm based design. Swarm de- sign and evolutionary design are used in this model in order to create an application that can find genetic circuits that would produce a desired behavior before these are tested in a lab. Not only will such a tool be a stepping stone in developing more powerful models that can test designs in silico (virtually) before they are tested in vivo (in a living orgranism), but it will also allow for development of such designs.Our Goals For EvoGEM
The main goal for this project will be to develop EvoGEM to use evolutionary design,effecient mutation operators on these circuits and an effecient fitness function that can solve the relatively simple problem of synthesizing a requested molecule considering the existing iGEM bio-bricks. The problem can be easy or more challenging depending on whether or not the molecule is the result of a pathway. The system would be designed to solve both possibilities.
Why This Could Be Important
It is important to notice that with such a problem being investigated, it is easy for a human to find a solution if given a small number of components and a simple prededefined behavior that is guaranteed to lie in a certain permutation of these components. However, as the number of available bio- bricks increases, and the potential grows, it becomes harder and harder to think of several different designs that would work. With thousands of bio-bricks in the iGEM registry disposal the possibilities are endless, but such a vast number is impossible for people to consider and the advantage of automating this process is self-evident.