"
Team:BostonU/Collaborations
From 2013.igem.org
| (21 intermediate revisions not shown) | |||
| Line 4: | Line 4: | ||
<h2>iGEM Collaborations</h2> | <h2>iGEM Collaborations</h2> | ||
<h5>Wellesley Desyne</h5> | <h5>Wellesley Desyne</h5> | ||
| - | |||
<ul> | <ul> | ||
<h7> | <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>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>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. 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.</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>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></h7 | + | <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" | + | <p><center><img src = "https://static.igem.org/mediawiki/2013/5/57/Collab.gif" width="400px"></center></p> |
| - | + | ||
<br> | <br> | ||
| + | <br></ul> | ||
<h5>Purdue Biomakers</h5> | <h5>Purdue Biomakers</h5> | ||
| - | |||
<ul> | <ul> | ||
| - | <h7> | + | <h7><p>We are also working closely with the <a href="https://2013.igem.org/Team:Purdue">Purdue Biomakers</a> team this year to work on a standardized data sheet.</p> |
| + | <p>While working from the 2012 BostonU Team’s start on the Data Sheet app, we learned that the Purdue Biomaker’s team had a very similar concept in mind for creating a <a href="https://2013.igem.org/Team:Purdue/Human_Practices/iGEM_Characterization_Standard">standardized way of sharing information</a> about parts. </p> | ||
| - | < | + | <p>Early in June, we contacted the Purdue team to let them know that much of the groundwork has already been laid by the 2012 team here at BostonU. We shared our rough draft of the data sheet format with them and inquired if they had any plans to write software to implement the new data sheet. |
| - | + | ||
| - | <p>< | + | By July, the Purdue replied to us that the would like to use our data sheet draft as the basis for the project. Purdue’s team members had been collecting survey data from over 75 teams around the world to find out what information they thought was essential to a data sheet and showed them a version of our draft. Purdue also video chatted with several teams to demonstrate what the data sheet’s functionality and ask for more feedback. We also video chatted with Purdue to discuss more changes to the data sheet format and how we wanted to propose that we would build a web app to create the datasheets. Each team began to develop a simple mock up of what we envisioned for the user interface and shared them with each other.</p> |
| + | |||
| + | <p>In early August, Thomas flew out to Indiana to visit Charlotte Hoo and Chris Thompson from the Purdue team to show them our progress and plans on the web app. At the meeting, we compared programs at talked about what the final product might look like. Both teams mutually agreed that the BostonU team would handle all of the software side of things while Purdue, with their extensive network of team contacts, would continue to refine some of the specific assay data fields for the data sheet and work on distribution and promotion of the new standard. Furthermore, one of our other collaborators, Jake Beal of BBN Technologies heard about our collaboration through iGEM HQ and offered to give some advice on the information that would be needed in the flow cytometry section of the data sheet. | ||
| + | |||
| + | |||
| + | <p><center><img src = "https://static.igem.org/mediawiki/2013/8/87/Purdue2.gif" height="300px"></center></p> | ||
| + | |||
| + | </ul> | ||
| + | <p></p></h7> | ||
<br> | <br> | ||
<br> | <br> | ||
| Line 35: | Line 39: | ||
<img src="https://static.igem.org/mediawiki/2013/3/35/Bbn.jpg" width="200px"> | <img src="https://static.igem.org/mediawiki/2013/3/35/Bbn.jpg" width="200px"> | ||
<br> | <br> | ||
| - | < | + | <h7><ul> |
| - | <ul | + | <p>We are collecting large quantities of characterization data from our flow cytometry experiments. To analyze this data, we have been working with BBN Technologies and utilizing their <a href = "https://synbiotools.bbn.com/">BBN Synthetic Biology Tools</a>. These tools came out of the <a href="http://pubs.acs.org/doi/abs/10.1021/sb300030d">TASBE</a> project, which was a collaborative effort between BBN Technologies, the Densmore Lab at Boston Univeristy, and the Weiss Lab at MIT.</p> |
| - | <p | + | <p>We have worked closely with Dr. Jacob Beal this summer to characterize constitutively expressed and repressible circuits. Specifically, Dr. Beal helped us design positive controls in order to successfully use the TASBE tools for quantitative fluorescence analysis (see <a href="https://2013.igem.org/Team:BostonU/Data">Data Collected</a>).</h7> |
| + | <br></ul> | ||
<br> | <br> | ||
| - | + | <h8>References</h8> | |
| + | <h3> | ||
| + | [1] Beal et al. (2012) "An End-to-End Workflow for Engineering of Biological Networks from High-Level Specifications." <i>ACS Synthetic Biology</i>, 2012, 1 (8), pp 317–331. DOI: 10.1021/sb300030d<br> | ||
| + | </h3> | ||
<br> | <br> | ||
<br> | <br> | ||
</html> | </html> | ||
Latest revision as of 03:04, 28 September 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.
Purdue Biomakers
We are also working closely with the Purdue Biomakers team this year to work on a standardized data sheet.
While working from the 2012 BostonU Team’s start on the Data Sheet app, we learned that the Purdue Biomaker’s team had a very similar concept in mind for creating a standardized way of sharing information about parts.
Early in June, we contacted the Purdue team to let them know that much of the groundwork has already been laid by the 2012 team here at BostonU. We shared our rough draft of the data sheet format with them and inquired if they had any plans to write software to implement the new data sheet. By July, the Purdue replied to us that the would like to use our data sheet draft as the basis for the project. Purdue’s team members had been collecting survey data from over 75 teams around the world to find out what information they thought was essential to a data sheet and showed them a version of our draft. Purdue also video chatted with several teams to demonstrate what the data sheet’s functionality and ask for more feedback. We also video chatted with Purdue to discuss more changes to the data sheet format and how we wanted to propose that we would build a web app to create the datasheets. Each team began to develop a simple mock up of what we envisioned for the user interface and shared them with each other.
In early August, Thomas flew out to Indiana to visit Charlotte Hoo and Chris Thompson from the Purdue team to show them our progress and plans on the web app. At the meeting, we compared programs at talked about what the final product might look like. Both teams mutually agreed that the BostonU team would handle all of the software side of things while Purdue, with their extensive network of team contacts, would continue to refine some of the specific assay data fields for the data sheet and work on distribution and promotion of the new standard. Furthermore, one of our other collaborators, Jake Beal of BBN Technologies heard about our collaboration through iGEM HQ and offered to give some advice on the information that would be needed in the flow cytometry section of the data sheet.
Corporate Collaborations
We are collecting large quantities of characterization data from our flow cytometry experiments. To analyze this data, we have been working with BBN Technologies and utilizing their BBN Synthetic Biology Tools. These tools came out of the TASBE project, which was a collaborative effort between BBN Technologies, the Densmore Lab at Boston Univeristy, and the Weiss Lab at MIT.
We have worked closely with Dr. Jacob Beal this summer to characterize constitutively expressed and repressible circuits. Specifically, Dr. Beal helped us design positive controls in order to successfully use the TASBE tools for quantitative fluorescence analysis (see Data Collected).
