Team:UC Davis
Tutorial
Explore our Code
Launch!
SBiDer: Synthetic Biocircuit Developer
Abstract
Genetic circuits are often difficult to engineer, requiring months to design, build, and test each individual genetic device involved in the circuit. SBiDer, a web tool developed by the UCSD Software iGEM team, will leverage existing devices to construct a database with consideration for the function of each device interpreted as boolean logic. The data can be queried by the user through SBiDer's visual interface to explore circuit designs. Users can search for existing circuits that can be used to assemble a complex circuit. The displayed circuit's literature reference, characterization data, and images of included devices can be viewed through the built-in table. We also provide a standalone modelling Python package that can be used to model circuits given by our online webtool. SBiDer's web of information can be expanded through user-generated additions to the database to improve the efficiency of the application and the accuracy of the models.
Project Description
Problem Statement
Synthetic genetic circuits created by synthetic biologists have yielded exciting applications such as biofuels production and cancer killing bacteria. These circuits are often difficult to engineer, requiring months to design, build, and test each individual genetic device involved in the circuit. Although there are many genetic devices that have been built, re-using these devices often requires a time-consuming review of the literature. The UCSD Software iGEM team will address this challenge by creating a web-tool that leverages existing genetic devices to create complex genetic circuits. We will accomplish this by:
- building a comprehensive database that captures the behavior, composition, and interactions of existing genetic devices in the literature
- constructing and visualizing the network of all synthetic genetic circuits that can interact with one another
- devising algorithms to search this network for the set of genetic devices that can be used to construct a complex genetic circuit.
- Perform some basic validation via kinetic modelling.
Aim 1 - Building a Database
We will mine the scientific literature for existing genetic devices and then construct a database that captures device characteristics such as:
- composition of devices
- function
- characterization data
- literature reference
Aim 2 - Constructing Network of Interacting Devices
We will connect known genetic devices together via device input and outputs to create a network of devices that can interact. We define a genetic device as a DNA construct transformed into cells that can cause expression of some protein in response to stimuli (or input). We will develop a web interface to facilitate access to the complex network that we have constructed. Our Web interface makes extensive use of Cytoscape, an open source bioinformatics software package for metabolic network visualization and simulation. In addition, the interface will generate SBOL Visual Images, a standard language that is easily understood by synthetic biologists all over the world. Users can also update our database with additional devices through this interface. Using the Cynetshare framework, users can share their circuit designs
Aim 3 - Searching the Network
This interface will allow researchers to query our database network for a circuit design expressed as logical operators such as “AND”, “OR”, and “NOR”, and retrieve the subnetwork of genetic devices that satisfies the circuit design. To Perform our search we modified several traditional graph search algorithms to traverse this graph, including but not limited to Prim’s algorithm (minimum spanning tree), Dijkstra’s algorithm and a breadth-first search. Results are visualized graphically in our web interface.
Welcome to iGEM 2015!
Your team has been approved and you are ready to start the iGEM season!
Before you start:
Please read the following pages:
Styling your wiki
You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.
While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.
Editing your wiki
On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world!
See tips on how to edit your wiki on the Template Documentation page.
Templates
This year we have created templates for teams to use freely. More information on how to use and edit the templates can be found on the Template Documentation page.
Tips
This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started:
- State your accomplishments! Tell people what you have achieved from the start.
- Be clear about what you are doing and how you plan to do this.
- You have a global audience! Consider the different backgrounds that your users come from.
- Make sure information is easy to find; nothing should be more than 3 clicks away.
- Avoid using very small fonts and low contrast colors; information should be easy to read.
- Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the iGEM 2015 calendar
- Have lots of fun!
Inspiration
You can also view other team wikis for inspiration! Here are some examples:
- 2014 SDU Denmark
- 2014 Aalto-Helsinki
- 2014 LMU-Munich
- 2014 Michigan
- 2014 ITESM-Guadalajara
- 2014 SCU-China
Uploading pictures and files
You can upload your pictures and files to the iGEM 2015 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name.
When you upload, set the "Destination Filename" to Team:YourOfficialTeamName/NameOfFile.jpg
. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)