Difference between revisions of "Team:USTC-Software/Improve"

(Prototype team page)
 
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
−
{{USTC-Software}}
+
{{USTC-Software/html/header}}
 +
 
 
<html>
 
<html>
 +
  <link href="https://2019.igem.org/Template:USTC-Software/css/default?action=raw&ctype=text/css" rel="stylesheet"
 +
    type="text/css" />
 +
  <link href="https://2019.igem.org/Template:USTC-Software/css/bootstrap?action=raw&ctype=text/css" rel="stylesheet"
 +
    type="text/css" />
 +
  <script src="https://2019.igem.org/Template:USTC-Software/js/jquery?action=raw&ctype=text/javascript"
 +
    type="text/javascript"></script>
 +
  <script src="https://2019.igem.org/Template:USTC-Software/js/popper?action=raw&ctype=text/javascript"
 +
    type="text/javascript"></script>
 +
  <script src="https://2019.igem.org/Template:USTC-Software/js/bootstrap?action=raw&ctype=text/javascript"
 +
    type="text/javascript"></script>
  
 +
  <div id="autoMenu2" class="autoMenu2"></div>
 +
  <div class="container">
 +
    <div class="row">
 +
      <!--    <div class="col-lg-2 col-md-0">-->
 +
      <!--      <div class="autoMenu d-none d-lg-block" data-autoMenu id="autoMenu"></div>-->
 +
      <!--    </div>-->
 +
      <div class="col-lg-12 col-md-12">
 +
        <div class="card page-content">
 +
          <div class="card-body">
 +
            <h1 class="text-center">Improve</h1>
 +
            <h3>Biobricks</h3>
 +
            <div class="passage">
 +
              <div class="text-center psgImg">
 +
                <img src="https://static.igem.org/mediawiki/2019/3/35/T--USTC-Software--Contribution_bio.png" alt="">
 +
              </div>
 +
              At the time when we were trying to design our algorithms to handle the Biobricks Recommendation, we had an
 +
              urgent need for a function that we can search Biobricks by specific reactions, metabolites, and genes. As
 +
              a result, we began to communicate with some of the other iGEM-software teams, including UESTC-Software,
 +
              the best software team last year, trying to get a perfect solution for this. However, we realized that
 +
              none of the their projects could satisfy our needs. We spent lots of time and finally managed to design a
 +
              new algorithm based on feature extraction used for searching Biobricks that can meet our needs.
 +
              <h3>Platform</h3>
 +
              <div class="passage">
 +
                <div class="text-center psgImg">
 +
                  <img src="https://static.igem.org/mediawiki/2019/c/c3/T--USTC-Software--Improve_platform.png" alt="">
 +
                </div>
 +
                Different from the other iGEM-Software computing projects, Alpha-Ant, for instance, did not have any
 +
                convenient ways to share users' findings when using the software. Since collaboration in scientific
 +
                research is quite important, we developed a simple sharing function based on web-link generating.
 +
                Researchers with the links can easily edit on these models, favor them, and even give them a score.
 +
              </div>
 +
              <h3>Message Queues</h3>
 +
              <div class="passage">
 +
                <div class="text-center psgImg">
 +
                  <img src="https://static.igem.org/mediawiki/2019/3/3f/T--USTC-Software--model_msg.png" alt="">
 +
                </div>
 +
                Some of the iGEM-Software projects have computing tasks that will consume lots of computation resources
 +
                during executing. Most of them handle both this kind of task and the services to users in the same
 +
                server. The characteristics increase the risk of reducing the user experience and even breaking down the
 +
                whole server.
 +
                <br><br>
 +
                Foresyn split our programs computing models from our website, and use message queues to send and receive
 +
                information about our computation. A queue is a data structure that stores things waiting to be handled,
 +
                and it obeys the "First Come, First Serve" principle. So, we can store our computing tasks in the queue,
 +
                and response to users instantly about the progress of his tasks.
 +
                <br><br>
 +
                So the risk of breaking down does not exist anymore, and users can have a better experience.
 +
                <h2 class="ref">References</h2>
 +
                <div class="ref-list">
 +
                  <ul>
 +
                    <li>Figure 1:
 +
                      http://www.netimperative.com/2019/04/facebook-sheds-light-on-news-feed-and-advertising-algorithm-secrets/
 +
                    </li>
 +
                    <li>Figure 2: https://rawcliffe.co.uk/tax-news/emi-share-option-schemes/</li>
 +
                    <li>Figure 3: https://www.cloudamqp.com/blog/2014-12-03-what-is-message-queuing.html</li>
 +
                  </ul>
 +
                </div>
 +
              </div>
 +
            </div>
 +
          </div>
 +
        </div>
  
−
<div class="column full_size judges-will-not-evaluate">
 
−
<h3>★  ALERT! </h3>
 
−
<p>This page is used by the judges to evaluate your team for the <a href="https://2019.igem.org/Judging/Medals">medal criterion</a> or <a href="https://2019.igem.org/Judging/Awards"> award listed below</a>. </p>
 
−
<p> Delete this box in order to be evaluated for this medal criterion and/or award. See more information at <a href="https://2019.igem.org/Judging/Pages_for_Awards"> Instructions for Pages for awards</a>.</p>
 
