Difference between revisions of "Team:UPO-Sevilla/Collaborations"

Line 1: Line 1:
{{UPO-Sevilla}}
+
{{:Team:UPO-Sevilla/Template:CSS}}
<html>
+
{{:Team:UPO-Sevilla/Template:JAVA}}
<div class="column full_size">
+
<html>
  
 +
<style type="text/css">
 +
 +
* {
 +
margin:0px;
 +
padding:0px;
 +
}
 +
 +
#header {
 +
margin:auto;
 +
width:500px;
 +
font-family:Arial, Helvetica, sans-serif;
 +
}
 +
 +
ul, ol {
 +
list-style:none;
 +
}
 +
 +
.nav > li {
 +
float:left;
 +
}
 +
 +
.nav li a {
 +
background-color:#CEECF5;
 +
color:#000;
 +
text-decoration:none;
 +
padding:10px 12px;
 +
display:block;
 +
}
 +
 +
.nav li a:hover {
 +
background-color:#434343;
 +
}
 +
 +
.nav li ul {
 +
display:none;
 +
position:absolute;
 +
min-width:140px;
 +
}
 +
 +
.nav li:hover > ul {
 +
display:block;
 +
}
 +
 +
.nav li ul li {
 +
position:relative;
 +
}
 +
 +
.nav li ul li ul {
 +
right:-140px;
 +
top:0px;
 +
}
 +
 +
</style>
 +
  <!--HEADER ROW-->
 +
  <div id="header-row">
 +
    <div class="container" style="height:75px">
 +
      <div class="row" style="height:75px">
 +
              <!--LOGO-->
 +
              <div class="span3"><a class="brand" href="#"><img src="https://static.igem.org/mediawiki/2016/9/94/T--UPO-Sevilla--upoescudo.jpg" width="200" height="400"></a></div>
 +
              <!-- /LOGO -->
  
<p>
+
            <!-- MAIN NAVIGATION -->
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.
+
              <div class="span9">
</p>
+
                <div class="navbar  pull-right" style="font-size:80%">
</div>
+
                  <div class="navbar-inner">
 +
                    <a data-target=".navbar-responsive-collapse" data-toggle="collapse" class="btn btn-navbar"><span class="icon-bar"></span><span class="icon-bar"></span><span class="icon-bar"></span></a>
 +
                    <div class="nav-collapse collapse navbar-responsive-collapse">
 +
                    <ul class="nav">
 +
                        <li><a href="https://2016.igem.org/Team:UPO-Sevilla">Home</a></li>
 +
 +
<li class="dropdown">
 +
                          <a class="dropdown-toggle" data-toggle="dropdown">Team<b class="caret"></b></a>
 +
                            <ul class="dropdown-menu">
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Team">Members</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Attributions">Attributions</a></li>
 +
                            </ul>
 +
                        </li>
 +
 +
<li class="dropdown">
 +
                          <a class="dropdown-toggle" data-toggle="dropdown">Project<b class="caret"></b></a>
 +
                            <ul class="dropdown-menu">
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Description">Description</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Design">Design</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Proof">Proof of Concept</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Demonstrate">Demonstrate</a></li>
 +
                            </ul>
 +
                        </li>
 +
                       
 +
                        <li class="dropdown">
 +
                          <a class="dropdown-toggle" data-toggle="dropdown">Parts<b class="caret"></b></a>
 +
                            <ul class="dropdown-menu">
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Basic_Part">Basic Parts</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Composite_Part">Composite Parts</a></li>
 +
  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Part_Collection">Part Collection</a></li>
 +
                            </ul>
 +
                        </li>
  
<div class="column half_size">
+
                        <li class="dropdown">
 +
                          <a class="dropdown-toggle" data-toggle="dropdown">Wet Lab<b class="caret"></b></a>
 +
                            <ul class="dropdown-menu">
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Protocols">Protocols</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Notebook">Notebook</a></li>
 +
  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Safety">Safety</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Results">Results</a></li>
 +
                            </ul>
 +
                        </li>
  
<h4> Which other teams can we work with? </h4>
+
                        <li class="dropdown">
<p>  
+
                          <a class="dropdown-toggle" data-toggle="dropdown">Dry Lab<b class="caret"></b></a>
You can work with any other team in the competition, including software, hardware, high school and other tracks. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.
+
                            <ul class="dropdown-menu">
</p>
+
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Software">Software</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Model">Modeling</a></li>
 +
                            </ul>
 +
                        </li>
 +
 +
                        <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Collaborations">Collaborations</a></li>
 +
 +
<li class="dropdown">
 +
                          <a class="dropdown-toggle" data-toggle="dropdown">Human Practices<b class="caret"></b></a>
 +
                            <ul class="dropdown-menu">
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Integrated_Practices">Integrated Practices</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/HP/Silver">HP Silver</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/HP/Gold">HP Gold</a></li>
 +
                                  <li><a href="https://2016.igem.org/Team:UPO-Sevilla/Engagement">Engagement</a></li>
  
<p>
+
                            </ul>
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.
+
                        </li>                             
