Team:SUSTC-Shenzhen-B/project.html

From 2013.igem.org

(Difference between revisions)
(Created page with "<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8" /> <script src="js/bootstrap.min.js"></script> <link type="text/css" rel="stylesheet" href...")
 
(66 intermediate revisions not shown)
Line 1: Line 1:
<html>
<html>
-
<head>
+
  <head>
-
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+
    <meta charset="utf-8" />
-
<script src="js/bootstrap.min.js"></script>
+
    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
-
<link type="text/css" rel="stylesheet" href="https://2013.igem.org/SUSTC-SZ-B_2013iGEM/CSS/bootstrap.min.css?action=raw&amp;ctype=text/css" />
+
-
<link type="text/css" rel="stylesheet" href="css/bootstrap-responsive.min.css" />
+
-
<style type="text/css">
+
-
p {
+
-
text-indent: 2em;
+
-
}
+
-
#iGEM_nav {
+
-
padding:0;
+
-
padding-left:15px;
+
-
padding-right: 15px;
+
-
}
+
-
#iGEM_nav img {
+
-
height: 40px;
+
-
}
+
-
#content {
+
-
margin: 82px;
+
-
}
+
-
</style>
+
-
<script>
+
-
$(document).ready(function(){
+
-
                        $("head style").remove();
+
-
                        $("#top-section").remove();
+
-
                        $("#top").remove();
+
-
                        $("#siteSub").remove();
+
-
                        $("#footer-box").remove(); 
+
-
                        $(".printfooter").remove();   
+
-
                        $(".firstHeading").remove();               
+
-
                        var menu = document.getElementById('menu');
+
-
var init = menu.offsetTop;
+
-
var docked;
+
-
                        alert("1");
+
-
window.onscroll = function () {
+
-
                            /*if (!docked && (menu.offsetTop - scrollTop() < 0)) {
+
-
  menu.style.top = 0;
+
-
  menu.style.position = 'fixed';
+
-
  menu.className = 'docked';
+
-
  docked = true;
+
-
                        alert("2");
+
-
                            }
+
-
                            else if (docked && scrollTop() <= init) {
+
-
  menu.style.position = 'absolute';
+
-
  menu.style.top = init + 'px';
+
-
  menu.className = menu.className.replace('docked', '');
+
-
  docked = false;
+
-
                            }*/
+
-
};
+
-
function scrollTop() {
+
-
return document.body.scrollTop || document.documentElement.scrollTop;
+
-
}
+
-
});
+
-
</script>
+
-
</head>
+
-
<body data-spy="scroll" data-target=".bs-docs-sidebar">
+
-
<div class="navbar navbar-inverse navbar-fixed-top">
+
-
  <div class="navbar-inner">
+
-
    <div class="container">
+
-
      <a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
+
-
        <span class="icon-bar"></span>
+
-
        <span class="icon-bar"></span>
+
-
        <span class="icon-bar"></span>
+
-
      </a>
+
-
      <ul class="nav">
+
-
  <li class="dropdown"><a id="iGEM_nav" href="#" class="dropdown-toggle" data-toggle="dropdown"><img src="img/iGEM-white.gif" /><b class="caret"></b></a>
+
-
    <ul class="dropdown-menu">
+
-
      <form class="navbar-search pull-left">
+
-
  <input type="text" class="search-query" placeholder="Search">
+
-
</form>
+
-
    </ul>
+
-
  </li>
+
-
</ul>
+
-
      <div class="nav-collapse collapse">
+
-
      <ul class="nav">
+
-
  <li class="active"><a href="#">Project</a></li>
+
-
  <li><a href="team.html">Team</a></li>
+
-
  <li><a href="human.html">Human Practice</a></li>
+
-
  <li><a href="notebook.html">Notebook</a></li>
+
-
</ul>
+
-
      </div>
+
-
    </div>
+
-
  </div>
+
-
</div>
+
-
<div id="content" class="container">
+
    <meta name="description" content="" />
-
<div class="row">
+
    <meta name="author" content="SUSTC-ShenZhen-B" />
-
<div class="span3 bs-docs-sidebar">
+
-
<ul class="nav nav-list" data-spy="affix" data-offset-top="200">
+
-
  <li class="active"><a href="#background">Background</a></li>
+
-
  <li><a href="#introduction">Introduction</a></li>
+
-
  <li><a href="#application">Application</a></li>
+
-
  <li><a href="#tutorial">Tutorial</a></li>
+
-
  <li><a href="#comment">Comment</a></li>
