Difference between revisions of "Team:BostonU HW/HP/Gold Integrated"

Line 82: Line 82:
 
</div>
 
</div>
  
<div class="main main-raised" id="Community">
+
<div class="main main-raised">
 
<div class="container text_box">
 
<div class="container text_box">
 
<h2>Biological Design Center and iGEM Outreach</h2>
 
<h2>Biological Design Center and iGEM Outreach</h2>
Line 93: Line 93:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Lysis">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Lysis">
<button class="btn btn-round btn-danger">Cell Lysis</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">Cell Lysis</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 99: Line 99:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Digestion">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Digestion">
<button class="btn btn-round btn-danger">DNA Digestion</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">DNA Digestion</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 105: Line 105:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Ligation">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Ligation">
<button class="btn btn-round btn-danger">Ligation</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">Ligation</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 111: Line 111:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Transformation">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Transformation">
<button class="btn btn-round btn-danger">Transformation</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">Transformation</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 119: Line 119:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/PCR">
 
<a href="https://2017.igem.org/Team:BostonU_HW/PCR">
<button class="btn btn-round btn-danger">PCR</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">PCR</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 125: Line 125:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Lysis">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Lysis">
<button class="btn btn-round btn-danger">Fluorescence Testing</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">Fluorescence Testing</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 131: Line 131:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Antibiotic">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Antibiotic">
<button class="btn btn-round btn-danger">Antibiotic Resistance Testing</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">Antibiotic Resistance Testing</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 137: Line 137:
 
<li>
 
<li>
 
<a href="https://2017.igem.org/Team:BostonU_HW/Culturing">
 
<a href="https://2017.igem.org/Team:BostonU_HW/Culturing">
<button class="btn btn-round btn-danger">Cell Culturing</button>
+
<button class="btn btn-round btn-danger" style="margin:0% !important;">Cell Culturing</button>
 
</a>
 
</a>
 
</li>
 
</li>
Line 160: Line 160:
 
</div>
 
</div>
  
<div class="main main-raised" id="Community">
+
<div class="main main-raised">
 
<div class="container text_box">
 
<div class="container text_box">
<h2>Biological Design Center and iGEM Outreach</h2>
+
<h2>Phenomyx</h2>
 
<div class="row">
 
<div class="row">
 
<div class="text_section" style="margin-bottom:3%;">
 
<div class="text_section" style="margin-bottom:3%;">
 
<div class="text">
 
<div class="text">
In order to determine what would make microfluidics more practical and accessible for synthetic biologists we reached out to the Biological Design Center at Boston University. The BDC promotes collaboration between scientists in order to create new biological innovations. We asked the BDC researchers what types of biological protocols are performed day-to-day in the lab. Based on their feedback we were able to identify eight common protocols performed by synthetic biologists:
+
During the course of the Fall semester the team also had to opportunity to tour Phenomyx, a microfluidics startup located at LabCentral in Boston. The tour was led by Salil Desai, their founder and Chief Technology Officer, who took us through their fabrication and testing space. During the course of the tour we were able to learn from his industry experience in microfluidic devices.
<ol>
+
<br>
<div class="col-md-5 col-md-offset-1" style="margin-bottom:3%;">
+
<br>
<li>
+
While discussing our fluid functionality checklist we were able to discuss our quantitative and qualitative metrics in some detail. A key point of the discussion was the importance of utilizing general metrics, instead of protocol or design specific metrics, when grading a chip. This way we can ensure that our system can be applied to chips at large without being specific to individual designs. This advice has been integral as we ensured that our finalized protocol used metric we were able to apply to any device design. The possibility of integrating our checklist into a software system was also pitched as a possible progression of MARS. Although we were unable to meet this goal for 2017, it provides an exciting direction for future iGEM teams to build on our project.
<a href="https://2017.igem.org/Team:BostonU_HW/Lysis">
+
</div>
<button class="btn btn-round btn-danger">Cell Lysis</button>
+
</div>
</a>
+
</div>
</li>
+
</div>
 +
</div>
  
<li>
+
<div class="main main-raised">
<a href="https://2017.igem.org/Team:BostonU_HW/Digestion">
+
<div class="container text_box">
<button class="btn btn-round btn-danger">DNA Digestion</button>
+
<h2>Black Hole Lab</h2>
</a>
+
<div class="row">
</li>
+
<div class="text_section" style="margin-bottom:3%;">
 +
<div class="text">
 +
