Difference between revisions of "Team:SYSU-Software/Description"

Line 7: Line 7:
 
               <h2 class = "juzhong">Problems: Our Motivations</h2>
 
               <h2 class = "juzhong">Problems: Our Motivations</h2>
 
               <p class = "wenzi juzhong">Software teams have an inborn connection to wet-lab teams’ needs.</p>
 
               <p class = "wenzi juzhong">Software teams have an inborn connection to wet-lab teams’ needs.</p>
−
               <div id = "one_block">
+
               <div id = "one_block1">
−
                   <img src = "https://static.igem.org/mediawiki/2015/a/a1/SYSU-Software_1_03.png">
+
                   <img src = "https://static.igem.org/mediawiki/2015/a/a1/SYSU-Software_1_03.png" id = "im1">
−
                   <div class = "wenzi" id = "one_block_you">
+
                  <img src = "https://static.igem.org/mediawiki/2015/3/3b/SYSU-Software_de2_03.png" id = "im2">
−
                       <b>1. Teams are encouraged to work together to tackle problems, but there is no platform that can supports collaborative building of genetic design in the community.</b> Teams might collaborate to design constructs, but their collaborations are usually not open to the public. In fact, some hard nuts (like, complex network behavior) can be tackled with the help of collective intelligence in the Synbio community.
+
                  <img src = "https://static.igem.org/mediawiki/2015/8/8f/SYSU-Software_de3_03.png" id = "im3">
 +
              </div>
 +
              <div id = "one_block2">
 +
                 
 +
                   <div class = "wenzi bw" id = "bw1">
 +
                       1. Teams are encouraged to work together to tackle problems, but there is no platform that can supports collaborative building of genetic design in the community.  
 
                   </div>
 
                   </div>
−
              </div>
 
−
          </div>
 
  
−
          <div id = "two">
+
                  <div class = "wenzi bw" id = "bw2">
−
              <div class = "wenzi" id = "two_zuo">
+
                      2. Teams are encouraged to “stand on the shoulder of the giants” while not to “re-invent the wheels”, but things goes not so smoothly.
−
                  <b>2. Teams are encouraged to “stand on the shoulder of the giants” while not to “re-invent the wheels”, but things goes not so smoothly.</b> Project descriptions are scattered in team wiki, and looking for a design is laborious. Further, different ways of representing designs in wiki makes them hard to understand. Worse still, without standardized bank of genetic design along with the wet-lab protocols, some of the constructs are not reproducible. [Click <a href="https://2015.igem.org/Team:SYSU-Software/Validation"><b>here</b></a> for our experience in reproducing a construct in wet-lab.]
+
                  </div>
−
              </div>
+
−
              <img src = "https://static.igem.org/mediawiki/2015/3/3b/SYSU-Software_de2_03.png">
+
−
          </div>
+
  
−
          <div id = "three">
+
                  <div class = "wenzi bw" id = "bw3">
−
              <img src = "https://static.igem.org/mediawiki/2015/8/8f/SYSU-Software_de3_03.png">
+
                      3. Teams are busy working on experiments and in need of a integrated solutions to wet-lab, not only genetic design.
−
              <div class = "wenzi" id = "three_you">
+
                  </div>
−
                  <b>3. Teams are busy working on experiments and in need of a integrated solutions to wet-lab, not only genetic design.</b> Wet-lab teams need a better tool to manage their protocol and schedule their experiment, a tool for navigation of parts information in Registry, and more importantly and irreplaceably, a tool for mathematical modeling.
+
 
               </div>
 
               </div>
 
           </div>
 
           </div>
 +
 +
 +
 +
 +
       
  
  
Line 36: Line 40:
 
                       <img src = "https://static.igem.org/mediawiki/2015/6/6e/SYSU-Software_de4_03.png">
 
                       <img src = "https://static.igem.org/mediawiki/2015/6/6e/SYSU-Software_de4_03.png">
 
                       <div class = "wenzi">
 
                       <div class = "wenzi">
−
                       A <b>crowdsourcing platform</b> that serves two inter-connected functions, to promote and facilitate <b>communication</b> and <b>collaborations</b> among iGEM teams, and to provide convenience to <b>work on a genetic design</b>, <b>identify problems</b> and <b>characterize and improve the functions</b>, collaboratively.
+
                       A <b>crowdsourcing platform</b> that serves two inter-connected functions, to promote and facilitate <b>communication and collaborations</b> among iGEM teams, and to provide convenience to <b>work on a genetic design</b>, <b>identify problems</b> and <b>characterise and improve the functions</b>, collaboratively.
 
                       </div>
 
                       </div>
 
                   </div>
 
                   </div>
Line 42: Line 46:
 
                       <img src = "https://static.igem.org/mediawiki/2015/a/aa/SYSU-Software_de4_05.png">
 
                       <img src = "https://static.igem.org/mediawiki/2015/a/aa/SYSU-Software_de4_05.png">
 
                       <div class = "wenzi">
 
                       <div class = "wenzi">
−
                       A <b>standardized</b> and <b>centralized</b> bank of projects of the past and future. This centralized bank could help improve <b>transparency and reproducibility</b> in iGEM by way of standard documentation of constructs and wet-lab protocols.
