Team:USTC Software/dev

From 2010.igem.org

Revision as of 20:07, 27 October 2010 by Soimort (Talk | contribs)


USTC Software

GATCAATTCAGCAGCTTTCTG
ATACGGCCAACAAAA
CTCCTACGAAAGGTGCACAAC
GATCAATTCAGCAGCTTT
TGACTCCTACGAAAGGTGCAC
AGGTTGTGAATTAATGCTCCG
ATGGATCAATTCAGCAGC
ATACGGCCAACAAAA
ATGGATCAATTCAGCAGCTTTTAAATA
CTCCTACGAAAGGTGCACAAC
TGACTCCTACGAAAGGTGCAC
AGGTTGTGAATTAATGCTCCG
ATGGATCAATTCAGCAGC
GATCAACAATTCTTCAGCAGCTTT
TGACTCCTACGAAAGGTGCACAAC
ATACGGCCAACAAAA
CTCCTACGAAAGGTGCACTGCAAC
Getting Started


[For iGEMers]
>> Have a look at our
Project and Human Practice

[For Biologists]
>> Getting to know our
MoDeL and Demos

[For Programmers]
>> Learn more about our software and source code

What's New?


[Oct. 27]
- Wiki Freeze

[Nov. 5~9]
- iGEM Jamboree @MIT


Recommendations For Our Project:

New Database Language
Demos of Automatic Modeling
Human Practice

Project


To promote public awareness of synthetic biology and introduce its basic ideas to the laymen, our team devoted to the development of an experimental video game which aims at instructing non-biologists to design and improve biological systems. Following the games-with-a-purpose paradigm in which players help solve scientific problems, we attempt to apply the human brain's puzzle-solving abilities to the complex designs of biological systems. While most of developed simulation tools are designed for experts to model the reaction networks from scratch, our game integrates a modeling environment in which users only need to submit their assembling of parts for our program to discover and generate the biological model automatically.

Learn more about our project ...
[Intro]   [User Interface]   [MoDeL]   [Algorithm]   [Resources]
MoDeL


A new language called MoDeL (Standard Biological Parts Modeling Database Language) is proposed for automatic modeling of biological systems. Due to introducing of novel concepts of species and reaction templates, which are two main components in MoDeL, interactions between species need not to be completely provided and thus making automation possible.

Learn more about MoDeL ...
[Intro]   [Features]   [Standardization]   [Future Work]
Demo


To show results of our program, some classical genetic regulatory networks are provided as demos, including toggle switch, repressilator as well as quorum-sensing oscillator. Each selected demo, representing a certain pattern of reaction network in biological process, is carefully designed to cover all our features as much as possible.

Have a look at our demos ...
Tools


Getting started with our tools !
Notebook


Have a look at our notebook ...
Human Practice


We started a long term human practice, "the C project", since this summer to explore the approaches of promotion of synthetic biology. "the C project", as we call, consists of three parts: Curriculum, Communication and Community. All three parts are carefully designed and organized.

Learn more about our human practice project ...
[Overview]   [The C Project]   [Safety]
Team


We are a team of both undergraduate and graduate students along with many advisors. This is the second year that USTC has sent a software team to iGEM.

Learn more about our team ...

Visitor Locations
Locations of visitors to this page

Introduction
Introduction

One-Minute Introduction

You are about to begin an exciting journey of the main ideas in MoDeL. For each picture, start from the green flag, follow the arrows, and finally you will reach the destination! Read on from the first step or click one of the three steps!

Chain-Node Model -> Template Modeling -> Automatic Modeling Database Language

Ustcs Go.jpg


Chain-Node Model

Ustcs WIKI widescreen 1.jpg


Ustcs WIKI widescreen 2.jpg


Ustcs WIKI widescreen 3.jpg


Ustcs WIKI widescreen 4.jpg


Ustcs WIKI widescreen 5.jpg


Back Up

Template Modeling

Ustcs WIKI widescreen 6.jpg


Ustcs WIKI widescreen 7.jpg


Back Up

Automatic Modeling Database Language

Ustcs WIKI widescreen 8.jpg

Back Up


Ustcs Finish.jpg

Read More on MoDeL Here! Read More on Our Project Here!

Features
Features

Features

Chain-Node Model

Figure 1: Logo of Chain-Node Model
In most manual modeling, complex is treated as a whole entity in reactions. Plenty of synthetic biology automatic modeling software treats complex the same way. However, there is a big difference between manual and automatic modeling, that is: Model constructors always know which detail of complex needs to be ignored or preserved, but software does not. So in most software, detailed structure has to be specified by modelers, otherwise will be ignored. In most cases, this requires plenty of manual operations and thus making the software not so automatic. Knowing this, MoDeL chooses to preserve detailed structure in complex and present Chain-Node Model, which view complex as a construction of its parts throughout the modeling process. With chain and nodes, describing large biological complex with a great number of basic units and binding sites becomes possible. It also offers great flexibility in modeling. Detailed concepts are explained below.


Abstract Concept of Chain

When it comes to biobrick assembly, DNA of plasmid is often considered as an abstract straight line where biobricks can be placed on and connected together. It actually acts as the basic frame of biobrick assembly. Inspired by this, we present the abstract concept of chain, which also acts as the basic frame of part assembly. Chain is an abstract straight line where different parts can be placed on and connected together. Part is the basic unit of chain, and chain can have as many parts as possible.
To go beyond DNA, and to unify the data structure of Species, we extend the concept of chain in MoDeL to include all the parts we can describe, including RNA, protein, and even compartment, compound and substituent, etc. Parts of DNA, RNA and protein, are all originated from DNA, and they are considered as “Sequence”. Sequence can be connected to other parts of sequence on a chain. On the contrary, parts of compartment and compound are considered as “Non-sequence”. Parts of non-sequence cannot be connected to any other part on a chain, which means, they can only exist on a One-Part-Chain. Substituent is used as a substitution of any other part, so it can be either sequence or non-sequence.
It is important here to mention that the Sequence/Non-sequence division is only a rule guide the modeling. It is not a constraint to Chain-Node model. Actually, we choose to maximally preserve the flexibility and leave all the freedom of constructing a species to users. Users are allowed to construct ANY species they can using Chain-Node Model. For example, one can create a strange species with compartment, compound, and DNA parts on the same chain, which makes little sense in biology. So, it is really up to the users to decide how to use Chain-Node Model in modeling.


Abstract Concept of Node

Node is used to characterize binding structure in biological complex. Node is an abstract concept of binding site or site that can be bond. Links always exist between a binding site and the sites it binds together, indicating the relationship between them. We use trees to represent the binding structure in complex. The parent node represents the binding site, and the child node represents the bond sites. For example the binding structure of TetR dimer is considered as a TetR2 node with two TetR nodes as its children. There is one exception though, the ROOT node. ROOT node is used as the top node in a tree. It can only have one child and no parent. The function of ROOT is to indicate that its child is the last binding site in this tree, and it binds to nothing any more.
In the reactions of promoter repression and activation, the promoter is repressed or activated after binding with repressor or inducer. So its properties are changed, and it is not the original promoter any more. This is an example where binding changes the properties of node. Since we do not store all the possible property alterations within one part, the solution is to replace the old part with a new part that stores the correct properties.
Available nodes can be both a part on a chain or a node of binding site, which leaves a lot of possibilities in constructing complicated binding structure. Again, there are no restrictions, but parts of compartments are not suggested to appear in a binding structure.


The Basic Assumption

The basic assumption of Chain-Node Model is that a part ALWAYS carries its properties wherever it is placed in an instance of Chain-Node Model. This means no matter how complicated the complex is, you can always keep track of the location and properties of every single part. By letting complex inherits its parts’ properties, the assumption saves modelers from rewriting the structure and function of each new complex. However, we should address that the assumption is not suitable for all circumstances. For example, under this assumption, a fusion protein will carry the properties of the fused proteins, which is not true in many cases. A fusion protein may not remain its old properties and even have new properties that none of the original parts have. In this case, our suggestion is to define the fusion protein as a new part. So it is suggested that users choose different strategies of describing the same thing in Chain-Node Model base on different situations, instead of modeling everything in the same way.


Examples

With great power there must come great responsibility. In order to use the powerful Chain-Node Model correctly, please have a look at a few examples we presents.
Example of a species: E.coli cell

In MoDeL, the cell of E.coli is described as a species with only one part of E.coli(see Figure 1). Since the concept of part has been extended greatly, living cells can be described in the same way other species. Compartment belongs to “Non-sequence”, so it is suggested that E.coli only exists as a one-part-species.