Over the summer we were in contact with Black Hole Lab who manufacture plug and play microfluidics for researchers. As we were in the beginning stages of fabrication, we had many questions for them regarding manufacturing processes and what standards they recommended in order to ensure quality control. Although they were unable to provide us with “industry standards” to utilise, Black Hole Lab advised us to build our checklist around our fabrication method. Many of the suggestions they made such as:
 +
<ul>
 +
<li>Checking the milled dimensions of primitives and channels </li>
 +
<li>Testing the maximum pressure chips can withstand</li>
 +
<li>Checking if the chip leaks or the seal breaks</li>
 +
</ul>
 +
were integrated into our preliminary checklists. In fact, testing for a channel’s maximum pressure and checking for seal leaks became two of the key quantitative and qualitative pillars in our final Fluid Functionality Checklist. To see how these were integrated into our Fluid Functionality Checklist, please click here.
 +
</div>
 +
</div>
 +
</div>
 +
</div>
 +
</div>
  
<li>
+
<div class="main main-raised">
<a href="https://2017.igem.org/Team:BostonU_HW/Ligation">
+
<div class="container text_box">
<button class="btn btn-round btn-danger">Ligation</button>
+
<h2>Blacktrace - Dolomite</h2>
</a>
+
<div class="row">
</li>
+
<div class="text_section" style="margin-bottom:3%;">
 
+
<div class="text">
<li>
+
Blacktrace is a company involved with designing and manufacturing modular microfluidics for research and industry. Our conversation with them revolved around how they approached quality control, as well as what types of problems they encountered when handing off microfluidics to consumers.
<a href="https://2017.igem.org/Team:BostonU_HW/Transformation">
+
<button class="btn btn-round btn-danger">Transformation</button>
+
</a>
+
</li>
+
</div>
+
 
+
<div class="col-md-5 col-md-offset-1" style="margin-bottom:3%;">
+
<li>
+
<a href="https://2017.igem.org/Team:BostonU_HW/PCR">
+
<button class="btn btn-round btn-danger">PCR</button>
+
</a>
+
</li>
+
 
+
<li>
+
<a href="https://2017.igem.org/Team:BostonU_HW/Lysis">
+
<button class="btn btn-round btn-danger">Fluorescence Testing</button>
+
</a>
+
</li>
+
 
+
<li>
+
<a href="https://2017.igem.org/Team:BostonU_HW/Antibiotic">
+
<button class="btn btn-round btn-danger">Antibiotic Resistance Testing</button>
+
</a>
+
</li>
+
 
+
<li>
+
<a href="https://2017.igem.org/Team:BostonU_HW/Culturing">
+
<button class="btn btn-round btn-danger">Cell Culturing</button>
+
</a>
+
</li>
+
</div>
+
 
+
</ol>
+
 
<br>
 
<br>
These eight common protocols informed both the layout of our MARS Repository into Isolation, Modification, and Quantification, as well as the chips within it. Of our nine MARS chips, eight were designed to each perform one of these synbio protocols.
 
 
<br>
 
<br>
 +
During our conversation regarding educational materials provided to first time users, we were able to ask what key areas they focused on the most. When handing their products over to consumers, Blacktrace noted that they spent the most time covering thorough cleaning of microfluidic devices. When receiving a chip for the first time, many users underestimated the impact a tiny blockage or strand of hair can have. Although we cannot offer a two day training seminar for researchers using our chips, this feedback led to us including the “Cleaning” tutorial video and protocol in Microfluidics 101. To see these protocols, please click here.
 
<br>
 
<br>
We also reached out to the iGEM community via a poll; to see this poll, click here. (LINK) The purpose of this poll was to gauge how much the iGEM community knows about microfluidics, what procedures they perform every day in the lab, and what would get them interested in microfluidics. In total, we received 42 responses from teams all across the world. The results from this poll are summarised below.
 
 
<br>
 
<br>
<br>
+
We were also able to discuss their quality control motto which is to avoid testing every chip and instead ensure their fabrication process is airtight. Although this did not feed into our Fluid Functionality checklist directly, it inspired us to broaden the MARS archive through tutorial and how-to videos. Through this we will be able to streamline and simplify our workflow in order to reduce the number of errors future users experience.
POLLLLLLLLLL
+
<br>
+
<br>
+
These results validated our educational components of MARS. The introduction to microfluidics and video tutorials serve to educate the iGEM and greater synbio community about what microfluidics are and how to use them. Furthermore, this poll validated our choice of nine synthetic biology protocols to move onto microfluidic devices housed in the MARS archive.
+
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 20:19, 29 October 2017

