Team:SUSTC-Shenzhen-A/Notebook1

From 2012.igem.org

(Difference between revisions)
 
(9 intermediate revisions not shown)
Line 1: Line 1:
-
{{Template:SUSTC/pd_template}}
+
{{Template:SUSTC_A3}}
-
 
+
<html>
<html>
<head>
<head>
Line 81: Line 80:
   font-size: 13px;
   font-size: 13px;
   color:#333;
   color:#333;
 +
}
 +
#talkbubble_b {
 +
width: 544px;
 +
height:400px;
 +
//  background:#EFEFEF;
 +
background:#ffffff;
 +
position: relative;
 +
-moz-border-radius:    0px;
 +
-webkit-border-radius: 0px;
 +
border-radius:        10px;
 +
font-family: Tahoma, Geneva, sans-serif;
 +
font-size: 13px;
 +
color:#333;
}
}
#talkbubble_c1 {
#talkbubble_c1 {
-
   width: 862px;  
+
   width: 859px;  
-
   height:200px;  
+
   height:400px;  
//  background:#EFEFEF;
//  background:#EFEFEF;
   background:#ffffff;
   background:#ffffff;
Line 109: Line 121:
}
}
#talkbubble_c3 {
#talkbubble_c3 {
-
   width: 862px;  
+
   width: 859px;  
   height:200px;  
   height:200px;  
//  background:#EFEFEF;
//  background:#EFEFEF;
Line 123: Line 135:
#talkbubble1 {
#talkbubble1 {
   width: 275px;  
   width: 275px;  
-
   height:600px;  
+
   height:560px;  
//  background:#FAF0E6;
//  background:#FAF0E6;
   background:#f2eada;
   background:#f2eada;
Line 148: Line 160:
<body >
<body >
-
<table width="899" border="0" cellspacing="10px" cellpadding="10px">
+
<table width="899" border="0" cellspacing="10px" cellpadding="10px"align="center">
        <tr>
        <tr>
          <td valign="top"><div id="talkbubble_a">
          <td valign="top"><div id="talkbubble_a">
Line 155: Line 167:
<p>&nbsp;&nbsp;The weekly notebook includes the work process of every teammate everyday. Here you can see the detailed steps of finishing the two projects for iGEM competition, and go through the days that our projects grow up with us together.</p>
<p>&nbsp;&nbsp;The weekly notebook includes the work process of every teammate everyday. Here you can see the detailed steps of finishing the two projects for iGEM competition, and go through the days that our projects grow up with us together.</p>
<img src="https://static.igem.org/mediawiki/2012/f/f1/Devidingline.jpg">
<img src="https://static.igem.org/mediawiki/2012/f/f1/Devidingline.jpg">
-
<div></td>
+
<div>
 +
<div id="talkbubble_b">
 +
              <p class="title">Summerized Process</p>
 +
              <p><strong>Biosearch section1:</strong></p>
 +
              <ul>
 +
                <li>7.9~7.16</li>
 +
              </ul>
 +
              <p>All of our teammates enjoyed learning object c and using Xcode to program some necessary parts of our user interface(e.g. combo box).</p>
 +
              <ul>
 +
                <li>7.17</li>
 +
              </ul>
 +
              <p>In the first meeting, our group divided into two parts:UI &amp; data. The main structure and initial division of work had been confirmed.</p>
 +
              <ul>
 +
                <li>7.18</li>
 +
              </ul>
 +
              <p>In this day we determined three parts of our work: categories, search list, and search results. We also disgusted the search methods. From now, all the members started our group-work with clear aims.</p>
 +
             
 +
</div>
 +
 
 +
</td>
 +
 
 +
 
 +
 
         <td><div id="talkbubble1"><div class="sidebar_box"><div class="sidebar_box_top"></div>
         <td><div id="talkbubble1"><div class="sidebar_box"><div class="sidebar_box_top"></div>
Line 161: Line 195:
<p class="title1">Notebook</p>
<p class="title1">Notebook</p>
<img src="https://static.igem.org/mediawiki/2012/c/c9/Devidingline_side.jpg">
<img src="https://static.igem.org/mediawiki/2012/c/c9/Devidingline_side.jpg">
-
<p><strong>Abstruct</strong></p>
+
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Notebook"><strong>Abstruct</strong></a></p>
-
<p><strong>Xcode Torial(week 1)</strong></p>
+
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week1"><strong>Xcode Torial(week 1)</strong></a></p>
-
<p><strong>Biosearch No.1(week2,3)</strong></p>
+
<p><strong>Biosearch section1(week2,3)</strong></p>
-
<p>&nbsp;&nbsp;week 2</p>
+
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week2">week 2</a></p>
-
<p>&nbsp;&nbsp;week 3</p>
+
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week3">week 3</a></p>
-
<p><strong>Biosearch No.2(week4,5)</strong></p>
+
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week4&5"><strong>Biosearch section2(week4,5)</strong></a></p>
<p><strong>Tinker Cell(week,6,7)</strong></p>
<p><strong>Tinker Cell(week,6,7)</strong></p>
-
<p>&nbsp;&nbsp;week 6</p>
+
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week6">week 6</a></p>
-
<p>&nbsp;&nbsp;week 7</p>
+
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 7</a></p>
 +
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 8</a></p>
 +
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 9</a></p>
 +
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 10</a></p>
 +
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 11</a></p>
 +
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 12</a></p>
<div class="sidebar_box_bottom"></div>                     
<div class="sidebar_box_bottom"></div>                     
-
            </div>
