Team:SUSTC-Shenzhen-B/future.html
From 2013.igem.org
Line 1: | Line 1: | ||
<html> | <html> | ||
- | + | <head> | |
- | + | <meta charset="utf-8" /> | |
- | + | <meta http-equiv="content-type" content="text/html; charset=UTF-8" /> | |
- | + | ||
- | + | <meta name="description" content="" /> | |
- | + | <meta name="author" content="SUSTC-ShenZhen-B" /> | |
- | + | ||
- | + | <title>SUSTC-ShenZhen-B</title> | |
- | + | ||
- | + | <style type="text/css"> | |
- | + | #globalWrapper {width: 100%;font-size: 100%;} | |
- | + | #top-section {width: 100%; height:100%; border:none;} | |
- | + | #p-logo {display:none;} | |
- | + | #search-controls {display:none;} | |
- | + | .printfooter {display:none;} | |
- | + | #footer-box {border:none;} | |
- | + | .firstHeading {display:none;} | |
- | + | #content { border:none !important; width:1024px !important; background: url('') !important;} | |
- | + | #bodyContent {border:none;} | |
- | + | #catlinks {display:none;} | |
- | + | #footer-box {display:none;} | |
- | + | #menubar {display:none;} | |
- | + | body { | |
- | + | padding: 0; | |
- | + | } | |
- | + | ||
- | + | .caret { | |
- | + | display: inline-block; | |
- | + | width: 0; | |
- | + | height: 0; | |
- | + | margin-left: 2px; | |
- | + | vertical-align: middle; | |
- | + | border-top: 4px solid #000000; | |
- | + | border-right: 4px solid transparent; | |
- | + | border-bottom: 0 dotted; | |
- | + | border-left: 4px solid transparent; | |
- | + | content: ""; | |
- | + | } | |
- | + | .icon.caret { | |
- | + | opacity: 0.75; | |
- | + | } | |
- | + | .white.caret { | |
- | + | border-top-color: #FFFFFF; | |
- | + | } | |
- | + | .main.menu { | |
- | + | top: 0; | |
- | + | } | |
- | + | .script.image { | |
- | + | display: none; | |
- | + | } | |
- | + | </style> | |
- | + | <link rel="stylesheet" type="text/css" href="/SUSTC-SZ-B_2013iGEM/CSS/wiki-all.min.css?action=raw&ctype=text/css" /> | |
- | + | <link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700|Open+Sans:300italic,400,300,700" /> | |
- | + | ||
- | + | </head> | |
- | + | <body id="example"> | |
- | + | <div class="ui fixed transparent inverted main menu"> | |
- | + | <div class="container"> | |
- | + | <a href="#" class="brand">SUSTC-ShenZhen-B</a> | |
- | + | <div class="right menu"> | |
- | + | <a href="https://igem.org/User_Information" class="item">My Account</a> | |
- | + | </div> | |
- | + | <div href="/" class="ui dropdown link item"> | |
- | + | iGEM Home | |
- | + | <span class="icon white caret"></span> | |
- | + | <div class="menu"> | |
- | + | <a href="https://2013.igem.org/Main_Page" class="item">iGEM homepage</a> | |
- | + | <a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/future.html&action=edit" class="item">Edit</a> | |
- | + | </div> | |
- | + | </div> | |
- | + | <a href="project.html" class="item">Overview</a> | |
- | + | <a href="standard.html" class="item">Standard and database</a> | |
- | + | <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item active"> | |
- | + | Software | |
- | + | <span class="white caret"></span> | |
- | + | <div class="menu"> | |
- | + | <a href="circuitplus.html" class="item">Circuit+</a> | |
- | + | <a href="feature.html" class="item">Feature</a> | |
- | + | <a href="tutorial.html" class="item">Tutorial</a> | |
- | + | <a href="safety.html" class="item">Safety</a> | |
- | + | <a href="APIs.html" class="item">APIs</a> | |
- | + | <a href="feedback.html" class="item">Feedback</a> | |
- | + | <a href="future.html" class="item">Future</a> | |
- | + | </div> | |
- | + | </div> | |
- | + | <a href="clotho.html" class="item">Clotho</a> | |
- | + | <a href="lab.html" class="item">Lab management</a> | |
- | + | <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item"> | |
- | + | Human practice | |
- | + | <span class="white caret"></span> | |
- | + | <div class="menu"> | |
- | + | <a href="workshop.html" class="item">Workshop meeting</a> | |
- | + | <a href="publicity.html" class="item">Publicity</a> | |
- | + | </div> | |
- | + | </div> | |
- | + | <div href="/Team:SUSTC-Shenzhen-B/Project" class="ui dropdown link item"> | |
- | + | Team | |
- | + | <span class="white caret"></span> | |
- | + | <div class="menu"> | |
- | + | <a href="about.html" class="item">About us</a> | |
- | + | <a href="achievement.html" class="item">Achievement</a> | |
- | + | <a href="notebook.html" class="item">Notebook</a> | |
- | + | <a href="acknowledgement.html" class="item">Acknoledgement</a> | |
- | + | </div> | |
- | + | </div> | |
- | + | <a href="/Team:SUSTC-Shenzhen-B/Desktop" class="desktop item">Only Desktop visible</a> | |
- | + | </div> | |
- | + | </div> | |
- | + | <div class="header"> | |
- | + | <div class="segment"> | |
- | + | <div id="overview" class="container"> | |
- | + | <div class="introduction"> | |
+ | <h1 class="ui dividing header">Future</h1> | ||
+ | <p class="lead">The next version of Circuit+</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="main container page"> | ||
+ | <div class="peek"> | ||
+ | <div class="ui vertical pointing secondary menu"> | ||
+ | <a class="active item">Making standard for regulatory relations</a> | ||
+ | <a class="active item">Update Database</a> | ||
+ | <a class="active item">Improve SBOL</a> | ||
+ | <a class="active item">Redesign LGD</a> | ||
+ | <a class="active item">Cooperate with the Registry of Standard Biological Parts</a> | ||
+ | <a class="active item">Promote the software</a> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="page-container"> | ||
+ | <h2 class="ui dividing header">Making standard for regulatory relations</h2> | ||
+ | <section id="motivation"></section> | ||
+ | <p>So far, we have made standard for logical gene module and genetic circuit (RFC 101 and RFC 102). To represent the relations between parts in circuit and to go back to the origin idea in synthetic biology that relations exist in circuit, a standard to describe the logical relations between parts is needed. So, we will make this standard and revise existing standard RFC 101 and RFC 102 to make them compatible.</p> | ||
+ | <h2 class="ui dividing header">Update Database</h2> | ||
+ | <section id="motivation"></section> | ||
+ | <p>The information in the database is not perfect now. We will update database both from structure and content in the next version. The structure can be improved to coordinate the standard better. More and better quality of circuits will be recorded from collecting and uploading.</p> | ||
+ | <h2 class="ui dividing header">Improve SBOL</h2> | ||
+ | <section id="motivation"></section> | ||
+ | <p>We use extensions in SBOL exported by Circuit+ and this may result in some errors when other software reading this SBOL. We will fix this bug in the next version of Circuit+. We think we can also add our software to SBOL’s website as an example of how to use SBOL and join in the g+ group of SBOL to build a better SBOL.</p> | ||
+ | <h2 class="ui dividing header">Redesign LGD</h2> | ||
+ | <section id="motivation"></section> | ||
+ | <p>In the first plan of our software, Logical Genetic Designer, which is also can be written as LGD, would be very powerful. Except the functions that Logical Genetic Diagram have, Logical Genetic Designer can also help users to redesign the circuits and show the relations in the new circuits. It can also show the relations between parts in circuit and gene that on the typical plasmids of E. coli. What’s more, it can even do modeling. Equipped with Logical Genetic Designer, you can designer your circuit very easily and wet lab time will be reduced. However, as freshmen when we came up with this idea, we found it too difficult. So we decided to do that step by step and this is why you can see LGD’s first version, Logical Genetic Designer. Believe us and we will make a true LGD in the future.</p> | ||
+ | <h2 class="ui dividing header">Cooperate with the Registry of Standard Biological Parts</h2> | ||
+ | <section id="motivation"></section> | ||
+ | <p>We will contact the Registry of Standard Biological Parts. We have employed some data from the Registry through their API. The Registry and Circuit+ have many things in common and they are complementary to some degree. We think cooperation of the Registry of Standard Biological Parts and Circuit+ will open a new age of synthetic biology.</p> | ||
+ | <h2 class="ui dividing header">Promote the software</h2> | ||
+ | <section id="motivation"></section> | ||
+ | <p>We will promote our software as well as synthetic biology in the future. The open database needs your participation and we are waiting for you!</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | <div class="footer"> | ||
+ | <div class="ui divider"> | ||
+ | </div> | ||
+ | <div class="ui divided horizontal footer link list"> | ||
+ | <div class="item"> | ||
+ | © SUSTC-ShenZhen-B | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | <script type="text/javascript" src="http://code.jquery.com/jquery-2.0.3.min.js"></script> | ||
+ | <script type="text/javascript" src="https://2013.igem.org/SUSTC-SZ-B_2013iGEM/JS/wiki-all.min.js?action=raw&ctype=text/javascript"></script> | ||
+ | |||
+ | <script type="text/javascript"> | ||
+ | function png2text(pngurl, id, callback) { | ||
+ | var canvas = document.createElement("canvas"), | ||
+ | ctx = canvas.getContext("2d"); | ||
+ | img = new Image(); | ||
+ | |||
+ | img.id = 'pt-' + id; | ||
+ | img.className = 'script image'; | ||
+ | img.style.position = "absolute"; | ||
+ | img.style.left = "-10000px"; | ||
+ | document.body.appendChild(img); | ||
+ | |||
+ | img.onload = function() { | ||
+ | var | ||
+ | w = this.width, | ||
+ | h = this.height; | ||
+ | |||
+ | canvas.width = w; | ||
+ | canvas.height = h; | ||
+ | canvas.style.width = w+"px"; | ||
+ | canvas.style.height = h+"px"; | ||
+ | |||
+ | ctx.drawImage(this, 0, 0); | ||
+ | |||
+ | var data = ctx.getImageData(0, 0, w, h).data, | ||
+ | a = [], | ||
+ | len = data.length, | ||
+ | p = -1; | ||
+ | |||
+ | for (var i=0; i < len; i += 4) { | ||
+ | if (data[i] > 0) | ||
+ | a[++p] = String.fromCharCode(data[i]); | ||
+ | }; | ||
+ | |||
+ | canvas = undefined; | ||
+ | try { | ||
+ | //document.body.removeChild(img); | ||
+ | $('#pt-' + id).remove(); | ||
+ | } catch (e) { | ||
+ | } | ||
+ | |||
+ | if (callback) callback(a.join("")); | ||
+ | }; | ||
+ | |||
+ | img.src = pngurl; | ||
+ | } | ||
+ | |||
+ | function baseRemove() { | ||
+ | $('#top-section').remove(); | ||
+ | $('#content').attr('id', ''); | ||
+ | $('#bodyContent').attr('id', ''); | ||
+ | $('#globalWrapper').attr('id', ''); | ||
+ | |||
+ | $('.main.container.page').parent().attr('id', 'example'); | ||
+ | } | ||
+ | |||
+ | function loadJavascript() { | ||
+ | /* $.get("https://2013.igem.org/SUSTC-SZ-B_2013iGEM/JS/wiki-all.min.js?action=raw&ctype=text/javascript", function (data) { | ||
+ | eval(data); | ||
+ | }); */ | ||
+ | /* png2text('https://static.igem.org/mediawiki/2013/4/43/Wiki-all-min-js.png', 'wiki-all', function (text) { | ||
+ | eval(text); | ||
+ | }); */ | ||
+ | } | ||
+ | |||
+ | $(document).ready(function () { | ||
+ | baseRemove(); | ||
+ | loadJavascript(); | ||
+ | }); | ||
+ | </script> | ||
+ | </body> | ||
</html> | </html> |
Revision as of 01:55, 28 October 2013
Future
The next version of Circuit+
Making standard for regulatory relations
So far, we have made standard for logical gene module and genetic circuit (RFC 101 and RFC 102). To represent the relations between parts in circuit and to go back to the origin idea in synthetic biology that relations exist in circuit, a standard to describe the logical relations between parts is needed. So, we will make this standard and revise existing standard RFC 101 and RFC 102 to make them compatible.
Update Database
The information in the database is not perfect now. We will update database both from structure and content in the next version. The structure can be improved to coordinate the standard better. More and better quality of circuits will be recorded from collecting and uploading.
Improve SBOL
We use extensions in SBOL exported by Circuit+ and this may result in some errors when other software reading this SBOL. We will fix this bug in the next version of Circuit+. We think we can also add our software to SBOL’s website as an example of how to use SBOL and join in the g+ group of SBOL to build a better SBOL.
Redesign LGD
In the first plan of our software, Logical Genetic Designer, which is also can be written as LGD, would be very powerful. Except the functions that Logical Genetic Diagram have, Logical Genetic Designer can also help users to redesign the circuits and show the relations in the new circuits. It can also show the relations between parts in circuit and gene that on the typical plasmids of E. coli. What’s more, it can even do modeling. Equipped with Logical Genetic Designer, you can designer your circuit very easily and wet lab time will be reduced. However, as freshmen when we came up with this idea, we found it too difficult. So we decided to do that step by step and this is why you can see LGD’s first version, Logical Genetic Designer. Believe us and we will make a true LGD in the future.
Cooperate with the Registry of Standard Biological Parts
We will contact the Registry of Standard Biological Parts. We have employed some data from the Registry through their API. The Registry and Circuit+ have many things in common and they are complementary to some degree. We think cooperation of the Registry of Standard Biological Parts and Circuit+ will open a new age of synthetic biology.
Promote the software
We will promote our software as well as synthetic biology in the future. The open database needs your participation and we are waiting for you!