Figure 1: The Chain-Node Model of a E.coli cell
Example of a species: pLacI*:LacI4 and its tree structure of binding.

Here is another example of template species with more complicated structure.(see Figure 2) In biology, LacI tetramer (or LacI4) can bind with promoter pLacI as a repressor. When bond with LacI4, pLacI is repressed and its transcription speed will decrease significantly. In order to express this alteration, as mentioned above, we use another part of pLacI* with decreased transcription speed instead of pLacI in the species.

The structure of binding sites is shown in figure (see Figure 3). The graph indicates that LacI monomers first bind together to form LacI dimer, then LacI dimers forms LacI tetramer, and finally LacI4 binds with pLacI* to form pLacI*:LacI4.
Figure 2: Species of pLacI*:LacI4
Figure 3: Tree structure of binding in pLacI*:LacI4

Modeling with Templates

Manual modeling of biological system is widely used in synthetic biology. However, it requires an overall understanding of the biological network and large amount of data, making it difficult even for professionals. Actually, the data provided manually are redundant because different reactions may occur with a same mechanism. Based on this idea, we introduce the concept of Template, which is the minimal data set for describing biological reaction networks, as a feasible way to implement automatic modeling. The term “automatic” does not mean modeling without providing any information. Instead, we aim at providing minimal amount of data. Similar to C++ programming language, templates allow generic description of species of a certain structural pattern or reactions of a certain reaction mechanism.

Substituent and Template

There are two kinds of templates: Template Species and Template Reactions. They are designed to represent a family of species with similar structure and a family of reactions with similar mechanism respectively. In order to realize this idea, we add the container of Substituent into MoDeL. There are currently six objects in this container, ANY, ANYUB, ONE, ONEUB, NZ and NZUB. Though defined differently, they actually serve the same purpose: representing other parts. Let’s take ANY as an example (see Figure 4). ANY, represents parts on ONE chain and the number of represented parts can range from zero to infinity. For example, a DNA species with structure ANY - pTetR - ANY represents any DNA with part pTetR.
Figure 4: Template DNA species
A reaction with template species as its reactants, modifiers or products is a Template Reaction. A template reaction describes the core structure of reactant that causes the reaction to happen and provides a specification for generating reactions with the same mechanism. This could be understood more clearly by dividing parts in a species into functional groups -- a reaction template describes the interaction mechanism of these functional groups. For example, pTetR promoter is deactivated in presence of TetR dimer. The template species are pTetR DNA template and TetR dimer protein template (see Figure 5) and the functional groups are pTetR promoter and TetR dimer. All the parts of ANY should also be counted as a functional group, though they don’t have functions in this reaction. Any pair of species which partially contain pTetR DNA and TetR protein dimer respectively would bind according to the description of this reaction template. Modeling with templates allows users to define species and reactions only once for one certain family without rewriting them again in database.
Figure 5: Template reaction
We are still looking for more substituents. We are planning to have more detailed substituents that can replace certain number of parts on certain number of chains. Even the arrangement of parts and chains can be specified. We believe it will make our template modeling more powerful.


A Standard Language

MoDeL aims at providing a language and syntax standard for automatic modeling databases used in synthetic biology models. We will discuss a few relevant topics in the following sections.

Standard Biological Part Automatic Modeling Database Language

With plenty of information for automatic modeling needs to be stored, we design our database, and develop a standard language of describing the database. We call the language: MoDeL.
MoDeL (Standard Biological Part Automatic Modeling Database Language) is a database representation format for synthetic biology automatic modeling. This project of MoDeL aims at providing a language and syntax standard for automatic modeling databases used in synthetic biology models on a number of topics, including cell signaling pathways, metabolic pathways, biochemical reactions, gene regulations, and so on.
MoDeL is developed as a machine-readable format in XML fashion, programming languages with XML library API (such as libxml2 for C++) are strongly recommended for reading MoDeL database. USTC_Software has been devoted to the standardization of MoDeL. Documents can be found here. Example of database written in MoDeL can be downloaded on our [http://github.com/jkdirac/igame GitHub page].
MoDeL is an attempt to define a universal database markup language for synthetic biology automatic modeling. It supports descriptions of a wide variety of different parts, including biobrick, compound, compartment, substituent, and so on. It can also describe the species constructed by these parts, and reactions happen with the species, such as binding of species, dilution of species, degradation of proteins, amplification of cells, multi-compartment reactions, and so on.
Many traditional methods fail to consider structure of species when trying to markup reactions with only reactants, modifiers, products and kinetic laws. The best part of MoDeL is that it can preserve detailed structure in species and reactions using Chain-Node Model. Based on the model, MoDeL is able to markup almost all kinds of reactions in a detailed and clear way.

Overview of MoDeL

Figure 5 above is an example of a simple network of biochemical reactions(pTetR + TetR2 = pTetR*:TetR2) that can be automatically constructed using MoDeL:
MoDeL supports automatic construction of such network with only the input of its initial conditions and environmental parameters. In order to do this, obviously the data of parts, species, reactions, compartment, units and so on is needed. Besides, relationships between these components are also needed, so we can link to a reaction when we find a species. Data of relationship is stored as references and exists in most MoDeL components.
To define all the needed components in a systematic way, MoDeL organizes them in five component containers at the top level:
:: System: This container contains definitions of units, functions, rules and global parameters. These are all basic elements for other components of MoDeL, and many are mathematical concepts without direct synthetic biology meanings. The name of the container, System, separates this container from others which contains components of biological significance, and indicates this container includes the basic parameters of the whole system.
:: Compartment: This container contains definitions of compartments. Compartment here is considered as a holder of substance with certain volume, so it only stores related data such as units and volume. It also stores a list of compartments that are permitted to be placed inside. For compartments like E.coli that can multiply, a corresponding compartment with the same id will be created in the sub-container of compartment in Part.
:: Part: This container contains definitions of parts. Part includes the basic units that can be inserted in an abstract chain. The container of Part has five sub-containers which are: compartment, biobrick, compound, plasmidBackbone, and substituent. Biobrick contains biobricks from PartsRegistry together with other similar components created by users. Compartment contains cells and other microscopic organisms that can multiply. compound contains small molecules like IPTG and other compounds. PlasmidBackbone contains plasmid backbones come from PartsRegistry or defined by users. Substituent contains substitutes for template modeling.
:: Species: This container contains definitions of various species defined by Chain-Node Model. Each component stores the cnModel structure of chains and trees. Related reactions are also stored. It is suggested that the constructor of a database stores template species instead of real species in this container. Only in this way can he make use of the power feature of template modeling of MoDeL.
:: Reactions: This container contains definitions of various reactions. Each component has its own compartments, reactants, modifiers, products, substituent transfers, and kinetic law. This forms a detailed description of reactions. Again, constructor of a database is suggested to store template reactions instead of real reactions.
The organizational structure of components in MoDeL is shown in the following figure.
Figure 6: Structrue of MoDeL components
As mentioned above, reference relationships are stored in most components. The following figure shows the relationship between different components, the pointer pointing to a component indicates referencing to that component.
Figure 7: Reference relationship of MoDeL components
It is worth noting that MoDeL does not attempt to include all information about each component. In PartsRegistry, a long list of data in XML format is provided including part author, status, sequence, and even group access information. Such data are redundant for our database since they are not necessary elements needed to construct reaction network. Only the useful data is retained.

Relationship with SBML

SBML(The Systems Biology Markup Language) is a machine-readable language in XML fashion. It's oriented towards describing systems where biological entities are involved in, and modified by, processes that occur over time. As a widely used model exchange standard, SBML is chosen to be the output of our auto-modeling module.
Generally speaking, MoDeL needs not to be conformed to any constraints set by SBML. However, since SBML is a widely used standard, it is better for MoDeL to share common concepts and components with SBML as many as possible. For example, MoDeL still uses rules, function definitions and unit definitions in SBML. By doing so, it will be easier for software tools to change formats between MoDeL and SBML.
Standardization
Standardization

Standardization of MoDeL


Ustcs Notepad edited 2.jpg

MoDeL aims at providing a language and syntax standard for automatic modeling databases used in synthetic biology models. Knowing the importance, USTC_Software puts a lot of effort on the standardization of MoDeL. We have requested BBF RFC55 for MoDeL, and constructed a beta version of XML schema to describe the XML structure of MoDeL.

BBF RFC55

BBF RFC55: Standard Biological Part Automatic Modeling Database Language (MoDeL) mainly describes the detailed language specifications of MoDeL with concrete examples, which provides enough information for serious database constructors to build up a database on his own. As a highlight of MoDeL, the concept and the syntax of Chain-Node Model are described in detail. The content of document is currently arranged as follows:

Figure 1: Draft document of RFC55 - Table of Contents

The document of RFC55 has already been submitted. You can find it on the webpage of [http://openwetware.org/wiki/The_BioBricks_Foundation:RFC The BioBricks Foundation:RFC]. Following are some more previews at the draft document.

Figure 2: Preview at draft document of RFC55
Figure 3: Preview at draft document of RFC55

XML Schema

XML Schemas express shared vocabularies and allow machines to carry out rules made by people. They provide a means for defining the structure, content and semantics of XML documents. Being written in XML fashion, a Schema is perfect for MoDeL to allow software to perform check on syntax. Following is the preview of the beta version of XML Schema for MoDeL. The Schema can be downloaded at iGaME project page on SourceForge.

Figure 4: Preview at XML Schema of MoDeL
Figure 5: Preview at XML Schema of MoDeL
Future Work
Future Work

Future work


Ustcs The-future.jpg



To promote MoDeL for wide use as a standard, we need to refine the structure of MoDeL definition and extend its content to enable descriptions of more biological process. In the future, the new version of MoDeL will be proposed and new functions of iGame will be added.

Next version of MoDeL


MoDeL is young, to be exact, just born. There must be a long way before he can stand up and run by himself. At this stage, we have to take extra care of him. Knowing the drawbacks of MoDeL, we have already got a list of improvements waiting to be implemented in the next version of MoDeL. They are:

Enhance MoDeL to support description of intra-molecular reactions.

  • If it is applied, our software will become a useful tool to study the competition mechanism between intra-molecular and inter-molecular reactions.


More powerful substituents.

  • Only six kinds of substituents are far from meeting the demands of more accurate modeling and complex reaction mechanism. At present, substituent parts are limited to match only parts on one chain, and they are not allowed to represent a structure with more than one chains and trees. This needs the extension of definition of substituent parts by designing a unified format that can provide enough information.


Enable description of transcription and translation reactions.

  • Currently, transcription and translation are handled differently with other reactions. It is necessary to modify MoDeL to incorporate description of the two reactions.


Eliminate the inconsistencies.

  • In the current version of MoDeL, a bunch of inconsistencies exist. For example, the identifiers of compartments follow different restrictions from other global identifiers, and some components’ attributes are required to be a certain value. These problems make MoDeL not so elegant when looking at details. Work must be done to improve its consistency.


Be more independent.

  • Currently, some of MoDeL syntaxes are defined for specific algorithms of iGaME. Being a language for automatic modeling, cooperation with algorithm is reasonable. However, we believe there are too many compromises, thus causing a number of inconsistencies. In the next version, we are looking forward to a more independent MoDeL.




New functions of iGaME


iGaME grows together with MoDeL. In the one-year process of software development, we have achieved many of our goals, and found even more to be achieved. Looking ahead, we have the following wishes for iGaME.

User-friendly output for both professionals and amateurs.

  • It is far from enough to provide only dynamic curves as output because users may want more information about the biological system. Professionals may want to know the whole picture of reaction network, how do the species react with each other, and what influence do they have on the network. Amateurs may not be interested in curves, and they want to have a more straightforward concept of the network.

We are planning to give a graphic display of the reaction network by showing the change of species quantities dynamically. Users could understand the underlying reasons why a curve reaches its peak from the network. We also plan to show the topological structure of reactions in network. By connecting species with reactions, users can get a clear picture of the interconnections between species.
User-friendly input with fun

  • Powered by MoDeL, iGaME has already relieved users from inputting massive amount of data. However, we are still looking forward to make the input process more fun. Besides providing a graphical scene, we are planning to have more elements like story telling and character selecting. Moreover, result grading and multi-user interacting are to be added to make our software a real game.


Database Development Kit

  • Though we have presented the detail document of RFC 55 for MoDeL, modelers may still found it a tough job to construct a usable database. The Database Development Kit aims at aiding modelers with easy-to-use development tools. To achieve this, graphical tools for creating, removing, modifying data in database are needed. Parameter estimation tools and MoDeL syntax checking tools are also wanted. We are planning to have this kit in our future version, which will greatly reduce the difficulties for users to construct their own databases.


We believe the future of iGaME is bright !

Demo

1. Part: BBa_F2620
2. Toggle Switch
2.1. Modeling Details of Toggle Switch
3. Repressilator
3.1. Modeling Details of Repressilator


Part: BBa_F2620

BBa_F2620

Part:BBa_F2620 had been fully characterized with data in partsregistry [http://partsregistry.org/Part:BBa_F2620 BBa_F2620] page. It is a composite biobrick with three individual biobricks: pTetR (R0040), LuxR(C0062) and lux pR. Without AHL, transcriptional level of lux pR is extremal low because of lack of activator, LuxR-AHL dimer. If we add AHL into the system within a very short time, expression of mature GFP is expected to increase significantly. To measure behaviors of the system consisting of BBa_F2620 using our software tool, we construct a system using plasmid pSB3C5 and Part:BBa_F2620 as well as a reporter gene:

USTCs luxr gfp assembly.PNG

where we use two consecutive terminators to indicate a complete termination. Time course simulation was performed to generate transfer function of stable GFP concentrations versus AHL concentration. It is of high consistence with experiment done by [http://partsregistry.org/Part:BBa_F2620:Transfer_Function Haseloff Lab, MIT]:

USTCs Transfer function.png

where GFP concentration is directly proportional to its synthetic rate. In our simulation, we add AHL of concentration ranging from 1E-10 to 1E-5 M (increasing by order of magnitude) to the reactor within one minute. Details of modeling are described here.

We also plot time and dose response measurements of GFP stable concentration following addition of AHL. We choose the same AHL concentrations as done in testing the transfer function and plot their dynamic curves of GFP:

USTC s dose response.PNG

A similar work to measure system response of luxr-plux to inducer AHL was done by USTC 2009 iGEM team. Besides measurement of dose response of GFP stable concentrations following addition of AHL, they construct four constitutive promoters, [http://partsregistry.org/wiki/index.php/Part:BBa_K176026 BBa_K176026], [http://partsregistry.org/wiki/index.php/Part:BBa_K176126 BBa_K176126], [http://partsregistry.org/wiki/index.php/Part:BBa_K176128 BBa_K176128], [http://partsregistry.org/wiki/index.php/Part:BBa_K176130 BBa_K176130], and quantitatively measured their effects to the response curves. The construction is modified by replacing pTet with the four promoters and pSB3C5 with high copy plasmid pSB1A3 (copy number: 200). Since there are no tetR protein existed in the system, we keep lux pR unchanged (it is equivalent to use pLux/Tet hybrid promoter).

The results is shown for each (we plot GFP concentration versus time and compare it with experiment measument):

  • Part:BBa_K176026 (Promoter Strength: 0.55 1/s)
USTCs Comp K176026.PNG
  • Part:BBa_K176126 (promoter strength: 0.0192 1/s)
USTCs Comp K176126.PNG
  • Part:BBa_K176128 (promoter strength: 0.0016 1/s)
Comp 176128.PNG
  • Part:BBa_K176130 (promoter strength: 6.4E-5 1/s)
Comp 176130.PNG


Toggle Switch

Toggle Switch

The toggle switch is composed of two repressors and two promoters, each of which is inhibited by the repressor transcribed by the other promoter. We choose pLacI and pTetR as the two promoters, and the repressors are TetR and LacI, respectively. Theoretically, if ratio of LacI to TetR is greater than 1, strong binding of LacI to pLacI repress transcription initiation from pLacI and therefore quantities of TetR will decrease, which in turn relieves its repression to pTet leading to increase of quantities of LacI itself. In this situation, concentration of LacI is far greater than that of tetR, whose expression is repressed at an extream low level and the system enters into its 'LacI' state. Similar analysis will do for TetR and the system will enter into 'TetR' state if its quantity dominates. To show transition between the two states, IPTG is added in 1s after the system enters into 'LacI' state completely. The assembling of parts are construcuted as follows:

Parts assembling: the top assembling is the construction used in our software and the bottom one is the toggle switch design in [http://www.nature.com/nature/journal/v403/n6767/full/403339a0.html Construction of a genetic toggle switch in Escherichia coli].

where we use two consecutive terminators to indicate a complete termination. Time course simulation was performed to generate the state transition:

State of system has changed to 'TetR' state from 'LacI' state after adding inducer IPTG at 40000s.

The legend used in the figure is not clear. 13:DNA;(lacI153)4, 11:DNA;(tetR154)2, and 14:DNA;(lacI153)4;(tetR154)2 means binding products of initial plasmid with lacI tetramer at site pLacI gene, with tetR dimer at site pTet gene, and with lacI tetramer and tetR dimer both, respectively. At the beginning, initial plasmids are all bound with lacI tetramer and the system is in its 'LacI' state. After adding inducer IPTG at 40000s, concentration of tetR dimer increases and plasmids bound with lacI tetramer start to bind with tetR dimer and form complex of plasmids, lacI tetramer, and tetR dimer. At about 70000s, all plasmids bound with lacI tetramer are further bound with tetR dimer. At about 85000s, due to repression of expression of lacI, plasmids bound with LacI tetramer and tetR dimer both start to unbind to form plasmids bound with tetR dimer only and the system steps into its 'TetR' state gradually. Details of modeling is available here.


Modeling Details of Toggle Switch

Modeling Details of Toggle Switch

Key points of this modeling are:

  • LacI protein tends to form LacI dimer, which tends to form LacI tetramer further.
  • Only LacI tetramer binds with pLacI gene and thus repressing expression of its downstream genes.
  • TetR protein only forms dimer.
  • Only tetR dimer binds with pTet gene and thus repressing expression of its downstream genes.
  • One IPTG molecule binds with one LacI tetramer to form complex IPTG:LacI4 and one aTc molecule binds with one tetR dimer to form complex aTc:TetR2.

An overview of species list is provided:

Species list of toggle-switch network.

where each species with its specific identifier has its own meaning:

  • 0:E_coli : E.coli cell;
  • 1:IPTG: IPTG in flask;
  • 2:DNA: initial transformed plasmids;
  • 3:IPTG: IPTG in E.coli due to diffusion;
  • 4:RNA: mRNA of tetR and GFP;
  • 5:RNA: mRNA of LacI;
  • 6:tetR154: tetR protein;
  • 7:GFP12923: GFP;
  • 8:lacI153: LacI protein;
  • 9:(tetR154)2: tetR dimer;
  • 10:(lacI153)2: LacI dimer;
  • 11:DNA;(tetR154)2: complex of tetR dimer binding to pTet gene of plasmid DNA;
  • 12:(lacI153)4: LacI tetramer;
  • 13:DNA;(lacI153)4: complex of LacI tetramer binding to pLacI gene of plasmid DNA;
  • 14:DNA;(lacI153)4;(tetR154)2: complex of plasmid DNA with both pLacI and pTet genes bound with LacI tetramer and tetR dimer, respectively;
  • 15:IPTG;(lacI153)4: complex of IPTG binding with LacI tetramer;

Since there are 65 reactions in total, we only provide a screenshot (we strongly recommend users to run our example to learn more details about automatic modeling):

Species list of toggle-switch network.

Moreover, parameters of our modeling network are provided (we spend much efforts on tuning parameters) based on papers and estimates together:

  • Initial time: 0 s
  • Initial volumes:
    • Flask: 0.4 l
    • E_coli: 1.6856e-012 l
  • Initial concentrations:
    • 0:E_coli: 1e-020 mol/l
    • 1:IPTG: 0 mol/l
    • 2:DNA: 2.4e-009 mol/l
    • 3:IPTG: 0 mol/l
    • 4:RNA: 0 mol/l
    • 5:RNA: 0 mol/l
    • 6:tetR154: 0 mol/l
    • 7:GFP12923: 0 mol/l
    • 8:lacI153: 0 mol/l
    • 9:(tetR154)2: 0 mol/l
    • 10:(lacI153)2: 0 mol/l
    • 11:DNA;(tetR154)2: 0 mol/l
    • 12:(lacI153)4: 0 mol/l
    • 13:DNA;(lacI153)4: 0 mol/l
    • 14:DNA;(lacI153)4;(tetR154)2: 0 mol/l
    • 15:IPTG;(lacI153)4: 0 mol/l
  • Reaction parameters:
    • reproduction of Ecoli cell
      • growth constant: 0.000192 1/s
      • maximum concentration: 1.66e-012 mol/l
    • diffusion of IPTG molecule
      • diffusion constant: 0.014 1/s
    • transcription
      • transcription rate of pTet/pLacI: 0.5 1/s
    • replication of reverse pSB3C5
      • replication constant: 0.003 1/s
    • repression of reverse pSB3C5 replication
      • max concentration of pSB3C5: 2.847e-008 mol/l
    • translation
      • translation rate: 0.1 1/s
    • degradation of mRNAs
      • degradation of mRNA molecules: 0.0048 1/s
    • degradation of proteins in E.coli_3
      • degradation rate of proteins: 0.0023 1/s
    • Laci-Laci dimerization
      • kon: 1.25e+007 l/(mol*s)
      • koff: 10 1/s
    • binding forward-ptetR:tetR2
      • kon: 1e+008 l/(mol*s)
      • koff: 0.001 1/s
    • tetR-tetR dimerization_2
      • kon: 4e+011 1/(mol*s)
      • koff: 10 1/s
    • LacI2-LacI2 dimerization
      • kon: 1e+014 l/(mol*s)
      • koff: 10 1/s
    • binding reverse-placI:lacI4
      • kon: 4e+011 l/(mol*s)
      • koff: 0.04 1/s
    • IPTG:lacI4 binding
      • kon: 154000 l/(mol*s)
      • koff: 0.2 1/s



Repressilator

Repressilator

The repressilator is a synthetic genetic regulatory network designed to exhibit a stable oscillation shown via expression of GFP (green fluorescent protein). The work is reported by Michael B. Elowitz and Stanislas Leibler in their [http://www.nature.com/nature/journal/v403/n6767/full/403335a0.html work] at 2000. They constructed a system of three genes connected in a cyclical negative feedback loop so that gene A represses gene B, which represses gene C, which represses gene A. The implementation of this idea used a low copy plasmid encoding the repressilator, and the higher copy reporter, which were used to transform a culture of Escherichia coli.

Parts assembling: the top assembling is the construction used in our software and the bottom one is the toggle switch design in their work.

We construct a model to stimulate the behavior of repressilator, the results are showed as following:

USTCS repressilator.JPG

The meanings of the legend used in the figure are demonstrated as follows: [14 (lacI153)4] refers to the binding product of four lacI protein molecules, [12 (CIlam154)2] refers to the binding product of two CIlam protein molecules, while [10 (tetR154)2] refers to the binding product of two tetR protein molecules. The system exhibits oscillation behavior after initial time of 86000, the concentration of (lacI)4, (CIlam)2 and (tetR)2 changes periodically as the function of time. To be specific, the concentration of (tetR)2 increase when the concentration of (lacI)4 declines due to the remove of repression. And the concentration reaches the peak level when the concentration of (LacI)4 reaches its lowest level. Then the concentration of (tetR)2 decreases while the concentration of (CIlam)2 begins to arise because the repression from (tetR)2 is gradually relieved. Noted that the concentration peak level of (CIlam)2 and (tetR)2 are nearly more than twice the max concentration of (lacI)4, this may attribute to the difference of binding tendency between (CIlam)2, (tetR)2 and (lacI)4. The internal binding strength of (tetR)2 dimer and (CIlam)2 dimer are stronger than that of (lacI)4 tetramer. more details

Modeling Details of Repressilator

Modeling Details of Repressilator


Key points of this modeling are:

  • LacI protein tends to form LacI dimer, which tends to form LacI tetramer further.
  • Only LacI tetramer binds with pLacI gene and thus repressing expression of its downstream genes.
  • TetR protein only forms dimer.
  • Only tetR dimer binds with pTet gene and thus repressing expression of its downstream genes.
  • One IPTG molecule binds with one LacI tetramer to form complex IPTG:LacI4.
  • cIlam protein only forms dimer.
  • Only cIlam dimer binds with pcIlam gene and thus repressing expression of its downstream genes.


An overview of species list is provided:

USTCS graph1.JPG


where each species with its specific identifier has its own meaning:

  • 0:E_coli: E.Coli cell;
  • 1:IPTG: IPTG in flask;
  • 2:DNA: initial transformed plasmids;
  • 3:IPTG: IPTG in E.Coli due to diffusion;
  • 4:RNA: mRNA of tetR;
  • 5:RNA: mRNA of lacI;
  • 6:RNA: mRNA of cIlam;
  • 7:tetR154: tetR protein;
  • 8:lacI153: lacI protein;
  • 9:cIlam156: lacI protein;
  • 10:(tetR154)2: tetR dimer;
  • 11:(lacI153)2: lacI dimer;
  • 12:(cIlam156)2: cIlam dimer;
  • 13:DNA;(tetR154)2: complex of tetR dimer binding to pTet gene of plasmid DNA;
  • 14:(lacI153)4; lacI tetramer;
  • 15:DNA;(cIlam156)2: complex of cIlam dimer binding to pCI gene of plasmid DNA;
  • 16:DNA;(cIlam156)2;(tetR154)2: complex of plasmid of DNA with both pCI and pTet genes bound with cIlam dimer and tetR dimer;
  • 17:DNA;(lacI153)4: complex of LacI tetramer binding to pLacI gene plasmid DNA;
  • 18:DNA;(lacI153)4;(tetR154)2: complex of plasmid DNA with both pLacI and pTet genes bound with LacI tetramer and tetR dimer, respectively;
  • 19:IPTG;(lacI153)4: complex of LacI tetramer binding to pLacI gene of plasmid DNA;
  • 20:DNA;(cIlam156)2;(lacI153)4: complex of plasmid DNA with both pCI and placI genes bound with cIlam dimer and lacI tetramer, respectively;
  • 21:DNA;(cIlam156)2;(lacI153)4;(tetR154)2: complex of plasmid DNA with both pCI, placI and pTet genes bound with cIlam dimer, lacI tetramer and tetR dimer, respectively;

Since there are 153 reactions in total, we only provide a screenshot (we strongly recommend users to run our example to learn more details about automatic modeling):

USTCS graph2.JPG

Moreover, parameters of our modeling network are provided below:

  • Initial time: 0 s
  • Initial volumes:
  • Chemostat 0.1 l
  • E_coli 4.4247e-006 l
  • Initial concentrations:
  • 0:E_coli 1.05e-013 mol/l
  • 1:IPTG 0.001 mol/l
  • 2:DNA 2.4e-009 mol/l
  • 3:IPTG 0 mol/l
  • 4:RNA 0 mol/l
  • 5:RNA 0 mol/l
  • 6:RNA 0 mol/l
  • 7:tetR154 0 mol/l
  • 8:lacI153 0 mol/l
  • 9:cIlam156 0 mol/l
  • 10:(tetR154)2 0 mol/l
  • 11:(lacI153)2 0 mol/l
  • 12:(cIlam156)2 0 mol/l
  • 13:DNA;(tetR154)2 0 mol/l
  • 14:(lacI153)4 0 mol/l
  • 15:DNA;(cIlam156)2 0 mol/l
  • 16:DNA;(cIlam156)2;(tetR154)2 0 mol/l
  • 17:DNA;(lacI153)4 0 mol/l
  • 18:DNA;(lacI153)4;(tetR154)2 0 mol/l
  • 19:IPTG;(lacI153)4 0 mol/l
  • 20:DNA;(cIlam156)2;(lacI153)4 0 mol/l
  • 21:DNA;(cIlam156)2;(lacI153)4;(tetR154)2 0 mol/l
  • Initial values of global quantities:
  • ts 0
  • te 40000
  • s 0.001
  • t 0
  • Reaction parameters:
  • reproduction of Ecoli cell
    • kgr 0.000192 1/s
    • maxc 1.66e-012 mol/l
  • dilution of species in chemostat
    • k1 0.00017 1/s
  • diffusion of IPTG molecule
    • k_diff 0.014 ?
  • dilution_2 of species in E.coli
    • kgr 0.000192 1/s
    • maxc 1.66e-012 mol/l
  • transcription
    • k_tc 0.5 1/s
  • replication of reverse pSB1A3
    • kgr 0.003 1/s
  • repression of reverse pSB1A3 replication
    • kgr -0.003 ?
    • maxc 4.746e-007 ?
  • translation
    • k_tl 0.1 1/s
  • degradation of mRNAs
    • k1 0.0048 1/s
  • tetR-tetR dimerization
    • kon 1.79e+011 l/(mol*s)
  • degradation of proteins in E.coli
    • k1 0.0023 1/s
  • Laci-Laci dimerization
    • kon 1.25e+007 l/(mol*s)
  • cI (lambda)-cI (lambda) dimerization
    • kon 1.79e+011 l/(mol*s)
  • binding reverse-ptetR:tetR2
    • kon 1e+008 l/(mol*s)
  • LacI2-LacI2 dimerization
    • kon 1e+014 l/(mol*s)
  • binding reverse-pcI (lambda):cI2 (lambda)
    • kon 1e+009 l/(mol*s)
  • binding reverse-placI:lacI4
    • kon 4e+011 l/(mol*s)
  • IPTG:lacI4 binding
    • kon 154000 l/(mol*s)
Notebook

Monthly Notebook

March April May June
July August September October

Daily Notebook

March
MTWTFSS
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/1_March_2010 1] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/2_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 2] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/3_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/5_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 5] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/6_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 6] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/12_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 12] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/13_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 13] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/14_March_2010 14]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/16_March_2010 16] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/17_March_2010 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/19_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 19] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/20_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 20] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/21_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 21]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/22_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 22] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/23_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 23] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/24_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 24] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/25_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 25] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/26_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 26] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/30_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 30] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/31_March_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 31]
April
MTWTFSS
      [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/1_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 1] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/2_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 2] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/3_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/5_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 5] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/6_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 6] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/12_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 12] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/13_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 13] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/14_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 14] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/16_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 16] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/17_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/19_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 19] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/20_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 20] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/21_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 21] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/22_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 22] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/23_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 23] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/24_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 24] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/25_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 25]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/26_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 26] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/30_April_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 30]