BostonU_HW

Gold Human Practices

Integrating Our Microfluidics Knowledge

As our work on MARS progressed, many of the interactions we engaged in over the Summer had a direct impact on the project. Specific areas that were developed and modified as a result of our synthetic biologist and industry interactions are influencing the structure and content of our MARS chip archive, increasing accessibility to researchers through Microfluidics 101, and building the fluid functionality checklist. Through integrating the feedback, comments and advice received from various sources, we were able to significantly improve and refine MARS as a whole.

Biological Design Center and iGEM Outreach

In order to determine what would make microfluidics more practical and accessible for synthetic biologists we reached out to the Biological Design Center at Boston University. The BDC promotes collaboration between scientists in order to create new biological innovations. We asked the BDC researchers what types of biological protocols are performed day-to-day in the lab. Based on their feedback we were able to identify eight common protocols performed by synthetic biologists:

These eight common protocols informed both the layout of our MARS Repository into Isolation, Modification, and Quantification, as well as the chips within it. Of our nine MARS chips, eight were designed to each perform one of these synbio protocols.

We also reached out to the iGEM community via a poll; to see this poll, click here. (LINK) The purpose of this poll was to gauge how much the iGEM community knows about microfluidics, what procedures they perform every day in the lab, and what would get them interested in microfluidics. In total, we received 42 responses from teams all across the world. The results from this poll are summarised below.

POLLLLLLLLLL

These results validated our educational components of MARS. The introduction to microfluidics and video tutorials serve to educate the iGEM and greater synbio community about what microfluidics are and how to use them. Furthermore, this poll validated our choice of nine synthetic biology protocols to move onto microfluidic devices housed in the MARS archive.

Phenomyx

During the course of the Fall semester the team also had to opportunity to tour Phenomyx, a microfluidics startup located at LabCentral in Boston. The tour was led by Salil Desai, their founder and Chief Technology Officer, who took us through their fabrication and testing space. During the course of the tour we were able to learn from his industry experience in microfluidic devices.

While discussing our fluid functionality checklist we were able to discuss our quantitative and qualitative metrics in some detail. A key point of the discussion was the importance of utilizing general metrics, instead of protocol or design specific metrics, when grading a chip. This way we can ensure that our system can be applied to chips at large without being specific to individual designs. This advice has been integral as we ensured that our finalized protocol used metric we were able to apply to any device design. The possibility of integrating our checklist into a software system was also pitched as a possible progression of MARS. Although we were unable to meet this goal for 2017, it provides an exciting direction for future iGEM teams to build on our project.

Black Hole Lab

Over the summer we were in contact with Black Hole Lab who manufacture plug and play microfluidics for researchers. As we were in the beginning stages of fabrication, we had many questions for them regarding manufacturing processes and what standards they recommended in order to ensure quality control. Although they were unable to provide us with “industry standards” to utilise, Black Hole Lab advised us to build our checklist around our fabrication method. Many of the suggestions they made such as:
  • Checking the milled dimensions of primitives and channels
  • Testing the maximum pressure chips can withstand
  • Checking if the chip leaks or the seal breaks
were integrated into our preliminary checklists. In fact, testing for a channel’s maximum pressure and checking for seal leaks became two of the key quantitative and qualitative pillars in our final Fluid Functionality Checklist. To see how these were integrated into our Fluid Functionality Checklist, please click here.

Blacktrace - Dolomite

Blacktrace is a company involved with designing and manufacturing modular microfluidics for research and industry. Our conversation with them revolved around how they approached quality control, as well as what types of problems they encountered when handing off microfluidics to consumers.

During our conversation regarding educational materials provided to first time users, we were able to ask what key areas they focused on the most. When handing their products over to consumers, Blacktrace noted that they spent the most time covering thorough cleaning of microfluidic devices. When receiving a chip for the first time, many users underestimated the impact a tiny blockage or strand of hair can have. Although we cannot offer a two day training seminar for researchers using our chips, this feedback led to us including the “Cleaning” tutorial video and protocol in Microfluidics 101. To see these protocols, please click here.

We were also able to discuss their quality control motto which is to avoid testing every chip and instead ensure their fabrication process is airtight. Although this did not feed into our Fluid Functionality checklist directly, it inspired us to broaden the MARS archive through tutorial and how-to videos. Through this we will be able to streamline and simplify our workflow in order to reduce the number of errors future users experience.