+
                       A <b>standardized</b> and <b>centralized</b> repository of projects of the past and future. This centralized repository could help improve transparency and reproducibility in iGEM by way of standard documentation of constructs and wet-lab protocols.
 
                       </div>
 
                       </div>
 
                   </div>
 
                   </div>
Line 48: Line 52:
 
                       <img src = "https://static.igem.org/mediawiki/2015/d/db/SYSU-Software_de4_08.png">
 
                       <img src = "https://static.igem.org/mediawiki/2015/d/db/SYSU-Software_de4_08.png">
 
                       <div  class = "four_block13_wenzi" class = "wenzi">
 
                       <div  class = "four_block13_wenzi" class = "wenzi">
−
                       A tool for genetic design that serves to closely connect the two parts mentioned. Users can use the tool to <b>re-design</b> constructs and systems in the bank, and also to <b>identify problems</b> or <b>improve functions in the constructs</b> presented by other teams in the open platform.
+
                       A tool for genetic design that serves to closely connect the two parts mentioned above. Users can use the tool to re-design constructs and systems in the repositories, and also to identify problems or improve functions in the constructs presented by other teams in the open platform.
 
                       </div>
 
                       </div>
 
                   </div>
 
                   </div>
Line 56: Line 60:
 
                       <img src = "https://static.igem.org/mediawiki/2015/1/19/SYSU-Software_de4_14.png">
 
                       <img src = "https://static.igem.org/mediawiki/2015/1/19/SYSU-Software_de4_14.png">
 
                       <div class = "wenzi">
 
                       <div class = "wenzi">
−
                       The tool should provide an <b>integrated solution to wet-lab</b>: mathematical modeling using experimental results, plasmid design, experiment scheduling and protocol management.
+
                       The tool should provide an integrated solution to wet-lab: mathematical modeling using experimental results, plasmid design, experiment scheduling and protocol management.
 
                       </div>
 
                       </div>
 
                   </div>
 
                   </div>
Line 62: Line 66:
 
                       <img src = "https://static.igem.org/mediawiki/2015/5/5f/SYSU-Software_de4_17.png">
 
                       <img src = "https://static.igem.org/mediawiki/2015/5/5f/SYSU-Software_de4_17.png">
 
                       <div class = "wenzi">
 
                       <div class = "wenzi">
−
                       Designs that <b>stand the test of time</b> should be able to migrate from the crowdsourcing platform to the bank.
+
                       Designs that stand the test of time should be able to migrate from the crowdsourcing platform to the repository.
 
                       </div>
 
                       </div>
 
                   </div>
 
                   </div>
 
               </div>
 
               </div>
 
           </div>
 
           </div>
−
 
−
 
−
          <div id = "five">
 
−
              <h2 class = "juzhong">Our project: A glimpse</h2>
 
−
              <div id = "five_block">
 
−
                  <img src = "https://static.igem.org/mediawiki/2015/d/d7/SYSU-Software_de5_03.png">
 
−
                  <div id = "five_block_you" class = "wenzi">
 
−
                      Our project consists of two inter-connected parts:<br><br>
 
−
                      <b>“Synbio Hub”</b>: a proof-of-principle platform for collaborative construction and standardized bank of genetic design. This part is further divided into two modules: <b>CORE Bank</b>, the bank, and <b>Co-development</b>, the crowdsourcing platform for collaborative design.<br><br>
 
−
                      <b>CORE Design</b>: a well-designed tool for genetic design, mathematical modeling, plasmid design and experiment scheduling with protocol management.<br><br>
 
−
                      <b>"Synbio Hub" and CORE Design</b>: Platform for community with powerful integrations.
 
−
                  </div>
 
−
              </div>
 
−
          </div>
 
−
      </div>
 
 
</html>
 
</html>
  
 
{{SYSU-Software/FOOTER}}
 
{{SYSU-Software/FOOTER}}

Revision as of 18:28, 18 September 2015

SYSU-SOFTWARE IGEM 2015

Description

Problems: Our Motivations

Software teams have an inborn connection to wet-lab teams’ needs.

1. Teams are encouraged to work together to tackle problems, but there is no platform that can supports collaborative building of genetic design in the community.
2. Teams are encouraged to “stand on the shoulder of the giants” while not to “re-invent the wheels”, but things goes not so smoothly.
3. Teams are busy working on experiments and in need of a integrated solutions to wet-lab, not only genetic design.

Solutions: Our Goals

A crowdsourcing platform that serves two inter-connected functions, to promote and facilitate communication and collaborations among iGEM teams, and to provide convenience to work on a genetic design, identify problems and characterise and improve the functions, collaboratively.
A standardized and centralized repository of projects of the past and future. This centralized repository could help improve transparency and reproducibility in iGEM by way of standard documentation of constructs and wet-lab protocols.
A tool for genetic design that serves to closely connect the two parts mentioned above. Users can use the tool to re-design constructs and systems in the repositories, and also to identify problems or improve functions in the constructs presented by other teams in the open platform.
The tool should provide an integrated solution to wet-lab: mathematical modeling using experimental results, plasmid design, experiment scheduling and protocol management.
Designs that stand the test of time should be able to migrate from the crowdsourcing platform to the repository.