+
          </div>
</td>
</td>
             </tr>
             </tr>
-
        </table>
 
-
<table width="899" border="0" cellspacing="10" cellpadding="10">
 
-
  <tr>
 
-
    <td><div id="talkbubble_c1">
 
-
<a name="Instructors" ></a>
 
-
<p class="title">Instructors</p>
 
-
<table border="0" cellspacing="0" cellpadding="0">
 
-
  <tr>
 
-
    <td>
 
-
<p><strong>Jiankui He</strong></p>
 
-
<p>Dr. JK is our primary contact, biota associate professor. </p>
 
-
<p>贺建奎实验室用物理,统计和信息学的交叉技术来研究复杂的生物系统。我们主要的研究集中于免疫基因组学,个体化医疗,生物信息学和系统生物学。贺建奎实验室将高通量测序应用到免疫细胞受体库的多样性研究,在免疫基因组学(immunome)方面有重要贡献。</p>
 
-
</td>
 
-
    <td>&nbsp;</td>
 
-
  </tr>
 
-
  <tr>
 
-
    <td><p><strong>Pu Li</strong></p></td>
 
-
    <td>&nbsp;</td>
 
-
  </tr>
 
-
  <tr>
 
-
    <td><p><strong>Jing Zhang</strong></p></td>
 
-
    <td>&nbsp;</td>
 
-
  </tr>
 
</table>
</table>
-
<p>
 
-
 
-
!(need a table)</p>
 
-
<img src="https://static.igem.org/mediawiki/2012/0/0b/Devidingline_whole.jpg">
 
-
<div></td>
 
-
      </tr>
 
-
  <tr>
 
-
    <td><div id="talkbubble_c2">
 
-
<a name="Student_Members" ></a>
 
-
<p class="title">Student Members</p>
 
-
<p>
 
-
<img src="https://static.igem.org/mediawiki/2012/0/0b/Devidingline_whole.jpg">
+
<table width="899" border="0" cellspacing="10" cellpadding="10" align="center">
-
<div></td>
+
-
      </tr>
+
-
  <tr>
+
-
    <td><div id="talkbubble_c3">
+
-
<a name="Advisors" ></a>
+
-
<p class="title">advisors</p>
+
-
<table>
+
   <tr>
   <tr>
-
     <td><p><strong>carnby yang</strong></p></td>
+
     <td><div id="talkbubble_c1">
-
    <td>&nbsp;</td>
+
<ul>
 +
                <li>7.21</li>
 +
              </ul>
 +
              <p>Members of data group in search results broke through the main problem of data base. By loading data directly from xml file which provided by partsregistry.org (It couldn't be loaded only if it was changed some parts of the form) and send into mysql, we could easily get partname-based-data from our database. With this optimized new database, UI group could test their work with high efficiency.</p>
 +
              <ul>
 +
                <li>7.23</li>
 +
              </ul>
 +
              <p>Discussing with Shenzhen Team, we were given a lot of advice of search methods and user interface. Knowing what users really needed, we got the ability to optimize the completed parts and improve the design of parts which would be added.</p>
 +
              <ul>
 +
                <li>7.25</li>
 +
              </ul>
 +
              <p>The work of searching part (list and result) had been done!</p>
 +
              <ul>
 +
                <li>7.27</li>
 +
              </ul>
 +
              <p>All parts of our project had been combined and tested. Now we're trying to optimize the user interface with unified style.</p>
 +
</div>
 +
</td>
   </tr>
   </tr>
-
  <tr>
 
-
    <td><p><strong>Rui Zhao</strong></p></td>
 
-
    <td>&nbsp;</td>
 
-
  </tr>
 
-
</table>
 
-
<div></td>
 
-
      </tr>
 
</table>
</table>
-
<!-- end of header -->
+
 
 +
 
 +
<!-- end of header -->
</body>
</body>
</html>
</html>
-
 
+
[[file:footbar.jpg|center]]
-
[[file:footbar.jpg]]
+

Latest revision as of 06:49, 21 September 2012

Abstruct

image 2

  The weekly notebook includes the work process of every teammate everyday. Here you can see the detailed steps of finishing the two projects for iGEM competition, and go through the days that our projects grow up with us together.

Summerized Process

Biosearch section1:

  • 7.9~7.16

All of our teammates enjoyed learning object c and using Xcode to program some necessary parts of our user interface(e.g. combo box).

  • 7.17

In the first meeting, our group divided into two parts:UI & data. The main structure and initial division of work had been confirmed.

  • 7.18

In this day we determined three parts of our work: categories, search list, and search results. We also disgusted the search methods. From now, all the members started our group-work with clear aims.

  • 7.21

Members of data group in search results broke through the main problem of data base. By loading data directly from xml file which provided by partsregistry.org (It couldn't be loaded only if it was changed some parts of the form) and send into mysql, we could easily get partname-based-data from our database. With this optimized new database, UI group could test their work with high efficiency.

  • 7.23

Discussing with Shenzhen Team, we were given a lot of advice of search methods and user interface. Knowing what users really needed, we got the ability to optimize the completed parts and improve the design of parts which would be added.

  • 7.25

The work of searching part (list and result) had been done!

  • 7.27

All parts of our project had been combined and tested. Now we're trying to optimize the user interface with unified style.

Footbar.jpg