"
Team:BostonU/Chimera
From 2014.igem.org
(Difference between revisions)
| (3 intermediate revisions not shown) | |||
| Line 22: | Line 22: | ||
<tr> | <tr> | ||
<td colspan="2" scope="col"> | <td colspan="2" scope="col"> | ||
| - | <h3>The Chimera Workflow</h3></td></tr> | + | <h3>The Chimera Characterization Workflow</h3></td></tr> |
<tr> | <tr> | ||
<td colspan="2" scope="col"> | <td colspan="2" scope="col"> | ||
| - | The Chimera workflow is intended to facilitate the predictive design of complex genetic regulatory networks. It employs a design-build-test engineering approach made unique by the inclusion of the following computational tools: <a href="http://eugenecad.org/">Eugene</a> and <a href="http://pigeoncad.org/">Pigeon</a> for designing, <a href="http://ravencad.org/">Raven</a> for assembling, and the <a href="https://synbiotools.bbn.com/">TASBE Tools</a> 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.</td></tr> | + | The Chimera characterization workflow is intended to facilitate the predictive design of complex genetic regulatory networks. It employs a design-build-test engineering approach made unique by the inclusion of the following computational tools: <a href="http://eugenecad.org/">Eugene</a> and <a href="http://pigeoncad.org/">Pigeon</a> for designing, <a href="http://ravencad.org/">Raven</a> for assembling, and the <a href="https://synbiotools.bbn.com/">TASBE Tools</a> 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.</td></tr> |
<tr> | <tr> | ||
<td scope="col"> | <td scope="col"> | ||
| - | <center><img src="https://static.igem.org/mediawiki/2014/1/1a/BU14_DBTcycle.png" width=" | + | <center><img src="https://static.igem.org/mediawiki/2014/1/1a/BU14_DBTcycle.png" width="450"></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> | <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> | ||
| Line 39: | Line 39: | ||
<tr> | <tr> | ||
<td colspan="2" scope="col"> | <td colspan="2" scope="col"> | ||
| - | 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><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><br><br> |
<center><img src="https://static.igem.org/mediawiki/2014/2/26/BU14_Overview_PhaseI_II_III.png" width="100%"></center> | <center><img src="https://static.igem.org/mediawiki/2014/2/26/BU14_Overview_PhaseI_II_III.png" width="100%"></center> | ||
| - | <br><br> | + | <br><br><br> |
</td> | </td> | ||
</tr> | </tr> | ||
Latest revision as of 00:15, 18 October 2014
| 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. Our group was motivated to start this project through our participation in the 6th International Workshop on Bio-Design Automation, at which important questions about software integration into wet lab experiments were discussed. Our goal is to bridge the gap between software tools and the wet lab to design a more efficient synthetic biology experimental process. |
 |
The Chimera Characterization Workflow | |
| The Chimera characterization workflow is intended to facilitate the predictive design of complex genetic regulatory networks. It employs a design-build-test engineering approach made unique by the inclusion of the following computational tools: Eugene and Pigeon 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. | |
 |
The end goal of the Chimera workflow is to collect high quality quantitative characterization data from genetic devices that can then be used to inform the users on which parts are reliable for use in more complex devices. Currently, this workflow uses flow cytometry as a means of measuring functionality of genetic devices due to the use of the TASBE tools, which allows users to easily process flow cytometry data. When it comes to the design and build aspects of this workflow, Chimera is unbiased when it comes to which assembly method the user selects thanks to Eugene and Raven, which are tools agnostic to assembly method. |
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. |
|