May
MTWTFSS
          [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/1_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 1] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/2_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 2]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/3_May_2010 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/5_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 5] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/6_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 6] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/10_May_2010 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/12_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 12] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/13_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 13] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/14_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 14] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/16_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 16]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/17_May_2010 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/19_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 19] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/20_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 20] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/21_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 21] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/22_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 22] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/23_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 23]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/24_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 24] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/25_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 25] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/26_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 26] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/30_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 30]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/31_May_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 31]
June
MTWTFSS
  [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/1_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 1] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/2_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 2] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/3_June_2010 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/5_June_2010 5] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/6_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 6]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/12_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 12] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/13_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 13]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/14_June_2010 14] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/16_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 16] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/17_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/19_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 19] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/20_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 20]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/21_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 21] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/22_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 22] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/23_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 23] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/24_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 24] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/25_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 25] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/26_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 26] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/30_June_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 30]
July
MTWTFSS
      [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/1_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 1] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/2_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 2] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/3_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/5_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 5] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/6_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 6] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/12_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 12] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/13_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 13] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/14_July_2010 14] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/16_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 16] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/17_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/19_July_2010 19] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/20_July_2010 20] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/21_July_2010 21] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/22_July_2010 22] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/23_July_2010 23] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/24_July_2010 24] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/25_July_2010 25]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/26_July_2010 26] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/27_July_2010 27] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/29_July_2010 29] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/30_July_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 30] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/31_July_2010 31]
