Team:EPF Lausanne/PolicyPractice
From 2014.igem.org
(25 intermediate revisions not shown) | |||
Line 12: | Line 12: | ||
<!-- MENU --> | <!-- MENU --> | ||
- | <nav class="navbar navbar-default" role="navigation"> | + | <nav class="navbar navbar-default navbar_alt" role="navigation"> |
<div class="container-fluid"> | <div class="container-fluid"> | ||
<!-- Brand and toggle get grouped for better mobile display --> | <!-- Brand and toggle get grouped for better mobile display --> | ||
Line 31: | Line 31: | ||
<div class="nav-collapse"> | <div class="nav-collapse"> | ||
<ul class="nav"> | <ul class="nav"> | ||
- | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne">Home</a></li> | |
<li class="dropdown"> | <li class="dropdown"> | ||
- | <a href=" | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown">Project <span class="caret"></span></a> |
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
- | <li | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Overview">Overview</a></li> |
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Envelope_stress_responsive_bacteria">Stress Responsive Bacteria</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Yeast">Osmo Responsive Yeast</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Microfluidics">Microfluidics</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Hardware">Hardware</a></li> | ||
<li><a href="https://2014.igem.org/Team:EPF_Lausanne/Applications">Applications</a></li> | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Applications">Applications</a></li> | ||
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/HumanPractice">Human Practices</a></li> | + | |
- | + | ||
+ | <!-- <li><a href="https://2014.igem.org/Team:EPF_Lausanne/HumanPractice">Human Practices</a></li> | ||
+ | --> </ul> | ||
</li> | </li> | ||
- | + | ||
- | <a href=" | + | <li class="dropdown"> |
+ | <a href="#" class="dropdown-toggle" data-toggle="dropdown">Achievements <span class="caret"></span></a> | ||
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/ | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Results">Results</a></li> |
- | + | ||
<li><a href="https://2014.igem.org/Team:EPF_Lausanne/Data">Data</a></li> | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Data">Data</a></li> | ||
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/ | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Judging">Judging</a></li> |
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Parts">Parts</a></li> | ||
</ul> | </ul> | ||
+ | </li> | ||
+ | |||
+ | <li class="dropdown"> | ||
+ | <a href="#" class="dropdown-toggle active" data-toggle="dropdown">Policy & Practices <span class="caret"></span></a> | ||
+ | <ul class="dropdown-menu" role="menu"> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/HumanPractice">Human Practices</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Safety">Bio Safety</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/PolicyPractice" class="active">Metafluidics</a></li> | ||
+ | |||
+ | <!-- <li><a href="https://2014.igem.org/Team:EPF_Lausanne/HumanPractice">Human Practices</a></li> | ||
+ | --> </ul> | ||
</li> | </li> | ||
<li class="dropdown"> | <li class="dropdown"> | ||
- | <a href=" | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown">Notebook <span class="caret"></span></a> |
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Team"> | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Notebook/Bacteria">Bacteria</a></li> |
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/ | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Notebook/Yeast">Yeast</a></li> |
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Notebook/Microfluidics">Microfluidics</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Protocol">Protocols</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
<li class="dropdown"> | <li class="dropdown"> | ||
- | <a href=" | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown">Team <span class="caret"></span></a> |
<ul class="dropdown-menu" role="menu"> | <ul class="dropdown-menu" role="menu"> | ||
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/ | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Notebook">Timeline</a></li> |
- | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/ | + | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Team">Meet us!</a></li> |
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Attributions">Attributions</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Acknowledgments">Acknowledgments</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
Line 77: | Line 99: | ||
<!-- ABSTRACT --> | <!-- ABSTRACT --> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | < | + | <div class="container"> |
+ | <div class="box" id="boxbread"> | ||
+ | <ol class="breadcrumb breadcrumb-arrow"> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne"><i class="glyphicon glyphicon-home"></i> Home</a></li> | ||
+ | <li class="dropdown"><a href="#" class="dropdown-toggle active" data-toggle="dropdown"><i class="glyphicon glyphicon-briefcase"></i> Policy & Practices <b class="caret"></b></a> | ||
+ | <ul class="dropdown-menu" role="menu"> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/HumanPractice">Human Practices</a></li> | ||
+ | <li><a href="https://2014.igem.org/Team:EPF_Lausanne/Safety">Bio Safety</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li><span><i class="glyphicon glyphicon-file"></i> Metafluidics</span></li> | ||
+ | </ol> | ||
+ | </div> | ||
- | < | + | <div class="row"> |
- | < | + | <div class="col col-md-9"> |
- | |||
- | |||
- | |||
+ | <div class="whitebg box"> | ||
- | <h3>Structure of the Microfluidic Parts Registry</h3> | + | <h1 class="cntr">METAFLUIDICS</h1> |
+ | <br/> | ||
+ | <h2>Microfluidic Chip Registry</h2> | ||
+ | <p>While designing and making our new microfluidic chips, the 2014 iGEM EPFL team realized that it would be a great to have a microfluidic iGEM registry analogue to the current iGEM DNA Parts registry. Similarly to BioBricks, microfluidic chips also have several levels of structures that can be combined and reused as building blocks.</p> | ||
+ | |||
+ | <p>Creating a database of these parts would contribute to the already enormous library of DNA parts, and would moreover give a help all the iGEM teams looking into integrating microfluidics in their projects.</p> | ||
+ | |||
+ | <p>As a microfluidic registry isn’t available, we created this one one with as template the DNA parts registry to make this novel registry's integration easy. We kept in mind that the registry will develop itself, just as chip designs will integrate new parts, so we designed a nomenclature system enabling both horizontal (adding types of parts) and vertical (adding sub-parts) expansion.</p> | ||
+ | |||
+ | |||
+ | |||
+ | <h3 id="structure">Structure of the Microfluidic Parts Registry</h3> | ||
- | <p> | + | <p>The suggested system for structuring the novel microfluidic parts registry is modeled as seen bellow. |
+ | Each box represents each type of reusable microfluidic design or protocol. <br/> | ||
+ | There is the Microfluidic Chip Design repository, which contains the pages where each team's designs are documented. <br/> | ||
+ | There is the Mask & Wafer Protocol repository, which contains the detailed protocols to make masks and wafers. <br/> | ||
+ | The third white box corresponds to the third repository, the Chip Fabrication Protocol repository. It contains the protocols to make the chips once the wafers are made. <br/> | ||
+ | Lastly, there is the Usage Protocol & Software repository, which contains the chip usage protocols and any software created to automatically control the chip. <br/> | ||
+ | The related pages in each repository are linked to one another in the following way: the Chip Design page will link to its Mask and Wafer Protocol, its Chip Fabrication Protocol, and to its Usage Protocol & Software page. In the graph below, links are represented by red arrows.</p> | ||
+ | <p>This design aims to blend in the current registry while maintaining a uniform structure of microfluidic reusable parts. </p> | ||
<div class="cntr"> | <div class="cntr"> | ||
<a href="https://static.igem.org/mediawiki/2014/f/f3/Screen_Shot_2014-10-13_at_22.21.03_.png" data-lightbox="img1" data-title="Classification of microfluidic parts"> | <a href="https://static.igem.org/mediawiki/2014/f/f3/Screen_Shot_2014-10-13_at_22.21.03_.png" data-lightbox="img1" data-title="Classification of microfluidic parts"> | ||
- | <img src="https://static.igem.org/mediawiki/2014/f/f3/Screen_Shot_2014-10-13_at_22.21.03_.png"></a> | + | <img src="https://static.igem.org/mediawiki/2014/f/f3/Screen_Shot_2014-10-13_at_22.21.03_.png" width="100%"></a> |
</div> | </div> | ||
- | <p>As such a structure needs a different submission page than the ones already existing, we designed it. You can find a sample submission page for microfluidic parts <a | + | <p>As such a structure needs a different submission page than the ones already existing, we designed it. You can find a sample submission page for microfluidic parts <a target="_blank" href="https://static.igem.org/mediawiki/2014/9/9d/Samplesubmission.png">here</a>. A sample page of a <a target="_blank" href="https://static.igem.org/mediawiki/2014/f/fa/Sampleinfo.png">Microfluidic Chip Information Page</a> was also made.</p> |
- | < | + | <h4>Chip Design Page</h4> |
- | <ul | + | <p>Similar to the DNA BioBricks pages, the Microfluidic Chip Design page includes: |
- | <li>A short description of the chip, its intended purpose</li> | + | <ul> |
- | <li>The design file of the chip*</li> | + | <li><p>A short description of the chip, its intended purpose</p></li> |
- | <li>An information page with the owner, the part type, a list of components, the intended material...</li> | + | <li><p>The design file of the chip*</p></li> |
- | <li>Links to the other parts related to this one (protocols used on this chip)</li> | + | <li><p>An information page with the owner, the part type, a list of components, the intended material...</p></li> |
+ | <li><p>Links to the other parts related to this one (protocols used on this chip)</p></li> | ||
</ul> | </ul> | ||
<p> * To make that possible, the iGEM server has to allow uploads of design files such as: .gds, .dxf, .cif, and .dvg.<p> | <p> * To make that possible, the iGEM server has to allow uploads of design files such as: .gds, .dxf, .cif, and .dvg.<p> | ||
+ | |||
+ | <h4>Mask & Wafer Protocol Page</h4> | ||
<p>The Mask & Wafer Protocol (MWP) pages consist of the detailed procedures of mask & wafer fabrication. They include a list of instruments and materials, and the exact procedure, organized as a series of bullet points.</p> | <p>The Mask & Wafer Protocol (MWP) pages consist of the detailed procedures of mask & wafer fabrication. They include a list of instruments and materials, and the exact procedure, organized as a series of bullet points.</p> | ||
+ | |||
+ | <h4>Chip Fabrication Protocol Page</h4> | ||
<p>The Chip Fabrication Protocol (CFP) pages are similar to the Mask & Wafer Protocol pages, as they are highly detailed and specific.</p> | <p>The Chip Fabrication Protocol (CFP) pages are similar to the Mask & Wafer Protocol pages, as they are highly detailed and specific.</p> | ||
<p>These pages are also linked to one another when used for the same chip, as can be seen in the diagram above. That creates a network of compatible protocols and procedures, very useful for other iGEM teams.</p> | <p>These pages are also linked to one another when used for the same chip, as can be seen in the diagram above. That creates a network of compatible protocols and procedures, very useful for other iGEM teams.</p> | ||
+ | <h4>Usage Protocol & Safety Page</h4> | ||
<p>The Usage Protocol & Software pages consist of the protocols for the experiments and chip setup procedures. These procedures can be less detailed and specific than those in the MWP and CFP pages, as they are more easily modified. They can be videos of the setup procedure. As microfluidic users sometimes create software to control their experiment automatically, this would be included in this page, for other teams to use.</p> | <p>The Usage Protocol & Software pages consist of the protocols for the experiments and chip setup procedures. These procedures can be less detailed and specific than those in the MWP and CFP pages, as they are more easily modified. They can be videos of the setup procedure. As microfluidic users sometimes create software to control their experiment automatically, this would be included in this page, for other teams to use.</p> | ||
- | <h3>Naming the parts</h3> | + | <h3 id="naming">Naming the parts</h3> |
<p>The microfluidic parts would be named similarly to the DNA BioBricks: | <p>The microfluidic parts would be named similarly to the DNA BioBricks: | ||
<div class="cntr"> | <div class="cntr"> | ||
<a href="https://static.igem.org/mediawiki/2014/5/5e/Nomenclature_pp.png" data-lightbox="img1" data-title="Nomenclature of microfluidic parts"> | <a href="https://static.igem.org/mediawiki/2014/5/5e/Nomenclature_pp.png" data-lightbox="img1" data-title="Nomenclature of microfluidic parts"> | ||
- | <img src="https://static.igem.org/mediawiki/2014/5/5e/Nomenclature_pp.png"></a> | + | <img src="https://static.igem.org/mediawiki/2014/5/5e/Nomenclature_pp.png" width="100%"></a> |
</div> | </div> | ||
<p>With this naming structure, a fast identification of the main type of chip is possible.</p> | <p>With this naming structure, a fast identification of the main type of chip is possible.</p> | ||
- | <p>The chips' units are not separated in different parts, as it is important to see the construction around each functional unit. However, as these units had to be found easily within the database, a selection of components was added to the <a target="_blank" href=" ">part submission page</a>, which would appear in the <a target="_blank" href=" ">information page</a>.</p> | + | <p>The chips' units are not separated in different parts, as it is important to see the construction around each functional unit. However, as these units had to be found easily within the database, a selection of components was added to the <a target="_blank" href="https://static.igem.org/mediawiki/2014/9/9d/Samplesubmission.png">part submission page</a>, which would appear in the <a target="_blank" href="https://static.igem.org/mediawiki/2014/f/fa/Sampleinfo.png">information page</a>.</p> |
+ | <h3 id="enlarging">Enlarging project possibilities</h3> | ||
+ | |||
+ | <p>iGEM projects are becoming more complex and innovative. The variety of organisms, biological components, and technologies are rapidly evolving leading to a restructuring of the context in which they can be integrated. We believe that microfluidic chips are the ideal devices to reunite these elements in an easy and safe way - no wonder they call them "labs on a chip".</p> | ||
+ | |||
+ | <p>Related to our <a target="_blank" href="https://2014.igem.org/Team:EPF_Lausanne/Safety">safety work</a>, the use of microfluidic chips improves risk management when working with genetically modified cells. Microfluidics provide a contained interface allowing bacteria to evolve in a stable and isolated environment.<br /> | ||
+ | This last point could turn out useful for the development of iGEM as it could expand the range of organisms possible for use. On the long term, this interface could allow iGEM teams to make use of level 2 organisms, and use of expensive organisms such as stem cells. We hope this novel interface will bring a surge of new ideas. | ||
+ | </p> | ||
+ | |||
+ | |||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | <div class="col col-md-3"> | ||
+ | <nav id="affix-nav" class="sidebar hidden-sm hidden-xs"> | ||
+ | <ul class="nav sidenav box" data-spy="affix" data-offset-top="200" data-offset-bottom="600"> | ||
+ | <li class="active"><a href="#enlarging">Enlarging project possibilities</a></li> | ||
+ | <li><a href="#structure">Structure of the Microfluidic Parts Registry</a></li> | ||
+ | <li><a href="#naming">Naming the parts</a></li> | ||
+ | |||
+ | |||
+ | </ul> | ||
+ | </nav> | ||
+ | </div> | ||
+ | </div> | ||
</div> | </div> | ||
Latest revision as of 23:46, 17 October 2014
METAFLUIDICS
Microfluidic Chip Registry
While designing and making our new microfluidic chips, the 2014 iGEM EPFL team realized that it would be a great to have a microfluidic iGEM registry analogue to the current iGEM DNA Parts registry. Similarly to BioBricks, microfluidic chips also have several levels of structures that can be combined and reused as building blocks.
Creating a database of these parts would contribute to the already enormous library of DNA parts, and would moreover give a help all the iGEM teams looking into integrating microfluidics in their projects.
As a microfluidic registry isn’t available, we created this one one with as template the DNA parts registry to make this novel registry's integration easy. We kept in mind that the registry will develop itself, just as chip designs will integrate new parts, so we designed a nomenclature system enabling both horizontal (adding types of parts) and vertical (adding sub-parts) expansion.
Structure of the Microfluidic Parts Registry
The suggested system for structuring the novel microfluidic parts registry is modeled as seen bellow.
Each box represents each type of reusable microfluidic design or protocol.
There is the Microfluidic Chip Design repository, which contains the pages where each team's designs are documented.
There is the Mask & Wafer Protocol repository, which contains the detailed protocols to make masks and wafers.
The third white box corresponds to the third repository, the Chip Fabrication Protocol repository. It contains the protocols to make the chips once the wafers are made.
Lastly, there is the Usage Protocol & Software repository, which contains the chip usage protocols and any software created to automatically control the chip.
The related pages in each repository are linked to one another in the following way: the Chip Design page will link to its Mask and Wafer Protocol, its Chip Fabrication Protocol, and to its Usage Protocol & Software page. In the graph below, links are represented by red arrows.
This design aims to blend in the current registry while maintaining a uniform structure of microfluidic reusable parts.
As such a structure needs a different submission page than the ones already existing, we designed it. You can find a sample submission page for microfluidic parts here. A sample page of a Microfluidic Chip Information Page was also made.
Chip Design Page
Similar to the DNA BioBricks pages, the Microfluidic Chip Design page includes:
A short description of the chip, its intended purpose
The design file of the chip*
An information page with the owner, the part type, a list of components, the intended material...
Links to the other parts related to this one (protocols used on this chip)
* To make that possible, the iGEM server has to allow uploads of design files such as: .gds, .dxf, .cif, and .dvg.
Mask & Wafer Protocol Page
The Mask & Wafer Protocol (MWP) pages consist of the detailed procedures of mask & wafer fabrication. They include a list of instruments and materials, and the exact procedure, organized as a series of bullet points.
Chip Fabrication Protocol Page
The Chip Fabrication Protocol (CFP) pages are similar to the Mask & Wafer Protocol pages, as they are highly detailed and specific.
These pages are also linked to one another when used for the same chip, as can be seen in the diagram above. That creates a network of compatible protocols and procedures, very useful for other iGEM teams.
Usage Protocol & Safety Page
The Usage Protocol & Software pages consist of the protocols for the experiments and chip setup procedures. These procedures can be less detailed and specific than those in the MWP and CFP pages, as they are more easily modified. They can be videos of the setup procedure. As microfluidic users sometimes create software to control their experiment automatically, this would be included in this page, for other teams to use.
Naming the parts
The microfluidic parts would be named similarly to the DNA BioBricks:
With this naming structure, a fast identification of the main type of chip is possible.
The chips' units are not separated in different parts, as it is important to see the construction around each functional unit. However, as these units had to be found easily within the database, a selection of components was added to the part submission page, which would appear in the information page.
Enlarging project possibilities
iGEM projects are becoming more complex and innovative. The variety of organisms, biological components, and technologies are rapidly evolving leading to a restructuring of the context in which they can be integrated. We believe that microfluidic chips are the ideal devices to reunite these elements in an easy and safe way - no wonder they call them "labs on a chip".
Related to our safety work, the use of microfluidic chips improves risk management when working with genetically modified cells. Microfluidics provide a contained interface allowing bacteria to evolve in a stable and isolated environment.
This last point could turn out useful for the development of iGEM as it could expand the range of organisms possible for use. On the long term, this interface could allow iGEM teams to make use of level 2 organisms, and use of expensive organisms such as stem cells. We hope this novel interface will bring a surge of new ideas.