Difference between revisions of "Team:Lethbridge/Collaborations"
Andyhudson (Talk | contribs) |
Chris.isaac (Talk | contribs) |
||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 37: | Line 37: | ||
div#footer-box {background-color: transparent;border: 0;margin: 0;padding: 0;width: auto;} | div#footer-box {background-color: transparent;border: 0;margin: 0;padding: 0;width: auto;} | ||
div#footer {color: inherit;font-size: inherit;text-align: left;} | div#footer {color: inherit;font-size: inherit;text-align: left;} | ||
| − | div#f- | + | div#f-poweblue-greybyico, div#f-copyrightico {float: none;} |
div#footer li {margin: 0;display: list-item; font-family: 'Roboto', sans-serif;} | div#footer li {margin: 0;display: list-item; font-family: 'Roboto', sans-serif;} | ||
</style> | </style> | ||
| Line 128: | Line 128: | ||
<ul id='dropdown2' class='dropdown-content' style="list-style-image: none; margin-left: 0px; width: auto;"> | <ul id='dropdown2' class='dropdown-content' style="list-style-image: none; margin-left: 0px; width: auto;"> | ||
<li><a href="https://2016.igem.org/Team:Lethbridge/Integrated_Practices" style="color:#616161;">Integrated Practices</a></li> | <li><a href="https://2016.igem.org/Team:Lethbridge/Integrated_Practices" style="color:#616161;">Integrated Practices</a></li> | ||
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Silver#intro" style="color:# | + | <li class="divider"></li> |
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Silver#interviews" style="color:# | + | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Silver#intro" style="color:#78909c;">Contact</a></li> |
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Silver#litrev" style="color:# | + | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Silver#interviews" style="color:#78909c;">Interviews</a></li><!--NEEDS STUFF--> |
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Gold#ridealong" style="color:# | + | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Silver#litrev" style="color:#78909c;">Literature Review</a></li> |
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Gold#protocol" style="color:# | + | <li class="divider"></li> |
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Gold#sampling" style="color:# | + | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Gold#ridealong" style="color:#ff8f00;">Ridealongs</a></li> |
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Gold#protocol" style="color:#ff8f00;">Protocol</a></li> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/HP/Gold#sampling" style="color:#ff8f00;">Sampling</a></li> | ||
</ul> | </ul> | ||
| − | <li><a href="https://2016.igem.org/Team:Lethbridge/Results" style=" | + | <li><a class="dropdown-button" href="#!" data-activates="dropdown4" style="display: block; padding-top: 19px; padding-bottom: 19px">Results</a></li> |
| + | <ul id='dropdown4' class="dropdown-content" style="list-style-image: none; margin-left: 0px; width: auto;"> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/Results#one" style="color:#616161;">Microbiome</a></li> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/Results#two" style="color:#616161;">Antibodies</a></li> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/Results#three" style="color:#616161;">RNAiCare</a></li> | ||
| + | </ul> | ||
<li><a class="dropdown-button" href="#!" data-activates="dropdown3" style="display: block; padding-top: 19px; padding-bottom: 19px">Team</a></li> | <li><a class="dropdown-button" href="#!" data-activates="dropdown3" style="display: block; padding-top: 19px; padding-bottom: 19px">Team</a></li> | ||
<ul id='dropdown3' class="dropdown-content" style="list-style-image: none; margin-left: 0px; width: auto;"> | <ul id='dropdown3' class="dropdown-content" style="list-style-image: none; margin-left: 0px; width: auto;"> | ||
| Line 169: | Line 176: | ||
<li class="no-padding"> | <li class="no-padding"> | ||
<ul class="collapsible collapsible-accordion"> | <ul class="collapsible collapsible-accordion"> | ||
| − | <li class="bold"><a class="collapsible-header waves-effect waves- | + | <li class="bold"><a class="collapsible-header waves-effect waves-blue">Practices</a> |
<div class="collapsible-body"> | <div class="collapsible-body"> | ||
<ul> | <ul> | ||
| Line 184: | Line 191: | ||
</ul> | </ul> | ||
</li> | </li> | ||
| − | + | <li class="no-padding"> | |
| − | + | <ul class="collapsible collapsible-accordion"> | |
| + | <li class="bold"><a class="collapsible-header waves-effect">Results</a> | ||
| + | <div class="collapsible-body"> | ||
| + | <ul> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/Results#one">Microbiome</a></li> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/Results#two">Antibodies</a></li> | ||
| + | <li><a href="https://2016.igem.org/Team:Lethbridge/Results#three">RNAiCare</a></li> | ||
| + | </ul> | ||
| + | </div> | ||
| + | </li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | <li class="no-padding"> | ||
<ul class="collapsible collapsible-accordion"> | <ul class="collapsible collapsible-accordion"> | ||
<li class="bold"><a class="collapsible-header waves-effect">Team</a> | <li class="bold"><a class="collapsible-header waves-effect">Team</a> | ||
| Line 207: | Line 226: | ||
<div class="row"> | <div class="row"> | ||
| − | <div class="col s12 | + | <div class="col s12 blue-grey darken-3"> |
<div class="container"> | <div class="container"> | ||
<div class="row"> | <div class="row"> | ||
<div class="col l12 s12"> | <div class="col l12 s12"> | ||
| − | < | + | <h2 class="thin white-text">Collaborations</h2> |
| − | <p class=" | + | <h4 class="thin white-text">Cooperation between iGEM Teams</h4> |
| + | <p class="grey-text text-lighten-4"></p> | ||
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
| − | |||
| − | <div class=" | + | <div class="col s12 m12 l4 green darken-2" id="marburg"> |
| − | <div class=" | + | <div class="container"> |
| − | <div class=" | + | <div class="row"> |
| − | <h3 class="white-text">Marburg Team</h3> | + | <div class="col s12"> |
| − | < | + | <a href="https://2016.igem.org/Team:Marburg"><h3 class="thin white-text">Marburg Team</h3></a> |
| − | </ | + | <p class="grey-text text-lighten-4">This year our iGEM team had the opportunity to form a trans-Atlantic collaboration with a team based in Marburg, Germany. We sought to determine the evolutionary trajectory of killswitches, with the Marburg team. Throughout this collaboration, the Marburg team assisted in modelling the behaviour and evolution of a previously described MazF killswitch. The Lethbridge team was able to devise a novel protocol for analyzing and accelerating the evolution of killswitches utilizing ultraviolet light. Our group also had killswitch parts synthesized by the Marburg group and improved upon them. This was a valuable collaborative opportunity which we hope to translate into a manuscript related to biocontainment and biosecurity trajectories over time. Our collaboration will be an ongoing one, with the aim of fully characterizing killswitches from a molecular standpoint as well as a computational modeling perspective.</p> |
| + | <img src="https://static.igem.org/mediawiki/2016/c/ca/T--Marburg--Syndustry_Logo_LS.svg" class="responsive-img center" style="max-height:300px;" /> | ||
| + | <h5 class="white-text">Experimental Protocol</h5> | ||
| + | <p class="grey-text text-lighten-4">500,000 microjoules of UV light was used to irradiate 200 microlitres of E. coli cells (OD600=0.1) containing an inducible plasmid expressing MazF. Cells were then plated on LB+agar plates containing antibiotic and inducer and grown for 16 hours at 37 degrees Celsius. The number of CFUs obtained after UV irradiation was compared to prior to irradiation and an escape frequency was obtained using this method. Clones which escape the killswitch will be sequenced to examine possible mutations allowing for their escape. Optimization of the amount of UV delivered as well as replication of these experiments are required, however it is a valuable step forward in assessing the evolution of killswitches. </p> | ||
| + | <img src="https://static.igem.org/mediawiki/2016/b/b7/T--Lethbridge--MAZF.jpg" class="responsive-img"/> | ||
| + | <p class="grey-text text-lighten-4">Figure 1. Plates containing the MazF killswitch (K2109111) before and after UV treatment.</p> | ||
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
| + | </div> | ||
| − | <div class=" | + | <div class="col s12 m12 l4 lime darken-4" id="bielefeld"> |
| − | <div class=" | + | <div class="container"> |
| − | <div class=" | + | <div class="row"> |
| − | <h3 class="white-text">Bielefeld | + | <div class="col s12"> |
| − | < | + | <a href="https://2016.igem.org/Team:Bielefeld-CeBiTec"><h3 class="thin white-text">Bielefeld CeBiTec</h3></a> |
| − | </ | + | <p class="grey-text text-lighten-4">Midway through the iGEM season, the Bielefeld iGEM team discovered that our teams share a significant overlap in our projects: both teams are engineering synthetic single domain antibody libraries and using a bacterial two hybrid system for antibody selection. Naturally, we were very interested to collaborate in order to discuss and overcome obstacles in the laboratory and compare our library and selection designs. We discussed these details in five separate video conferencing calls. During the ensuing discussions, we were able to identify several important design considerations, such as theoretical antibody library complexity, methods for maximizing cloning efficiency and selectable markers for positive hits in the two hybrid. Additional details regarding our conversations have been recorded in our joint Collaboration Notebook.</p> |
| + | <img src="https://static.igem.org/mediawiki/2016/4/45/Bielefeld_CeBiTec_2016_10_13_X_homebutton.png" class="responsive-img center" style="max-height:300px; max-width:300px;" /> | ||
| + | <p class="grey-text text-lighten-4">In addition to our discussions, we also exchanged control parts as well as DNAs encoding different target epitopes to raise antibodies against. The Bielefeld Team provided us with their anti-GFP control samples which included an antibody with sub-optimal binding which may be used to assess the sensitivity/stringency of the bacterial-two-hybrid detection system. In turn, we provided the Bielefeld Team with an influenza capsid protein antigen. The purpose of the latter would allow our two teams to compare the efficacy of our respective antibody libraries and/or selection systems to identify antibodies with high affinity and specificity towards a common ligand.</p> | ||
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
| + | </div> | ||
| − | <div class=" | + | <div class="col s12 m12 l4 red darken-1" id="lethhs"> |
| − | <div class=" | + | <div class="container"> |
| − | <div class=" | + | <div class="row"> |
| − | <h3 class="white-text">Lethbridge | + | <div class="col s12"> |
| − | < | + | <a href="https://2016.igem.org/Team:Lethbridge_HS"><h3 class="thin white-text">Lethbridge High School</h3></a> |
| − | + | <p class="grey-text text-lighten-4">This year we collaborated with the Lethbridge High School iGEM Team. We provided mentorship for the team by teaching them lab skills at a GeekStarter workshop held at the University of Lethbridge. We also helped them troubleshoot issues with their lab work. In return, the high school team helped us by prepping lab materials that we would need for later experiments. As well, we helped each other by working out any issues on our wikis. Overall, collaborating with the high school team solidified the iGEM community around the University of Lethbridge. </p> | |
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
| + | </div> | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | </div><!-- End row --> | ||
| + | |||
| + | |||
| + | |||
| + | </main></div><!--End Content --> | ||
| − | |||
| − | |||
<!-- Scripts --> | <!-- Scripts --> | ||
Latest revision as of 01:38, 20 October 2016
Collaborations
Cooperation between iGEM Teams
Marburg Team
This year our iGEM team had the opportunity to form a trans-Atlantic collaboration with a team based in Marburg, Germany. We sought to determine the evolutionary trajectory of killswitches, with the Marburg team. Throughout this collaboration, the Marburg team assisted in modelling the behaviour and evolution of a previously described MazF killswitch. The Lethbridge team was able to devise a novel protocol for analyzing and accelerating the evolution of killswitches utilizing ultraviolet light. Our group also had killswitch parts synthesized by the Marburg group and improved upon them. This was a valuable collaborative opportunity which we hope to translate into a manuscript related to biocontainment and biosecurity trajectories over time. Our collaboration will be an ongoing one, with the aim of fully characterizing killswitches from a molecular standpoint as well as a computational modeling perspective.
Experimental Protocol
500,000 microjoules of UV light was used to irradiate 200 microlitres of E. coli cells (OD600=0.1) containing an inducible plasmid expressing MazF. Cells were then plated on LB+agar plates containing antibiotic and inducer and grown for 16 hours at 37 degrees Celsius. The number of CFUs obtained after UV irradiation was compared to prior to irradiation and an escape frequency was obtained using this method. Clones which escape the killswitch will be sequenced to examine possible mutations allowing for their escape. Optimization of the amount of UV delivered as well as replication of these experiments are required, however it is a valuable step forward in assessing the evolution of killswitches.
Figure 1. Plates containing the MazF killswitch (K2109111) before and after UV treatment.
Bielefeld CeBiTec
Midway through the iGEM season, the Bielefeld iGEM team discovered that our teams share a significant overlap in our projects: both teams are engineering synthetic single domain antibody libraries and using a bacterial two hybrid system for antibody selection. Naturally, we were very interested to collaborate in order to discuss and overcome obstacles in the laboratory and compare our library and selection designs. We discussed these details in five separate video conferencing calls. During the ensuing discussions, we were able to identify several important design considerations, such as theoretical antibody library complexity, methods for maximizing cloning efficiency and selectable markers for positive hits in the two hybrid. Additional details regarding our conversations have been recorded in our joint Collaboration Notebook.
In addition to our discussions, we also exchanged control parts as well as DNAs encoding different target epitopes to raise antibodies against. The Bielefeld Team provided us with their anti-GFP control samples which included an antibody with sub-optimal binding which may be used to assess the sensitivity/stringency of the bacterial-two-hybrid detection system. In turn, we provided the Bielefeld Team with an influenza capsid protein antigen. The purpose of the latter would allow our two teams to compare the efficacy of our respective antibody libraries and/or selection systems to identify antibodies with high affinity and specificity towards a common ligand.
Lethbridge High School
This year we collaborated with the Lethbridge High School iGEM Team. We provided mentorship for the team by teaching them lab skills at a GeekStarter workshop held at the University of Lethbridge. We also helped them troubleshoot issues with their lab work. In return, the high school team helped us by prepping lab materials that we would need for later experiments. As well, we helped each other by working out any issues on our wikis. Overall, collaborating with the high school team solidified the iGEM community around the University of Lethbridge.