+
-
  <li><a href="#safety">Safety Form</a></li>
+
-
  <li><a href="#sponsor">Sponsor</a></li>
+
-
</ul>
+
-
</div>
+
-
<div class="span9">
+
-
<h2>Overview</h2>
+
-
<p>Our project, 3 Miao BioCommunity, is different from all the iGem software projects in the past, for we have an ambition to create a community for the whole synthetic biology. This community is based on our original idea, the Mind Road. Mind Road is a net structural mind map that can help users think and share ideas, which can function as a platform for all synthetic biology ideas exchange. </p>
+
-
<p>Based on the Mind Road, our community now has a theme—— share ideas. With this theme, we intend to build our 3Miao BioCommunity. In this community, we offer LGD and TTEC as useful tool for users to process the ideas. LGD is a genetic circuit designer which can present the logical relationship of related parts. What is more, users can also post their own ideas and comment on others’ work, like Facebook and Twitter.</p>
+
-
<h2 id="background">Background</h2>
+
-
<p>Before we got our idea, we had reviewed all the software projects of the last three years and classified them into 6 categories (fig1). As showing in the picture, designing CAD takes up the majority of these projects. As expected, most of them share the similar ideas. After a certain time of thinking, we found that it is really reasonable that iGem software projects can hardly be quite innovative, for the lack of professional knowledge and the limitation of the usage of software during synthetic biology study. But also, if we continue to follow these ideas, our project is far away from being creative or original. Then it occurred to us, why don’t we write a program to help at least the wet lab members to get new ideas? Thus, we decided to make a difference, to create our own Mind Road—— a net structural mind map—— to assist either iGEMers or professional synthetic biology researchers to come up with and share their ideas.</p>
+
-
<p>Even though the mind map idea is good, it is not good enough. What’s more, comparing with computer software, synthetic biology lacks such community for knowledge and skills exchange, like GitHub. So setting Mind Road as the theme, we decided to take a bold step, to establish a simple and free online platform with high interaction ability intended for everyone interested in synthetic biology.</p>
+
-
<h2 id="introduction">Introduction</h2>
+
-
<h3>Mind Road</h3>
+
-
<p>A useful net structural mind map to help users know what the existing synthetic biology projects and what else they can do.</p>
+
-
<h3>LGD</h3>
+
-
<p>Short for logical genetic designer, LGD is a genetic circuit CAD that can present the detail information of the engineering bacteria and “calculate” the relationship of related parts based on our database.</p>
+
-
<h3>TTEC</h3>
+
-
<p>TTEC is the abbreviation of Transcriptional Terminator Efficiency Calculator. It is the last year’s project of SUSTC and can calculate the efficiency of a terminator. TTEC plays an important role of building up our synthetic biology community in the future.</p>
+
-
<h2 id="application">Application</h2>
+
    <title>SUSTC-ShenZhen-B</title>
-
<p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
 
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
    <style type="text/css">
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #globalWrapper {width: 100%;font-size: 100%;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #top-section {width: 100%; height:100%; border:none;}
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #p-logo {display:none;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #search-controls {display:none;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      .printfooter {display:none;}
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #footer-box {border:none;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      .firstHeading {display:none;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #content { border:none !important; width:1024px !important; background: url('') !important;}
-
</p>
+
      #bodyContent {border:none;}
-
<h2 id="tutorial">Tutorial</h2>
+
      #catlinks {display:none;}
-
<p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #footer-box {display:none;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      #menubar {display:none;}
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      body {
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        padding: 0;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      }
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
 
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      .caret {
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        display: inline-block;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        width: 0;
-
</p>
+
        height: 0;
-
<h2 id="comment">Comment</h2>
+
        margin-left: 2px;
-
<p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        vertical-align: middle;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        border-top: 4px solid #000000;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        border-right: 4px solid transparent;
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        border-bottom: 0 dotted;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        border-left: 4px solid transparent;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        content: "";
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      }
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      .icon.caret {
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        opacity: 0.75;
-
</p>
+
      }
-
<h2 id="safety">Safety Form</h2>
+
      .white.caret {
-
<p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        border-top-color: #FFFFFF;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      }
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      .main.menu {
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        top: 0;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      }
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      .script.image {
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        display: none;
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      }
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
    </style>
-
</p>
+
    <link rel="stylesheet" type="text/css" href="/SUSTC-SZ-B_2013iGEM/CSS/wiki-all.min.css?action=raw&amp;ctype=text/css" />
-
<h2 id="sponsor">Sponsor</h2>
+
    <link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700|Open+Sans:300italic,400,300,700" />
-
<p>We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
 
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
  </head>
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
  <body id="example">
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
    <div class="ui fixed transparent inverted main menu">
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
      <div class="container">
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        <a href="#" class="brand">SUSTC-ShenZhen-B</a>
-
mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        <div class="right menu">
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
          <a href="http://circuitplus.org" class="item">Visit Circuit+</a>
-
We want to establish a user-friendly web2.0 platform which can function as both a handy tool kit and a community. There are mainly 3 reasons that we choose a webpage instead of a native application. First, current software need to users don’t need to download our software. Second, a webpage is not limited with the system, which means users can log in our webpage wherever they can reach the internet. And the last, all the information can be stored by the cloud, so users don’t have to worry about their information being lost.
+
        </div>
-
</p>
+
        <div href="/" class="ui dropdown link item">
-
</div>
+
          iGEM
-
</div>
+
          <span class="icon white caret"></span>
-
</div>
+
          <div class="menu">
-
</body>
+
            <a href="https://2013.igem.org/Main_Page" class="item">iGEM homepage</a>
 +
            <a href="/Team:SUSTC-Shenzhen-B" class="item">wiki homepage</a>
 +
            <a href="https://igem.org/User_Information" class="item">My Account</a>
 +
            <a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/project.html&amp;action=edit" class="item">Edit</a>
 +
          </div>
 +
        </div>
 +
        <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/project.html" class="item active">Overview</a>
 +
        <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/standard.html" class="item">Standard and database</a>
 +
        <div href="/" class="ui dropdown link item">
 +
          Software
 +
          <span class="white caret"></span>
 +
          <div class="menu">
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/circuitplus.html" class="item">Circuit+</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/tutorial.html" class="item">Tutorial</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/safety.html" class="item">Safety</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/feedback.html" class="item">Feedback</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/future.html" class="item">Future</a>
 +
            <a href="/Team:SUSTC-Shenzhen-B/lab.html" class="item">Lab Manager</a>
 +
            <a href="/Team:SUSTC-Shenzhen-B/clotho.html" class="item">Clotho</a>
 +
          </div>
 +
        </div>
 +
        <div href="/" class="ui dropdown link item">
 +
          Human practice
 +
          <span class="white caret"></span>
 +
          <div class="menu">
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/workshop.html" class="item">Workshop meeting</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/publicity.html" class="item">Publicity</a>
 +
          </div>
 +
        </div>
 +
        <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/achievement.html" class="item">Achievement</a>
 +
        <div href="/" class="ui dropdown link item">
 +
          Team
 +
          <span class="white caret"></span>
 +
          <div class="menu">
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/about.html" class="item">About us</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/notebook.html" class="item">Notebook</a>
 +
            <a href="https://2013.igem.org/Team:SUSTC-Shenzhen-B/acknowledgement.html" class="item">Acknowledgement</a>
 +
          </div>
 +
        </div>
 +
      </div>
 +
    </div>
 +
    <div class="header">
 +
      <div class="segment">
 +
        <div id="overview" class="container">
 +
          <div class="introduction">
 +
            <h1 class="ui dividing header">Overview</h1>
 +
            <p class="lead">Have a glimpse of our project.</p>
 +
          </div>
 +
        </div>
 +
      </div>
 +
    </div>
 +
    <div class="main container page">
 +
      <div class="peek">
 +
        <div class="ui vertical pointing secondary menu">
 +
          <a class="active item">Motivation</a>
 +
          <div class="link item">Actions
 +
            <div class="menu">
 +
              <a class="item">Technical standard</a>
 +
              <a class="item">Circuit+</a>
 +
              <a class="item">LGD</a>
 +
              <a class="item">SBOL</a>
 +
              <a class="item">Clotho application: Circuit List and TTEC</a>
 +
            </div>
 +
          </div>
 +
          <a class="active item" href="/Team:SUSTC-Shenzhen-B">Back to Homepage</a>                     
 +
        </div>
 +
      </div>
 +
      <div class="page-container">
 +
        <h2 class="ui dividing header">Motivation</h2>
 +
        <section id="motivation"></section>
 +
        <p>Our project focuses on genetic circuits. In the last ten years, iGEM competition has produced and collected thousands of biobricks. And extensive efforts have been made to create the technique standard for biobricks. A genetic circuit usually composes of several biobricks and can perform some predefined function. Our project aim to go one step further, that we develop the technique standard for genetic circuits and build up a central database for collecting and sharing genetic circuits.</p>
 +
 
 +
        <h2 class="ui dividing header">Actions</h2>
 +
        <section id="actions"></section>
 +
        <p>So, here are our actions</p>
 +
        <h3><img src="https://static.igem.org/mediawiki/2013/4/40/Standard%2832%29.png" />Technical standard</h3>
 +
        <p>We proposed two technical standards this year (RFC 101 and RFC 97) to define logical gene module and genetic circuits.</p>
 +
        <h3><img src="https://static.igem.org/mediawiki/2013/a/a3/Logo%2832%29.png">Circuit+</h3>
 +
        <h5>a central database for genetic circuits</h5>
 +
        <p>Inspired by the Registry of Standard Biological Part database, we came up with an ambitious plan that we should make the Registry of Standard Genetic Circuit. Our goal is to collect all previous iGEM projects and all published synthetic biology projects.</p>
 +
        <p>The ultimate goal of our project is to promote sharing in synthetic biology community! We have a future plan of establishing a community based on Mind Road and LGD, for we clearly know the importance of sharing design. To make the sharing efficient and effective, we proposed a technique standard for documentation of a genetic circuit</p>
 +
        <h3><img src="https://static.igem.org/mediawiki/2013/6/60/Lab%2832%29.png" />LGD</h3>
 +
        <p>LGD is short for Logical Genetic Digram. It is a computer aided graphical generator integrated into our database. User can see the circuits and the relations between parts.</p>
 +
        <h3><img src="https://static.igem.org/mediawiki/2013/7/71/Humanpractise%2832%29.png" />SBOL</h3>
 +
        <p>Our software support SBOL. SBOL is used in the data-exchanging interface of the software and users can upload and comment circuits.</p>
 +
        <h3><img src="https://static.igem.org/mediawiki/2013/2/2d/Clotho%2832%29.png" />Clotho application: Circuit List and TTEC</h3>
 +
        <p>We developed a Clotho version of circuitplus, with the name “Circuit List”. We also developed TTEC in clotho, which is originally created by SUSTC-Shenzhen-B in 2012.</p>
 +
      </div>
 +
    </div>
 +
 
 +
    <div class="footer">
 +
      <div class="ui divider">
 +
      </div>
 +
      <div class="ui divided horizontal footer link list">
 +
        <div class="item">
 +
          &copy; 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&amp;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>

Latest revision as of 03:26, 29 October 2013

SUSTC-ShenZhen-B

SUSTC-ShenZhen-B
Visit Circuit+
iGEM
iGEM homepage wiki homepage My Account Edit
Overview Standard and database
Software
Circuit+ Tutorial Safety Feedback Future Lab Manager Clotho
Human practice
Workshop meeting Publicity
Achievement
Team
About us Notebook Acknowledgement

Overview

Have a glimpse of our project.

Motivation
Actions
Technical standard Circuit+ LGD SBOL Clotho application: Circuit List and TTEC
Back to Homepage

Motivation

Our project focuses on genetic circuits. In the last ten years, iGEM competition has produced and collected thousands of biobricks. And extensive efforts have been made to create the technique standard for biobricks. A genetic circuit usually composes of several biobricks and can perform some predefined function. Our project aim to go one step further, that we develop the technique standard for genetic circuits and build up a central database for collecting and sharing genetic circuits.

Actions

So, here are our actions

Technical standard

We proposed two technical standards this year (RFC 101 and RFC 97) to define logical gene module and genetic circuits.

Circuit+

a central database for genetic circuits

Inspired by the Registry of Standard Biological Part database, we came up with an ambitious plan that we should make the Registry of Standard Genetic Circuit. Our goal is to collect all previous iGEM projects and all published synthetic biology projects.

The ultimate goal of our project is to promote sharing in synthetic biology community! We have a future plan of establishing a community based on Mind Road and LGD, for we clearly know the importance of sharing design. To make the sharing efficient and effective, we proposed a technique standard for documentation of a genetic circuit

LGD

LGD is short for Logical Genetic Digram. It is a computer aided graphical generator integrated into our database. User can see the circuits and the relations between parts.

SBOL

Our software support SBOL. SBOL is used in the data-exchanging interface of the software and users can upload and comment circuits.

Clotho application: Circuit List and TTEC

We developed a Clotho version of circuitplus, with the name “Circuit List”. We also developed TTEC in clotho, which is originally created by SUSTC-Shenzhen-B in 2012.

© SUSTC-ShenZhen-B

Retrieved from "http://2013.igem.org/Team:SUSTC-Shenzhen-B/project.html"