Difference between revisions of "Team:BostonU HW/Attributions"

Line 163: Line 163:
 
<area id="lfr" shape="rect" coords="569,75,656,155" style="outline:none;" onclick='$("#LFRModal").modal();' />
 
<area id="lfr" shape="rect" coords="569,75,656,155" style="outline:none;" onclick='$("#LFRModal").modal();' />
 
<area id="ucf" shape="rect" coords="678,24,912,188" style="outline:none;" onclick='$("#UCFModal").modal();' />
 
<area id="ucf" shape="rect" coords="678,24,912,188" style="outline:none;" onclick='$("#UCFModal").modal();' />
−
<area id="mintSyntax" shape="rect" coords="980,19,1083,86" style="outline:none;" onclick='$("#mintSyntaxModal").modal("show");' />
+
<area id="mintSyntax" shape="rect" coords="980,19,1083,86" style="outline:none;" onclick='$("#mintModal").modal("show");' />
 
<area id="3duf" shape="rect" coords="996,128,1094,179" style="outline:none;" onclick='$("#3dufModal").modal();' />
 
<area id="3duf" shape="rect" coords="996,128,1094,179" style="outline:none;" onclick='$("#3dufModal").modal();' />
 
<area id="mDevice" shape="rect" coords="338,215,527,272" style="outline:none;" onclick='$("#mDeviceModal").modal();' />
 
<area id="mDevice" shape="rect" coords="338,215,527,272" style="outline:none;" onclick='$("#mDeviceModal").modal();' />
Line 247: Line 247:
 
</div>
 
</div>
  
−
<div class="modal fade" data-backdrop="false" id="mintSyntaxModal" role="dialog">
+
<div class="modal fade" data-backdrop="false" id="mintModal" role="dialog">
 
     <div class="modal-dialog">
 
     <div class="modal-dialog">
 
       <!-- Modal content-->
 
       <!-- Modal content-->
Line 265: Line 265:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> Liquid Flow Relations are specifications of inputs and outputs. It was created by R. Sanka. </h4>
+
           <h4> 3duf is a microfluidics CAD tool. It allows the user to draw our their microfluidic device with channels, valves and ports. It was created by J. Lippai. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 277: Line 277:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> UCFs are files that define what each operation in the liquid flow relation means. For instance, what does '+' mean in a microfluidic context? It was created by R. Sanka. </h4>
+
           <h4> The device visual preview provides the user with a sample view of what their microfluidic device will look like during developement. This has been done by the iGEM team. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 289: Line 289:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> MINT is a microfluidic netlist language, which creates abstraction from the specification to the design. It was created by R. Sanka. </h4>
+
           <h4> uShroom Mapper is a.... It was created by the iGEM team. </h4>
−
        </div>
+
−
    </div>
+
−
  </div>
+
−
</div>
+
−
 
+
−
<div class="modal fade" data-backdrop="false" id="mintModal" role="dialog">
+
−
    <div class="modal-dialog">
+
−
      <!-- Modal content-->
+
−
      <div class="modal-content">
+
−
        <div class="modal-header" style="padding:35px 50px;">
+
−
          <button type="button" class="close" data-dismiss="modal">&times;</button>
+
−
          <h4> Liquid Flow Relations are specifications of inputs and outputs. It was created by R. Sanka. </h4>
+
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 313: Line 301:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> UCFs are files that define what each operation in the liquid flow relation means. For instance, what does '+' mean in a microfluidic context? It was created by R. Sanka. </h4>
+
           <h4> NetSynth is... It was created by R. Sanka. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 325: Line 313:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> MINT is a microfluidic netlist language, which creates abstraction from the specification to the design. It was created by R. Sanka. </h4>
+
           <h4> Fluigi Place and Route tool takes in the three inputs of rules and specifications, and uses the information to best place and route the channels and valves of the microfluidic device. It was created by R. Sanka. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 337: Line 325:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> Liquid Flow Relations are specifications of inputs and outputs. It was created by R. Sanka. </h4>
+
           <h4> Design rules are rules related to how microfluidics work and how fluid flows through. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 349: Line 337:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> UCFs are files that define what each operation in the liquid flow relation means. For instance, what does '+' mean in a microfluidic context? It was created by R. Sanka. </h4>
+
           <h4> Performance rules are those related to how the route can be best optimized to what the user has provided. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 361: Line 349:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> MINT is a microfluidic netlist language, which creates abstraction from the specification to the design. It was created by R. Sanka. </h4>
+
           <h4> Hardware constraints include the size of the available chip, the size of the drill bit (which corresponds to the size of the channels), and so on. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 373: Line 361:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> Liquid Flow Relations are specifications of inputs and outputs. It was created by R. Sanka. </h4>
+
           <h4> Parametric Hardware is a pump setup that can easily be altered to adapt to any size. It was created by the iGEM team. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 385: Line 373:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> UCFs are files that define what each operation in the liquid flow relation means. For instance, what does '+' mean in a microfluidic context? It was created by R. Sanka. </h4>
+
           <h4> The hardware setup is the pump array with the arduino and servos. This layout was created by the iGEM team. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 397: Line 385:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> MINT is a microfluidic netlist language, which creates abstraction from the specification to the design. It was created by R. Sanka. </h4>
+
           <h4> This is the microfluidic chip through which fluids flow. It can be made using a CNC mill, and was designed and created by A. Lashkaripour. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 409: Line 397:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> MINT is a microfluidic netlist language, which creates abstraction from the specification to the design. It was created by R. Sanka. </h4>
+
           <h4> Makerfluidics is the back-end to linking other programs to the graphical user interface. It was made by R. Silva. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
Line 421: Line 409:
 
         <div class="modal-header" style="padding:35px 50px;">
 
         <div class="modal-header" style="padding:35px 50px;">
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
 
           <button type="button" class="close" data-dismiss="modal">&times;</button>
−
           <h4> MINT is a microfluidic netlist language, which creates abstraction from the specification to the design. It was created by R. Sanka. </h4>
+
           <h4> The graphical user interface controls the entire workflow from specify to design to build. It was made by the iGEM Team. </h4>
 
         </div>
 
         </div>
 
     </div>
 
     </div>

Revision as of 21:58, 30 June 2016

Attributions



Our Advisor

Douglas Densmore: dougd@bu.edu



Our Mentors



Ryan Silva

Electircal Engineering

rjsilva@bu.edu


Radhakrishna Sanka

Electrical and Computer Engineering

sanka@bu.edu


Joshua Lippai

Electrical and Computer Engineering

jlippai@bu.edu




Ali Lashkaripour

Biomedical Engineering

lashkari@bu.edu


Luis Ortiz

Molecular Biology, Cell Biology & Biochemistry (MCBB)

lortiz15@bu.edu


Marilene Pavan

Molecular and Synthetic Biologyy

mapavan@bu.edu




Divya Israni

Biomedical Engineering with B.S. Bioengineering

disrani@bu.edu



Our Workflow

Please click on individual components to see details and attributions.




Thank you to our sponsors for their support





Copyright © Boston University Hardware Team Website 2016