Team:BostonU/Chimera

From 2014.igem.org

(Difference between revisions)
Line 23: Line 23:
The Chimera workflow is intended to facilitate the predictive design of complex genetic regulatory networks. It employs a three-cycle approach characterized by the use of computational tools: Eugene for designing, Raven for assembling, and the TASBE Tools for testing genetic constructs. Depending on the researcher's knowledge of device design and assembly, the Chimera workflow can be adjusted in its reliance on the computational tools employed.<br><br>  
The Chimera workflow is intended to facilitate the predictive design of complex genetic regulatory networks. It employs a three-cycle approach characterized by the use of computational tools: Eugene for designing, Raven for assembling, and the TASBE Tools for testing genetic constructs. Depending on the researcher's knowledge of device design and assembly, the Chimera workflow can be adjusted in its reliance on the computational tools employed.<br><br>  
<br><br>
<br><br>
-
<center><img src="https://static.igem.org/mediawiki/2014/1/1a/BU14_DBTcycle.png" width="50%"></center>
+
 
-
<center><capt>This is a graphic depiction of where the software tools Eugene, Pigeon, Raven, and TASBE Tools enter into the classic design-build-test engineering cycle. We also have a Share branch to reflect sharing our data with the iGEM community on the Registry Pages and also through the Synthetic Biology Open Language (SBOL) sharing capabilities.</capt></center>
+
</td>
-
<br><br>
+
<td scope="col"><img src="https://static.igem.org/mediawiki/2014/1/1a/BU14_DBTcycle.png" width="35%" style="float:right" style= "margin-left:10px"><br><br><capt>This is a graphic depiction of where the software tools Eugene, Pigeon, Raven, and TASBE Tools enter into the classic design-build-test engineering cycle. We also have a Share branch to reflect sharing our data with the iGEM community on the Registry Pages and also through the Synthetic Biology Open Language (SBOL) sharing capabilities.</capt></td>
 +
 
 +
 
A desired genetic device behavior and an idea of the parts required are all a researcher needs to begin using Chimera. Once these characteristics have been targeted, the workflow can be used to guide a researcher to building their intended device more efficiently. The following is a general outline of the Chimera workflow. An example of BU 2014's test case can be found on our <a href="https://2014.igem.org/Team:BostonU/Workflow">workflow</a> page, in which we test the functionality of Chimera by using it to assemble a priority encoder.<br>
A desired genetic device behavior and an idea of the parts required are all a researcher needs to begin using Chimera. Once these characteristics have been targeted, the workflow can be used to guide a researcher to building their intended device more efficiently. The following is a general outline of the Chimera workflow. An example of BU 2014's test case can be found on our <a href="https://2014.igem.org/Team:BostonU/Workflow">workflow</a> page, in which we test the functionality of Chimera by using it to assemble a priority encoder.<br>
     <table width="100%" border="0" cellspacing="15" cellpadding="0">
     <table width="100%" border="0" cellspacing="15" cellpadding="0">

Revision as of 22:35, 15 October 2014



Project Chimera A desired genetic device behavior and an idea of the parts required are all a researcher needs to begin using Chimera. Once these characteristics have been targeted, the workflow can be used to guide a researcher to building their intended device more efficiently. The following is a general outline of the Chimera workflow. An example of BU 2014's test case can be found on our workflow page, in which we test the functionality of Chimera by using it to assemble a priority encoder.
Synthetic biology research revolves around design-build-test cycles for the production of genetic devices. An effective process often depends on protocol robustness and a thorough understanding of individual genetic components. Currently, limited software integration and part characterization represent significant stymying factors to the growth of the field, particularly as researchers endeavor to construct increasingly complex devices with behavior that is difficult to predict.

We seek to strengthen the traditional design-build-test cycle by developing a workflow that utilizes bio-design automation software tools and builds upon a thoroughly characterized library of parts. 		ChimeraPlasmid

The Chimera three-cycle workflow


The Chimera workflow is intended to facilitate the predictive design of complex genetic regulatory networks. It employs a three-cycle approach characterized by the use of computational tools: Eugene for designing, Raven for assembling, and the TASBE Tools for testing genetic constructs. Depending on the researcher's knowledge of device design and assembly, the Chimera workflow can be adjusted in its reliance on the computational tools employed.

This is a graphic depiction of where the software tools Eugene, Pigeon, Raven, and TASBE Tools enter into the classic design-build-test engineering cycle. We also have a Share branch to reflect sharing our data with the iGEM community on the Registry Pages and also through the Synthetic Biology Open Language (SBOL) sharing capabilities.

Phase I


Compile and test library of basic parts.

Phase II


Assemble and test range of TU variants.

Phase III


Assemble and test complex device.







Our Sponsors

Retrieved from "http://2014.igem.org/Team:BostonU/Chimera"