Difference between revisions of "Team:BostonU/Collaborations"
| Line 52: | Line 52: | ||
<center><hr style= "width:702px; height: 3px; background-color:#0071A7"></center> | <center><hr style= "width:702px; height: 3px; background-color:#0071A7"></center> | ||
| − | <br><div id = "instruct"><center style = "color:#0071A7; font-size:150%;">Click on a | + | <br><div id = "instruct"><center style = "color:#0071A7; font-size:150%;">Click on a school to read about our collaboration</center><br></div> |
Revision as of 23:33, 15 October 2016
In the beginning of the summer, we collaborated with MIT, specifically their Recombinase team. Topics discussed included structures of recombinase circuits, phylogenic tree of recombinases, as well as the orthogonality of various heterospecific site-recombinase pairs. In addition, we worked with the entire MIT team to prepare for the NEGEM #1 conference, practicing both presentations and responding to audience questions.
During NEGEM #1, we mingled with the other teams to potentially collaborate to improve experimental projects or human practices projects. While there, we learned WPI was using microscopy to analyze fluorescence in their experiments and offered them to use our flow cytometers to help them quantify their data. They took us up on the offer and drove to our lab where we prepped their cells and ran them through our flow cytometer. We also helped them analyze and interpret their data using the FloJo program.
We collaborated with our fellow home team, BostonU HW (Hardware) to accomplish one of our Human Practices projects, a blog about intellectual property in synthetic biology and software. The first blog was a team effort to introduce our readers to intellectual property, patents, copyrights, etc. and to establish the tone for our blogs. Each subsequent blog was then switched off so the wet lab team wrote one week and the hardware team wrote the following week. Of course our bloggers, Castor and Pollux, always edited each other's work before it was uploaded. We also met weekly with the Hardware team to work on our team Wikis together, whether it was how to code to get a desired aesthetic or to test the practicality and functionality of the websites.