−
</div>
 
  
 +
      </div>
 +
      <!--autoMenu css and js files, generate Menu of each article-->
 +
      <!--<link href="https://2019.igem.org/Template:USTC-Software/css/autoMenu?action=raw&ctype=text/css" rel="stylesheet">-->
 +
      <!--<script src="https://2019.igem.org/Template:USTC-Software/js/autoMenu?action=raw&ctype=text/javascript"></script>-->
  
−
<div class="clear"></div>
+
      <!--autoMenu css and js files, generate Menu of each article-->
 +
      <link href="https://2019.igem.org/Template:USTC-Software/css/autoMenu2?action=raw&ctype=text/css" rel="stylesheet">
 +
      <script src="https://2019.igem.org/Template:USTC-Software/js/autoMenu2?action=raw&ctype=text/javascript"></script>
  
 +
      <!--scrollBar js. when scroll down, a cat will be there-->
 +
      <script src="https://2019.igem.org/Template:USTC-Software/js/addScrollBar?action=raw&ctype=text/javascript"></script>
  
−
<div class="column full_size">
+
      <!-- make content Menu fixed-->
−
<h1>Improve a Previous Part or Previous Project</h1>
+
      <script src="https://2019.igem.org/Template:USTC-Software/js/makeIndexFixed?action=raw&ctype=text/javascript"></script>
−
<p>For teams seeking to improve upon a previous part or project, you should document all of your work on this page. Please remember to include all part measurement and characterization data on the part's main page on the Registry. Please include a link to your improved part's Registry page on this page.</p>
+
  
−
<h3>Gold Medal Criterion #2</h3>
+
      <!--add background-->
−
<p><b>Improve a Previous Part - Standard Tracks:</b> Convince the judges that you have created a new BioBrick Part that has a functional improvement upon an existing BioBrick Part. You must perform experiments with both parts to demonstrate this improvement. Clearly document the quantitative experimental characterization data on the Part's Main Page on the Registry for both the existing and new parts (see the <a href="http://parts.igem.org/Help:Document_Parts">Registry Document Parts page</a> for instructions).
+
      <script src="https://2019.igem.org/Template:USTC-Software/js/addBackground?action=raw&ctype=text/javascript"></script>
−
<br><br>
+
−
Both the existing and new part must be <a href="http://parts.igem.org/Help:Standards/Assembly/RFC10">RFC10</a> or Type IIS compatible. The sequences of the new and existing parts must be different. The existing part must NOT be from your 2019 part number range and must be different from the part you used in Bronze #4. The new part you create must also be different from the new part documented in Silver #1. Please see the <a href="https://2019.igem.org/Measurement/Resources">Measurement Resources page</a> for more information about experimental characterization data.
+
−
<br><br>
+
−
<b>Improve a Previous Project - Special Tracks:</b> Improve the function of an existing iGEM project (that your current team did not originally create) and display your achievement on your wiki.</p>
+
  
 +
      <link href="https://2019.igem.org/Template:USTC-Software/css/pageContent?action=raw&ctype=text/css" rel="stylesheet">
  
−
</div>
+
      <!--add blockquote style-->
 +
      <link rel="stylesheet" href="https://2019.igem.org/Template:USTC-Software/css/blockquote?action=raw&ctype=text/css">
 +
      <!-- some updated css style -->
 +
      <!--<style>-->
 +
      <!--div.card p {margin: 20px;}-->
 +
      <!--div.card h2,h3,h4 {margin: 25px;}-->
 +
      <!--div.card h1 {margin-top: 30px;}-->
 +
      <!--div.card img {margin-left: 30px; margin-right:30px;}-->
 +
      <!--</style>-->
 +
</html>
  
−
 
+
{{USTC-Software/html/footer}}
−
 
+
−
</html>
+

Latest revision as of 13:23, 21 October 2019

Improve

Biobricks

At the time when we were trying to design our algorithms to handle the Biobricks Recommendation, we had an urgent need for a function that we can search Biobricks by specific reactions, metabolites, and genes. As a result, we began to communicate with some of the other iGEM-software teams, including UESTC-Software, the best software team last year, trying to get a perfect solution for this. However, we realized that none of the their projects could satisfy our needs. We spent lots of time and finally managed to design a new algorithm based on feature extraction used for searching Biobricks that can meet our needs.

Platform

Different from the other iGEM-Software computing projects, Alpha-Ant, for instance, did not have any convenient ways to share users' findings when using the software. Since collaboration in scientific research is quite important, we developed a simple sharing function based on web-link generating. Researchers with the links can easily edit on these models, favor them, and even give them a score.

Message Queues

Some of the iGEM-Software projects have computing tasks that will consume lots of computation resources during executing. Most of them handle both this kind of task and the services to users in the same server. The characteristics increase the risk of reducing the user experience and even breaking down the whole server.

Foresyn split our programs computing models from our website, and use message queues to send and receive information about our computation. A queue is a data structure that stores things waiting to be handled, and it obeys the "First Come, First Serve" principle. So, we can store our computing tasks in the queue, and response to users instantly about the progress of his tasks.

So the risk of breaking down does not exist anymore, and users can have a better experience.

References

  • Figure 1: http://www.netimperative.com/2019/04/facebook-sheds-light-on-news-feed-and-advertising-algorithm-secrets/
  • Figure 2: https://rawcliffe.co.uk/tax-news/emi-share-option-schemes/
  • Figure 3: https://www.cloudamqp.com/blog/2014-12-03-what-is-message-queuing.html