Team:BostonU/Collaborations

From 2013.igem.org

(Difference between revisions)
Line 3: Line 3:
<br><br>
<br><br>
<h1>iGEM Collaborations</h1>
<h1>iGEM Collaborations</h1>
-
<h10>Wellesley Desyne</h10>
+
<h9>Wellesley Desyne</h9>
-
<p>We are working closely with the <a href="https://2013.igem.org/Team:Wellesley_Desyne">Wellesley Desyne</a> software team this year.</p>
+
<h7><p>We are working closely with the <a href="https://2013.igem.org/Team:Wellesley_Desyne">Wellesley Desyne</a> software team this year.</p>
<p>On June 3 and 4, we hosted the Wellesley team for a two day workshop.  On June 3, the BU team reviewed some fundamental biology and synthetic biology concepts and held a <a href="https://2013.igem.org/Team:BostonU/Clotho">Eugene</a> tutorial.  We went over some famous genetic circuits and wrote Eugene scripts for them.</p>
<p>On June 3 and 4, we hosted the Wellesley team for a two day workshop.  On June 3, the BU team reviewed some fundamental biology and synthetic biology concepts and held a <a href="https://2013.igem.org/Team:BostonU/Clotho">Eugene</a> tutorial.  We went over some famous genetic circuits and wrote Eugene scripts for them.</p>
Line 12: Line 12:
<p>On June 14, we traveled to Wellesley's campus to continue discussing our projects.  The BU team broke up into three small groups and met with each Wellesley project team who described their project and tested out some of their initial software.  Later, we held an open discussion where each Wellesley project group discussed the feedback and suggestions they received from earlier in the day.</p>
<p>On June 14, we traveled to Wellesley's campus to continue discussing our projects.  The BU team broke up into three small groups and met with each Wellesley project team who described their project and tested out some of their initial software.  Later, we held an open discussion where each Wellesley project group discussed the feedback and suggestions they received from earlier in the day.</p>
-
<p>Throughout the summer, we have kept in contact with Wellesley to discuss Eugene and Eugenie.  We provided feedback on their existing designs and explained how Eugene is intended to be used and how a visual representation would aid someone who does not understand the Eugene scripting code.  We also provided sample Eugene code for some of our experiments so the Wellesley team could have Eugene code to test their prototypes with.  Members of the Wellesley team came to some of our weekly Eugene meetings with the Eugene team.  They also came to BU to present their paper prototypes of Eugenie and get feedback from the Eugene team and the BU iGEM team.  Furthermore, the BU iGEM team took part in user studies for Eugenie.</p>
+
<p>Throughout the summer, we have kept in contact with Wellesley to discuss Eugene and Eugenie.  We provided feedback on their existing designs and explained how Eugene is intended to be used and how a visual representation would aid someone who does not understand the Eugene scripting code.  We also provided sample Eugene code for some of our experiments so the Wellesley team could have Eugene code to test their prototypes with.  Members of the Wellesley team came to some of our weekly Eugene meetings with the Eugene team.  They also came to BU to present their paper prototypes of Eugenie and get feedback from the Eugene team and the BU iGEM team.  Furthermore, the BU iGEM team took part in user studies for Eugenie.</p></h7>
<p><center><img src = "https://static.igem.org/mediawiki/2013/5/57/Collab.gif"></center></p>
<p><center><img src = "https://static.igem.org/mediawiki/2013/5/57/Collab.gif"></center></p>

Revision as of 13:42, 14 August 2013



iGEM Collaborations

Wellesley Desyne

We are working closely with the Wellesley Desyne software team this year.

On June 3 and 4, we hosted the Wellesley team for a two day workshop. On June 3, the BU team reviewed some fundamental biology and synthetic biology concepts and held a Eugene tutorial. We went over some famous genetic circuits and wrote Eugene scripts for them.

On June 4, both the Wellesley and BU teams presented their iGEM projects to each other and provided constructive feedback. The BU team also held a wet lab tour.

On June 14, we traveled to Wellesley's campus to continue discussing our projects. The BU team broke up into three small groups and met with each Wellesley project team who described their project and tested out some of their initial software. Later, we held an open discussion where each Wellesley project group discussed the feedback and suggestions they received from earlier in the day.

Throughout the summer, we have kept in contact with Wellesley to discuss Eugene and Eugenie. We provided feedback on their existing designs and explained how Eugene is intended to be used and how a visual representation would aid someone who does not understand the Eugene scripting code. We also provided sample Eugene code for some of our experiments so the Wellesley team could have Eugene code to test their prototypes with. Members of the Wellesley team came to some of our weekly Eugene meetings with the Eugene team. They also came to BU to present their paper prototypes of Eugenie and get feedback from the Eugene team and the BU iGEM team. Furthermore, the BU iGEM team took part in user studies for Eugenie.





Corporate Collaborations



We are collecting large quantities of characterization data from our flow cytometry experiments. To analyze this data, we have been working closely with Raytheon BBN Technologies and utilizing their BBN Synthetic Biology Tools.