|
|
| Line 59: |
Line 59: |
| | </div> | | </div> |
| | | | |
| − | <div class="main main-raised" style="margin-top:5%" id="uF_101"> | + | <div class="main main-raised" style="margin-top:5% margin-bottom:3%;" id="uF_101"> |
| | <div class="container"> | | <div class="container"> |
| | <h2>Microfluidics 101</h2> | | <h2>Microfluidics 101</h2> |
| Line 77: |
Line 77: |
| | </div> | | </div> |
| | | | |
| − | <div class="main main-raised" style="margin-top:5%" id ="Chip_Repo">
| |
| − | <div class="container">
| |
| − | <h2>Mars Repository</h2>
| |
| − | <div class="text">
| |
| − | In order to make microfluidics a practical field for synthetic biologists, we created the MARS microfluidic chip repository. This repository hosts nine microfluidic chips that each perform a fundamental synthetic biological protocol. These nine protocols were determined after reaching out to synthetic biologists in the Boston University and iGEM communities. Each chip comes with all the required design files and documentation so that a synthetic biologist could download, manufacture, and test any chip in the repository. The nine chips in the MARS repository are as follows:
| |
| − | </div>
| |
| − | </div>
| |
| | | | |
| − | <div class="container">
| |
| − | <h3>Cellular Lysis | Dylan</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>DNA Digestion | Dinithi</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>Cell Sorting | Dinithi</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>Ligation | Sarah</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>Transformation | Sarah</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>PCR | Sarah</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>Antibiotic Resistance | Dylan</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>Fluorescence Testing | Dinithi</h3>
| |
| − | </div>
| |
| − | <div class="container">
| |
| − | <h3>Cell Culturing | Dylan</h3>
| |
| − | </div>
| |
| − |
| |
| − | <div class="container" >
| |
| − | <div class="text" style="margin-bottom:3%; margin-top:3%;">
| |
| − | For more information regarding each chip, please see our <a href="https://2017.igem.org/Team:BostonU_HW/Archive">MARS repository page</a>
| |
| − | </div>
| |
| − | </div>
| |
| − |
| |
| − | </div>
| |
| − |
| |
| − | <div class="main main-raised" style="margin-top:5%; margin-bottom:3%;" id="FF">
| |
| − | <div class="container">
| |
| − | <h2>Fluid Functionality</h2>
| |
| − | <div class="text">
| |
| − | In order to verify whether or not a microfluidic device is functional, a grading system was developed: the Fluid Functionality Checklist. This fluid functionality system was broken up into two portions: a qualitative checklist and a quantitative analysis.
| |
| − | </div>
| |
| − | </div>
| |
| − |
| |
| − | <div class="container">
| |
| − | <h3>Qualitative Checklist | Dylan, Sarah, and Dinithi</h3>
| |
| − | <div class="text">
| |
| − | The qualitative portion of the fluid functionality checklist consists of various failure modes. These are visual cues that something has gone wrong while running a chip, such as liquid leaking out of a channel or primitive. If a chip passes each of these qualitative checks, it is deemed “fluid functional.” If a chip does not pass each of these qualitative checks, the user moves to the quantitative analysis to determine why the chip failed.
| |
| − | </div>
| |
| − | </div>
| |
| − |
| |
| − | <div class="container">
| |
| − | <h3>Quantitative Analysis | Dylan and Sarah</h3>
| |
| − | <div class="text" style="margin-bottom:3%;">
| |
| − | The quantitative portion of the fluid functionality checklist consists of various quantitative analyses. Two forms of analysis are included in this portion of our evaluation system: physics-based primitive analysis and image processing-based analysis. Physics based analysis helps to determine if a qualitative failure occurred because the incorrect primitive dimensions and/or flow rate were used. Image processing analysis is used to evaluate the functionality of primitives such as mixers. Using these analyses, a user can both determine why their chip failed and evaluate the functionality of key primitives.
| |
| − | </div>
| |
| − | </div>
| |
| − |
| |
| − | </div>
| |
| | </div> | | </div> |
| | | | |
