Team:BU Wellesley Software/Project Overview
From 2011.igem.org
m |
|||
(68 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
<html> | <html> | ||
- | <head> | + | <head> |
+ | <title>BU-Wellesley iGEM Team: Meet the Team Members</title> | ||
+ | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> | ||
+ | <script src="http://cdn.jquerytools.org/1.2.5/full/jquery.tools.min.js?foo"></script> | ||
<style type="text/css"> | <style type="text/css"> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
/*hide default igem banner and reformat style into blank slate*/ | /*hide default igem banner and reformat style into blank slate*/ | ||
#globalWrapper {width: 100%;} | #globalWrapper {width: 100%;} | ||
Line 31: | Line 21: | ||
#content {width: 100%; border:none;} | #content {width: 100%; border:none;} | ||
#bodyContent {border:none;} | #bodyContent {border:none;} | ||
- | |||
/*actual content styles*/ | /*actual content styles*/ | ||
- | + | body {width: 800px; margin:auto;} | |
- | #bu-wellesley_wiki_content a {color:#69d01d;} | + | |
- | #bu-wellesley_wiki_content a:hover {text-decoration:none; color:# | + | #bu-wellesley_wiki_content {height:auto; line-height:100%;} |
+ | /*#bu-wellesley_wiki_content a {color:#69d01d;}*/ | ||
+ | #bu-wellesley_wiki_content a:hover {text-decoration:none; color:#3d3f3c;} | ||
+ | |||
+ | .navbar li {color: #ffffff;} | ||
+ | .navbar li a {color: #ffffff;} | ||
+ | .navbar li a:hover {background:#69d01d; color: #ffffff;} | ||
/*only use for current page content header (i.e. Team, G-nomeSurferPro, etc)*/ | /*only use for current page content header (i.e. Team, G-nomeSurferPro, etc)*/ | ||
Line 43: | Line 38: | ||
text-transform: uppercase; | text-transform: uppercase; | ||
text-decoration: none; | text-decoration: none; | ||
- | text-align: | + | text-align: center; |
- | color: # | + | color: #3d3f3c; |
- | font-size: | + | font-size: 32pt; |
- | + | ||
} | } | ||
</style> | </style> | ||
- | + | <link rel="stylesheet" type="text/css" href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/Team.css"> | |
- | <link rel="stylesheet" type="text/css" href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/ | + | |
- | + | ||
<script type="text/javascript"> | <script type="text/javascript"> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
</script> | </script> | ||
- | |||
</head> | </head> | ||
- | <body> | + | <body class="basiclayout"> |
+ | <div id="bu-wellesley_wiki_content"> | ||
+ | <p style="text-align:center;"><a href="https://2011.igem.org/Team:BU_Wellesley_Software"><img src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/banner.png" width="800px"></a></p> | ||
+ | <ul id="nav"> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Team">Team</a></li> | ||
+ | <li><a href="#">Project</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Project_Overview">Overview</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Clotho">Clotho</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro">G-nome Surfer Pro</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer">Optimus Primer</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet">Trumpet</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow">Puppetshow</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook">eLabNotebook</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Wet_Lab">Wet Lab</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Downloads_and_Tutorials">Downloads and Tutorials</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li><a href="#">Process</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Methodology">Methodology</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Safety">Safety</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Notebook">Notebook</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Outreach">Outreach</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Tips">Tips and Tricks</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Gold">Medal Fulfillment</a></li> | ||
+ | <li><a href="#">Additional Info</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Acknowledgement">Acknowledgement</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Social">Fun</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
- | |||
- | |||
- | |||
<br> | <br> | ||
<h6>Project Overview</h6> | <h6>Project Overview</h6> | ||
<br><br> | <br><br> | ||
- | < | + | <center> |
- | + | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Clotho">Clotho</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro">G-nome Surfer Pro</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer">Optimus Primer</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet">Trumpet</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow">Puppetshow</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook">eLabNotebook</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Wet_Lab">Wet Lab</a> | <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Downloads_and_Tutorials">Downloads and Tutorials</a> | |
- | + | </center> | |
- | + | <p> | |
- | + | <br><br> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
<p><p> | <p><p> | ||
- | + | <center> | |
+ | <div id="project_wheel"> | ||
+ | <img name="wheel" src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png" width="700px" alt="wheel" usemap="#wheelmap" > | ||
+ | <map name="wheelmap"> | ||
+ | <area shape="rect" coords="64,1,263,168" alt="Gnome" href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-gnome.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | <area shape="rect" coords="1,213,156,420" alt="Primer" href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-optimus.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | <area shape="rect" coords="145,450,380,588" alt="Trumpet" href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-trumpet.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | <area shape="rect" coords="470,380,602,563" alt="Puppetshow" href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-puppet.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | <area shape="rect" coords="540,170,699,323" alt="eLab" href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-elab.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | <area shape="rect" coords="373,1,576,126" alt="eLab" href="https://2011.igem.org/Team:BU_Wellesley_Software/Wet_Lab" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-wetlab.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | <area shape="rect" coords="218,230,470,317" alt="clotho" href="https://2011.igem.org/Team:BU_Wellesley_Software/Clotho" | ||
+ | onMouseOver="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel-clotho.png'" | ||
+ | onMouseOut="document.wheel.src='http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/ProjectLogos/wheel.png'"/> | ||
+ | </map> | ||
+ | </div> | ||
+ | </center> | ||
+ | <p> | ||
+ | <div class="project_abstract"> | ||
+ | <!--<p> | ||
+ | We present tools which facilitate the research, design, and fabrication of biological constructs. Our workflow comprises <a href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro">G-nome Surfer Pro</a> for research, <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet">Trumpet</a> and <a href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer">Optimus Primer</a> for design, and <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow">Puppetshow</a> and <a href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook">eLabNotebook</a> for the construction of those designs. <a href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro">G-nome Surfer Pro</a> promotes collaborative | ||
+ | research by allowing users to browse genes, Parts, and other DNA along with their associated | ||
+ | literature on a table-top surface. Using <a href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer">Optimus Primer</a>, primers can be designed for the selected | ||
+ | Parts. <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet">Trumpet</a> generates permutable constructs from these Parts by interleaving invertase sites | ||
+ | among them. To assemble these permutable constructs, we present a Protocol Automation Stack | ||
+ | comprising a high-level programming language called <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow">Puppetshow</a>, executable on a robot. For improving | ||
+ | manual protocol execution, we are developing an <a href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook">eLabNotebook</a> that helps capture data, and | ||
+ | schedule resources and lab activities. Our unique tools offer an end-to-end workflow that is | ||
+ | collaborative, includes wetlab automation and organization, and provides algorithms for designing | ||
+ | configurable constructs. | ||
+ | </p>--> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <h1>Design Cycle</h1> | ||
+ | <p> | ||
+ | Synthetic biological systems of the future will require that software design flows and laboratory experimentation be closely coupled into what is commonly referred to as the design-build-test cycle. Our project expands on this process by creating a collection of novel software tools. These software tools not only tackle challenging technical problems (automated genetic circuit design, liquid handling robot automation) but also introduce innovative approaches to the way in which users interact both with each other as well as with computers. In addition, we carry out wetlab experiments using our tools to validate our approach. We feel that all three areas (technical solutions, innovative interfaces, and wetlab validation) are crucial and allow our project to standout from traditional iGEM software projects. Our design cycle is organized around the following five areas: | ||
+ | |||
+ | <ol> | ||
+ | <li><b>Hypothesis forming</b> - In this stage, high level decisions are made regarding the system architecture, desired functionality, relevant background literature, and overall vision of the project and system. | ||
+ | <ul><li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro">G-nome Surfer Pro</a> promotes collaborative research by allowing users to browse genes, Parts, and other DNA along with their associated literature on a table-top surface. | ||
+ | </ul> | ||
+ | |||
+ | <li><b>Specification</b> - Here the required system components are formally captured and any constraints on the design are specified. | ||
+ | <ul><li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer">Optimus Primer</a> provides both a desktop as well as a table-top surface environment to generate primers for selected Parts from the hypothesis forming stage. | ||
+ | </ul> | ||
+ | |||
+ | <li><b>Design</b> - This is the process of transforming the specification into a collection of biological building blocks with sufficient information to physically assemble them in the laboratory environment. | ||
+ | <ul><li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet">Trumpet</a> generates permutable genetic circuit constructs from the Specification stage designs by interleaving invertase sites at strategic locations within genetic Devices. | ||
+ | </ul> | ||
+ | |||
+ | <li><b>Physical Assembly</b> - Assembling DNA constructs is a series of transformations which take DNA primitives and combine them into Composite Parts. Issues such as efficiency, design cost, and reliability should be taken into account using optimized algorithms and tools. | ||
+ | <ul><li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow">Puppetshow</a> assembles these permutable constructs from the Design stage using a Protocol Automation Stack comprising a high-level programming language executable on a liquid handling robot. | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook">eLabNotebook</a> helps capture data, and schedule resources and lab activities creating a more design automation friendly laboratory environment. | ||
+ | </ul> | ||
+ | |||
+ | <li><b>Test</b> - Finally, the assembled construct must be verified. In the event that it does not work, the design cycle can continue incorporating the knowledge gained at this stage to try to improve the overall process. | ||
+ | <ul><li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Wet_Lab">Wet Lab</a> experimentation tested our tools and methodology by beginning to create a framework for investigating transcription factor interactions in Tuberculosis. | ||
+ | </ul> | ||
+ | </ol> | ||
+ | </p> | ||
+ | <p> | ||
+ | |||
+ | <h1>Integration</h1> | ||
+ | <p> | ||
+ | In order to integrate these areas fully together we built upon the <a href="https://2011.igem.org/Team:BU_Wellesley_Software/Clotho">Clotho</a> design framework. Clotho is a portable and extensible collection of open-source application software, a concise data model, and a core software development platform for synthetic biological engineering. Being open-source and easily extensible, Clotho is built to address the current and future needs of synthetic biologists. Clotho's data model captures the data associated with synthetic biological parts, devices, systems, and samples, in a unified relational database. Clotho's application software is modularized into "Apps" which all exchange biological data with a database through a uniform interface. Furthermore, Clotho's core platform introduces a concise and simple application programming interface (API) to developers who wish to contribute new applications to Clotho and create customized in-house tools. The API establishes a vocabulary at a level of abstraction familiar to synthetic biologists. </p> | ||
+ | |||
+ | </div><br> | ||
+ | |||
</div><!--end bu-wellesley_wiki_content div--> | </div><!--end bu-wellesley_wiki_content div--> | ||
+ | |||
+ | <br> | ||
+ | For a more extended overview, check out our talk at the Americas Regional competition: | ||
+ | <br> | ||
+ | <br> | ||
+ | |||
+ | <center> | ||
+ | <iframe width="560" height="315" src="http://www.youtube.com/embed/xVfQyxbHEhU" frameborder="0" allowfullscreen </iframe> | ||
+ | </center> | ||
+ | |||
+ | |||
</body> | </body> | ||
</html> | </html> |
Latest revision as of 20:01, 18 October 2011
Project Overview
Design Cycle
Synthetic biological systems of the future will require that software design flows and laboratory experimentation be closely coupled into what is commonly referred to as the design-build-test cycle. Our project expands on this process by creating a collection of novel software tools. These software tools not only tackle challenging technical problems (automated genetic circuit design, liquid handling robot automation) but also introduce innovative approaches to the way in which users interact both with each other as well as with computers. In addition, we carry out wetlab experiments using our tools to validate our approach. We feel that all three areas (technical solutions, innovative interfaces, and wetlab validation) are crucial and allow our project to standout from traditional iGEM software projects. Our design cycle is organized around the following five areas:
- Hypothesis forming - In this stage, high level decisions are made regarding the system architecture, desired functionality, relevant background literature, and overall vision of the project and system.
- G-nome Surfer Pro promotes collaborative research by allowing users to browse genes, Parts, and other DNA along with their associated literature on a table-top surface.
- Specification - Here the required system components are formally captured and any constraints on the design are specified.
- Optimus Primer provides both a desktop as well as a table-top surface environment to generate primers for selected Parts from the hypothesis forming stage.
- Design - This is the process of transforming the specification into a collection of biological building blocks with sufficient information to physically assemble them in the laboratory environment.
- Trumpet generates permutable genetic circuit constructs from the Specification stage designs by interleaving invertase sites at strategic locations within genetic Devices.
- Physical Assembly - Assembling DNA constructs is a series of transformations which take DNA primitives and combine them into Composite Parts. Issues such as efficiency, design cost, and reliability should be taken into account using optimized algorithms and tools.
- Puppetshow assembles these permutable constructs from the Design stage using a Protocol Automation Stack comprising a high-level programming language executable on a liquid handling robot.
- eLabNotebook helps capture data, and schedule resources and lab activities creating a more design automation friendly laboratory environment.
- Test - Finally, the assembled construct must be verified. In the event that it does not work, the design cycle can continue incorporating the knowledge gained at this stage to try to improve the overall process.
- Wet Lab experimentation tested our tools and methodology by beginning to create a framework for investigating transcription factor interactions in Tuberculosis.
Integration
In order to integrate these areas fully together we built upon the Clotho design framework. Clotho is a portable and extensible collection of open-source application software, a concise data model, and a core software development platform for synthetic biological engineering. Being open-source and easily extensible, Clotho is built to address the current and future needs of synthetic biologists. Clotho's data model captures the data associated with synthetic biological parts, devices, systems, and samples, in a unified relational database. Clotho's application software is modularized into "Apps" which all exchange biological data with a database through a uniform interface. Furthermore, Clotho's core platform introduces a concise and simple application programming interface (API) to developers who wish to contribute new applications to Clotho and create customized in-house tools. The API establishes a vocabulary at a level of abstraction familiar to synthetic biologists.
For a more extended overview, check out our talk at the Americas Regional competition: