Difference between revisions of "Team:HZAU-China"

Line 1: Line 1:
 
{{HZAU-China}}
 
{{HZAU-China}}
 
<html>
 
<html>
<div class = "project_description" >
 
<h3>Project description</h3>
 
  
<p>The biological pattern formation is a important research field in Systems Biology. In the past 50 years, there were several major breakthroughs on finding the mechanisms of biological pattern formation. Many classical theories have been proposed, for instance, The Turing Model (A.M.TURING et al, 1952) and The Clock And Wavefront Model (Cooke, J, 1976), etc. With the emergence of Synthetic Biology, many research teams are trying to understand and verify these theoretical models with the ideology of Synthetic Biology and some developments have been made (Liu Chenli et al, 2013). However, the understanding to the mechanisms of biological pattern formation is far from mature. For this year, we are aiming at developing a system in which computers are used to guide the biological pattern formation. In this project, the easy operability and strong control ability of computers are exploited to monitor and regulate the growth process of bacterial community in real time to achieve the shape we want. Our system can also be extended to eukaryotic cell community which will be useful in aiding the development of biological tissues and the regeneration of organs.
+
<head>
</p>
+
    <meta charset="UTF-8">
</div>
+
    <title>body</title>
 +
    <style type="text/css">
 +
        *{margin: 0;padding: 0;}
 +
        .content_wrapper{
 +
            width: 100%;
 +
            height:1800px;
 +
            background-color: #dfe6ed;
 +
        }
 +
        .header{
 +
            width: 100%;
 +
            height: 580px;
 +
            position: relative;
 +
        }
 +
        .title{
 +
            width: 80%;
 +
            height: 10%;
 +
            position: absolute;
 +
            top:10%;
 +
            left: 10%;
 +
        }
 +
        .header_left{
 +
            width: 10%;
 +
            height: 10%;
 +
            position: absolute;
 +
            top:61%;
 +
            left: 31%;
  
<div class="column full_size" >
+
        }
<img src="http://placehold.it/800x300/d3d3d3/f2f2f2">
+
        .header_right{
</div>
+
            width: 10%;
 +
            height: 10%;
 +
            position: absolute;
 +
            top:20%;
 +
            left:47%;
 +
        }
  
<div class="column full_size" >
 
<h2> Welcome to iGEM 2016! </h2>
 
<p>Your team has been approved and you are ready to start the iGEM season! </p>
 
  
</div>
 
  
<div class="column half_size" >
+
        .main_part{
<h5>Before you start: </h5>
+
            width: 100%;
<p> Please read the following pages:</p>
+
            height: 880px;
<ul>
+
            position: absolute;
<li>  <a href="https://2016.igem.org/Requirements">Requirements page </a> </li>
+
            top: 600px;
<li> <a href="https://2016.igem.org/Wiki_How-To">Wiki Requirements page</a></li>
+
            left: 0;
<li> <a href="https://2016.igem.org/Resources/Template_Documentation"> Template Documentation </a></li>
+
        }
</ul>
+
        .bar_name{
</div>
+
            width:80%;
 +
            height: 20%;
 +
            position: absolute;
 +
            top: 0px;
 +
            left: 0;
 +
        }
 +
        .tmp_img{
 +
            width: 20%;
 +
            height: 20%;
 +
            position: absolute;
 +
            top: 0;
 +
            left: 80%;
 +
        }
 +
        .part1{
 +
            width: 30%;
 +
            height: 80%;
 +
            position: absolute;
 +
            top: 20%;
 +
            left: 2.5%;
 +
        }
  
<div class="column half_size" >
+
        .part2{
<div class="highlight">
+
            width: 30%;
<h5> Styling your wiki </h5>
+
            height: 80%;
<p>You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.</p>
+
            position: absolute;
<p>While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.</p>
+
            top: 20%;
</div>
+
            left: 35%;
</div>
+
        }
 +
        .part3{
 +
            width: 30%;
 +
            height: 80%;
 +
            position: absolute;
 +
            top: 20%;
 +
            left: 67.5%;
 +
        }
 +
        .decoration{
 +
            width: 100%;
 +
            height: 8%;
 +
            position: absolute;
 +
            top: 8%;
 +
            left: 0;
 +
        }
 +
        .words{
 +
            width: 330px;
 +
            height: 60%;
 +
            position: absolute;
 +
            top: 20%;
 +
            left: 10%;
 +
            background-color: #dec5df;
 +
        }
 +
        .bottom{
 +
            width: 180px;
 +
            height: 8%;
 +
            position: absolute;
 +
            top: 83%;
 +
            left: 30%;
 +
        }
 +
        .view_more{
 +
            display: block;
 +
            width: 100%;
 +
            height: 50px;
 +
            line-height: 50px;
 +
            text-decoration: none;
 +
            color: #7d489c;
 +
            font-family: Arial;
 +
            font-size: 25px;
 +
            font-weight: bold;
 +
            border: 2px solid rgba(230,158,230,0.6);
 +
            box-sizing: border-box;
 +
            padding-left: 25px;
 +
            margin:0 auto;
 +
            transition:border 0.4s ease;
 +
            position: relative;
 +
        }
 +
        .view_more:hover{
 +
            border: 2px solid rgba(110, 33, 134,0.8);
 +
        }
  
<div class="column full_size" >
 
<h5> Wiki template information </h5>
 
<p>We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the <a href="https://2016.igem.org/Judging/Pages_for_Awards/Instructions">Pages for awards</a> link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!</p>
 
  
</div>
 
  
  
 +
        .last_part{
 +
            width:100%;
 +
            height: 500px;
 +
            position: absolute;
 +
            top:1500px;
 +
            left: 0;
 +
        }
 +
        .last_head{
 +
            width: 20%;
 +
            height: 12%;
 +
            position: absolute;
 +
            top:8%;
 +
            left: 40%;
 +
            background-color: #72c9b6;
 +
        }
 +
        .last_body{
 +
            width: 80%;
 +
            height: 20%;
 +
            position: absolute;
 +
            top: 25%;
 +
            left: 10%;
 +
            background-color: #72c9b6;
 +
        }
 +
        .last_bottom{
 +
            width: 13%;
 +
            height: 10%;
 +
            position: absolute;
 +
            top: 50%;
 +
            left: 45%;
 +
        }
 +
        .last_img1{
 +
            width: 50%;
 +
            height: 30%;
 +
            position: absolute;
 +
            top: 70%;
 +
            left: 50%;
 +
        }
 +
        .last_img2{
 +
            width: 15%;
 +
            height: 45%;
 +
            position: absolute;
 +
            top: 55%;
 +
            left:70%;
 +
        }
  
  
<div class="column half_size" >
+
        .footer{
<h5> Editing your wiki </h5>
+
            width: 100%;
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>
+
            height: 300px;
<p> <a href="https://2016.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
+
            position: absolute;
 +
            top: 2000px;
 +
            left: 0;
 +
        }
  
</div>
+
    </style>
 +
</head>
  
  
<div class="column half_size" >
+
<body>
<h5>Tips</h5>
+
<div class="content_wrapper">
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
+
<ul>
+
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
+
<li>Be clear about what you are doing and how you plan to do this.</li>
+
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
+
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
+
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
+
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2016.igem.org/Calendar">iGEM 2016 calendar</a> </li>
+
<li>Have lots of fun! </li>
+
</ul>
+
</div>
+
  
 +
    <div class="header"><img src="https://static.igem.org/mediawiki/2016/e/e4/Igem_2016_hzau_header_background.png" width="1348" height="580"> </div>
 +
    <div class="title"><h1>this is main topic!</h1></div>
 +
    <div class="header_left"><img src="https://static.igem.org/mediawiki/2016/3/3f/Igem_2016_hzau_header_table.png" width="250" height="210"></div>
 +
    <div class="header_right"><img src="https://static.igem.org/mediawiki/2016/7/72/Igem_2016_hzau_header_human.png" width="300" height="480"></div>
  
<div class="column half_size" >
+
    <div class="main_part"><img src="https://static.igem.org/mediawiki/2016/5/58/Igem_2016_interbody_mainpart.png" width="1348" height="1200" >
<h5>Inspiration</h5>
+
        <div class="bar_name"><h2>about us!</h2></div>
<p> You can also view other team wikis for inspiration! Here are some examples:</p>
+
        <div class="tmp_img"></div>
<ul>
+
<li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
+
<li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
+
<li> <a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a> </li>
+
<li> <a href="https://2014.igem.org/Team:Michigan"> 2014 Michigan</a></li>
+
<li> <a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara </a></li>
+
<li> <a href="https://2014.igem.org/Team:SCU-China"> 2014 SCU-China </a></li>
+
</ul>
+
</div>
+
  
<div class="column half_size" >
+
        <div class="part1"><img src="https://static.igem.org/mediawiki/2016/7/76/Igem_2016_hzau_body_white_regtangle.png" width="407" height="680">
<h5> Uploading pictures and files </h5>
+
            <div class="decoration"><img src="https://static.igem.org/mediawiki/2016/b/b4/Igem_2016_hzau_decoration_tmp.png" width="410" height="60"></div>
<p> You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
+
When you upload, set the "Destination Filename" to <br><code>T--YourOfficialTeamName--NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
+
  
 +
            <div class="words">
 +
                <p>In our project, the communication between these two parts is mutual which means that we need
 +
                    a two-way interface device composed of Light Receiving part and Light Controlling part. For
 +
                    the former one, cells were cultivated on a microfluidic chip and observed by fluorescence microscope.</p>
 +
                <p>And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco.
 +
                    Besides, we have made a different device to achieve the phase 2 collaborated with Model and another to
 +
                    complete the test of light control system with Wet Lab. Most important of all are that these two
 +
                    devices all turned to work successfully.</p>
 +
            </div>
 +
            <div class="bottom">
 +
            <a href="#" class="view_more">view more</a>
 +
            </div>
 +
        </div>
 +
 +
        <div class="part2"><img src="https://static.igem.org/mediawiki/2016/7/76/Igem_2016_hzau_body_white_regtangle.png" width="407" height="680">
 +
            <div class="decoration"><img src="https://static.igem.org/mediawiki/2016/b/b4/Igem_2016_hzau_decoration_tmp.png" width="410" height="60"></div>
 +
            <div class="words">
 +
                <p>abcdIn our project, the communication between these two parts is mutual which means that we need
 +
                    a two-way interface device composed of Light Receiving part and Light Controlling part. For
 +
                    the former one, cells were cultivated on a microfluidic chip and observed by fluorescence microscope.
 +
                    And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco.
 +
                    Besides, we have made a different device to achieve the phase 2 collaborated with Model and another to
 +
                    complete the test of light control system with Wet Lab. Most important of all are that these two
 +
                    devices all turned to work successfully.</p>
 +
            </div>
 +
            <div class="bottom">
 +
                <a href="#" class="view_more">view more</a>
 +
            </div>
 +
        </div>
 +
 +
        <div class="part3"><img src="https://static.igem.org/mediawiki/2016/7/76/Igem_2016_hzau_body_white_regtangle.png" width="407" height="680">
 +
            <div class="decoration"><img src="https://static.igem.org/mediawiki/2016/b/b4/Igem_2016_hzau_decoration_tmp.png" width="410" height="60"></div>
 +
            <div class="words">
 +
                <p>abcdIn our project, the communication between these two parts is mutual which means that we need
 +
                    a two-way interface device composed of Light Receiving part and Light Controlling part. For
 +
                    the former one, cells were cultivated on a microfluidic chip and observed by fluorescence microscope.
 +
                    And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco.
 +
                    complete the test of light control system with Wet Lab. Most important of all are that these two
 +
                    devices all turned to work successfully.</p>
 +
            </div>
 +
            <div class="bottom">
 +
                <a href="#" class="view_more">view more</a>
 +
            </div>
 +
        </div>
 +
 +
    </div>
 +
 +
    <div class="last_part"><img src="https://static.igem.org/mediawiki/2016/a/a1/Igem_2016_hzau_inter_body.png" width="1348" height="500">
 +
        <div class="last_head"><h2>interlab</h2></div>
 +
        <div class="last_body"><h4>And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco.</h4></div>
 +
        <div class="last_bottom">
 +
            <a href="#" class="view_more">view more</a>
 +
        </div>
 +
        <div class="last_img1"><img src="https://static.igem.org/mediawiki/2016/5/55/Igem_2016_hzau_bottom_grass.png" width="600" height="150"></div>
 +
        <div class="last_img2"><img src="https://static.igem.org/mediawiki/2016/0/00/Igem_2016_interbody_man.png" width="180" height="235"></div>
 +
    </div>
 +
 +
    <div class="footer"><img src="https://static.igem.org/mediawiki/2016/2/23/Igem_2016_hzau_bottom_box.png" width="1384" height="300">
 +
    </div>
  
<div class="button_click"  onClick=" parent.location= 'https://2016.igem.org/Special:Upload '"> 
 
UPLOAD FILES
 
</div>
 
  
 
</div>
 
</div>
 +
</body>
 +
  
 
</html>
 
</html>

Revision as of 08:20, 17 September 2016

body

this is main topic!

about us!

In our project, the communication between these two parts is mutual which means that we need a two-way interface device composed of Light Receiving part and Light Controlling part. For the former one, cells were cultivated on a microfluidic chip and observed by fluorescence microscope.

And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco. Besides, we have made a different device to achieve the phase 2 collaborated with Model and another to complete the test of light control system with Wet Lab. Most important of all are that these two devices all turned to work successfully.

abcdIn our project, the communication between these two parts is mutual which means that we need a two-way interface device composed of Light Receiving part and Light Controlling part. For the former one, cells were cultivated on a microfluidic chip and observed by fluorescence microscope. And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco. Besides, we have made a different device to achieve the phase 2 collaborated with Model and another to complete the test of light control system with Wet Lab. Most important of all are that these two devices all turned to work successfully.

abcdIn our project, the communication between these two parts is mutual which means that we need a two-way interface device composed of Light Receiving part and Light Controlling part. For the former one, cells were cultivated on a microfluidic chip and observed by fluorescence microscope. And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco. complete the test of light control system with Wet Lab. Most important of all are that these two devices all turned to work successfully.

interlab

And for the last one, light (LED beads) can be controlled by the computer through a Single Chip Micyoco.