Difference between revisions of "Team:Queens Canada/Collaborations"

 
(14 intermediate revisions by 2 users not shown)
Line 71: Line 71:
  
  
<p class="big"><font size="5" color="black"><br><br>This year, QGEM collaborated with the Ontario Genetically Engineered Machine Collective, which is composed of iGEM teams from the universities of Toronto, Guelph (new this year), Waterloo, McMaster, and Ottawa. With oGEM, we meet several times during the year to discuss ways to promote iGEM in Ontario, funding strategies, project troubleshooting, and new ways to collaborate for wet lab, dry lab, and policy and practice departments.
+
<p class="big"><font size="5" color="black"><br><br>This year, QGEM collaborated with the Ontario Genetically Engineered Machine (oGEM) Collective, which is composed of iGEM teams from the universities of Toronto, Guelph (new this year), Waterloo, McMaster, and Ottawa. With oGEM, we meet several times during the year to discuss ways to promote iGEM in Ontario, funding strategies, project troubleshooting, and new ways to collaborate for wet lab, dry lab, and policy and practice departments.
 
<br><br>
 
<br><br>
One of the oGEM collaborations featured this year was promoting iGEM to new potential teams, and creating a detailed database of helpful tips and tricks for wiki development - a task most teams noticeably struggle with. Through web conferencing, email, and simply communicating ideas in person at the oGEM meetings, these valuable tidbits and thoughts were shared. The ability to discuss QGEM's wiki struggles with others, and gain insight into possible methods of remediation, was extremely valuable to QGEM. <font></p>
+
One of the oGEM collaborations featured this year was promoting iGEM to new potential teams, and creating a detailed database of helpful tips and tricks for wiki development - a task most teams noticeably struggle with. Through web conferencing, email, and simply communicating ideas in person at the oGEM meetings, these valuable tidbits and thoughts were shared. The ability to discuss QGEM's wiki struggles with others, and gain insight into possible methods of remediation, was extremely valuable to QGEM.<font></p>
 
<br>
 
<br>
  
Line 90: Line 90:
 
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">Canadian iGEM Newsletter</span></center></font></h1><hr/>
 
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">Canadian iGEM Newsletter</span></center></font></h1><hr/>
 
<br>
 
<br>
<p class="big"><font size="5" face="Corbel"> This summer, the University of Calgary initiated a Canadian iGEM Newsletter - a fantastic opportunity QGEM was eager to participate in. As each participating iGEM team shared monthly recaps (pertaining to all aspects of their respective projects), QGEM was able to easily learn what other iGEM teams were up to. Thus, allowing faster communication between teams given a deeper understanding of each other's work, and therefore, stronger collaborations.  
+
<p class="big"><font size="5" face="Corbel"> This summer, the University of Calgary initiated a Canadian iGEM Newsletter - a fantastic opportunity QGEM was eager to participate in. As each participating iGEM team shared monthly recaps (pertaining to all aspects of their respective projects), QGEM was able to easily learn what other iGEM teams were up to. Thus, allowing faster communication between teams given a deeper understanding of each other's work, and therefore, stronger collaborations. QGEM has participated in all Canadian iGEM Newsletters to date (two volumes).  
 
<br><br>
 
<br><br>
 
Participation in the Canadian iGEM Newsletter allowed QGEM to realize the parallels existing between QGEM's project, and Waterloo's. Ultimately resulting in communicating the idea of a collaboration between the two teams.<font></p>
 
Participation in the Canadian iGEM Newsletter allowed QGEM to realize the parallels existing between QGEM's project, and Waterloo's. Ultimately resulting in communicating the idea of a collaboration between the two teams.<font></p>
  
  
<img float="left" src="https://static.igem.org/mediawiki/2017/0/0b/T--Queens_Canada--CanadianiGEMNewsletter2Cover.png" style="height:auto;width:33%;padding:50px 0px 75px 0px">
+
<img float="left" src="https://static.igem.org/mediawiki/2017/0/0b/T--Queens_Canada--CanadianiGEMNewsletter2Cover.png" style="height:auto;width:33%;padding:10px 0px 0px 0px">
<img float="left" src="https://static.igem.org/mediawiki/2017/b/b7/T--Queens_Canada--CanadianiGEMN2QueensP1.png" style="height:auto;width:33%;padding:75px 0px 75px 0px">
+
<img float="left" src="https://static.igem.org/mediawiki/2017/b/b7/T--Queens_Canada--CanadianiGEMN2QueensP1.png" style="height:auto;width:33%;padding:10px 0px 0px 0px">
<img float="left" src="https://static.igem.org/mediawiki/2017/5/55/T--Queens_Canada--CanadianiGEMN2QueensP2.png" style="height:auto;width:33%;padding:75px 0px 75px 0px">
+
<img float="left" src="https://static.igem.org/mediawiki/2017/5/55/T--Queens_Canada--CanadianiGEMN2QueensP2.png" style="height:auto;width:33%;padding:10px 0px 0px 0px">
  
 
</div>  
 
</div>  
Line 108: Line 108:
 
<div style="background-color:#afbee8;color:white;padding:50px 150px 50px 150px;">
 
<div style="background-color:#afbee8;color:white;padding:50px 150px 50px 150px;">
  
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">Methods and Materials</span></center></font></h1><hr/>
+
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">Collaboration with Waterloo</span></center></font></h1><hr/>
 
<br>
 
<br>
 
<br>
 
<br>
  
<div class="center"><img src="https://static.igem.org/mediawiki/2017/2/21/T--Queens_Canada--Protocol.png" alt="Interlab study protocols." height ="auto" width=70%"></div>
 
<font face="Corbel" font style="line-height:1.5" font size="2" color="black"><figcaption><center>Interlab Study Protocols</font>
 
<br>
 
<br>
 
  
 
+
<p class="big"><font size="5" color="black" face="Corbel"> This summer, QGEM's Dry Lab created a ratiometric software application. This program works to read user input of designated protein ratio in the biofilm. Based on other user input constraints, such as organism and plasmid backbone, the program then outputs the required promoter and RBS sequences needed to produce such a biofilm.
<p class="big"><font size="5" color="black" face="Corbel"><We transformed the six plasmids containing the six test device constructs (J364000, J364001, J364002, J364003, J364004, J364005) as well as the positive and negative controls into the <i>E. coli</i> DH5a strain. After picking two colonies from each transformation, we grew up the cells and started the calibration protocols of OD600 reference point using the LUDOX solution. FITC was used as the standard for fluorescence. We used a Molecular Devices SpectraMax M2e plate reader on the topreading setting for both our OD600 and fluorescent measurements. Black 96-well plates with clear bottoms were used. We measured fluorescence at an excitation wavelength 395nm and emission wavelength of 508nm [2].</font></p>
+
<br><br>
 +
Given the striking similarity in QGEM's bifunctional biofilm optimization project, to that of Waterloo's prion based, a logical collaboration existed between the two team. This summer QGEM faced a deficit in web development knowledge, which Waterloo was eager to aid with - graciously offering to building a web accessible version of the software for public use. Both teams planned to build upon the existing software program, broadening its bases of organism knowledge. QGEM primarily worked with E.coli this summer, and thus, the program solely contained an E.coli database. In contrast, Waterloo worked with Yeast this summer, and therefore planned to add Yeast data to our organism database. Waterloo hoped to then utilize the program, allowing faster progression of their project - as optimal parts of their organism would be quickly brought to their knowledge, saving valuable time.
 +
<br><br>
 +
Unfortunately, this collaboration between teams did not happen until late into the summer, and not enough time existed to complete the collaboration to its full extent. Nevertheless, the opportunity to discuss projects to parallel in idea and execution provided imperative problem solving aid to both teams. Waterloo brought to the attention of QGEM, various parameters that should and could be incorporated into the ratiometric program. For example, looking into the effects of degradation rates of protein production. Incorporating these aspects produced in much stronger, more accurate results from the ratiometric program. Similar feedback, along with tips and tricks, were given back to Waterloo who similarly directly benefited from the ongoing collaboration.
 +
</font></p>
 
<br>
 
<br>
 
<br>
 
<br>
  
<font face="Arial" font size="5"><a href="https://static.igem.org/mediawiki/2017/8/85/InterLab_2017_Plate_Reader_Protocol.pdf" style = "color:rgb(128,128,128); text-decoration:none;"><font color="#808080">Interlab Protocols (PDF)</font></a>
 
 
<br>
 
<br>
 
 
</font>
 
</font>
 
</div>
 
</div>
Line 134: Line 130:
 
</div>
 
</div>
  
<div style="background-color:#afbee8;color:white;padding:50px 150px 50px 150px;"
+
<div style="background-color:#afbee8;color:white;padding:50px 150px 50px 150px;">
 
+
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">
+
Results and Discussion
+
</span></center></font></h1><hr/>
+
  
 +
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">Collaboration with Sydney</span></center></font></h1><hr/>
 
<br>
 
<br>
<br>
 
<div class="center">
 
<img src="https://static.igem.org/mediawiki/2017/b/b0/T--Queens_Canada--Fluorescein.png" alt="absorbance at 600 nm" height="auto" width="50%">
 
<font face="Corbel" font style="line-height:1.5" font size="2" color="black"><figcaption><center><b>Fig 1.</b> Fluorescein standard curve.</font></center></figcaption></div>
 
 
<br>
 
<br>
  
<p class="big"><font size="5" color="black" face="Corbel">The above fluorescence calibration curve (Fig. 1) was created by measuring fluorescence intensity of different concentrations of fluorescein.</font></p>
 
  
<div class="center">
+
<p class="big"><font size="5" color="black" face="Corbel"> This summer, QGEM was contacted by the University of Sydney iGEM team, who were interested in learning more about the oGEM network in their quest to set up an Australasian iGEM network. As a result, QGEM shared with Sydney iGEM details on how oGEM meetings are organized and structured during the summer, and provided information on meeting agendas, topics of discussion at oGEM meetings, methods of communication, sponsorships for oGEM meetups, and strategies for promoting oGEM to industry and academia. Some advice we gave regarding setting up an iGEM network included:</font><br><br></p>
<img src="https://static.igem.org/mediawiki/2017/9/9c/T--Queens_Canada--FI_Graph_Normalized_Interlab_Study.png" alt="Fluorescents of the test devices." height="auto" width="50%">
+
<ul float="left"><font size="4" face="Lucida Sans Unicode">
<font face="Corbel" font style="line-height:1.5" font size="2" color="#b0bee1"><figcaption><center><b>Fig 2.</b> This graph shows the fluorescence of each test device measured every two hours over a span of 6 hours.</font></center></figcaption></div>
+
<li>Establishing a consistent and effective form of communication between all teams (e.g. Slack)</li>
 +
<li>Drafting an iGEM handbook for new teams to ease transitioning year to year</li>
 +
<li>Contacting a local organization with similar values for a partnership to sponsor future team meetups (e.g. Ontario Genomics for oGEM)</li>
 +
<br><br>
 +
</font>
 +
</ul>
 +
<p class="big"><font size="5" color="black" face="Corbel">Starting a new iGEM team is no easy task. For this reason, we encourage all iGEM teams to build national/regional networks to support team collaboration, promote iGEM and synthetic biology to academia and industry, and encourage other universities and high schools to become involved with iGEM!</font><br><br></p>
 
<br>
 
<br>
 
<p class="big"><font size="5" color="black" face="Corbel">Cultures were sampled at the += 0,2,4,6 hour marks in 500ml aliquots from 10ml cultures. All samples were added to a 96-well plate to measure fluorescence intensity. Fluorescent values were normalized prior to plotting. All points on the graphs are the average of the two colonies grown (which themselves are the average of 4 wells each). Test device 2 had the greatest overall increase in fluorescence. Both the negative control device and the LB+ chloramphenicol sample had no significant increase in fluorescence.</font></p>
 
 
 
<br>
 
<br>
<div class="center">
 
<img src="https://static.igem.org/mediawiki/2017/e/e1/T--Queens_Canada--OD600.png" alt="absorbance at 600 nm" height="auto" width="50%">
 
<font face="Corbel" font style="line-height:1.5" font size="2" color="#b0bee1"><figcaption><center><b>Fig 3.</b> This graph shows the absorbance at 600 nanometres of each cell culture, which<br>provides an estimate for the number of cells in the samples.</font></center></figcaption></div>
 
  
<p class="big"><font size="5" color="black" face="Corbel">Every test device exhibits steady, somewhat sigmoidal bacterial growth. The LB + chloramphenicol sample shows no change in OD600 over time.</font></p>
 
</div>
 
 
<div style="height:30px;width:100%">
 
<img src="https://static.igem.org/mediawiki/2017/6/64/T--Queens_Canada--NavyNavBackground1.jpg" style="width:100%;height:30px">
 
</div>
 
 
<div style="background-color:#afbee8;color:white;padding:50px 150px 50px 150px;">
 
 
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">Conclusions</span></center></font></h1><hr/>
 
<br>
 
<font face="Corbel" font style="line-height:1.5" font size="5" color="black">
 
<ul><li>The Queen's_Canada iGEM team was grateful for the opportunity to contribute to the Interlab Study for the first time.</li>
 
<li>It appears that our cells only began expressing significant amounts of GFP after the 4-hour mark. One would expect the curve of increasing GFP fluorescence to mirror the curve of OD600, if GFP expression is truly constitutive. The OD600 curve shows steady, somewhat sigmoidal growth, while the fluorescent intensity curve is a plateau until after 4 hours have elapsed. </li>
 
<li>This suggests either a certain threshold concentration of GFP is required to be detectable by our plate reader, or that GFP expression only begins at a certain cell density threshold (which is reached at approximately 0.2 OD on our Figure 3 graph). </li>
 
<li> Both the LB + chloramphenicol and negative control wells showed no significant increase in fluorescence, as expected. <li?>
 
 
</font>
 
</font>
 
 
</div>
 
</div>
  
<img src="https://static.igem.org/mediawiki/2017/6/64/T--Queens_Canada--NavyNavBackground1.jpg" style="width:100%;height:30px">
 
</div>
 
 
<div style="background-color:#afbee8;color:white;padding:50px 150px 50px 150px;">
 
 
<h1><font color="black" face="Arial"><center><span style="font-weight:normal; font-size: 23pt">References</span></center></font></h1><hr/>
 
<br>
 
 
<ol><font style="line-height:1.5" "left-margin:0" font face="corbel" font size="2" color="black">
 
<li>Kwok, R. 2010. Five hard truths for synthetic biology. Nature, 463, 288.</li>
 
<li>Chalfie, M., Tu, Y., Euskirchen, G., Ward, W. W., Prasher, D. C. 1994. Green Fluorescent Protein as a Marker for Gene Expression. Science: 263(5148), 802-805. </li>
 
</font></ol>
 
  
 
</body>
 
</body>

Latest revision as of 01:07, 2 November 2017

Queen's Canada iGEM team was very excited to collaborate with various other iGEM teams this past summer. Together, we were able to build a stronger iGEM community, and progress in our respective projects - the insight of others providing great advancement.




