Difference between revisions of "Team:iTesla-SoundBio/Collaborations"

 
(71 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{iTesla-SoundBio}}
 
{{iTesla-SoundBio}}
 
<html>
 
<html>
<html>
+
 
<style> /*STYLE FOR ALL PAGES*/
+
<style>
body { background: #9cb8b3; }
+
body {
{ /* Replaces "root" div -- filtered out all iGEM wiki settings (see first <script>)*/
+
     font-family: "Lato", sans-serif;
     width: 100%;
+
 
    height: 100vh;
+
    background-size:cover;
+
    background-repeat:no-repeat;
+
    /*background-image:url("https://raddinteractive.com/wp-content/uploads/Chalkboard-background-e1463542024446.jpg");
+
    */
+
    background-color: whitesmoke;
+
    margin: 0px;
+
    padding: 0px;
+
}
+
/* Style the top navigation bar */
+
.topnav {
+
    overflow: hidden;
+
    background-color: #333;
+
    font-family: Bahnschrift;
+
    font-size: 15px;
+
    width: 100%;
+
    margin-top: -10px;
+
}
+
/* Style the topnav links */
+
.topnav a {
+
    float: right;
+
    display: block;
+
color: #f2f2f2;
+
    text-align: center;
+
    padding: 14px 16px;
+
    text-decoration: none;
+
/*for transitions when hovering*/
+
-o-transition: color .2s ease-out, background 1s ease-in;
+
-ms-transition: color .2s ease-out, background 1s ease-in;
+
-moz-transition: color .2s ease-out, background 1s ease-in;
+
-webkit-transition: color .2s ease-out, background 1s ease-in;
+
}
+
.topnav a img {
+
    height: 10%;
+
    width: 10%;
+
}
+
.topnav a.logo {
+
    float: left;
+
}
+
/* Change color on hover */
+
.topnav a:hover, .dropdown:hover .dropdown-button {
+
    background-color: #ddd;
+
    color: black;
+
   
+
}
+
.dropdown {
+
    float: right;
+
    overflow: hidden;
+
 
}
 
}
  
.dropdown .dropdown-button {
+
p {
    font-size: 16px;   
+
margin-left: 20px
    border: none;
+
    outline: none;
+
    color: white;
+
    padding: 14px 16px;
+
    background-color: inherit;
+
    font-family: inherit;
+
    margin: 0;
+
    cursor: pointer;
+
    /*for transitions when hovering*/
+
-o-transition: color .2s ease-out, background 1s ease-in;
+
-ms-transition: color .2s ease-out, background 1s ease-in;
+
-moz-transition: color .2s ease-out, background 1s ease-in;
+
-webkit-transition: color .2s ease-out, background 1s ease-in;
+
 
}
 
}
.dropdown-content {
+
.sidenav {
     /* opacity: 0; */
+
     height: 100%;
     display: none;
+
     width: 180px;
     position: absolute;
+
     position: fixed;
    background-color: whitesmoke;
+
    min-width: 160px;
+
    box-shadow: 0px 8px 16px 0px rgba(0,0,0,0.2);
+
 
     z-index: 1;
 
     z-index: 1;
 +
    top: 0;
 +
    left: 0;
 +
    background-color: #111;
 +
    overflow-x: hidden;
 +
    padding-top: 100px;
 
}
 
}
.dropdown-content a {
+
 
    float: none;
+
.sidenav a {
    color: black;
+
     padding-top: 5px 5px 5px 5px;
     padding: 12px 16px;
+
 
     text-decoration: none;
 
     text-decoration: none;
 +
    font-size: 20px;
 +
    color: #818181;
 
     display: block;
 
     display: block;
    text-align: left;
 
 
}
 
}
  
.dropdown-content a:hover {
+
.sidenav a:hover {
     background-color: white;
+
     color: #f1f1f1;
 
}
 
}
  
.dropdown:hover .dropdown-content {
+
.main {
     display: block;
+
     margin-left: 180px; /* Same as the width of the sidenav */
    /*
+
     padding: 0px 10px;
     opacity: 1;
+
     font-family: arial;  
     transition: all 1s ease;
+
     font-size: 20px;  
     -webkit-transition: all 1s ease;
+
     padding: 30px
     */
+
 
}
 
}
/* Base DIVs for whole website */
+
@media screen and (max-height: 450px) {
#root {
+
    .sidenav {padding-top: 15px;}
position: absolute;
+
    .sidenav a {font-size: 18px;}
font-size: 16px;
+
width: 100%;
+
height: auto;
+
margin: auto;
+
background-color: Whitesmoke;
+
 
}
 
}
#wrapper { /* Wraps all critical website content */
+
 
