Difference between revisions of "Team:Cornell/Collaborations"

 
(20 intermediate revisions by 2 users not shown)
Line 43: Line 43:
 
     nav {
 
     nav {
 
         grid-area: navbar;
 
         grid-area: navbar;
    }
 
 
    .nav-bar-logo {
 
        width: 180px;
 
        padding-top: 12px;
 
 
     }
 
     }
  
Line 53: Line 48:
 
         display: grid;
 
         display: grid;
 
         grid-template-columns: auto auto auto;
 
         grid-template-columns: auto auto auto;
 +
    }
 +
 +
    .nav-first-col {
 +
        display: inline-grid;
 
     }
 
     }
  
Line 58: Line 57:
 
         display: inline-grid;
 
         display: inline-grid;
 
     }
 
     }
 +
 
     .nav-third-col {
 
     .nav-third-col {
 
         display: inline-grid;
 
         display: inline-grid;
Line 90: Line 90:
 
     /******************** STANDARD PAGE GRID END ********************/
 
     /******************** STANDARD PAGE GRID END ********************/
  
     @import url('https://fonts.googleapis.com/css?family=Merriweather|Open+Sans|Raleway');
+
    /******************** ALL FONTS START ********************/
 +
     @import url('https://fonts.googleapis.com/css?family=Merriweather|Open+Sans:400,700|Raleway');
 +
    @font-face {
 +
        font-family: 'Futura';
 +
        src: url('../futura/futura\ medium\ bt.ttf');
 +
    }
 +
 
 +
    body {
 +
        font-family: 'Open Sans', sans-serif;
 +
    }
 +
 
 +
    .dropbtn, .dropdown-content {
 +
        font-size: 16px;
 +
    }
 +
 
 +
    .standard-page-banner > svg > text, .standard-page-content-title, .standard-page-side-bar-wrapper, .standard-page-content-subheading {
 +
        font-family: 'Futura', sans-serif;
 +
    }
 +
    /******************** ALL FONTS END ********************/
 +
 
 
     html,
 
     html,
 
     body {
 
     body {
Line 106: Line 125:
 
     p {
 
     p {
 
         color: #000;
 
         color: #000;
        font-family: 'Open Sans', sans-serif;
 
 
     }
 
     }
  
Line 127: Line 145:
 
     .nav-bar-logo img {
 
     .nav-bar-logo img {
 
         width: 140px;
 
         width: 140px;
    }
 
 
    .nav-bar-main-menu {
 
        font-family: 'Raleway', sans-serif;
 
 
     }
 
     }
  
Line 183: Line 197:
  
 
     .toolkit-dropdown-content {
 
     .toolkit-dropdown-content {
         width: 590px;
+
         width: 620px;
 
         left: -160px;
 
         left: -160px;
 
     }
 
     }
Line 258: Line 272:
 
         position: relative;
 
         position: relative;
 
         padding-right: 18px;
 
         padding-right: 18px;
 +
        padding-left: 18px;
 
         border-right: 0.5px solid white;
 
         border-right: 0.5px solid white;
 
     }
 
     }
Line 278: Line 293:
 
         background-size: cover;
 
         background-size: cover;
 
         fill: black;
 
         fill: black;
         font-size: 14px;
+
         font-size: 12px;
 
     }
 
     }
  
Line 288: Line 303:
 
         text-decoration: none;
 
         text-decoration: none;
 
         color: #016c64;
 
         color: #016c64;
        font-weight: bold;
 
 
         font-size: 16px;
 
         font-size: 16px;
 
     }
 
     }
Line 297: Line 311:
 
         padding-right: 15px;
 
         padding-right: 15px;
 
         vertical-align: middle;
 
         vertical-align: middle;
         margin: 0;
+
         margin: 40px !important;
 
     }
 
     }
  
