"
Team:Berkeley Software
From 2009.igem.org
| Line 27: | Line 27: | ||
<center><b><h2>Welcome to the 2009 iGEM UC Berkeley Software Team Wiki.</h2></b></center> | <center><b><h2>Welcome to the 2009 iGEM UC Berkeley Software Team Wiki.</h2></b></center> | ||
| - | <font size="4">S</font>ynthetic biology promises to introduce a new paradigm to the biological world. One which is less of a design science and more of an engineering discipline. In order | + | <font size="4">S</font>ynthetic biology promises to introduce a new paradigm to the biological world. One which is less of a design science and more of an engineering discipline. In order to fulfill this promise, a set of core design activities must be made more amenable to design automation techniques. The first step requires identifying DNA sequences of interest and packaging them as "standard parts". Once these parts, have been created, the next step is to construct composite "devices". Finally, devices must be physically created with samples in the lab. Each of these stages has a number of sub-problems and each is equally important in the overall design process. Our project focuses on the latter two processes, device creation and physical assembly. This web page has been designed to introduce you to our project so that you can not only learn more about our activities and use the associated tools but also contribute and collaborate with us! Specifically our project organized around the development of three tools: |
[[Team:Berkeley_Software/Eugene|Eugene]] - A domain specific language for the specification of biological constructs. | [[Team:Berkeley_Software/Eugene|Eugene]] - A domain specific language for the specification of biological constructs. | ||
Revision as of 16:11, 2 October 2009
Welcome to the Berkeley Software team's wiki. Our wiki is currently under construction. We apologize for its temporarily disorganized state.
Welcome to the 2009 iGEM UC Berkeley Software Team Wiki.
Synthetic biology promises to introduce a new paradigm to the biological world. One which is less of a design science and more of an engineering discipline. In order to fulfill this promise, a set of core design activities must be made more amenable to design automation techniques. The first step requires identifying DNA sequences of interest and packaging them as "standard parts". Once these parts, have been created, the next step is to construct composite "devices". Finally, devices must be physically created with samples in the lab. Each of these stages has a number of sub-problems and each is equally important in the overall design process. Our project focuses on the latter two processes, device creation and physical assembly. This web page has been designed to introduce you to our project so that you can not only learn more about our activities and use the associated tools but also contribute and collaborate with us! Specifically our project organized around the development of three tools:
Eugene - A domain specific language for the specification of biological constructs.
Spectacles - A visual editing framework for the design of composite biological devices and the assignment of functional concepts to physical realizations.
Kepler - Development of actors and automated assembly processes for the scientific workflow management system, [http://kepler-project.org Kepler].
While each of these efforts is powerful in its own right, together they form the basis for a complete design framework. To accomplish this integration, the Clotho design environment and its core set of APIs has been revamped to accommodate these efforts. This not only makes the design process easy for today but paves the way to future designs.
We encourage you now to check out the site, play with the tools, and ask questions. Our intention is that this be a community effort. We have worked with Stanford, the University of Minnesota, the University of Washington, and Microsoft Research India to create a truly collaborative environment. You could be next. So think of a tool to create, a suggestion to make, or a problem to solve!
Pages:
