Difference between revisions of "Team:BostonU/Collaborations"
| Line 327: | Line 327: | ||
<p class="inline-heading-type mainwrap">BostonU_HW Collaboration: Microfluidics</p> | <p class="inline-heading-type mainwrap">BostonU_HW Collaboration: Microfluidics</p> | ||
<p class="body-type mainwrap"> </p> | <p class="body-type mainwrap"> </p> | ||
| − | <p class="body-type mainwrap">We collaborated with the Boston University Hardware team. We followed the protocols they provided us and assembled three types of chips: PCR, digestion and a toehold chip they designed specifically for our project. To test out functionality of the chips we used color dye to imitate the process of biological fluid flowing into the chip. The toehold chip had a relatively serious leakage problem, and air bubbles in the valves blocked the way for color dye to get through. We hypothesize several reasons that explained why the leakage happened and redid some steps to improve the assembly. After several rounds of tests and trials with all the chips, we gave BU Hardware team some feedback about our thoughts of the chips and how it could potentially be improved. We also pointed out steps on the protocols that appeared unclear to us as users and suggested them to explain purposes of certain steps better to make sure users understand why they are important. </p> | + | <p class="body-type mainwrap indented">We collaborated with the Boston University Hardware team. We followed the protocols they provided us and assembled three types of chips: PCR, digestion and a toehold chip they designed specifically for our project. To test out functionality of the chips we used color dye to imitate the process of biological fluid flowing into the chip. The toehold chip had a relatively serious leakage problem, and air bubbles in the valves blocked the way for color dye to get through. We hypothesize several reasons that explained why the leakage happened and redid some steps to improve the assembly. After several rounds of tests and trials with all the chips, we gave BU Hardware team some feedback about our thoughts of the chips and how it could potentially be improved. We also pointed out steps on the protocols that appeared unclear to us as users and suggested them to explain purposes of certain steps better to make sure users understand why they are important. </p> |
<p class="body-type mainwrap"> </p> | <p class="body-type mainwrap"> </p> | ||
<div class="carousel mainwrap body-type"> | <div class="carousel mainwrap body-type"> | ||
| Line 342: | Line 342: | ||
<div class="counter" count="5"> / 5</div> | <div class="counter" count="5"> / 5</div> | ||
</div> | </div> | ||
| + | <p class="body-type mainwrap"> </p> | ||
</div> | </div> | ||
<div id="backgroundimage2"><div class="background-gradient-up"> | <div id="backgroundimage2"><div class="background-gradient-up"> | ||
Revision as of 05:33, 24 October 2017
COLLABORATIONS
BostonU_HW Collaboration: Microfluidics
We collaborated with the Boston University Hardware team. We followed the protocols they provided us and assembled three types of chips: PCR, digestion and a toehold chip they designed specifically for our project. To test out functionality of the chips we used color dye to imitate the process of biological fluid flowing into the chip. The toehold chip had a relatively serious leakage problem, and air bubbles in the valves blocked the way for color dye to get through. We hypothesize several reasons that explained why the leakage happened and redid some steps to improve the assembly. After several rounds of tests and trials with all the chips, we gave BU Hardware team some feedback about our thoughts of the chips and how it could potentially be improved. We also pointed out steps on the protocols that appeared unclear to us as users and suggested them to explain purposes of certain steps better to make sure users understand why they are important.
