Team:SUSTC-Shenzhen-B/circuit.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="http://code.jquery.com/jquery-2.0.3.min.js"></script> ...")
Line 42: Line 42:
                                                         <li><a href="https://igem.org/Team_Wikis?year=2013">Back to iGEM Wiki Page</a></li>
                                                         <li><a href="https://igem.org/Team_Wikis?year=2013">Back to iGEM Wiki Page</a></li>
                                                         <li class="divider"></li>
                                                         <li class="divider"></li>
-
                                                         <li><a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/project.html&amp;action=edit">Edit</a></li>
+
                                                         <li><a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/circuit.html&amp;action=edit">Edit</a></li>
-
                                                         <li><a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/project.html&amp;action=history">History</a></li>
+
                                                         <li><a href="/wiki/index.php?title=Team:SUSTC-Shenzhen-B/circuit.html&amp;action=history">History</a></li>
                                                         <li><a href="https://igem.org/User_Information">My Account</a></li>
                                                         <li><a href="https://igem.org/User_Information">My Account</a></li>
     </ul>
     </ul>
Line 89: Line 89:
                                                 <li><a href="#mindroad">Mind Road</a></li>
                                                 <li><a href="#mindroad">Mind Road</a></li>
                                                 <li><a href="#lgd">LGD</a></li>
                                                 <li><a href="#lgd">LGD</a></li>
-
                                                 <li><a href="#ttec">TTEC on Clotho</a></li>
+
                                                 <li><a href="#tutorial">Tutorail</a></li>
                                                 <li><a href="#future">Future Plan</a></li>
                                                 <li><a href="#future">Future Plan</a></li>
-
  <li><a href="#tutorial">Tutorial</a></li>
 
   <li><a href="#feedback">Feedback</a></li>
   <li><a href="#feedback">Feedback</a></li>
-
  <li><a href="#safety">Safety Form</a></li>
 
-
  <li><a href="#achievement">Achievement</a></li>
 
</ul>
</ul>
</div>
</div>
<div class="span9">
<div class="span9">
-
<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>
<h2 id="introduction">Introduction</h2>
<h3>Mind Road</h3>
<h3>Mind Road</h3>

Revision as of 12:11, 27 September 2013

Introduction

Mind Road

A useful net structural mind map to help users know what the existing synthetic biology projects and what else they can do.

LGD

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.

TTEC

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.

Circuit Registry

Mind Road

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.

Circuit List

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.

LGD

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.

TTEC on Clotho

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.

Tutorial

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.

Feedback

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.

Safety Form

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.

Achievement

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.