|
|
| Line 226: |
Line 226: |
| | | | |
| | | | |
| - | <h1>SBiDer: Synthetic Biocircuit Developer</h1> | + | <h1>Safety</h1> |
| - | <h3>Abstract</h3> | + | <h3>Safety Training</h3> |
| | <p> | | <p> |
| - | 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. The displayed circuit's literature reference, characterization data, and images of included devices can be viewed through the built-in table. Basic validation of the circuit performance is also provided within in the interface. 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.
| + | Safety is an important aspect of the iGEM project requirements, and we understand and respect that. As a software team, we do no work in any wet lab capacity, but just as safety training teaches best practices and behaviours in lab, we have used our safety training to employ best practices and behaviours in developing software. We have covered topics including but not limited to: using GitHub, commenting/documenting code, and how to abstract/re-factor code. </p> |
| | <p> | | <p> |
| - | <h1>Project Description</h1>
| + | We did not use formal lab safety materials as we did not work in any lab at all. |
| - | <h3>Problem Statement</h3>
| + | |
| - | <p>
| + | |
| - | 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:
| + | |
| | </p> | | </p> |
| - | <ol>
| + | |
| - | <li>building a comprehensive database that captures the behavior, composition, and interactions of existing genetic devices in the literature</li> | + | <h3>Who is responsible for biological safety at our institution?</h3> |
| - | <li>constructing and visualizing the network of all synthetic genetic circuits that can interact with one another</li>
| + | |
| - | <li>devising algorithms to search this network for the set of genetic devices that can be used to construct a complex genetic circuit.</li>
| + | |
| - | <li>Perform some basic validation via kinetic modelling.</li>
| + | |
| - | </ol>
| + | |
| - | <h3>Aim 1 - Building a Database</h3>
| + | |
| | <p> | | <p> |
| - | We will mine the scientific literature for existing genetic devices and then construct a database that captures device characteristics such as:
| + | Department of Environment, Health & Safety at UCSD. The project has not been discussed with the department as we anticipate no safety hazards. You can find the biosafety guidelines of our institution <a href = "http://blink.ucsd.edu/safety/research-lab/biosafety/">here.</a> |
| | </p> | | </p> |
| - | <li>composition of devices</li>
| |
| - | <li>function</li>
| |
| - | <li>characterization data</li>
| |
| - | <li>literature reference</li>
| |
| - | </ol>
| |
| - | We will design our database by rigorously constructing an entity relationship diagram and then normalizing these relationships to construct tables for a relational database.
| |
| - | <h3>Aim 2 - Constructing Network of Interacting Devices</h3>
| |
| | <p> | | <p> |
| - | 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</p>
| + | Also, these are the regulations that govern biosafety in general in research laboratories in the United States: http://sis.nlm.nih.gov/enviro/labsafety.html |
| - | <h3>Aim 3 - Searching the Network</h3>
| + | |
| - | <p>
| + | |
| - | 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
| + | |
| | </p> | | </p> |
| - | <!--main content -->
| |
| - | <table width="70%" align="center">
| |
| - |
| |
| - |
| |
| - | <tr>
| |
| - |
| |
| - |
| |
| - | </tr>
| |
| - |
| |
| - |
| |
| - | </tr>
| |
| - |
| |
| - |
| |
| - |
| |
| - |
| |
| - |
| |
| - | </td>
| |
| - |
| |
| - | <tr> <td colspan="3" height="15px"> </td></tr>
| |
| - | <tr><td bgColor="#e7e7e7" colspan="3" height="1px"> </tr>
| |
| - | <tr> <td colspan="3" height="5px"> </td></tr>
| |
| - |
| |
| - |
| |
| - | <!--requirements section -->
| |
| - | <tr><td colspan="3"> <h3> Requirements </h3></td></tr>
| |
| - | <tr>
| |
| - | <td width="45%" valign="top">
| |
| - |
| |
| - | <p> Please be sure to keep these links, your audience will want to find your: </p>
| |
| - |
| |
| - | <!-- Links to other team pages -->
| |
| - | <ul>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software">Home</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Team">Team</a> </li>
| |
| - | <li><a href="https://igem.org/Team.cgi?year=2013&team_name=UCSD_Software">Official Team Profile</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Project">Project</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Parts">Parts</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Modeling">Modeling</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Notebook">Notebook</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Safety">Safety</a> </li>
| |
| - | <li><a href="https://2014.igem.org/Team:UCSD_Software/Attributions">Attributions</a> </li>
| |
| - |
| |
| - | </ul>
| |
| - |
| |
| - | </td>
| |
| - |
| |
| - | <td > </td>
| |
| - | <td width="45%">
| |
| - |
| |
| - | <p>There are a few wiki requirements teams must follow:</p>
| |
| - | <ul>
| |
| - | <li>All pages, images and files must be hosted on the <a href ="https://2014.igem.org/Special:Upload"> 2014.igem.org server</a>. </li>
| |
| - | <li>All pages must be created under the team’s name space.</li>
| |
| - | <li>As part of your documentation, keep the links from the menu to the left. </li>
| |
| - | <li>Do not use flash in wiki code. </li>
| |
| - | <li>The <a href="https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png"> iGEM logo </a> should be placed on the upper part of every page and should link to <a href="https://2014.igem.org/Main_Page">2014.igem.org</a>.</li>
| |
| - | </ul>
| |
| - | <p>Visit the <a href="https://2014.igem.org/Wiki_How-To"> Wiki How To page </a> for a complete list of requirements, tips and other useful information. </p>
| |
| - |
| |
| - | </td>
| |
| - | </tr>
| |
| - |
| |
| | | | |
| - | <tr> <td colspan="3" height="15px"> </td></tr>
| |
| - | <tr><td bgColor="#e7e7e7" colspan="3" height="1"> </tr>
| |
| | | | |
| | | | |
| | | | |
| - | </table>
| |
| | <script> | | <script> |
| | $(document).ready(function(){ | | $(document).ready(function(){ |
Safety
Safety Training
Safety is an important aspect of the iGEM project requirements, and we understand and respect that. As a software team, we do no work in any wet lab capacity, but just as safety training teaches best practices and behaviours in lab, we have used our safety training to employ best practices and behaviours in developing software. We have covered topics including but not limited to: using GitHub, commenting/documenting code, and how to abstract/re-factor code.
We did not use formal lab safety materials as we did not work in any lab at all.
Who is responsible for biological safety at our institution?
Department of Environment, Health & Safety at UCSD. The project has not been discussed with the department as we anticipate no safety hazards. You can find the biosafety guidelines of our institution here.
Also, these are the regulations that govern biosafety in general in research laboratories in the United States: http://sis.nlm.nih.gov/enviro/labsafety.html
"
