|
|
| Line 1: |
Line 1: |
| | + | <!doctype html> |
| | <html class="no-js"> | | <html class="no-js"> |
| | <head> | | <head> |
| Line 7: |
Line 8: |
| | <meta name="viewport" | | <meta name="viewport" |
| | content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"> | | content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"> |
| − | <title>Project</title> | + | <title>Base Wiki</title> |
| | | | |
| | <!-- Set render engine for 360 browser --> | | <!-- Set render engine for 360 browser --> |
| Line 33: |
Line 34: |
| | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/amazeuiMinCss?action=raw&ctype=text/css"> | | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/amazeuiMinCss?action=raw&ctype=text/css"> |
| | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/wikiCss?action=raw&ctype=text/css"> | | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/wikiCss?action=raw&ctype=text/css"> |
| − | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/projectCss?action=raw&ctype=text/css"> | + | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/improvementCss?action=raw&ctype=text/css"> |
| | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/mainCss?action=raw&ctype=text/css"> | | <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:SJTU-Software/mainCss?action=raw&ctype=text/css"> |
| − | <style>
| |
| − | table, td, th
| |
| − | {
| |
| − | border:1px solid black;
| |
| − | }
| |
| − | </style>
| |
| | </head> | | </head> |
| − | <body class = "am-animation-fade am-animation-delay"> | + | <body> |
| − | <div data-am-widget="gotop" class="am-gotop am-gotop-fixed">
| + | <div class = "improvementTitle"> |
| − | <a href="#top" title=""> | + | <h1>Improvement<h1> |
| − | <img class="am-gotop-icon-custom" src="https://static.igem.org/mediawiki/2015/6/6c/SJTU-SOFTWARE.gototop.png"
| + | |
| − | />
| + | |
| − | </a>
| + | |
| − | </div>
| + | |
| − | | + | |
| − | <br/>
| + | |
| − | <nav class="scrollspy-nav" data-am-scrollspy-nav="{offsetTop: 100}" data-am-sticky>
| + | |
| − | <br/>
| + | |
| − | <ul class="am-avg-sm-7 am-thumbnails mainNav">
| + | |
| − | <li class = "navItem"> | + | |
| − | <a href="home">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "1" src="https://static.igem.org/mediawiki/2015/4/4a/SJTU-SOFTWARE.1-1.png" />
| + | |
| − | <p class = "navPhoto">Home</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | <li class = "navItem">
| + | |
| − | <a href="project">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "2" src="https://static.igem.org/mediawiki/2015/4/4c/SJTU-SOFTWARE.2-2.png" />
| + | |
| − | <p class = "navPhoto">Project</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | <li class = "navItem">
| + | |
| − | <a href="document">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "3" src="https://static.igem.org/mediawiki/2015/6/63/SJTU-SOFTWARE.3-1.png" />
| + | |
| − | <p class = "navPhoto">Document</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | <li class = "navItem">
| + | |
| − | <a href="requirement">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "4" src="https://static.igem.org/mediawiki/2015/d/d0/SJTU-SOFTWARE.4-1.png" />
| + | |
| − | <p class = "navPhoto">Requirement</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | <li class = "navItem">
| + | |
| − | <a href="saftyPolicyconcern">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "5" src="https://static.igem.org/mediawiki/2015/2/2a/SJTU-SOFTWARE.5-1.png" />
| + | |
| − | <p class = "navPhoto">Safty<br/>policy<br/>concern</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | <li class = "navItem">
| + | |
| − | <a href="humanPractice">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "6" src="https://static.igem.org/mediawiki/2015/0/08/SJTU-SOFTWARE.6-1.png" />
| + | |
| − | <p class = "navPhoto">Human<br/>practice</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | <li class = "navItem">
| + | |
| − | <a href="team">
| + | |
| − | <img class="am-thumbnails navPhoto" id = "7" src="https://static.igem.org/mediawiki/2015/b/b7/SJTU-SOFTWARE.7-1.png" />
| + | |
| − | <p class = "navPhoto">Team</p>
| + | |
| − | </a>
| + | |
| − | </li>
| + | |
| − | </ul>
| + | |
| − | </nav>
| + | |
| − | <br/>
| + | |
| − | <br/>
| + | |
| − | | + | |
| − | <div class = "project" id = "block">
| + | |
| − | <div id = "block1" class = "am-panel-group">
| + | |
| − | <div class = " project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'slide-bottom'}">
| + | |
| − | <a name = "Background" id = "Background"></a>
| + | |
| − | <hr class = "border-line"/>
| + | |
| − | <div class = "backgroundContent am-panel-hd">
| + | |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block1', target: '#do-not-say-1'}"><b>Background</b></h4>
| + | |
| − | </div>
| + | |
| − | <div class="am-panel-collapse am-collapse backgroundContent" id = "do-not-say-1">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <p class = " Background">
| + | |
| − | As we know, there are more than 20,000 biobricks in iGEM official standard database and the number of biobrick keeps increasing every year. Based on the fact that sequencing technology gave birth to bioinformatics, we assumed that with the explosive increase of biobricks, it will be harder for synthetic biologists to manually find good biobricks which meets the requirements when they are trying to create new devices with existing parts. This issue will inevitably lead to the birth of softwares and databases especially related to synthetic biology and these intelligent tools will further promote the rapid development of synthetic biology. So we integrated biobricks data before September from the iGEM official standard database and then developed a visual online device-designing system for synthetic biology researchers.<br/>
| + | |
| − | Meanwhile, in order to facilitate the researchers to look for better biobricks, we combined the search function and scoring system from the 2014 SJTU Software’s EasyBBK with our own system. In this way, users can find biobricks in line with their requirements more quickly.<br/>
| + | |
| − | </p>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| | </div> | | </div> |
| − | <div id = "block7" class = "am-panel-group"> | + | <div class = "improvementContent"> |
| − | <div class = " project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'slide-bottom'}">
| + | <br/> |
| − | <a name = "Design" id = "Design"></a>
| + | <p> The school of life science and biotechnology of Shanghai Jiao Tong University is one of the best in China. We have a long tradition of taking part in the iGEM competition. However, until 2014, we only had wet lab team for our school and our seniors organized the first software team of SJTU. Thanks to the experience shared by last year’s software team, we have a much more mature software team this year.</p> |
| − | <hr class = "border-line"/>
| + | <p> Before we considering the project of this year, we firstly conducted carefully investigation on projects of former software teams. During the process, we found a common problem that the former project only got maintenance for the year when the team took the competition. After several years, we cannot contact the people who were responsible for the software then and some of the software are excellent. In order to prevent this problem from happening to our project, we consulted the members of last year’s software team after we determined our main idea. Consequentially, we absorbed the most important results of easyBBK in our software. First of all, as an outstanding software, easyBBK has a highlight in the search function. So we added the search function on our push system (which helps users to construct and design devices. Moreover, we made the scoring system of easyBBK to be more flexible by allowing users to choose the weight of different parts and filter the score range.</p> |
| − | <div class = "designContent am-panel-hd">
| + | <p> Meanwhile, we use the usage count of every existing biobricks to determine the difference of their performances. After standardizing the format of biological data, we can have better and more concrete standards like the expression level to evaluate the property of biobricks. In the end, we hope SJTU software teams can continue to inherit and develop the work of former teams. This would meet the requirements of iGEM competition better.</p> |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block7', target: '#do-not-say-2'}"><b>Design&Algorithm</b></h4>
| + | <p> When we have collaborations with other igem teams, we find that most of teams use new parts to build their devices. Due to the new parts don't have enough feedbacks and uesd times which are the core grading standards in our algorithm, our software is hard to evaluate those kind of bricks with a high score. However, when we use blastn to compare the new parts' sequence with the existing parts ' sequence in the database, we find that most of the new parts ' sequence have high similarity with the old part in the database. Some parts even have same sequence as old parts in the database. And we also find that there are many parts with the same sequence in the database. So we want to add the blastn function to our website. When the researchers upload a part to the database, we can compare its sequence with the parts in the database. If there are some parts with same sequence as the new one in the database, we can inform the researchers this information and refuse the upload. <br/> |
| − | </div>
| + | The blastn function can also help the users to find out which biobricks in the database is similar to their own biobrick. By checking these biobricks' information, users may get more help and enlightenment in their reseaches. What's more, blastn function can help our algorithm to evaluate the devices that cantain the new parts, which have been explained in our collaborations with other igem teams. <br/> |
| − | <div class="am-panel-collapse am-collapse backgroundContent" id = "do-not-say-2">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <p class = "Introduction"> <b>Introduction<br/></b> | + | |
| − | Our software, BASE, has four functions: search, recommendation, evaluation and upload. Via search function, users can search for parts or devices using IDs or features as keywords. In recommendation interface, users can draw their devices. They can also give some keywords when drag an icon to the chain to get a list of parts which fit the require and other parts best. When using evaluation, users firstly enter a device that they designed, then our software can give advice for each part to improve their devices.Finally, users can upload their device to the IGEM part registry and BASE’s database. For the first three functions, we develop a set of scoring system to evaluate the effectiveness and ease of use of the parts and devices.
| + | |
| − | </p>
| + | |
| − | <p class = "Methods"> <b>Method<br/></b> | + | |
| − | We get the data of parts from IGEM part registry. A total of 14971 bio-bricks are recorded in the database. Then we divide them into two groups, parts and devices, according to whether the biobrick has subparts. Among them, ??? are parts and ??? are devices. For each bio-brick, there’re four different websites:
| + | |
| − | http://parts.igem.org/cgi/xml/part.cgi?part=BBa_???
| + | |
| − | http://parts.igem.org/cgi/partsdb/part_info.cgi?part_name=BBa_???
| + | |
| − | http://parts.igem.org/partsdb/get_part.cgi?part=BBa_???
| + | |
| − | http://parts.igem.org/Part:BBa_???:Experience
| + | |
| − | When collecting data, we simply replace the ??? with the bricks’ ID.
| + | |
| − | We then extract information from the websites. The information include Part_status, Sample_status, Part_results, Uses, DNA_status, Qualitative_experience, Group_favorite, Star_rating, Del, Groups, Number_comments, Ave_rating. And we take most of the above factors into account when scoring bio-bricks.
| + | |
| − | As for optimizing the weight of these factors, we firstly analyze the distribution of value of the factors to choose the factors that can distinguish the parts most effectively. Then we select 40 parts and 40 devices as the training sets. Finally we get the weight by combining results of several methods.
| + | |
| − | </p>
| + | |
| − | <p class = " Results"><b>Results<br/></b>
| + | |
| − | 1.scores for different values of factors
| + | |
| − | To build a scoring system, we start at giving scores to the values of these factors. With the help of wet lab researchers, we rank the values of discrete type according to their effect on researches, and choose a relatively good method to transform successive values into values between 0 and 1.
| + | |
| − | For discrete values, we have a scoring table as below.
| + | |
| − | </p>
| + | |
| − | <div class = "am-g">
| + | |
| − | | + | |
| − | <table class = "am-u-sm-5 " >
| + | |
| − | <tr>
| + | |
| − | <th rowspan = "2">Part status</th>
| + | |
| − | <td>Released HQ 2013</td>
| + | |
| − | <td>1</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>other</td>
| + | |
| − | <td>0</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th rowspan = "4">Sample status</td>
| + | |
| − | <td>In Stock</td>
| + | |
| − | <td>1</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>It's complicated</td>
| + | |
| − | <td>0.5</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>For Reference Only</td>
| + | |
| − | <td>0.25</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>other</td>
| + | |
| − | <td>0</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th rowspan = "2">DNA Status</th>
| + | |
| − | <td>Available</td>
| + | |
| − | <td>1</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>other</td>
| + | |
| − | <td>0</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th rowspan = "3">Part Results</th>
| + | |
| − | <td>Works</td>
| + | |
| − | <td>1</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>Issues</td>
| + | |
| − | <td>0.25</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>Fails;None;Null</td>
| + | |
| − | <td>0</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th rowspan = "2">Star Rating</th>
| + | |
| − | <td>1</td>
| + | |
| − | <td>1</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>Null</td>
| + | |
| − | <td>0</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th rowspan = "3">Qualitative_<br/>experience</th>
| + | |
| − | <td>Works</td>
| + | |
| − | <td>1</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>Issues</td>
| + | |
| − | <td>0.25</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>other</td>
| + | |
| − | <td>0</td>
| + | |
| − | </tr>
| + | |
| − | </table>
| + | |
| − | <p class = "am-u-sm-6 Results">
| + | |
| − | For those successive values, such as used times, average rating, number of comments, we develop two scoring methods. The “average rating” factor has only 5 values, so we just simply score it as a arithmetic progression. As for the other two factors, the distribution of values seems very unbalanced. And since we can be convinced that a brick is good when it’s used several tens times and the feedbacks are good, there’s no need to force a brick to get used for a thousand times before it’s recommended to other users, though some of the parts are actually used hundreds or even thousands of times. So we calculate the score by the expression below.
| + | |
| − | Score=log(n+1)/log(nmax+1)
| + | |
| − | The n in the expression refers to the values. By using this expression, we reduce the effect of extreme values and make the scores more convincing.
| + | |
| − | </p>
| + | |
| − | </div>
| + | |
| − | <p> And the optimized weight of the factors are shown in the table below.<br/> | + | |
| − | Table2:<br/>
| + | |
| − | </p>
| + | |
| − | <div class = "am-g">
| + | |
| − | <table class = "am-u-sm-5" >
| + | |
| − | <tr>
| + | |
| − | <th width = "40%">Part Status</th>
| + | |
| − | <td width = "60%">10</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Sample Status</th>
| + | |
| − | <td>10</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>DNA Status</th>
| + | |
| − | <td>10</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Part Results</th>
| + | |
| − | <td>15</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Star Rating</th>
| + | |
| − | <td>10</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Qualitative_<br/>experience</th>
| + | |
| − | <td>5</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Used Times</th>
| + | |
| − | <td>15</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Average Rating</th>
| + | |
| − | <td>20</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <th>Number<br/>of Comments</th>
| + | |
| − | <td>5</td>
| + | |
| − | </tr>
| + | |
| − | </table>
| + | |
| − | <p class = "am-u-sm-6 Results">The above scoring system are used to evaluate all the bricks in our databases. It become effective in all the functions except upload. However, we still have another scoring system for devices.
| + | |
| − | </p>
| + | |
| − | </div>
| + | |
| − | <p class = "Results">
| + | |
| − | 2.devices scoring method with relationship between parts
| + | |
| − | This method is mainly used in the evaluation function. For a device which is just designed by users, the score we get through the first method actually mean nothing, as there’re no information for the device on the registry. So we need to develop a new evaluation system based on its composing parts and relationships between the parts.
| + | |
| − | When evaluating the relationships between parts, we take several factors into consideration, such as the frequency and the average score when the parts are used together and so on.
| + | |
| − | Firstly the weight of the two aspects is confirmed. The default ratio is 65% for the parts and 35% for the relationships. In the first aspect, the weight of different types is dynamic. It’s influenced by the number and type of the parts. However it still shows the different significance of the parts. But in the second aspect, all relationships share the same weight.
| + | |
| − | Then the scoring begins. Given that wet lab researchers care more about the outcome of a device, we search for functional coding parts in the device, and optimize it in the first place. After the user locks the functional parts, we start to optimize other parts. The order is decided according to their type and location in the device.
| + | |
| − | Since there’re two scoring system for devices, the weight in the second one is adjusted to make the scores made by different method close so that scores for new devices can have the comparability with those already in the database.
| + | |
| | | | |
| − | 3.Adding parts one by one
| + | </p> |
| − | This method is mainly used in recommendation function. It’s similar to the second one, but it only cares about the new adding part and relationships when doing the recommendations. The weight’s also adjusted to fit the other two method.
| + | |
| − | </p>
| + | |
| − | <p class = "Reference"><b>Reference<br/><br/></b>
| + | |
| − | Morgan Madec, Yves Gendrault, Christophe Lallement, Member, IEEE, Jacques Haiech. A game-of-life like simulator for design-oriented modeling of BioBricks in synthetic biology, 34th Annual International Conference of the IEEE EMBS, San Diego, California USA, 28 August - 1 September, 2012<br/><br/>
| + | |
| − | Suvi Santala, * Matti Karp, and Ville Santala, Monitoring Alkane Degradation by Single BioBrick Integration to an Optimal Cellular Framework, Synth. Biol. 2012, 1, 60 −64<br/><br/>
| + | |
| − | Patrick M Boyle1, Devin R Burrill1, Mara C Inniss1, Christina M Agapakis1, Aaron Deardon, Jonathan G DeWerd, Michael A Gedeon, Jacqueline Y Quinn, Morgan L Paull, Anugraha M Raman, Mark R Theilmann, Lu Wang, Julia C Winn, Oliver Medvedik, Kurt Schellenberg, Karmella A Haynes,Alain Viel, Tamara J Brenner, George M Church, Jagesh V Shah1 and Pamela A Silver, A BioBrick compatible strategy for genetic modification of plants, Journal of Biological Engineering 2012, 6:8<br/><br/>
| + | |
| − | Ilya B. Tikh & Mark Held & Claudia Schmidt-Dannert, BioBrickTM compatible vector system for protein expression in Rhodobacter sphaeroides, Appl Microbiol Biotechnol (2014) 98:3111–3119<br/><br/>
| + | |
| − | Jacob E. Vick & Ethan T. Johnson & Swat i Choudhar y & Sarah E. Bloch & Fern ando Lope z-Galleg o & Poonam Sr ivastava & Ilya B. Tikh & Grays on T. Wawrzy n & Claud ia Sc hmidt-Da nnert, Optimized compa tible set of BioBrick™ vectors for met abolic pathway engineering, Appl Microbiol Biotechnol (2011) 92:1275–1286<br/><br/>
| + | |
| − | Methods in Molecular Biology: Synthetic+Gene+Networks, John M. Walker, Wilfried Weber, Martin Fussenegger, Humana Press, 2012<br/><br/>
| + | |
| − | </p>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | | + | |
| − | <div class = "project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'scale-down'}"> | + | |
| − | <a name = "Validaction" id = "Validaction"></a>
| + | |
| − | <hr class = "border-line"/>
| + | |
| − | <div class = "validactionContent am-panel-hd">
| + | |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block2', target: '#do-not-say-3'}"><b>Validaction</b></h4>
| + | |
| − | </div>
| + | |
| − | <div class="am-panel-collapse am-collapse validactionContent" id = "do-not-say-3">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <p class = " validaction">勾勾丑丑哒</p>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | | + | |
| − | <div id = "block6" class = "am-panel-group">
| + | |
| − | <div class = "project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'scale-down'}">
| + | |
| − | <a name = "Improvement" id = "Demo"></a>
| + | |
| − | <hr class = "border-line" />
| + | |
| − | <div class = "demoContent am-panel-hd">
| + | |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block6', target: '#do-not-say-8'}"><b>Improvement</b></h4>
| + | |
| − | </div>
| + | |
| − | <div class="am-panel-collapse am-collapse demoContent" id = "do-not-say-8">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <p class = "improvement"><br/>The school of life science and biotechnology of Shanghai Jiao Tong University is one of the best in China. We have a long tradition of taking part in the iGEM competition. However, until 2014, we only had wet lab team for our school and our seniors organized the first software team of SJTU. Thanks to the experience shared by last year’s software team, we have a much more mature software team this year.<br/>
| + | |
| − | Before we considering the project of this year, we firstly conducted carefully investigation on projects of former software teams. During the process, we found a common problem that the former project only got maintenance for the year when the team took the competition. After several years, we cannot contact the people who were responsible for the software then and some of the software are excellent. In order to prevent this problem from happening to our project, we consulted the members of last year’s software team after we determined our main idea. Consequentially, we absorbed the most important results of easyBBK in our software. First of all, as an outstanding software, easyBBK has a highlight in the search function. So we added the search function on our push system (which helps users to construct and design devices. Moreover, we made the scoring system of easyBBK to be more flexible by allowing users to choose the weight of different parts and filter the score range.<br/>
| + | |
| − | Meanwhile, we use the usage count of every existing biobricks to determine the difference of their performances. After standardizing the format of biological data, we can have better and more concrete standards like the expression level to evaluate the property of biobricks. In the end, we hope SJTU software teams can continue to inherit and develop the work of former teams. This would meet the requirements of iGEM competition better.<br/></p>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | <div id = "block3" class = "am-panel-group">
| + | |
| − | <div class = "project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'scale-down'}">
| + | |
| − | <a name = "Demo" id = "Demo"></a>
| + | |
| − | <hr class = "border-line" />
| + | |
| − | <div class = "demoContent am-panel-hd">
| + | |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block3', target: '#do-not-say-4'}"><b>Demo</b></h4>
| + | |
| − | </div>
| + | |
| − | <div class="am-panel-collapse am-collapse demoContent" id = "do-not-say-4">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <p class = "">勾勾傻傻哒</p>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | <div id = "block4" class = "am-panel-group">
| + | |
| − | <div class = "project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'scale-down'}">
| + | |
| − | <a name = "Download" id = "Download"></a>
| + | |
| − | <hr class = "border-line" />
| + | |
| − | <div class = "demoContent am-panel-hd">
| + | |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block4', target: '#do-not-say-5'}"><b>Download</b></h4>
| + | |
| − | </div>
| + | |
| − | <div class="am-panel-collapse am-collapse downloadContent" id = "do-not-say-5">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <a href = "http://www.igembase.com" target = "_blank">勾勾么么哒</a>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | <div id = "block5" class = "am-panel-group">
| + | |
| − | <div class = "project-content am-panel am-panel-default" data-am-scrollspy="{animation: 'scale-down'}">
| + | |
| − | <a name = "Achivement" id = "Achivement"></a>
| + | |
| − | <hr class = "border-line"/>
| + | |
| − | <div class = "achivementContent am-panel-hd">
| + | |
| − | <h4 class = "am-panel-title" data-am-collapse="{parent: '#block5', target: '#do-not-say-6'}"><b>Achivement</b></h4>
| + | |
| − | </div>
| + | |
| − | <div class="am-panel-collapse am-collapse achivementContent" id = "do-not-say-6">
| + | |
| − | <div class = "panel-hd">
| + | |
| − | <p class = "achivement">1.We firstly include relationships between parts to the evaluation of devices.<br/>
| + | |
| − | 2.Our software can help in the whole process that a user designs a new device: the optimization of one part and another, and the visualization of the device.<br/>
| + | |
| − | 3.Our software enable users to design their personalised weight for part evaluation.<br/>
| + | |
| − | 4.Our software help users upload their parts more easily and can expand its own database.<br/>
| + | |
| − | 5.Our software is web-based, which is more convenient for users to use.<br/>
| + | |
| − | </p>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| − | </div>
| + | |
| | </div> | | </div> |
| − | </div>
| |
| − | <div class = "last">
| |
| − | </div>
| |
| | <footer> | | <footer> |
| | <div class = "am-g"> | | <div class = "am-g"> |
| Line 390: |
Line 67: |
| | <script src="https://2015.igem.org/Template:SJTU-Software/jqueryMinJs?action=raw&ctype=text/javascript"></script> | | <script src="https://2015.igem.org/Template:SJTU-Software/jqueryMinJs?action=raw&ctype=text/javascript"></script> |
| | <script src="https://2015.igem.org/Template:SJTU-Software/niceScrollJs?action=raw&ctype=text/javascript"></script> | | <script src="https://2015.igem.org/Template:SJTU-Software/niceScrollJs?action=raw&ctype=text/javascript"></script> |
| − | <script src="https://2015.igem.org/Template:SJTU-Software/projectJs?action=raw&ctype=text/javascript"></script>
| |
| | <!--<![endif]--> | | <!--<![endif]--> |
| | <!--[if lte IE 8 ]> | | <!--[if lte IE 8 ]> |
The school of life science and biotechnology of Shanghai Jiao Tong University is one of the best in China. We have a long tradition of taking part in the iGEM competition. However, until 2014, we only had wet lab team for our school and our seniors organized the first software team of SJTU. Thanks to the experience shared by last year’s software team, we have a much more mature software team this year.
Before we considering the project of this year, we firstly conducted carefully investigation on projects of former software teams. During the process, we found a common problem that the former project only got maintenance for the year when the team took the competition. After several years, we cannot contact the people who were responsible for the software then and some of the software are excellent. In order to prevent this problem from happening to our project, we consulted the members of last year’s software team after we determined our main idea. Consequentially, we absorbed the most important results of easyBBK in our software. First of all, as an outstanding software, easyBBK has a highlight in the search function. So we added the search function on our push system (which helps users to construct and design devices. Moreover, we made the scoring system of easyBBK to be more flexible by allowing users to choose the weight of different parts and filter the score range.
Meanwhile, we use the usage count of every existing biobricks to determine the difference of their performances. After standardizing the format of biological data, we can have better and more concrete standards like the expression level to evaluate the property of biobricks. In the end, we hope SJTU software teams can continue to inherit and develop the work of former teams. This would meet the requirements of iGEM competition better.
When we have collaborations with other igem teams, we find that most of teams use new parts to build their devices. Due to the new parts don't have enough feedbacks and uesd times which are the core grading standards in our algorithm, our software is hard to evaluate those kind of bricks with a high score. However, when we use blastn to compare the new parts' sequence with the existing parts' sequence in the database, we find that most of the new parts' sequence have high similarity with the old part in the database. Some parts even have same sequence as old parts in the database. And we also find that there are many parts with the same sequence in the database. So we want to add the blastn function to our website. When the researchers upload a part to the database, we can compare its sequence with the parts in the database. If there are some parts with same sequence as the new one in the database, we can inform the researchers this information and refuse the upload.
The blastn function can also help the users to find out which biobricks in the database is similar to their own biobrick. By checking these biobricks' information, users may get more help and enlightenment in their reseaches. What's more, blastn function can help our algorithm to evaluate the devices that cantain the new parts, which have been explained in our collaborations with other igem teams.