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

Line 1: Line 1:
−
{{USTC-Software}}
+
{{USTC-Software/html/header}}
 
<html>
 
<html>
  
 +
<!--对应链接<li><a href="https://2019.igem.org/Team:USTC-Software/Collaborations">Collaborations</a></li>-->
 +
<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>
 +
<script src="https://2019.igem.org/common/MathJax-2.5-latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
  
 +
<div class="autoMenu2" id="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">Demonstrate</h1>
 +
          <h3>Let's Foresee</h3>
 +
          <div class="passage">
 +
            This year, our team design a software project that can foresee. Believe it or not, just click and see our
 +
            project Foresyn: Making Reliable Customized Flux Analysis With Ease.
 +
            <br>
 +
            <div class="psgImg">
 +
              <video controls height="480" width="760">
 +
                <source src="../../File/T--USTC-Software--educational_video.mp4" type="video/mp4">
 +
              </video>
 +
            </div>
 +
          </div>
 +
          <h3>Feedback</h3>
 +
          <div class="passage">
 +
            <div class="notepaper">
 +
              <figure class="quote">
 +
                <blockquote class="curly-quotes">
 +
                  Your project has a very friendly UI, the web design is clear, and the data content is abundant. The
 +
                  project makes great integration between biobricks of iGEM and FBA analysis, so it’s convenient to make
 +
                  better research of the metabolic flux. But we find some contents are not so friendly to users.
 +
                  First, the user should enter a json file with metabolite and coefficient to create a reaction.
 +
                  However, it’s unfriendly for a regular user to create json files. We have an idea that user can enter
 +
                  the chemical equations and the frontend changes them into json files automatically and sends to the
 +
                  backend.
 +
                  Besides, users still need to enter the model id manually. Considering there are plenty of models in
 +
                  your well-integrated database, it will be more convenient if they can choose from the known models.
 +
                </blockquote>
 +
                <figcaption class="quote-by">— SJTU-Software 2019</figcaption>
 +
              </figure>
 +
            </div>
 +
            <br>
 +
            <div class="notepaper">
 +
              <figure class="quote">
 +
                <blockquote class="curly-quotes">
 +
                  Your work is terrific and straight hit the point. We are concerned about such troublesome issues, and
 +
                  some of our teammates usually complain about doing experiments that cost so much time. The software
 +
                  just fit our need. Meanwhile, it is elementary to use and user-friendly. We like to use it, but there
 +
                  are still some insufficient parts. For example, we are sometimes waiting for a bit longer to get the
 +
                  result.
 +
                </blockquote>
 +
                <figcaption class="quote-by">— USTC 2019</figcaption>
 +
              </figure>
 +
            </div>
 +
          </div>
  
  
  
  
 +
        </div>
 +
      </div>
 +
    </div>
 +
  </div>
 +
</div>
  
−
<div class="column full_size">
+
<!--autoMenu css and js files, generate Menu of each article-->
−
<h1>Demonstrate</h1>
+
<!--<link href="https://2019.igem.org/Template:USTC-Software/css/autoMenu?action=raw&ctype=text/css" rel="stylesheet">-->
−
<h3>Gold Medal Criterion #4</h3>
+
<!--<script src="https://2019.igem.org/Template:USTC-Software/js/autoMenu?action=raw&ctype=text/javascript"></script>-->
  
−
<p>
+
<!--autoMenu css and js files, generate Menu of each article-->
−
Teams that can show their system working under real world conditions are usually good at impressing the judges in iGEM. To achieve gold medal criterion #4, convince the judges that your engineered system works.
+
<link href="https://2019.igem.org/Template:USTC-Software/css/autoMenu2?action=raw&ctype=text/css" rel="stylesheet">
−
<br><br>
+
<script src="https://2019.igem.org/Template:USTC-Software/js/autoMenu2?action=raw&ctype=text/javascript"></script>
−
Your engineered system has to work under realistic conditions. Your system must comply with all <a href="https://2019.igem.org/Safety/Rules">rules</a> and <a href="https://2019.igem.org/Safety/Policies">policies</a> approved by the iGEM Safety Committee. Your system can derive from or make functional a previous iGEM project by your team or by another team. For multi-component projects, the judges may consider the function of individual components.
+
  
−
</p>
+
<!--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>
  
−
<p>
+
<!-- make content Menu fixed-->
−
To be eligible for this award, you must add clear documentation to this page and delete the alert box at the top of this page.
+
<script src="https://2019.igem.org/Template:USTC-Software/js/makeIndexFixed?action=raw&ctype=text/javascript"></script>
−
</p>
+
  
−
<p>
+
<!--add background-->
−
Please see the <a href="https://2019.igem.org/Judging/Medals">2019 Medals Page</a> for more information.
+
<script src="https://2019.igem.org/Template:USTC-Software/js/addBackground?action=raw&ctype=text/javascript"></script>
−
</p>
+
  
 +
<link href="https://2019.igem.org/Template:USTC-Software/css/pageContent?action=raw&ctype=text/css" rel="stylesheet">
  
−
 
+
<!--add figure <index>-->
−
</div>
+
<script src="https://2019.igem.org/Template:USTC-Software/js/insertNumForPics?action=raw&ctype=text/javascript"></script>
 +
<link href="https://2019.igem.org/Template:USTC-Software/css/blockquote?action=raw&ctype=text/css" rel="stylesheet">
  
  
Line 36: Line 106:
  
 
</html>
 
</html>
 +
{{USTC-Software/html/footer}}

Revision as of 02:15, 22 October 2019

Demonstrate

Let's Foresee

This year, our team design a software project that can foresee. Believe it or not, just click and see our project Foresyn: Making Reliable Customized Flux Analysis With Ease.

Feedback

Your project has a very friendly UI, the web design is clear, and the data content is abundant. The project makes great integration between biobricks of iGEM and FBA analysis, so it’s convenient to make better research of the metabolic flux. But we find some contents are not so friendly to users. First, the user should enter a json file with metabolite and coefficient to create a reaction. However, it’s unfriendly for a regular user to create json files. We have an idea that user can enter the chemical equations and the frontend changes them into json files automatically and sends to the backend. Besides, users still need to enter the model id manually. Considering there are plenty of models in your well-integrated database, it will be more convenient if they can choose from the known models.
— SJTU-Software 2019

Your work is terrific and straight hit the point. We are concerned about such troublesome issues, and some of our teammates usually complain about doing experiments that cost so much time. The software just fit our need. Meanwhile, it is elementary to use and user-friendly. We like to use it, but there are still some insufficient parts. For example, we are sometimes waiting for a bit longer to get the result.
— USTC 2019