August
MTWTFSS
            [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/1_August_2010 1]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/2_August_2010 2] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/3_August_2010 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/5_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 5] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/6_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 6] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/12_August_2010 12] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/13_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 13] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/14_August_2010 14] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/16_August_2010 16] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/17_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/19_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 19] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/20_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 20] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/21_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 21] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/22_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 22]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/23_August_2010 23] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/24_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 24] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/25_August_2010 25] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/26_August_2010 26] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/28_August_2010 28] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_August_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/30_August_2010 30] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/31_August_2010 31]
September
MTWTFSS
    [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/1_September_2010 1] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/2_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 2] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/3_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 3] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/4_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 4] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/5_September_2010 5]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/6_September_2010 6] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/7_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 7] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/8_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 8] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/9_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/11_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 11] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/12_September_2010 12]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/13_September_2010 13] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/14_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 14] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/15_September_2010 15] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/16_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 16] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/17_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 17] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/18_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 18] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/19_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 19]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/20_September_2010 20] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/21_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 21] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/22_September_2010 22] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/23_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 23] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/24_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 24] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/25_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 25] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/26_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 26]
[http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_September_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/30_September_2010 30]
October
MTWTFSS
        [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/1_October_2010 1] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/2_October_2010 2] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/3_October_2010 3]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/4_October_2010 4] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/5_October_2010 5] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/6_October_2010 6] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/7_October_2010 7] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/8_October_2010 8] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/9_October_2010 9] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/10_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 10]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/11_October_2010 11] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/12_October_2010 12] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/13_October_2010 13] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/14_October_2010 14] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/15_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 15] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/16_October_2010 16] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/17_October_2010 17]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/18_October_2010 18] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/19_October_2010 19] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/20_October_2010 20] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/21_October_2010 21] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/22_October_2010 22] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/23_October_2010 23] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/24_October_2010 24]
