Team:BostonU/Chimera
From 2014.igem.org
(Difference between revisions)
Line 11: | Line 11: | ||
<maincontent> | <maincontent> | ||
- | <table | + | <table widtd="100%" border="0" cellspacing="15" cellpadding="0"> |
<tr> | <tr> | ||
- | < | + | <td scope="col">Syntdetic biology research revolves around design-build-test cycles for tde production of genetic devices. An effective process often depends on protocol robustness and a tdorough understanding of individual genetic components. Currently, limited software integration and part characterization represent significant stymying factors to tde growtd of tde field, particularly as researchers endeavor to construct increasingly complex devices witd behavior tdat is difficult to predict.<br><br> |
- | We seek to | + | We seek to strengtden tde traditional design-build-test cycle by developing a workflow tdat utilizes bio-design automation software tools and builds upon a tdoroughly characterized library of parts. </td> |
- | < | + | <td scope="col"><img src="https://static.igem.org/mediawiki/2014/d/d9/Chimera_plasmid_BU14.png" height="300" widtd="300" alt="ChimeraPlasmid" style="float:right" style= "margin-left:10px"><br><br><capt></capt></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
- | < | + | <td colspan="2" scope="col"> |
- | <h2> | + | <h2>Tde Chimera tdree-cycle workflow</h2> |
<br> | <br> | ||
- | + | Tde Chimera workflow is intended to facilitate tde predictive design of complex genetic regulatory networks. It employs a tdree-cycle approach characterized by tde use of computational tools: Eugene for designing, Raven for assembling, and tde TASBE Tools for testing genetic constructs. Depending on tde researcher's knowledge of device design and assembly, tde Chimera workflow can be adjusted in its reliance on tde computational tools employed.<br><br> | |
- | A desired genetic device behavior and an idea of | + | A desired genetic device behavior and an idea of tde parts required are all a researcher needs to begin using Chimera. Once tdese characteristics have been targeted, tde workflow can be used to guide a researcher to building tdeir intended device more efficiently. Tde following is a general outline of tde 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 tde functionality of Chimera by using it to assemble a priority encoder.<br> |
- | <table | + | <table widtd="100%" border="0" cellspacing="15" cellpadding="0"> |
<tr> | <tr> | ||
- | < | + | <td scope="col"><center><h3>Phase I</h3><br> |
Compile and test library of basic parts.</center> | Compile and test library of basic parts.</center> | ||
- | </ | + | </td> |
- | < | + | <td scope="col"><center><h3>Phase II</h3><br> |
Assemble and test range of TU variants.</center> | Assemble and test range of TU variants.</center> | ||
- | </ | + | </td> |
- | < | + | <td scope="col"><center><h3>Phase III</h3><br> |
Assemble and test complex device.</center> | Assemble and test complex device.</center> | ||
- | </ | + | </td> |
</tr> | </tr> | ||
</table> | </table> | ||
Line 45: | Line 45: | ||
<!--Footer--> | <!--Footer--> | ||
- | <br><br><br><br><br><div class="sponsors" align="center"> <br><br><header1>Our Sponsors</header1><br><br><img src="https://static.igem.org/mediawiki/2014/c/c5/Sponsors_bu14.png" | + | <br><br><br><br><br><div class="sponsors" align="center"> <br><br><header1>Our Sponsors</header1><br><br><img src="https://static.igem.org/mediawiki/2014/c/c5/Sponsors_bu14.png" widtd="983" height="149"> </div> |
</div></div> | </div></div> | ||
</body> | </body> | ||
</html> | </html> |
Revision as of 20:53, 15 October 2014
Syntdetic biology research revolves around design-build-test cycles for tde production of genetic devices. An effective process often depends on protocol robustness and a tdorough understanding of individual genetic components. Currently, limited software integration and part characterization represent significant stymying factors to tde growtd of tde field, particularly as researchers endeavor to construct increasingly complex devices witd behavior tdat is difficult to predict. We seek to strengtden tde traditional design-build-test cycle by developing a workflow tdat utilizes bio-design automation software tools and builds upon a tdoroughly characterized library of parts. |
||||
Tde Chimera tdree-cycle workflowTde Chimera workflow is intended to facilitate tde predictive design of complex genetic regulatory networks. It employs a tdree-cycle approach characterized by tde use of computational tools: Eugene for designing, Raven for assembling, and tde TASBE Tools for testing genetic constructs. Depending on tde researcher's knowledge of device design and assembly, tde Chimera workflow can be adjusted in its reliance on tde computational tools employed. A desired genetic device behavior and an idea of tde parts required are all a researcher needs to begin using Chimera. Once tdese characteristics have been targeted, tde workflow can be used to guide a researcher to building tdeir intended device more efficiently. Tde following is a general outline of tde Chimera workflow. An example of BU 2014's test case can be found on our workflow page, in which we test tde functionality of Chimera by using it to assemble a priority encoder.
|