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

(Prototype team page)
 
 
(26 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
{{USTC-Software}}
+
{{ USTC-Software/html/header }}
−
<html>
+
  
  
 +
<html>
  
−
<div class="column full_size judges-will-not-evaluate">
+
<link href="https://2019.igem.org/Template:USTC-Software/css/default?action=raw&ctype=text/css" rel="stylesheet"
−
<h3>★  ALERT! </h3>
+
      type="text/css"/>
−
<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>
+
<link href="https://2019.igem.org/Template:USTC-Software/css/bootstrap?action=raw&ctype=text/css" rel="stylesheet"
−
<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>
+
      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 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">Collaborations</h1>
 +
          <h3>UESTC</h3>
 +
          <div class="passage">
 +
            Since our project is based on the database, our project's first step is to collect data
 +
            from multiple databases. From the very beginning, we took a look on the description of 2019 UESTC-Software's project.
 +
            Luckily, we found that the UESTC team had already done the work of collecting data from various databases to
 +
            build their project, BioMaster 2.0. <br>
 +
            <div class="text-center psgImg">
 +
              <img alt="" src="https://static.igem.org/mediawiki/2019/archive/a/ac/20191020164953%21T--UESTC-software--advantage_10.png">
 +
              <p>Figure 1: UESTC biomaster</p>
 +
            </div>
 +
            Our work is built on the database, and UESTC-Software does a great job on the database, so we proposed collaboration with them. From their project, we predicted some prominent promoters and matched the resulting promoters to our corresponding responses, and the resulting responses would be based on our recommended algorithm to analyze metabolic balance in our model. Their results predict great output on our model, and we link the results to their database to validate and refine their projects.
 +
            <div class="text-center psgImg">
 +
              <img src="https://static.igem.org/mediawiki/2019/8/8a/T--USTC-Software--hp_meetinccic.jpg" alt="">
 +
              <p>Figure 2: Communicating with UESTC</p>
 +
            </div>
 +
            Through the way of developing the project, we also contributed our biobricks to their project which they might need. Their project was updated as well. During the process of our communication, both of our project were upgraded. This kind of cooperation is profound and coordinated in software engineering, which significantly enhances the user experience.
 +
          </div>
 +
          <h3>SYSU</h3>
 +
          <div class="passage">
 +
            In June, we visited SYSU and had a meeting with their iGEM team members. We communicated with our team projects and gave helpful suggestions to each other.  We stated that our work to optimize our database, which was at a grand scale and then linking the output to FBA’s input. However, the students and professor from SYSU pointed out that our idea about optimizing massive databases was not targeted for Synthetic Biology. There was a bias that our work done to optimize the databases will distract us from designing FBA workflow and its efficiency.
 +
            <div class="psgImg text-center">
 +
              <img alt="" src="https://static.igem.org/mediawiki/2019/7/74/T--USTC-Software--colla_zhongshan.jpg">
 +
              <p>Figure 3: Meeting between SYSU team</p>
 +
            </div>
 +
            Mutually, we listened to their project carefully, asked several questions, and had an overall understanding. Knowing that their work would relate to the calculation of Metabolic equilibrium analysis, we recommended our project, and they said they would be glad to use our software.
 +
          </div>
 +
          <h3>Tongji</h3>
 +
          <div class="passage">
 +
              The software should get rid of the virus just as the virus will quickly destroy an organism. But besides the attacking virus, we software team still must complete the project without any vulnerability existed. It’s necessary that we software teams need to test the program with each other. When our team’s elite programmer Keyu Tao helped test the code of Team Tongji, he found a significant vulnerability. Entering some specific characters within some particular interface search box can conduct SQL injection. After our warning and detailed document, they improved their codes and fixed the bug.
 +
          </div>
 +
          <h3>SJSU</h3>
 +
          <div class="passage">
 +
            In June, we visited SYSU and had a meeting with their iGEM team members. We communicated with our team projects and gave helpful suggestions to each other.  We stated that our work to optimize our database, which was at a grand scale and then linking the output to FBA’s input. However, the students and professor from SYSU pointed out that our idea about optimizing massive databases was not targeted for Synthetic Biology. There was a bias that our work done to optimize the databases will distract us from designing FBA workflow and its efficiency.
 +
            <div class="psgImg text-center">
 +
              <img alt="" src="https://static.igem.org/mediawiki/2019/a/a7/T--USTC-Software--colla_feedback.png">
 +
              <p>Figure 4: Feedbacks from SJSU after first test period</p>
 +
            </div>
 +
            After the first period of development, we cooperated with SJSU to test projects for each other. We gained much useful advice, with which we improved our projects. They said we had a very friendly UI; our web design was concise, and the data content was abundant. Our project made high integration between biobricks of iGEM and FBA analysis, so it’s convenient to make better research of the metabolic flux. Also, they gave us some feedback that we still had some defects, and gave us some advice. First, the user should enter a JSON file with metabolite and coefficient to create a reaction. However, it’s unfriendly for users to create JSON files manually. Besides, considering there are plenty of models in our well-integrated database, people don’t need to enter the model id manually but can choose from the known models.          </div>
 +
<h3>USTC</h3>
 +
          <div class="passage">
 +
            The USTC team is the other team of our school, which focuses on biology, and most of their members majored
 +
            in biology. Therefore, we communicate a lot throughout the whole project.
 +
            <br>
 +
            <div class="psgImg">
 +
              <img alt="" src="https://static.igem.org/mediawiki/2019/d/d4/T--USTC-Software--colla_ustc1.jpg">
 +
              <p>Figure 5: Having a meeting with USTC team</p>
 +
            </div>
 +
            Our team, together with the USTC team, has conducted a 4-day experimental training in the lab, which aims at
 +
            helping more students to use our tools effectively and efficiently. Although most of our software team
 +
            members majored in computer science, we know more clearly about how the basic experiment is conducted and
 +
            what we can do to help synthetic biology researchers to improve their working efficiency through the process
 +
            of doing biology experiments.
 +
            <div class="psgImg">
 +
              <img alt="" src="https://static.igem.org/mediawiki/2019/5/52/T--USTC-Software--colla_exp.png">
 +
              <p>Figure 6: Conducting experimental training</p>
 +
            </div>
 +
            <br>
 +
            What's more, Pengcen Jiang, a member form the USTC team, has helped us how to use cobra tools and gave us a
 +
            lot of suggestions on how to convert our data into practical meaning.
 +
            <br>
 +
            <br>
 +
            After having built our project, we invite the USTC team to test our tools. They give us a lot of advice on
 +
            how to upgrade our project. Thanks for their feedback.
 +
          </div>
 +
          <h3>SDU</h3>
 +
          <div class="passage">We also helped a girl from the SDU who had trouble in creating animation by software
 +
            during the time when we attended the CCIC meeting.
 +
            <br>
 +
          </div>
 +
         
 +
        </div>
 +
      </div>
 +
    </div>
 +
  </div>
 
</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>Collaborations</h1>
+
<script src="https://2019.igem.org/Template:USTC-Software/js/makeIndexFixed?action=raw&ctype=text/javascript"></script>
  
−
<p>
+
<!--add background-->
−
Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.
+
<script src="https://2019.igem.org/Template:USTC-Software/js/addBackground?action=raw&ctype=text/javascript"></script>
−
</p>
+
  
−
<h3>Silver Medal Criterion #2</h3>
+
<link href="https://2019.igem.org/Template:USTC-Software/css/pageContent?action=raw&ctype=text/css" rel="stylesheet">
−
<p>
+
−
Document your collaboration(s) clearly on this page to compete for the silver medal criterion #2 on collaboration. Please see the <a href="https://2019.igem.org/Judging/Medals">2019 Medals Page</a> for more information.
+
−
</p>
+
−
</div>
+
  
−
<div class="column two_thirds_size">
+
<!-- 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>-->
  
−
<h4> Which other teams can we work with? </h4>
+
</html>
−
<p>
+
−
You can work with any other team in the competition, including standard, software, open, and high school track teams. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.
+
−
</p>
+
  
−
<p>
+
{{USTC-Software/html/footer}}
−
In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
+
−
</p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
<div class="column third_size">
+
−
<p>
+
−
Here are some suggestions for projects you could work on with other teams:
+
−
</p>
+
−
 
+
−
<ul>
+
−
<li> Improve the function of another team's BioBrick Part or Device</li>
+
−
<li> Characterize another team's part </li>
+
−
<li> Debug a construct </li>
+
−
<li> Model or simulate another team's system </li>
+
−
<li> Test another team's software</li>
+
−
<li> Help build and test another team's hardware project</li>
+
−
<li> Mentor a high-school team</li>
+
−
</ul>
+
−
</div>
+
−
 
+
−
 
+
−
</html>
+

Latest revision as of 02:14, 22 October 2019


Collaborations

UESTC

Since our project is based on the database, our project's first step is to collect data from multiple databases. From the very beginning, we took a look on the description of 2019 UESTC-Software's project. Luckily, we found that the UESTC team had already done the work of collecting data from various databases to build their project, BioMaster 2.0.

Figure 1: UESTC biomaster

Our work is built on the database, and UESTC-Software does a great job on the database, so we proposed collaboration with them. From their project, we predicted some prominent promoters and matched the resulting promoters to our corresponding responses, and the resulting responses would be based on our recommended algorithm to analyze metabolic balance in our model. Their results predict great output on our model, and we link the results to their database to validate and refine their projects.

Figure 2: Communicating with UESTC

Through the way of developing the project, we also contributed our biobricks to their project which they might need. Their project was updated as well. During the process of our communication, both of our project were upgraded. This kind of cooperation is profound and coordinated in software engineering, which significantly enhances the user experience.

SYSU

In June, we visited SYSU and had a meeting with their iGEM team members. We communicated with our team projects and gave helpful suggestions to each other. We stated that our work to optimize our database, which was at a grand scale and then linking the output to FBA’s input. However, the students and professor from SYSU pointed out that our idea about optimizing massive databases was not targeted for Synthetic Biology. There was a bias that our work done to optimize the databases will distract us from designing FBA workflow and its efficiency.

Figure 3: Meeting between SYSU team

Mutually, we listened to their project carefully, asked several questions, and had an overall understanding. Knowing that their work would relate to the calculation of Metabolic equilibrium analysis, we recommended our project, and they said they would be glad to use our software.

Tongji

The software should get rid of the virus just as the virus will quickly destroy an organism. But besides the attacking virus, we software team still must complete the project without any vulnerability existed. It’s necessary that we software teams need to test the program with each other. When our team’s elite programmer Keyu Tao helped test the code of Team Tongji, he found a significant vulnerability. Entering some specific characters within some particular interface search box can conduct SQL injection. After our warning and detailed document, they improved their codes and fixed the bug.

SJSU

In June, we visited SYSU and had a meeting with their iGEM team members. We communicated with our team projects and gave helpful suggestions to each other. We stated that our work to optimize our database, which was at a grand scale and then linking the output to FBA’s input. However, the students and professor from SYSU pointed out that our idea about optimizing massive databases was not targeted for Synthetic Biology. There was a bias that our work done to optimize the databases will distract us from designing FBA workflow and its efficiency.

Figure 4: Feedbacks from SJSU after first test period

After the first period of development, we cooperated with SJSU to test projects for each other. We gained much useful advice, with which we improved our projects. They said we had a very friendly UI; our web design was concise, and the data content was abundant. Our project made high integration between biobricks of iGEM and FBA analysis, so it’s convenient to make better research of the metabolic flux. Also, they gave us some feedback that we still had some defects, and gave us some advice. First, the user should enter a JSON file with metabolite and coefficient to create a reaction. However, it’s unfriendly for users to create JSON files manually. Besides, considering there are plenty of models in our well-integrated database, people don’t need to enter the model id manually but can choose from the known models.

USTC

The USTC team is the other team of our school, which focuses on biology, and most of their members majored in biology. Therefore, we communicate a lot throughout the whole project.

Figure 5: Having a meeting with USTC team

Our team, together with the USTC team, has conducted a 4-day experimental training in the lab, which aims at helping more students to use our tools effectively and efficiently. Although most of our software team members majored in computer science, we know more clearly about how the basic experiment is conducted and what we can do to help synthetic biology researchers to improve their working efficiency through the process of doing biology experiments.

Figure 6: Conducting experimental training


What's more, Pengcen Jiang, a member form the USTC team, has helped us how to use cobra tools and gave us a lot of suggestions on how to convert our data into practical meaning.

After having built our project, we invite the USTC team to test our tools. They give us a lot of advice on how to upgrade our project. Thanks for their feedback.

SDU

We also helped a girl from the SDU who had trouble in creating animation by software during the time when we attended the CCIC meeting.