[http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/25_October_2010 25] [http://2010.igem.org/Team:USTC_SOFTWARE/Notebook/Meetings/26_October_2010 26] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/27_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 27] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/28_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 28] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/29_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 29] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/30_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 30] [http://2010.igem.org/wiki/index.php?title=Team:USTC_SOFTWARE/Notebook/Meetings/31_October_2010&preload=Team:USTC_SOFTWARE/Template/Meetings&action=edit 31]
Overview
Overview

As a tutor game aimed at improving the understanding and facilitating IGEM and synthesis biology, iGAME itself is exactly a great way of human practice. With iGAME, people do not feel any distance to synthesis biology any more. Actually, it is time for everyone to join this trend to be as cool as Sheldon’s new biologist girlfriend.

However, we do not stop here. We paid great effort to the safety issue and we have been dedicated to improving the knowledge of synthesis biology from classes and tried to share the part we contribute to the worldwide. We innovatively plot a new way of spreading the spirits of IGEM by starting our own community and we will never stop sharing and communicating.

The C Project
The C Project

As a tutor game aimed at improving the understanding and facilitating IGEM and synthetic biology, iGAME itself is exactly a great way of human practice. With iGAME, people do not feel any distance to synthetic biology any more. Actually, it is time for everyone to join this trend to be as cool as Sheldon’s new biologist girlfriend. However, we do not stop here. We paid great effort to the safety issue and we have been dedicated to improving the knowledge of synthesis biology from classes and tried to share the part we contribute to the worldwide. We innovatively plot a new way of spreading the spirits of IGEM by starting our own community and we will never stop sharing and communicating.

--Luojun Wang, author of USTC_SOFTWARE human practice

USTC Software hp author.jpg


Human Practice,"the C project"

Although we do software, we also keep eyes on promotion of synthetic biology and sharing our own program. Therefore, we started a long term human practice, “the C project”, since this summer.“the C project”, as we call, consists of three parts: Curriculum, Communication and Community.

Curriculum


As a IGEM team, we try to let people as many as possible to know what synthetic biology is. Therefore, advisors of our team, Haiyan Liu and Jiong Hong, have established a set of synthesis biology curriculum this summer. We have done many works related to human practice on the curriculum.

  1. Jiong Hong (in the right picture), advisor of our team, gave lectures introducing safety and ethnics issues of synthetic biology.
  2. Luojun Wang (in the head picture), members of our team, gave lectures promoting iGAME.
  3. A survey* on how students know about synthetic biology and their interests for tutor game was made.(*the survey statistics comes from a sample of 240 students. Numbers of undergraduates, masters and PhDs are 160, 60 and 20)
USTC Software hp guy1.jpg

Analysis of the results of the survey The first chart shows students' favorite game types for iGAME, and the second chart shows their knowledge of IGEM project.

USTC Software hp chart.png
USTC Software hp chart2.png

The Circos Map
We tried many methods to plot our survey more straightforwardly and clearly before we finally chose Circos [http://mkweb.bcgsc.ca/circos mkweb.bcgsc.ca/circos]. Circos is biological software used to plot genome elements and relationship. Here, we innovatively used Circos to demonstrate our survey.(as in the right picture) Circos is somehow like pie chart yet it can present multi information as all the statistics are proportional and clear on the graph.

In the graph, there are three circles. The inner circle stands for their knowledge of synthetic biology, and middle circle stands for their interests of iGame. Deeper the color is, the more they know of synthetic biology or the more they are interested in iGame. For example, light pink means they know little about synthetic biology and deep green means they are very interested of the coming tutor games. The outer circle, however, stands for their major;light green for biology major and light orange for other majors. As the graph shows, synthetic biology is still new to them as the majority have little idea of it, for which is what we will continue our project in the future. However, we are delighted to see that their interests of tutor game are fairly strong.

Referring to the possible game types, adventure and strategy games are students’ favorite, while some of them prefer stimulation and action games. In our program, we tried our best to listen to their voice and develop a game which is both educational and appealing.

USTC Software hp chart1.png

Communication


We’d like to share what we have achieved with the world, so we did and will do a great deal to communicate with others and learn. For example, we collaborate closely with USTC wet team to learn what biology majors think of iGame and improve. Several seminars have been hold to make sure our program can really help the promotion of both synthesis biology and our tutor game. In addition, further transnational communication is not absent, like we had a deep talk with Dr. Joy Yueyue Zhang*(*BIOS Centre, London School of Economics and Politics Science) on how our program can change the development of both IGEM and make biology a better subject.

Yet we do not stop here. We have sent emails to other teams for further communications and asked for their opions on how we can improve iGame. What is more, all our codes are shared on github[http://github.com/jkdirac/igame](in the right picture). With fixes and new features putting forward every day,any one in any corner of the world can learn and keep update of our work, not just from the surface, but from codes and essense of our work. This is really a great way of communication, for we do not have to say too much to put our achieves across to those who really want to know our work, which really works. Great contributions have been given through github and we get a lot of advices and opinions as well.

USTC Software hp london.jpg

Community


To better promote synthesis and the spirit of IGEM, we decided to establish a community together with IGEM USTC team. For the community, we have set regular classes and lectures for both synthesis biology and IGEM. We also open our laboratory to our community members and teach them basic skills of biology experiment(as in the right picture), like PCR. Of course, this is the main field we will update our progress on in the future.

USTC Software hp yz.jpg

More information of our community and other human practice of USTC IGEM team, please click2010 USTC IGEM humanpractice!

Safety
Safety

Safety

safety concerns

As a software team, our team does not produce any typical biological safety or ethnic issues. However, we still take safety into account from as many aspects as possible:

1. Safety for programmers

Most of our work is mainly done in front of computers, which is not ergonomically to programmers as working in such environment may cause much exhaust and stress. Therefore, we made a series of regulations to guarantee they are not exposed to computers constantly for too long time and recreational area is within 10 meters. What is more, every time our programmers go to web labs, we make sure that there would be safety equipment as well as accompanies for them.

USTC Software hp fun1.jpg

2. Safety for public

We are aware what our software will bring to teenagers or youngsters, and our software is ensured that no violent or sexual scene or content is included. We also did a lot of work to estimate and reduce the possible errors or faults users may encounter in the future.

3.Safety for software

To better protect our intellectual property rights, we have consulted IPRs centre of USTC in case of future problem. We will restrict the use of our software and we will apply for a patent later.

4.Safety for campus

We are quite aware when we perform our work or lecture in campus, and no disorder or turbulence has shown during in the above activity.

5.Other safety concerns

(i) Our team made no new BioBrick parts (or devices), and no safety issues happened from this. (ii)No biosafety group or committee protested our project.

Suggestions for future development of safety in dry lab.

Although a lot of work is done to ensure the safety of programmers in dry lab, a lot of work still remains to be done. And here we present some brief ideas on how we can develop the safety for programmers.

1. In many conditions, programmers in a dry lab have to share places with experiment operators due to limited space, which may lead to underlying health problems. Therefore, we suggest that strict rules should be made to provide independent space for programmers.

2. We take it for granted that not only safety for programmers, but the safety for intellectual property should be taken into consideration. Thus we suggest that all codes and other achievement should be granted with copyrights before sharing.

Overview
Overview

Team Overview

Team

This year 10 students started the iGEM USTC Software team: Chen Liao, Zheng Wang, Kun Jiang, Jue Wang, Luojun Wang, Yubo Qi, Zhaoyi Li, Zhengda He, Shangyu Luo and Mort Yao. There are only 8 of us in the picture, while the only female team member, Jue Wang was in Beijing engaging for her TOEFL exam, and Shangyu Luo had gone to Hong Kong for studying in The University of Hong Kong as an exchange student. What a pity! But they will join us at the iGEM 2010 Jamboree.

USTC has formed two IGEM teams this year, one wet lab team and one dry lab team. As many students majoring in biology was attracted to the wet lab team, our team consists of students from other departments, such as Mathematics, Physics, Computer Science and so on. Thanks to our instructors Hao Jiang and Zhaofeng Luo, with their professional instruction, we are guided to decide the project plan, design and implementation.

About iGEM@USTC

The iGEM Team of USTC are the combination of the exact tradition of USTC and the exact vitality of the young. Rigorous daily schoolwork has provided the team members with a solid foundation of basic knowledge, and an innovative spirit enables us to stand on the frontier of the modern science.

In 2007, Jian Zhan, Bo Ding, Rui Ma, Xiaoyu Ma, Yun Zhao, Ziqing Liu and Xiaofeng Su, guided by Prof. Haiyan Liu, Prof. Jiarui Wu and Prof. Zhonghuai Hou, won the "Best Foundational Technology Prize" and a Gold Medal, with the project "Extensible Logic Circuit in Bacteria".

In 2008, Xunyao Wu, He Shen, Genxin Liu, Jia Liu, Binjie Xu, Yanting Xue, Yu Chen, Zhen Xu, Bo Ding and Jian Zhan, guided by Prof. Haiyan Liu, won a Silver Medal, with the project "Artificial Multi-cellular Self-organization System".

In 2009, Hao Jiang, Li Xing, Hao Wu, Zongxiao He, Danqian Liu, Chao Li, Jiayi Dou, Hanyu Lu, Hao Zhou and Bing Wu, guided by Zhaofeng Luo, Jian Zhan, Jiong Hong and Xiaoxiao Ma, won a Gold Medal, with the project "E. coli Automatic Directed Evolution Machine (E.ADEM)".

In 2009 we also formed a software team for the first time. Wei Pan, Yuwei Cui, Jiahao Li, Yu He and Xiaomo Yao, guided by Bo Ding, also won a Gold Medal, with the Project "Automatic Biological Circuit Design (ABCD)".

Since last year we have accumulated some experience from the project of Automatic Biological Circuit Design (ABCD), we expect to develop a synthetic biology game this time. The game aims at teaching non-biologists how to design biological systems so that players can compete to improve their designs in order to help biologists create the best engineered machines!

For more information, go to [http://biotech.ustc.edu.cn/forum/forumdisplay.php?fid=26 USTC iGEM Forum].

About USTC

  • Message from the President

A university is the important assurance of maintaining belief, developing science and culture. It is a significant symbol of the level of civilization achieved by a nation.

  • USTC Today

The University of Science and Technology of China is a new type of university established by the Chinese Academy of Sciences (CAS) after the founding of People's Republic of China. The establishment of the University is aimed at fostering high-level personnel of science and technology absolutely necessary for the development of the national economy, national defense construction, and education in science and technology. The University was founded in Beijing in September of 1958. Mr. Guo Moruo is the first president of the University...

  • History of USTC

"Pooling the entire strength of the CAS for the development of USTC and combining the institutes of the CAS with the departments at USTC" "Studying hard and excelling in both integrity and specialty"USTC was established in Beijing in September, 1958 under the presidential leadership of Guo Moruo. The establishment was hailed as "a major event in the history of Chinese science and education"...

For more information, please visit [http://en.ustc.edu.cn/ http://en.ustc.edu.cn/] (in English) and [http://www.ustc.edu.cn/ http://www.ustc.edu.cn/] (in Chinese).

Team Cooperation

iGEM 2010 China Meetup Shanghai 5/6th Aug, 2010

On August 5th, teams from 7 top universities in China, SJTU-BioX-Shanghai, ECUST-Shanghai, Peking, Tsinghua, USTC & USTC_Software, ZJU-China, and Sun Yat-sen University all gathered in Shanghai and had a nice day at the iGEM 2010 China Meetup.
The meetup started around 9 with a short speech by Professor Lin He, head of Shanghai Jiao Tong University Bio-X Institute, which hosted the event. Then each team made a presentation displaying their projects and progresses since the summer began, followed by free questioning and discussion time. And when it was near the end of the day, student members had a hour or two to talk and play freely with each other, with a big meal waiting ahead for them.
For more information, go to https://2010.igem.org/Events/China_meetup.

Gallery

Student Members
Student Members


Student Members

Xiaomo Yao

I am soumort! I have nothing to say!!

Chen liao

My Profile:

Chen Liao, Room 418, Key Lab of Quantum Information, CAS, East Campus, USTC Hefei, Anhui 230026, China, liaochen@mail.ustc.edu.cn

I’ve just began my first year in the Optics and Optical Engineering program as a master candidate at University of Science and Technology of China. I became interested in iGEM because I found it a great chance to learn synthetic biology. Since iGEM is a student-run and student-manage programe which encourages students both to work collectively in a team and work individually to complete one's own task, it is a great experience to exercise my team working ability as well as creative ideas. In the last months, especially the summer, I worked with students from different disciplines to design and implement our project together and have learnt a lot from them. It is rather a wonderful experience to work with all team members. (^▽^)

As a student of department of physics, my research area is development of first principle theory and implementation of LCAO (Linear Combination of Atomic Orbitals) algorithms. As a member of [http://lqcc.ustc.edu.cn/helx/ LiXin He's group], I have successfully implemented atomic force calculation in LCAO method and my next project is to modify and develop algorithms under condition of magnetic B field. Besides scientific research, I do sports very often. Basketball is my favorite and my favorite basketball player is Kevin Garnett (K.G.), his professional attitude on the court as well as his individual character in the life impresses me a lot.


Zhen Wang

I am Zhen Wang!

Zhen Wang, Room 418, Key Lab of Quantum Information, CAS, East Campus, USTC Hefei, Anhui 230026, China. Email: xqqixp@mail.ustc.edu.cn; wangzhen.ustc@gmail.com;

Hi, I'm Zhen Wang, I mainly work on MoDeL and Database of iGAME. As a member of Lixin He's research group, I focus mainly on calculation of quantum information, quantum correlation and entanglement.

You might have noticed that my address is same as Liao's. Yes, we are from the same Research Group, and the same department, too. It will be boring if I repeat all the information again, so I am going to write some experience of myself participating iGEM2010.

As a student majoring physics, it is hard for me to believe that I can participate in a biology project. Luckily, to my great surprise, these two areas are not so far apart. Modeling and analyzing skills of physics can also be used in biology, and dry project always means a lot of coding task, I can handle that, too. Of course, there is plenty of biology I need to learn, but with the help of our instructor and wet team members, I learn it fast. So I want to tell everyone that there's no limit in iGEM, join in and unleash your power!

Kun Jiang

Email: jkdirac@mail.ustc.edu.cn

I am Kun Jiang, the cheif software developer in iGem 2010 USTC_Software team, responsible for designing the global architecture of our software and developing the ODE Solver module, Berkley database interface module and several simple tools for teammates.

It is my second year of studying in computer applied technology lab of Institute of Plasma Physics Chinese Academy of Sciences as a master candidate. I am interesting in software engineering and Computer Sicence. Last year I noticed the recruit advertisement of iGem 2010 USTC_Software team in school BBS website. I make the decision to apply immediately. It's really happy for me during those past server months working with our team.

I play Ping Pong most during my spare time, because Ping Pong is a sport emphasizes on speed, skill and acting harmony ability rather than brute force. And I go jogging every day, which i think is a good way to relieve pressure and keep me in health!

I want to be a brilliant software engineer developing some brilliant works. I gain strong knowledge in software engineering and computer algorithms. IGEM 2010 is one step to my ambitions, it is a important project but not the last project of my engineering life, I wish I would develop more and more softwares in future. If you need help, do not hesitate to contact me please!

Yubo Qi

I am Yubo Qi!

Yubo Qi 3005, national labotarory for physical sciences at the microscape

I am an undergraduate student in theoretical physics. But I am also interested in chemical physics and biology. In my labotarory, I concentrate on the calculation about transmission in nanostructure. However, biology science is also my favourite. So, I decide to join USTC_Software team of iGem 2010. Now I write database of biology reaction for my team. I love biology, chemistry, physics and decide to devote myself to the research of interdisipline in the future.

Luojun Wang

Luojun Wang(Vic Wong)

Dept. of Statistics & Finance, USTC, Hefei, Anhui 230026, China;

Lab of Systems Biology of Hefei National Laboratory for Physical Sciences at the Microscale, USTC, Hefei, Anhui 230026, China

vicwong@mail.ustc.edu.cn; victorwangluo@gmail.com;

Hey, I'm Vic, an undergraduate senior student majoring in mathematical statistics. Yet my research field is biology statistics, and that is why I'm here.

For IGEM, I'm mainly responsible for human practice and have been giving lectures as well as other promotions on both synthesis biology and IGAM. It is this special experience that has not only made my college life amazing, but also presented me with a broader view of biology. Besides working for IGEM, I've also been researching biology statistics, including bioinformatics and biology networks.

My goal is to be a biostatistician in the future, on which I'm gonna keep putting effort. Now I'm applying for an opportunity to study as a biostatistics PhD. Good luck to me, huh? : )

Jue Wang

I am Jue Wang!:)

Dept. of Math, USTC, Hefei, Anhui 230026, China;

Email: juewang@mail.ustc.edu.cn

Hi,I am Jue, a Math majored senior student. As the boundaries among different disciplines of science are now blurring, I want to handle the ideology of maths to arrive at a higher standpoint to try to understand the principle of life. iGEM provides us with such a good state to learn from utilization.

In this group, I am the unique girl among nine boys, and the most frequently spoken of mine is "Oh, it's my duty to get some soy sauce! " Strange, huh? The connotation of it is not words but meanings. Those guys are too gentle to arrange me doing something of coding.So I am more involved in clerical works, I design the team uniform and our logo,arrange the scheduling and get in touch with sponsors and alumni connection. My life is full of unpredictable tasks, who can tell me what is the next?

Zhaoyi Li

My profile:


Zhaoyi Li, Hefei National Laboratory for Physical Sciences at Microscale & National Synchrotron Radiation Laboratory, East Campus, USTC Hefei, Anhui 230026, China, lizhaoyi@mail.ustc.edu.cn </p>

During my 2 years’ journey in the nano world, I got to know iGEM and joined in USTC Software team with great honor. Just as NEW YORK TIMES says, iGEM is a Do-It-Yourself Genetic Engineering Program. I am strongly attracted by this idea and cannot help imaging the science fiction picture where our daily life is changed by our genetic machine. It is unforgettable to have a brainstorm with talents from different academic background and turn our imagines into reality. Thanks to iGEM, I experienced a new trip in the synthetic biology and benefited a lot from my partners. Also, to compete against more than 1,000 other students from 100 schools, including many top-flight institutions is exciting.

I love traveling and always enjoy trips with my friends. I have a dream that one day I can travel around the world to discover the great scenery make new friends and experience different culture. Sports is also my favorite, I am good at playing football and gifted in table tennis.

Zhenda He

I am Zhenda he!

Hello , everyone! My name is He Zhengda , a student from Chemical Physics Department in University of Science and Technology of China . To be a member in 2010 USTC_Software is a really great time for me during the boring semester ! I met a lot of interesting people in the IGEM lab , and I wish to meet all you guys during the Jamboree . I have a enormorous interest in math , computer science and designing stuff . I am a Wiki interface designer in our team . So I hope everyone like it . It's a short description of me~ See you in the Jamboree!

Shangyu Luo

I am Shangyu Luo!

Introduction: Hi all, I am Shangyu Luo. It is my Chinese name and my English name is Seraph. I am very pleased with attending iGEM competition with my teammates of USTC SOFTWARE. My major is computer science and I am interested in both computer and biology. During this competition, I gain a lot and make many friends. Thanks for my teammates, teachers and School of Computer Science and Technology! Additionally, I favor AI (Artificial Intelligence) in the fields of computer science, if you would like to create some beings together with me and to make them intelligent, please feel free to contact with me! Thanks all!

By Seragh
lsyurd@gmail.com
School of Computer Science and Technology
University of Science and Technology of China

Instructors
Instructors

Instructors

Zhaofeng Luo
  • Mail: lzf@ustc.edu.cn
Hao Jiang
  • Mail:haojiang@mail.ustc.edu.cn
  • Major: Cell Biology
  • Research Interests: Synthetic Biology, Directed Evolution
  • E-mail: haojiang@mail.ustc.edu.cn
  • Former 2009 iGem USTC team member
Collaboration
Collaboration

Cooperation with USTC wet team

It's always a good experience working with our wet team through the whole summer. During the process of iGEM 2010, we learn from each other and help each other to achieve more! This year we cooperate with USTC team in modeling and human practice. Read the following sections for more details.

Modeling

This year the team of USTC focuses on the construction a Host-cell-free Reaction Chamber using Synthetic Biology methods. We help them to visualize an artificial organelle of capacity. For more details, please refer to our wet team's modeling page.

Human Practice

This year, we also had close collaboration with USTC wet team on human practice, for the simple reason that none of us is biology major and we had to resort to biology major fellows for professional advice. Besides, we had several activities together; we presented several campus lectures promoting both synthetic biology and IGEM, and we started our IGEM community together. The collaboration with them not only enhanced the quality of our work, but improved the biology knowledge of our own.

iGEM2010 China Meetup Shanghai

Something amazing happened at Shanghai this summer...


Help with surveys

Penn State & Warsaw Team


This year Penn State iGEM team created a survey about Genetically Modified Organisms (GMOs) in Agriculture. The survey included questions about where and when GMOs should be used, GMOs containing a lysis device, and other questions dealing with the use of GMOs. USTC Software iGEMers are happy to be participants in the survey, and we wish a good result will come out! We also help team Warsaw fill out their survey forms.

Penn State logo.png
Ustcs Warsaw2.png
Sponsorship
Sponsorship

Attribution and Contributions


No iGEM project is done in a day. It requires good team work for 12 months to achieve it. USTC_Software team is built up by 10 students (7 undergraduates, 3 graduates) and two main instructors. Throughout the summer of 2010, our team members have been working cooperatively with our instructors to realize the idea of iGaME. We also appreciate the help from numerous people caring about USTC Software team. Our thank goes to all the listed and unlisted names on the Acknowledgments page.

Details about each team member's work are listed below: Instructors:

Zhaofeng Luo


  • Build up the team, organize the early training of iGEM, which includes brainstorming, previous work summary, and basic training on synthetic biology experiments.


Hao Jiang


  • Brainstorm together with team members, and raise the prototype of Chain-Node Model in the process. Contribute to develop the concept of Chain-Node Model into a complete language of MoDeL. Answering questions for non-biological students. Help with the parameter adjustment in our process of modeling.


Chen Liao


  • Contribute to develop the concept of Chain-Node Model into a complete language of MoDeL. Construct the automatic modeling algorithm for MoDeL, and finish most of the relevant codes. Cooperate in the structure constructing of MoDeL. Do the modeling of our demos, and related wiki editing.


Zhen Wang


  • Contribute to develop the concept of Chain-Node Model into a complete language of MoDeL. Construct database examples in MoDeL. Define the syntax and refine the language. Finish the RFC and other documents on MoDeL and edit related wiki pages. Design the User Interface of input process. Cooperate in algorithm developing and modeling.


Kun Jiang


  • Write codes on DBXML interface, UI and so on. Integrate the core algorithm with Qt, COPASI and DBXML. Take charge of code merging on Github. Design and construct wiki.


Luojun Wang


  • Take charge of our human practice – the C project, and write related wiki contents. Correct grammar errors in documents and wiki pages.


Jue Wang


  • Take charge of trip scheduling, sponsor contact, T-shirt designing, and so on. Write related wiki contents.


Zhaoyi Li


  • Investigate the work of synchronized E.coli clock and finish the database for it in MoDeL with Zhen Wang. Correct grammar errors in documents and wiki pages.


Yubo Qi


  • Investigate the work of EPF-Lausanne 2009 and finish the database for it in MoDeL with Zhen Wang and Zhengda He.


Zhengda He


  • Investigate the work of EPF-Lausanne 2009 and finish the database for it in MoDeL with Yubo Qi and Zhen Wang. Summarize some of the previous work briefly. Raise ideas about User Interface.


Shangyu Luo


  • Join the brainstorming about MoDeL structure. Investigate on database formats. Summarize useful information from previous work.

Mort Yao


  • Wiki, team logo and uniform design, the MosQt UI library built on C++ and Qt.
Acknowledgement
Acknowledgement

We would like to thank:

Our instructors

  • Ing. Zhaofeng Luo
  • Dr. Hao Jiang

The School of Life Sciences for hosting our team by providing lab space

  • The administrator of 363

The Computer applied technology lab .Institute of Plasma Physics Chinese Academy of Sciences

  • Prof. Zhenshan Ji

Complex Disease and Systems Biology Lab of the School of Life Sciences USTC

  • Prof. Jiarui Wu

Key Lab of Quantum Information, Chinese Academy of Sciences USTC

  • Prof. Lixin He

The Boston USTC Alumni Association

  • Chi Gao
  • Kai Pan
  • Yan Zhao
  • Lei Dai
  • Yunxing Ma
  • Jin Huang
  • Xiaochun Fan

The University of Science and Technology of China Initiative Foundation

  • Zhifeng Liu

All the students who joined the iGEM brainstorm early this summer, and helped us summarize previous work.

Sponsorship

The University of Science and Technology of China Initiative Foundation

Teaching Affair Office, USTC

School of Life Sciences, USTC

The USTC Alumni Foundation

The Department of Mathematics,USTC

The School of Life Sciences(SLS), USTC

Graduate School, USTC

The School of Physical Sciences(SPS),USTC

You are now using the Slideshow mode. Click ZOOM IN / OUT again to quit.