</p>
+
                    </ul>
 +
                  </div>
  
</div>
+
                  </div>
 +
                </div>
 +
              </div>
 +
            <!-- MAIN NAVIGATION --> 
 +
      </div>
 +
    </div>
 +
  </div>
  
 +
<!-- /HEADER ROW -->
 +
<div class="container">
  
 +
<!--PAGE TITLE-->
  
<div class="column half_size">
+
<div class="row">
<p>
+
<div class="span12">
Here are some suggestions for projects you could work on with other teams:
+
<div class="page-header">
</p>
+
<h1 style="text-align:center">
 +
COLLABORATIONS
 +
</h1>
 +
</div>
 +
</div>
 +
</div>
  
<ul>
+
<p style="font-size:15px;margin-bottom:10px">UPO-Sevilla, UPF-CRG-Barcelona and Valencia_UPV teams met up this year to share their projects. From that point on, and on-going active communication has continued. As a result, UPO-Sevilla and UPF-CGR-Barcelona teams found that they both were working with metabolic pathway modeling. Particularly, assessment of metabolite concentrations in different biochemical routes were necessary.</p>
<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 simulating 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>
+
  
 +
<p style="font-size:15px;margin-bottom:10px">And so, it was time for the corresponding dry labs to cooperate. It turned out that both softwares were actually very similar, although UPO-Sevilla’s software assumed the first metabolite in the pathway to be a “source” and therefore constant in concentration. This is justified by the need to model primarily assimilation of a constant source of glycerol by <i>Pseudomonas putida</i>.</p>
  
 +
<p style="font-size:15px;margin-bottom:10px">At the same time, there was a consensus between the groups to specialize in the format of the computer applications. UPF-CGR-Barcelona team opted for a more user-friendly approach (“Polyenzime”), displaying a graphical interface. This way, they facilitate computer analysis of biochemical pathways even for non-computer experts, and this constitutes an excellent contribution in the field. Then, UPO-Sevilla team worked to orient its metabolic pathway modeling software to advanced users. That is, researchers interested in making an intensive use of the program, or developers pursuing implementing the software as a module for their own programs. For this goal, all of the input parameters and output results in the application are set in the form of text files.</p>
 +
 +
<img src="">
 +
 +
<!--Footer
 +
==========================-->
 +
 +
<footer>
 +
    <div class="container">
 +
      <div class="row">
 +
        <div class="span6"><br>
 +
        </div>
 +
        <div class="span6">
 +
            <div class="social pull-right">
 +
 +
<a href="https://www.youtube.com/channel/UCXUAle_ywH8F127dWBYrhgw" target="_blank" title="Youtube official page"><img src="https://static.igem.org/mediawiki/2016/a/ac/T--UPO-Sevilla--youtube.jpg" width="60" style="height:50px"</a>
 +
 +
<a href="https://www.facebook.com/profile.php?id=100006118518232&fref=ts" target="_blank" title="Facebook official page"><img src="https://static.igem.org/mediawiki/igem.org/thumb/8/8b/FaceBook-icon.png/120px-FaceBook-icon.png" width="60" height="60"></a>
 +
 +
<a href=https://twitter.com/iGEM_UPO target="_blank" title="Twitter official page"><img src="https://static.igem.org/mediawiki/igem.org/thumb/1/1a/Twitter_logo.png/120px-Twitter_logo.png" width="60" height="60"></a>
 +
 +
<a href="https://www.instagram.com/igemupo/" target="_blank" title="Instagram official page"><img src="https://static.igem.org/mediawiki/2016/thumb/f/f7/Instagram.jpeg/120px-Instagram.jpeg.png" width="60" height="60"></a>
 +
             
 +
            </div>
 +
        </div>
 +
      </div>
 +
    </div>
 +
</footer>
 +
 +
<!--/.Footer-->
 +
 +
  </body>
 
</html>
 
</html>

Revision as of 17:45, 15 October 2016

UPO-Sevilla, UPF-CRG-Barcelona and Valencia_UPV teams met up this year to share their projects. From that point on, and on-going active communication has continued. As a result, UPO-Sevilla and UPF-CGR-Barcelona teams found that they both were working with metabolic pathway modeling. Particularly, assessment of metabolite concentrations in different biochemical routes were necessary.

And so, it was time for the corresponding dry labs to cooperate. It turned out that both softwares were actually very similar, although UPO-Sevilla’s software assumed the first metabolite in the pathway to be a “source” and therefore constant in concentration. This is justified by the need to model primarily assimilation of a constant source of glycerol by Pseudomonas putida.

At the same time, there was a consensus between the groups to specialize in the format of the computer applications. UPF-CGR-Barcelona team opted for a more user-friendly approach (“Polyenzime”), displaying a graphical interface. This way, they facilitate computer analysis of biochemical pathways even for non-computer experts, and this constitutes an excellent contribution in the field. Then, UPO-Sevilla team worked to orient its metabolic pathway modeling software to advanced users. That is, researchers interested in making an intensive use of the program, or developers pursuing implementing the software as a module for their own programs. For this goal, all of the input parameters and output results in the application are set in the form of text files.