Line 306: Line 320:
 
     .standard-page-content-title {
 
     .standard-page-content-title {
 
         font-size: 24px;
 
         font-size: 24px;
        font-weight: 700;
 
 
         color: #000 !important;
 
         color: #000 !important;
 
         position: relative;
 
         position: relative;
Line 361: Line 374:
 
           </div>
 
           </div>
 
           <div class="dropdown">
 
           <div class="dropdown">
             <button class="dropbtn">OUTREACH</button>
+
             <button class="dropbtn active-page">OUTREACH</button>
 
             <div class="dropdown-content outreach-dropdown-content">
 
             <div class="dropdown-content outreach-dropdown-content">
 
               <a href="https://2019.igem.org/Team:Cornell/Public_Engagement">EDUCATION & ENGAGEMENT</a>
 
               <a href="https://2019.igem.org/Team:Cornell/Public_Engagement">EDUCATION & ENGAGEMENT</a>
Line 391: Line 404:
 
                 </div>
 
                 </div>
 
                 <div class="nav-second-col">
 
                 <div class="nav-second-col">
                   <li class="pd-list-title"><b>DESIGN</b></li>
+
                   <li class="pd-list-title"><b>PRODUCT DEVELOPMENT</b></li>
 
                   <li><a href="https://2019.igem.org/Team:Cornell/DesignProcess">DESIGN PROCESS</a></li>
 
                   <li><a href="https://2019.igem.org/Team:Cornell/DesignProcess">DESIGN PROCESS</a></li>
 +
                  <li><a href="https://2019.igem.org/Team:Cornell/Hardware">HARDWARE</a></li>
 
                 </div>
 
                 </div>
 
                 <div class="nav-third-col">
 
                 <div class="nav-third-col">
Line 407: Line 421:
 
           </div>
 
           </div>
 
           <div class="dropdown">
 
           <div class="dropdown">
             <button class="dropbtn active-page"
+
             <button class="dropbtn"
 
               onclick="location.href='https://2019.igem.org/Team:Cornell'">HOME</button>
 
               onclick="location.href='https://2019.igem.org/Team:Cornell'">HOME</button>
 
           </div>
 
           </div>
Line 416: Line 430:
 
     <!------------------------ STANDARD PAGE BANNER START ------------------------>
 
     <!------------------------ STANDARD PAGE BANNER START ------------------------>
 
     <header class="standard-page-banner"
 
     <header class="standard-page-banner"
       style="background-image: url(https://static.igem.org/mediawiki/2019/a/a9/T--Cornell--CollabBanner.png)">
+
       style="background-image: url(https://static.igem.org/mediawiki/2019/c/ce/T--Cornell--collab-banner.jpeg)">
 
       <svg viewBox="0 0 100 100" width=100% height=100%>
 
       <svg viewBox="0 0 100 100" width=100% height=100%>
        <circle cx="50" cy="50" r="40" fill="white" fill-opacity="0.4" />
 
 
         <text text-anchor="middle" alignment-baseline="middle" x=50% y=50%>Collaborations</text>
 
         <text text-anchor="middle" alignment-baseline="middle" x=50% y=50%>Collaborations</text>
 
       </svg>
 
       </svg>
Line 484: Line 497:
 
           </p>
 
           </p>
 
           <br><br>
 
           <br><br>
           <iframe src="https://static.igem.org/mediawiki/2019/b/ba/T--Cornell--Collabs.pdf" height="500" width="800"></iframe>
+
           <iframe src="https://static.igem.org/mediawiki/2019/b/ba/T--Cornell--Collabs.pdf" height="600" width="800"></iframe>
 
           <br><br>
 
           <br><br>
 
         </div>
 
         </div>
Line 492: Line 505:
 
           </div>
 
           </div>
 
           <hr class="green-accent-line-left">
 
           <hr class="green-accent-line-left">
          <br><br>
 
          <img class="standard-page-content-image" src="https://static.igem.org/mediawiki/2019/0/01/T--Cornell--Korea.png"
 
            style="height: 400px; width: 500px">
 
 
           <div class="standard-page-content-subheading" style="font-weight: 1000">Korea_HS iGEM</div>
 
           <div class="standard-page-content-subheading" style="font-weight: 1000">Korea_HS iGEM</div>
 
           <p class="standard-page-content-text">
 
           <p class="standard-page-content-text">
Line 506: Line 516:
 
             a follow-up meeting on August 3rd, 2019, for an update on the team’s progress on their project and to answer
 
             a follow-up meeting on August 3rd, 2019, for an update on the team’s progress on their project and to answer
 
             any remaining questions they had regarding the competition. </p>
 
             any remaining questions they had regarding the competition. </p>
 +
          <img class="standard-page-content-image" src="https://static.igem.org/mediawiki/2019/0/01/T--Cornell--Korea.png"
 +
            style="height: 400px; width: 650px">
 +
          <div class="standard-page-content-subheading" style="font-weight: 1000">Ohio State iGEM</div>
 +
          <p class="standard-page-content-text">
 +
            Our team also spoke with the Ohio State iGEM team to provide guidance on team organization and the competition timeline. We provided recommendations based on the resources that have worked best for our team, such as the online scheduling platform When2Meet that helps with finding meeting times that work best for the group. We also addressed questions Ohio State iGEM had regarding how to integrate human practices into their project. </p>
 
         </div>
 
         </div>
 
         <div class="standard-page-content-section">
 
         <div class="standard-page-content-section">
Line 512: Line 527:
 
           </div>
 
           </div>
 
           <hr class="green-accent-line-left">
 
           <hr class="green-accent-line-left">
          <br><br>
 
          <img class="standard-page-content-image" src="https://static.igem.org/mediawiki/2019/d/de/T--Cornell--WilliamMary.png" style="height: 400px; width: 300px">
 
 
           <br><br>
 
           <br><br>
 
           <p class="standard-page-content-text">
 
           <p class="standard-page-content-text">
             On September 22nd, Cornell iGEM held a Skype meeting with the members of W&M iGEM to discuss the integration
+
             On September 22nd, Cornell iGEM held a Skype meeting with the members of W&M iGEM to discuss the integration of their curli fibers into our bioreactor. Since curli fibers enable biofilm development, our team sought to use them to encapsulate more bacteria, which would lead to higher efficiency. After we received the DNA parts from W&M iGEM, we compared the concentration of curli fiber-expressing bacteria and control bacteria in the beads. To do so, we cultured both types of bacteria overnight and induced the curli fiber expressing bacteria with 10 mM IPTG for 4 hours. We encapsulated both sets of bacteria using our alginate bead protocol and submerged them in water overnight. Then, 5 g of beads were dissolved in sodium citrate and serial dilutions were performed to find the final concentration of bacteria in our beads. We found that the control group had a colony count of roughly 4*10<sup>5</sup> whereas the modified groups yielded 2.5*10<sup>6</sup> colonies, so with a single run we were able to produce a significantly greater amount of bacteria. These results suggest that our system could be run at greater efficiency.
            of their curli fibers into our bioreactor. Since curli fibers enable biofilm development, our team sought to
+
            use them to improve the efficiency of trapping our bacteria in alginate beads. After we received the DNA
+
            parts from W&M iGEM, we tested whether the efficiency of our bioreactor was higher with or without the curli
+
            fibers. [results?]
+
 
             <br><br>
 
             <br><br>
             Our team also forwarded our alginate bead formation protocol to W&M iGEM so they could look for the
+
             Our team also forwarded our alginate bead formation protocol to W&M iGEM, and they were able to successfully get their pDawn optogenetic bacteria into the beads. </p>
            experimental conditions that promote optimized bacterial adhesion onto the alginate beads. [results?] </p>
+
          <img class="standard-page-content-image" src="https://static.igem.org/mediawiki/2019/d/de/T--Cornell--WilliamMary.png" style="height: 350px; width: 300px">
 +
          <img class="standard-page-content-image" src="https://static.igem.org/mediawiki/2019/8/84/T--Cornell--ControlGroup.png" style="height: 350px; width: 300px">
 +
          <img class="standard-page-content-image" src="https://static.igem.org/mediawiki/2019/a/a1/T--Cornell--TreatedGroup.png" style="height: 350px; width: 300px">
 
         </div>
 
         </div>
 
         <div class="standard-page-content-section">
 
         <div class="standard-page-content-section">
Line 552: Line 563:
 
         </div>
 
         </div>
 
         <div class="icon-wrapper">
 
         <div class="icon-wrapper">
           <a class="icon" href="https://www.instagram.com/cugem/"><img
+
           <a class="icon" href="https://www.instagram.com/cugem/" style="padding: 0;"><img
 
               src="https://static.igem.org/mediawiki/2019/3/37/T--Cornell--Instagram.png"></a>
 
               src="https://static.igem.org/mediawiki/2019/3/37/T--Cornell--Instagram.png"></a>
 
         </div>
 
         </div>

Latest revision as of 21:41, 21 October 2019

Team:Cornell - 2019.igem.org

Collaborations
Overview



This year, Cornell iGEM had the honor of working with several different iGEM teams across the globe on both technical- and outreach-oriented collaborations. We received valuable feedback on how to improve our informational booklet designed to educate members of the community on the issue of harmful algal blooms (HABs). We also mentored a new high school team and helped them get up-to-speed with how the iGEM competition runs. Finally, we worked with another team to optimize and test components of the Wet Lab aspects of our respective projects. Through these partnerships, our team was able to expand upon the possibilities of collaborative synthetic biology and learn more about how we can solve big issues using microscopic tools.

Harmful Algal Blooms (HABs) Informational Booklet



Cornell iGEM sought to demystify the subject of HABs by creating an informational booklet that summarizes the background, prevalence, and existing treatment methods for HABs. We sent the first draft of our booklet to Ohio State iGEM and Toronto iGEM to obtain feedback on the content and formatting of our booklet to ensure it is readily accessible to readers. Below, we have detailed the feedback provided to us by these teams and how we incorporated their suggestions into the final draft presented on our Wiki.

Ohio State iGEM

The members of the Ohio State iGEM team found our booklet very informative and well-cited. However, their feedback mentioned that our booklet had too much technical detail that occasionally took away from the primary focus of each section, so we cut down and made our sections more concise. We also took their advice to include a brief sentence explaining the examples listed on the Current Solutions page before discussing their respective pros and cons.

Toronto iGEM

Toronto iGEM recommended reformatting the Current Solutions page to make it easier for readers to compare between example solutions and to recognize their respective strengths and weaknesses. Going off of this suggestion, our team made modifications to the Current Solutions section and also decided to include an additional page recapitulating the ways in which our project covers the weak points of other solutions.





Mentorship

Korea_HS iGEM

Over the summer, our team mentored the Korea_HS iGEM team after they reached out to us with questions about the iGEM competition process. We held an initial Skype meeting on July 6th, 2019, where we shared our project ideas and our experiences on iGEM. As it was Korea_HS’s first year participating in the competition, we provided insight into what iGEM is and what Cornell iGEM has done as a team in the past. In regards to the competition itself, Korea_HS had questions regarding the characterization section of the Bronze Medal criteria and the formatting of the presentation and the poster, so we explained the characterization section and provided tips on how to efficiently and effectively prepare for each portion of the competition. We had a follow-up meeting on August 3rd, 2019, for an update on the team’s progress on their project and to answer any remaining questions they had regarding the competition.

Ohio State iGEM

Our team also spoke with the Ohio State iGEM team to provide guidance on team organization and the competition timeline. We provided recommendations based on the resources that have worked best for our team, such as the online scheduling platform When2Meet that helps with finding meeting times that work best for the group. We also addressed questions Ohio State iGEM had regarding how to integrate human practices into their project.

William & Mary iGEM



On September 22nd, Cornell iGEM held a Skype meeting with the members of W&M iGEM to discuss the integration of their curli fibers into our bioreactor. Since curli fibers enable biofilm development, our team sought to use them to encapsulate more bacteria, which would lead to higher efficiency. After we received the DNA parts from W&M iGEM, we compared the concentration of curli fiber-expressing bacteria and control bacteria in the beads. To do so, we cultured both types of bacteria overnight and induced the curli fiber expressing bacteria with 10 mM IPTG for 4 hours. We encapsulated both sets of bacteria using our alginate bead protocol and submerged them in water overnight. Then, 5 g of beads were dissolved in sodium citrate and serial dilutions were performed to find the final concentration of bacteria in our beads. We found that the control group had a colony count of roughly 4*105 whereas the modified groups yielded 2.5*106 colonies, so with a single run we were able to produce a significantly greater amount of bacteria. These results suggest that our system could be run at greater efficiency.

Our team also forwarded our alginate bead formation protocol to W&M iGEM, and they were able to successfully get their pDawn optogenetic bacteria into the beads.

SZTA_Szeged_HU iGEM



Cornell iGEM held a Skype call with members of SZTA_Szeged_HU iGEM on September 14th. We exchanged public engagement surveys as a way to broaden the scope of our respective projects by gaining feedback from an international perspective.