This year, QGEM collaborated with the Ontario Genetically Engineered Machine (oGEM) Collective, which is composed of iGEM teams from the universities of Toronto, Guelph (new this year), Waterloo, McMaster, and Ottawa. With oGEM, we meet several times during the year to discuss ways to promote iGEM in Ontario, funding strategies, project troubleshooting, and new ways to collaborate for wet lab, dry lab, and policy and practice departments.

One of the oGEM collaborations featured this year was promoting iGEM to new potential teams, and creating a detailed database of helpful tips and tricks for wiki development - a task most teams noticeably struggle with. Through web conferencing, email, and simply communicating ideas in person at the oGEM meetings, these valuable tidbits and thoughts were shared. The ability to discuss QGEM's wiki struggles with others, and gain insight into possible methods of remediation, was extremely valuable to QGEM.


Canadian iGEM Newsletter



This summer, the University of Calgary initiated a Canadian iGEM Newsletter - a fantastic opportunity QGEM was eager to participate in. As each participating iGEM team shared monthly recaps (pertaining to all aspects of their respective projects), QGEM was able to easily learn what other iGEM teams were up to. Thus, allowing faster communication between teams given a deeper understanding of each other's work, and therefore, stronger collaborations. QGEM has participated in all Canadian iGEM Newsletters to date (two volumes).

Participation in the Canadian iGEM Newsletter allowed QGEM to realize the parallels existing between QGEM's project, and Waterloo's. Ultimately resulting in communicating the idea of a collaboration between the two teams.

Collaboration with Waterloo




This summer, QGEM's Dry Lab created a ratiometric software application. This program works to read user input of designated protein ratio in the biofilm. Based on other user input constraints, such as organism and plasmid backbone, the program then outputs the required promoter and RBS sequences needed to produce such a biofilm.

Given the striking similarity in QGEM's bifunctional biofilm optimization project, to that of Waterloo's prion based, a logical collaboration existed between the two team. This summer QGEM faced a deficit in web development knowledge, which Waterloo was eager to aid with - graciously offering to building a web accessible version of the software for public use. Both teams planned to build upon the existing software program, broadening its bases of organism knowledge. QGEM primarily worked with E.coli this summer, and thus, the program solely contained an E.coli database. In contrast, Waterloo worked with Yeast this summer, and therefore planned to add Yeast data to our organism database. Waterloo hoped to then utilize the program, allowing faster progression of their project - as optimal parts of their organism would be quickly brought to their knowledge, saving valuable time.

Unfortunately, this collaboration between teams did not happen until late into the summer, and not enough time existed to complete the collaboration to its full extent. Nevertheless, the opportunity to discuss projects to parallel in idea and execution provided imperative problem solving aid to both teams. Waterloo brought to the attention of QGEM, various parameters that should and could be incorporated into the ratiometric program. For example, looking into the effects of degradation rates of protein production. Incorporating these aspects produced in much stronger, more accurate results from the ratiometric program. Similar feedback, along with tips and tricks, were given back to Waterloo who similarly directly benefited from the ongoing collaboration.



Collaboration with Sydney




This summer, QGEM was contacted by the University of Sydney iGEM team, who were interested in learning more about the oGEM network in their quest to set up an Australasian iGEM network. As a result, QGEM shared with Sydney iGEM details on how oGEM meetings are organized and structured during the summer, and provided information on meeting agendas, topics of discussion at oGEM meetings, methods of communication, sponsorships for oGEM meetups, and strategies for promoting oGEM to industry and academia. Some advice we gave regarding setting up an iGEM network included:

  • Establishing a consistent and effective form of communication between all teams (e.g. Slack)
  • Drafting an iGEM handbook for new teams to ease transitioning year to year
  • Contacting a local organization with similar values for a partnership to sponsor future team meetups (e.g. Ontario Genomics for oGEM)


Starting a new iGEM team is no easy task. For this reason, we encourage all iGEM teams to build national/regional networks to support team collaboration, promote iGEM and synthetic biology to academia and industry, and encourage other universities and high schools to become involved with iGEM!