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

(Prototype team page)
 
 
(17 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{SYSU-Software}}
 
{{SYSU-Software}}
 
<html>
 
<html>
 +
<link rel="stylesheet" type="text/css" href="https://2015.igem.org/Team:SYSU-Software/Description/CSS?action=raw&amp;ctype=text/css"/>
 +
<div id="contentContainer">
 +
          <h1 class = "juzhong">Description</h1>
 +
          <div id = "one">
 +
              <h2 class = "juzhong">Problems: Our Motivations</h2>
 +
              <p class = "wenzi juzhong">Software teams have an inborn connection to wet-lab teams’ needs.</p>
 +
              <div id = "one_block1">
 +
                  <img src = "https://static.igem.org/mediawiki/2015/a/a1/SYSU-Software_1_03.png" id = "im1">
 +
                  <img src = "https://static.igem.org/mediawiki/2015/3/3b/SYSU-Software_de2_03.png" id = "im2">
 +
                  <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>
  
−
<h2> Project Description </h2>
+
                  <div class = "wenzi bw" id = "bw2">
 +
                      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.
 +
                  </div>
  
−
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
                  <div class = "wenzi bw" id = "bw3">
−
<br />
+
                      3. Teams are busy working on experiments and in need of a integrated solutions to wet-lab, not only genetic design.
 +
                  </div>
 +
              </div>
 +
          </div>
  
−
<h5>What should this page contain?</h5>
 
−
<ul>
 
−
<li> A clear and concise description of your project.</li>
 
−
<li>A detailed explanation of why your team chose to work on this particular project.</li>
 
−
<li>References and sources to document your research.</li>
 
−
<li>Use illustrations and other visual resources to explain your project.</li>
 
−
</ul>
 
  
  
−
<br />
 
−
<h4>Advice on writing your Project Description</h4>
 
  
−
<p>
+
       
−
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements.
+
−
</p>
+
  
−
<p>
 
−
Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
 
−
</p>
 
  
 +
          <div id = "four">
 +
              <h2 class = "juzhong">Solutions: Our Goals</h2>
 +
              <div id = "four_block1" class = "wenzi">
 +
                  <div id = "four_block11">
 +
                      <img src = "https://static.igem.org/mediawiki/2015/6/6e/SYSU-Software_de4_03.png">
 +
                      <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.
 +
                      </div>
 +
                  </div>
 +
                  <div id = "four_block12">
 +
                      <img src = "https://static.igem.org/mediawiki/2015/a/aa/SYSU-Software_de4_05.png">
 +
                      <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.
 +
                      </div>
 +
                  </div>
 +
                  <div id = "four_block13">
 +
                      <img src = "https://static.igem.org/mediawiki/2015/d/db/SYSU-Software_de4_08.png">
 +
                      <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.
 +
                      </div>
 +
                  </div>
 +
              </div>
 +
              <div id = "four_block2" class = "wenzi">
 +
                  <div id = "four_block21">
 +
                      <img src = "https://static.igem.org/mediawiki/2015/1/19/SYSU-Software_de4_14.png">
 +
                      <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.
 +
                      </div>
 +
                  </div>
 +
                  <div id = "four_block22">
 +
                      <img src = "https://static.igem.org/mediawiki/2015/5/5f/SYSU-Software_de4_17.png">
 +
                      <div class = "wenzi">
 +
                      Designs that <b>stand the test of time</b> should be able to migrate from the crowdsourcing platform to the bank.
 +
                      </div>
 +
                  </div>
 +
              </div>
 +
          </div>
  
−
<br />
 
−
<h4>References</h4>
 
−
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you though about your project and what works inspired you.</p>
 
  
 +
          <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 useful integrations.
 +
                  </div>
 +
              </div>
 +
          </div>
 +
      </div>
 +
</html>
  
−
 
+
{{SYSU-Software/FOOTER}}
−
<h4>Inspiration</h4>
+
−
<p>See how other teams have described and presented their projects: </p>
+
−
 
+
−
<ul>
+
−
<li><a href="https://2014.igem.org/Team:Imperial/Project"> Imperial</a></li>
+
−
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> UC Davis</a></li>
+
−
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">SYSU Software</a></li>
+
−
</ul>
+
−
 
+
−
</div>
+
−
</html>
+

Latest revision as of 16:56, 1 October 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 characterize and improve the functions, collaboratively.
A standardized and centralized bank of projects of the past and future. This centralized bank 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. Users can use the tool to re-design constructs and systems in the bank, 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 bank.

Our Project: A Glimpse

Our project consists of two inter-connected parts:

“Synbio Hub”: a proof-of-principle platform for collaborative construction and standardized bank of genetic design. This part is further divided into two modules: CORE Bank, the bank, and Co-development, the crowdsourcing platform for collaborative design.

CORE Design: a well-designed tool for genetic design, mathematical modeling, plasmid design and experiment scheduling with protocol management.

"Synbio Hub" and CORE Design: Platform for community with useful integrations.