Difference between revisions of "Team:Vanderbilt/Collaborations"

Line 1: Line 1:
{{Team:Vanderbilt/css/assets.css}}
+
{{Vanderbilt}}
{{Team:Vanderbilt/css/style.css}}
+
{{Team:Vanderbilt/js/jquery.js}}
+
{{Team:Vanderbilt/js/assets.js}}
+
{{Team:Vanderbilt/js/scripts.js}}
+
{{Team:Vanderbilt/header}}
+
<html>
+
<style>
+
  
#sideMenu, #top_title {display:none;}
+
<h3> Inter-university Collaborations </h3>
body {background-color:white; }
+
#content { padding:0px; width:100%; margin-top: -125px; margin-left:0px;}
+
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
+
</style>
+
     
+
     
+
          <section class="experience bg-midnight-blue">
+
            <div class="container">
+
                <div class="row">
+
                    <div class="col-sm-10">
+
                        <h3>Collaborations</h3>
+
<b> Inter-university Collaborations </b>
+
 
<p> Our team was fortunate to have multiple productive collaborations with other iGEM teams from around the world. First, we volunteered to test software developed by the University College of London’s iGEM team for designing gene circuits. We shared our experience using their software and suggested several changes to improve it versitility. </p>
 
<p> Our team was fortunate to have multiple productive collaborations with other iGEM teams from around the world. First, we volunteered to test software developed by the University College of London’s iGEM team for designing gene circuits. We shared our experience using their software and suggested several changes to improve it versitility. </p>
 
<p> We were also proud to help mentor a new iGEM team. Rice University’s iGEM team was interested in incorporating software into their project, but to do so they needed a stronger background in coding. Since our team has a history of integrating complex software with our projects, notably for this year’s project and last year’s, we asked our experienced members to lend their expertise. We were in contact with their team and gave advice on software.  </p>
 
<p> We were also proud to help mentor a new iGEM team. Rice University’s iGEM team was interested in incorporating software into their project, but to do so they needed a stronger background in coding. Since our team has a history of integrating complex software with our projects, notably for this year’s project and last year’s, we asked our experienced members to lend their expertise. We were in contact with their team and gave advice on software.  </p>
Line 26: Line 7:
 
<p>Because the University of Virginia’s project was centered on the idea of biocontainment which is one of the applications that prompted our own project, we engaged with their team to look at current attitudes and policies toward biocontainment. Our team discussed a series of survey responses and provided the University of Virginia’ team with examples of applying biocontainment in systems that use parts from our two projects.</p>
 
<p>Because the University of Virginia’s project was centered on the idea of biocontainment which is one of the applications that prompted our own project, we engaged with their team to look at current attitudes and policies toward biocontainment. Our team discussed a series of survey responses and provided the University of Virginia’ team with examples of applying biocontainment in systems that use parts from our two projects.</p>
 
<p>Lastly, we gave feedback to Paris-Saclay’s iGEM team for their human practices work on Responsible Research and Innovation through a series of responses that we wrote about our own interpretation of those principles and their role in our project work.</p>
 
<p>Lastly, we gave feedback to Paris-Saclay’s iGEM team for their human practices work on Responsible Research and Innovation through a series of responses that we wrote about our own interpretation of those principles and their role in our project work.</p>
</html>
 

Revision as of 06:25, 27 November 2016

Inter-university Collaborations

Our team was fortunate to have multiple productive collaborations with other iGEM teams from around the world. First, we volunteered to test software developed by the University College of London’s iGEM team for designing gene circuits. We shared our experience using their software and suggested several changes to improve it versitility.

We were also proud to help mentor a new iGEM team. Rice University’s iGEM team was interested in incorporating software into their project, but to do so they needed a stronger background in coding. Since our team has a history of integrating complex software with our projects, notably for this year’s project and last year’s, we asked our experienced members to lend their expertise. We were in contact with their team and gave advice on software.

Because the University of Virginia’s project was centered on the idea of biocontainment which is one of the applications that prompted our own project, we engaged with their team to look at current attitudes and policies toward biocontainment. Our team discussed a series of survey responses and provided the University of Virginia’ team with examples of applying biocontainment in systems that use parts from our two projects.

Because the University of Virginia’s project was centered on the idea of biocontainment which is one of the applications that prompted our own project, we engaged with their team to look at current attitudes and policies toward biocontainment. Our team discussed a series of survey responses and provided the University of Virginia’ team with examples of applying biocontainment in systems that use parts from our two projects.

Lastly, we gave feedback to Paris-Saclay’s iGEM team for their human practices work on Responsible Research and Innovation through a series of responses that we wrote about our own interpretation of those principles and their role in our project work.