height: auto;
+
blockquote {
width: 90%;
+
     font-family: "Times New Roman", Times, serif;
background-color: white;
+
    font-size: 28px;
/*border-style: solid;
+
     color: darkblue;
border-width: 1px;
+
border-color: black;
+
border-radius: 10px;*/
+
margin: auto;
+
display: table;
+
}
+
/*Load special fonts*/
+
@font-face {
+
     font-family: CenturyGothic;
+
    src: url(https://static.igem.org/mediawiki/2018/b/b9/T--iTesla-SoundBio--CenturyGothic.ttf);
+
}
+
@font-face {
+
font-family: Ubuntu-L;
+
src: url(https://static.igem.org/mediawiki/2018/8/85/T--iTesla-SoundBio--Ubuntu-L.ttf);
+
}
+
/*text styles*/
+
#title {
+
  font-family: Ubuntu-L;
+
  font-size: 92px;
+
  padding: 20px 40px;
+
  text-align: center;
+
  text-transform: uppercase;
+
  text-rendering: optimizeLegibility;
+
}
+
/*shadow classes*/
+
.elegantshadow {
+
    color: #131313;
+
    /*background-color: #e7e5e4;*/
+
    letter-spacing: .15em;
+
    text-shadow:
+
      1px -1px 0 #767676,
+
      -1px 2px 1px #737272,
+
      -2px 4px 1px #767474,
+
      -3px 6px 1px #787777,
+
      -4px 8px 1px #7b7a7a,
+
      -5px 10px 1px #7f7d7d,
+
      -6px 12px 1px #828181,
+
      -7px 14px 1px #868585,
+
      -8px 16px 1px #8b8a89,
+
      -9px 18px 1px #8f8e8d,
+
      -10px 20px 1px #949392,
+
      -11px 22px 1px #999897,
+
      -12px 24px 1px #9e9c9c,
+
      -13px 26px 1px #a3a1a1,
+
      -14px 28px 1px #a8a6a6,
+
      -15px 30px 1px #adabab,
+
      -16px 32px 1px #b2b1b0,
+
      -17px 34px 1px #b7b6b5,
+
      -18px 36px 1px #bcbbba,
+
      -19px 38px 1px #c1bfbf,
+
      -20px 40px 1px #c6c4c4,
+
      -21px 42px 1px #cbc9c8,
+
      -22px 44px 1px #cfcdcd,
+
      -23px 46px 1px #d4d2d1,
+
      -24px 48px 1px #d8d6d5,
+
      -25px 50px 1px #dbdad9,
+
      -26px 52px 1px #dfdddc,
+
      -27px 54px 1px #e2e0df,
+
      -28px 56px 1px #e4e3e2;
+
  }
+
  .deepshadow {
+
     color: #e0dfdc;
+
    background-color: #333;
+
    letter-spacing: .1em;
+
    text-shadow:
+
      0 -1px 0 #fff,
+
      0 1px 0 #2e2e2e,
+
      0 2px 0 #2c2c2c,
+
      0 3px 0 #2a2a2a,
+
      0 4px 0 #282828,
+
      0 5px 0 #262626,
+
      0 6px 0 #242424,
+
      0 7px 0 #222,
+
      0 8px 0 #202020,
+
      0 9px 0 #1e1e1e,
+
      0 10px 0 #1c1c1c,
+
      0 11px 0 #1a1a1a,
+
      0 12px 0 #181818,
+
      0 13px 0 #161616,
+
      0 14px 0 #141414,
+
      0 15px 0 #121212,
+
      0 22px 30px rgba(0, 0, 0, 0.9);
+
  }
+
  .insetshadow {
+
    color: #202020;
+
    background-color: #2d2d2d;
+
    letter-spacing: .1em;
+
    text-shadow:
+
      -1px -1px 1px #111,
+
      2px 2px 1px #363636;
+
  }
+
  .retroshadow {
+
    color: #2c2c2c;
+
    background-color: #d5d5d5;
+
    letter-spacing: .05em;
+
    text-shadow:
+
      4px 4px 0px #d5d5d5,
+
      7px 7px 0px rgba(0, 0, 0, 0.2);
+
  }
+
/* Animation Transitions */
+
.imgFadeIn {
+
  -webkit-animation: appear 1s;
+
  animation: appear 1s;
+
  -webkit-animation-fill-mode: forwards;
+
  animation-fill-mode: forwards;
+
}
+
@-webkit-keyframes appear {
+
  0% { left: 500px; opacity: 0; }
+
  100% { left: 16px; opacity: 1;
+
 
}
 
}
  
@keyframes appear {
+
img {
  0% { left: 500px; opacity: 0; }
+
      float: right;
  100% { left: 16px; opacity: 1; } 
+
}
+
/* Style the footer */
+
.footer {
+
    background-color: #f1f1f1;
+
    padding: 10px;
+
    text-align: center;
+
    width: 100vw;
+
 
}
 
}
 
</style>
 
</style>
  
<style> <!-- Page Specific CSS -->
+
<body>
/*PAGE SPECIFIC CSS*/
+
<div id="wrapper">
/* Style the header */
+
<script>
.header {
+
     $("#title").text("Collaborations")
    background-color: #f1f1f1;
+
    padding: 30px;
+
    text-align: center;
+
    font-size: 28px;
+
    width: 95vw;
+
}
+
/* Create three equal columns that floats next to each other */
+
.column {
+
    float: left;
+
    height: 50%;
+
    width: 33.33%;
+
    padding: 0px
+
/* If padding is wanted, change the value of px*/
+
}
+
/* Clear floats after the columns */
+
.row:after {
+
    content: "";
+
    display: table;
+
    clear: both;
+
    width: 100vw;
+
}
+
 
+
/* Make the text over image*/
+
.container {
+
    position: relative;
+
    text-align: center;
+
    color: black
+
}
+
.container1 {
+
    position: relative;
+
    text-align: center;
+
    color: white
+
}
+
 
+
.centered {
+
    position: absolute;
+
    bottom: 8px;
+
    left: 50%;
+
    transform: translate(-50%, -50%);
+
    font-size:18px
+
}
+
</style>
+
<!-- The following reset code was given by William Kwok from the UW iGEM team -->
+
<!-- Add on-page javascript for destroying default iGEM CSS and adding a loading animation -->
+
<!-- I do it twice to run once so the page loading animation gets correct styling the first run -->
+
<!-- Second run is just to make sure everything gets ran -->
+
<script type="text/javascript">
+
     $('div#content').removeAttr('id').attr('id', 'contentBox');
+
    $('a#top').remove();
+
    $('div#top_title').remove();
+
    $('div#HQ_page').removeAttr('id');
+
    $('div.mw-body').removeAttr('class');
+
    $('div#mw-content-text').removeAttr('id');
+
    $('div#bodyContent').removeAttr('id');
+
    $('div.mw-content-ltr>p').addClass('meta');
+
    $('div.mw-content-ltr').removeAttr('class');
+
    document.getElementById("root").innerText = "Page loading...";
+
    $(document).ready(function () {
+
        $('div#content').removeAttr('id').attr('id', 'contentBox');
+
        $('a#top').remove();
+
        $('div#top_title').remove();
+
        $('div#HQ_page').removeAttr('id');
+
        $('div.mw-body').removeAttr('class');
+
        $('div#mw-content-text').removeAttr('id');
+
        $('div#bodyContent').removeAttr('id');
+
        $('div.mw-content-ltr>p').addClass('meta');
+
        $('div.mw-content-ltr').removeAttr('class');
+
    })
+
 
</script>
 
</script>
<body>
+
<h2 id="lesserTitle"> iTesla-SoundBio & Baltimore BioCrew</h2>
    <div class="topnav">
+
   
        <a class="logo" href="#"><img src="https://static.igem.org/mediawiki/2018/8/87/T--iTesla-SoundBio--teamlogo.png"></a>
+
<img src="https://static.igem.org/mediawiki/2018/f/fb/T--iTesla-SoundBio--newLogo.png" width="27%">
  
        <!-- Floats right hence in opposite order -->
+
<div id="" style="backround-color: teal">
        <a href="https://2018.igem.org/Team:iTesla-SoundBio/Project/Safety">Safety</a>
+
<u><h3 style="font-size: 30px">iGEM Guide for Community Laboratories</h3></u>
        <a href="https://2018.igem.org/Team:iTesla-SoundBio/Project/Interlab">InterLab</a>
+
<p style= "font-size: 20px;">
        <a href="https://2018.igem.org/Team:iTesla-SoundBio/team">Team</a>
+
This year, we collaborated with the Baltimore BioCrew, another high school iGEM team, to create an iGEM Guide for Community Laboratories that are interesting in starting a high school iGEM team. With the unique circumstances of being a high school team and working out of a community lab, we have had to surpass different challenges and situations that many teams may not have come across. We were also aware that many community labs around the world were interested in participating in iGEM, but were having difficulties to do so -- so by designing a guide, we hope to help these labs with some of the issues that they are facing, as they are ones that we have faced.  
        <div class="dropdown">
+
            <button class="dropdown-button">Human Practices</button>
+
            <div class="dropdown-content">
+
                  <a href="https://2018.igem.org/Team:iTesla-SoundBio/Outreach">Outreach</a>
+
                    <a href="https://2018.igem.org/Team:iTesla-SoundBio/Collaborations">Collaborations</a>
+
                <a href="https://2018.igem.org/Team:iTesla-SoundBio/Attributions">Attributions</a>
+
  
            </div>
+
</br></br>
        </div>
+
     
+
   
+
        </div>
+
    </div>
+
  
    <div id="wrapper">
+
To begin, and before we created our guide, we contacted community laboratories in many different countries to see what issues they had faced in trying to participate in iGEM. We reached out to around 29 community labs around the world, the email reading as follows:
        <h2 id="title" class="retroshadow">Collaborations</h2>
+
</p>
 
+
<!--
+
    <div class="row">
+
        <div class="column" style="background-color:#ccccff;"><div class= "container">
+
            <a href="https://2018.igem.org/Team:iTesla-SoundBio/labnotebook"><img src="https://static.igem.org/mediawiki/2018/c/c1/T--iTesla-Soundbio--writing1.jpg" alt= "labnotebook", width= 100%, height=400px></a>
+
  
        <div class="centered">LabNotebook</div>
+
</br>
        </div>
+
  
 +
<b><ol style= "font-size: 20px;">
 +
<li>Have you ever considered having an iGEM team? If so, what were the perceived barriers? (i.e. fundraising, finding students or mentors, etc)</li>
 +
<li>Would a report detailing our experiences in creating and maintaining an iGEM team be useful to you?</li>
 +
</ol></b>
  
        <div class="column" style="background-color:#bbb;"><div class= "container1">
+
</br></br>
         
+
        <div class="centered">Project Description</div>
+
        </div>
+
  
        <div class="column" style="background-color:#ccc;"><div class= "container">
+
<p style= "font-size: 20px;">
     
+
We were ecstatic to hear back from 11 community labs from around the world (BosLab, BioCurious, Bricobio, ReaGent, Ronin Genetics, The Open Science Network, DIY Bio Hong Kong, Victoria Makerspace, AbroBios, BioBlaze, and Bioscope). Many of them expressed struggles with: 
 +
</p>
  
        <div class="centered">Human Practices</div>
+
</br>
        </div>
+
  
    </div>
+
<b><ul style= "font-size: 20px; margin-left: 20px; list-style-type: disc;">
-->
+
<li>“Recruiting and finding high commitment amongst members”</li>
    </div>
+
<li>“Not knowing how [to] fundraise or raise money for a team”</li>
 +
<li>“Organizing a team”</li>
 +
<li>“Biology background knowledge”</li>
 +
</ul></b>
  
 +
<a href="https://static.igem.org/mediawiki/2018/9/96/T--iTesla-SoundBio--iGEM_Guide_for_Community_Laboratories_UPDATED.pdf" target="blank"><img src="https://static.igem.org/mediawiki/2018/8/81/T--iTesla-SoundBio--Guide.png" width="28.5%" style="float: left;"></a>
  
<div class="column full_size judges-will-not-evaluate">
+
<p style= "font-size: 20px;">
<h3>★  ALERT! </h3>
+
With their replies, we structured our guide to consist of 6 sections to best address some of the concerns that we had heard. These sections are:  
<p>This page is used by the judges to evaluate your team for the <a href="https://2018.igem.org/Judging/Medals">medal criterion</a> or <a href="https://2018.igem.org/Judging/Awards"> award listed below</a>. </p>
+
</p>
<p> Delete this box in order to be evaluated for this medal criterion and/or award. See more information at <a href="https://2018.igem.org/Judging/Pages_for_Awards"> Instructions for Pages for awards</a>.</p>
+
</div>
+
  
 +
</br>
  
<div class="clear"></div>
+
<b><p style= "font-size: 20px; margin-left: 70px">
 +
1. Recruiting </br>
 +
2. Communication & Tools</br>
 +
3. Leadership</br>
 +
4. Timeline/Scheduling</br>
 +
5. Protocols & Lab Notebooks</br>
 +
6. Fundraising</br>
 +
</p></b>
  
 +
</br> </br>
  
<div class="column full_size">
+
<p style= "font-size: 20px;">
<h1>Collaborations</h1>
+
In each section, we outlined some of our recommendations for new teams, some background from our teams’ experiences, and other alternative ideas and solutions that we had brainstormed.  As our experience with iGEM continues, we plan on adding more sections and we are striving to encourage more community laboratories to invite local high schoolers to compete in iGEM.
  
<p>
+
</br></br>
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.
+
For a live, and more updated version of our guide, check out this <a href="https://docs.google.com/document/d/1rmqtM9J1DPVhSCylAfuPao6wIaTCBS5ICnYcDnF1Wus/edit" target="blank">Google Doc</a>.  
 
</p>
 
</p>
  
<h3>Silver Medal Criterion #2</h3>
 
<p>
 
Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the <a href="https://2018.igem.org/Judging/Medals">2018 Medals Page</a> for more information.
 
</p>
 
 
</div>
 
</div>
  
<div class="column two_thirds_size">
+
</br>
 
+
<h2 id="lesserTitle">iTesla-SoundBio, Tacoma RAINMakers, & Team Washington</h2>
<h4> Which other teams can we work with? </h4>
+
<u><h3 style="font-size: 30px">Pacific Northwest iGEM Meetup hosted by the Washington iGEM team</h3></u>
<p>  
+
<p style= "font-size: 20px;">
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.
+
On August 18th and 19th iGEM teams from around Washington (Tacoma RAINMakers, Team Washington & iTesla-SoundBio) met up to share ideas, give feedback, and bond over our shared love for synthetic biology. This event gave us great opportunities to prepare for the jamboree and hear from people working in the biotech industry and academia.
 +
</br></br>
 +
We had the opportunity to meet with iGEM ambassadors, Holly Bowman and Amy Chen, about our project. Holly was a part of the 2017 Georgia State Team, whose project we decided to base our work off of. She described the setbacks her team had faced and gave us suggestions to improve our progress. The advice of the ambassadors gave us meaningful insight on the future steps we should take for wetlab, human practices, and beyond.
 +
After a mock jamboree poster session, practice presentations, and talks from our keynote speakers, we headed to Gasworks Park for an outreach event. There we got Seattle families involved in synthetic biology activities and talked about our iGEM project. All in all, the PNW iGEM Meetup was an awesome opportunity to prepare for the Giant Jamboree and gain a thorough understanding of the projects of other iGEM teams, as well as the work currently being done in the field of synthetic biology.
 
</p>
 
</p>
  
<p>
+
<h2 id="lesserTitle"> Mentorship with Team Washington</h2>
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 style= "font-size: 20px;"> This year we received help from the Washington iGEM team in terms of training and selecting presenters, human practices, basic wetlab procedure, and InterLab support. In terms of selecting presenters, Washington iGEM's Angel Wong and Andrew Hu critiqued each iTesla-SoundBio audition by giving feedback. Multiple members helped introduce new members to Benchling.com, pipette technique, and transformation procedure as well. They also kindly let us use their plate readers for the InterLab readings. </p>
</p>
+
  
</div>
+
<img src="https://static.igem.org/mediawiki/2018/3/3e/T--iTesla-SoundBio--Collaborations_Pictures.png" width="100%">
  
 
 
<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>
 
</div>
 
 
 
</body>
 
</body>
 
</html>
 
</html>

Latest revision as of 04:52, 17 October 2018

iTesla-SoundBio & Baltimore BioCrew

iGEM Guide for Community Laboratories

This year, we collaborated with the Baltimore BioCrew, another high school iGEM team, to create an iGEM Guide for Community Laboratories that are interesting in starting a high school iGEM team. With the unique circumstances of being a high school team and working out of a community lab, we have had to surpass different challenges and situations that many teams may not have come across. We were also aware that many community labs around the world were interested in participating in iGEM, but were having difficulties to do so -- so by designing a guide, we hope to help these labs with some of the issues that they are facing, as they are ones that we have faced.

To begin, and before we created our guide, we contacted community laboratories in many different countries to see what issues they had faced in trying to participate in iGEM. We reached out to around 29 community labs around the world, the email reading as follows:


  1. Have you ever considered having an iGEM team? If so, what were the perceived barriers? (i.e. fundraising, finding students or mentors, etc)
  2. Would a report detailing our experiences in creating and maintaining an iGEM team be useful to you?


We were ecstatic to hear back from 11 community labs from around the world (BosLab, BioCurious, Bricobio, ReaGent, Ronin Genetics, The Open Science Network, DIY Bio Hong Kong, Victoria Makerspace, AbroBios, BioBlaze, and Bioscope). Many of them expressed struggles with:


  • “Recruiting and finding high commitment amongst members”
  • “Not knowing how [to] fundraise or raise money for a team”
  • “Organizing a team”
  • “Biology background knowledge”

With their replies, we structured our guide to consist of 6 sections to best address some of the concerns that we had heard. These sections are:


1. Recruiting
2. Communication & Tools
3. Leadership
4. Timeline/Scheduling
5. Protocols & Lab Notebooks
6. Fundraising



In each section, we outlined some of our recommendations for new teams, some background from our teams’ experiences, and other alternative ideas and solutions that we had brainstormed. As our experience with iGEM continues, we plan on adding more sections and we are striving to encourage more community laboratories to invite local high schoolers to compete in iGEM.

For a live, and more updated version of our guide, check out this Google Doc.


iTesla-SoundBio, Tacoma RAINMakers, & Team Washington

Pacific Northwest iGEM Meetup hosted by the Washington iGEM team

On August 18th and 19th iGEM teams from around Washington (Tacoma RAINMakers, Team Washington & iTesla-SoundBio) met up to share ideas, give feedback, and bond over our shared love for synthetic biology. This event gave us great opportunities to prepare for the jamboree and hear from people working in the biotech industry and academia.

We had the opportunity to meet with iGEM ambassadors, Holly Bowman and Amy Chen, about our project. Holly was a part of the 2017 Georgia State Team, whose project we decided to base our work off of. She described the setbacks her team had faced and gave us suggestions to improve our progress. The advice of the ambassadors gave us meaningful insight on the future steps we should take for wetlab, human practices, and beyond. After a mock jamboree poster session, practice presentations, and talks from our keynote speakers, we headed to Gasworks Park for an outreach event. There we got Seattle families involved in synthetic biology activities and talked about our iGEM project. All in all, the PNW iGEM Meetup was an awesome opportunity to prepare for the Giant Jamboree and gain a thorough understanding of the projects of other iGEM teams, as well as the work currently being done in the field of synthetic biology.

Mentorship with Team Washington

This year we received help from the Washington iGEM team in terms of training and selecting presenters, human practices, basic wetlab procedure, and InterLab support. In terms of selecting presenters, Washington iGEM's Angel Wong and Andrew Hu critiqued each iTesla-SoundBio audition by giving feedback. Multiple members helped introduce new members to Benchling.com, pipette technique, and transformation procedure as well. They also kindly let us use their plate readers for the InterLab readings.