Difference between revisions of "Team:UCL/Software"

 
(122 intermediate revisions by 4 users not shown)
Line 39: Line 39:
 
-->
 
-->
  
−
<script src="https://cferdinandi.github.io/smooth-scroll/dist/js/smooth-scroll.js"></script>
 
 
<script>
 
<script>
−
smoothScroll.init({
+
 
−
speed: 1000,
+
  $(function () {
−
easing: 'easeInOutCubic',
+
  $('.content').myTooltip({
−
offset: 0,
+
    speed: 200,
−
updateURL: true,
+
    closeOnClick: true
−
callbackBefore: function ( toggle, anchor ) {},
+
  });
−
callbackAfter: function ( toggle, anchor ) {}
+
 
−
});
+
});
−
</script>
+
 
 +
 
 +
 
 +
$.fn.myTooltip = function ( options ) {
 +
 
 +
 
 +
  var defaults = {
 +
    speed: 650,
 +
    closeOnClick: false,
 +
    tooltipClass: 'tooltip'
 +
  };
 +
 
 +
  var settings = $.extend( {}, defaults, options );
 +
 
 +
  var $this = $(this),
 +
      $tooltip = $this.find('.'+settings.tooltipClass);
 +
 
 +
 
 +
  setPosition();
 +
  $(window).resize(function () {
 +
    setPosition();
 +
  });
 +
 
 +
 
 +
  $this.mouseenter(function () {
 +
    $('.'+settings.tooltipClass, this).fadeIn(settings.speed);
 +
  }).mouseleave(function () {
 +
    $('.'+settings.tooltipClass, this).stop(true, true).fadeOut(settings.speed);
 +
  });
 +
 
 +
  if(settings.closeOnClick) {
 +
    $tooltip.click(function () {
 +
      $(this).stop(true, true).fadeOut(settings.speed);
 +
    });
 +
  }
 +
 
 +
 
 +
  function setPosition() {
 +
    $tooltip.css({top: $this.height(), left: 0});
 +
  }
 +
 
 +
};
 +
 
 +
</script>
 
<style>
 
<style>
  
Line 78: Line 120:
 
content: "";
 
content: "";
 
  background-image: url('https://static.igem.org/mediawiki/2015/9/90/UCL_Software.jpg');
 
  background-image: url('https://static.igem.org/mediawiki/2015/9/90/UCL_Software.jpg');
 +
      -webkit-filter: blur(2px);
 +
  -moz-filter: blur(2px);
 +
  -o-filter: blur(2px);
 +
  -ms-filter: blur(2px);
 +
  filter: blur(2px);
 
  background-repeat: no-repeat;
 
  background-repeat: no-repeat;
 
background-position: 0 0 0 0;
 
background-position: 0 0 0 0;
Line 102: Line 149:
 
#mobilebackground {
 
#mobilebackground {
 
   background-image: url('https://static.igem.org/mediawiki/2015/9/90/UCL_Software.jpg');
 
   background-image: url('https://static.igem.org/mediawiki/2015/9/90/UCL_Software.jpg');
 +
      -webkit-filter: blur(4px);
 +
  -moz-filter: blur(4px);
 +
  -o-filter: blur(4px);
 +
  -ms-filter: blur(4px);
 +
  filter: blur(4px);
 
     top: 0;
 
     top: 0;
 
     right: 0;
 
     right: 0;
Line 131: Line 183:
  
  
−
#wrapper {width: 80%; height: 100%; background: none; margin: 0 auto; position: relative; padding: 0; padding-top: 80px; margin-bottom: 200px; overflow: auto;}  
+
#wrapper {width: 80%; height: 100%; background: none; margin: 0 auto; position: relative; padding: 0; margin-bottom: 200px; overflow: auto;}  
  
−
 
−
 
−
.bigtitle {width: 42%; top: 35px; margin: 0 auto; font-size: 16px; background-image: url('https://static.igem.org/mediawiki/2015/e/e3/UCL_headercircle3.png'); text-align: center; line-height: 2;
 
−
    background-position: top center;  background-repeat: no-repeat; background-size: contain; padding: 9%; position: relative; margin-bottom: 100px; color: #0a0111;}
 
−
 
−
.bigtitle a {color: #493C54; text-decoration: none;}
 
  
  
Line 194: Line 240:
  
 
.titlecircle {width: 85%; margin: 0 auto; padding-top: 8%;}
 
.titlecircle {width: 85%; margin: 0 auto; padding-top: 8%;}
−
.title2 {font-family: League Script; font-size: 380%;}
+
.title2 {font-size: 380%;}
 +
  .bigtitle a {color:white;}
  
  
Line 288: Line 335:
 
@media(max-width:530px){
 
@media(max-width:530px){
 
.titlecircle {width: 75%;}
 
.titlecircle {width: 75%;}
−
.bigtitle {padding: 14%;}
+
.bigtitle {padding: 14%;color:white;}
 +
  .title2 {font-size:500%;}
 
.memberdescriptionL p, .memberdescriptionR p {font-size: 13px; line-height: 1.5;}
 
.memberdescriptionL p, .memberdescriptionR p {font-size: 13px; line-height: 1.5;}
−
 
 
}
 
}
  
Line 316: Line 363:
  
 
.titlecircle {width: 80%;  padding-top: 0; margin-top: -6%;}
 
.titlecircle {width: 80%;  padding-top: 0; margin-top: -6%;}
−
.title2 {font-size: 320%;}
 
 
.bigtitle p {line-height: 1.5 !important;}
 
.bigtitle p {line-height: 1.5 !important;}
  
Line 334: Line 380:
 
.titlecircle {width: 80%;}
 
.titlecircle {width: 80%;}
 
.bigtitle p {line-height: 1.3 !important;}
 
.bigtitle p {line-height: 1.3 !important;}
−
.title2 {font-size: 280%;}
 
 
}
 
}
 
    
 
    
 
    
 
    
 +
  
  
Line 351: Line 397:
 
<div id="wrapper">
 
<div id="wrapper">
  
−
<div class="bigtitle">
+
<div class="bigtitle" style="color:white">
 
<div class="titlecircle">
 
<div class="titlecircle">
  
  
 
<br><br>
 
<br><br>
−
  <span class="title2">Software</span>  
+
  <span class="title2">Software</span><hr style="height:1px; border:none; color:white; background-color:#fff;"><br><p style="margin-top: 5%; line-height: 1.7;font-family:Raleway;">
−
            <p style="margin-top: -30px; line-height: 1.9;margin-left: 20px;margin-right: 10px;">
+
 
               We have developed <b>two incredible tools</b> to help not only our project but all of iGEM! <br>
 
               We have developed <b>two incredible tools</b> to help not only our project but all of iGEM! <br>
 
                 <span class="arrow">  
 
                 <span class="arrow">  
Line 363: Line 408:
 
                 </span>
 
                 </span>
 
             </p></div> </div>  
 
             </p></div> </div>  
−
     <div id="submenu" style="padding-top: 150px;">
+
     <div id="submenu">
 
         <a data-scroll data-options='{ "easing": "linear" }' href="#mark" class="buttonblack">Mind-the-Mark</a>         
 
         <a data-scroll data-options='{ "easing": "linear" }' href="#mark" class="buttonblack">Mind-the-Mark</a>         
−
         <a data-scroll data-options='{ "easing": "linear" }' href="#model" class="buttonblack">Mind-the-Model</a>
+
         <a data-scroll data-options='{ "easing": "linear" }' href="#growth" class="buttonblack">Mind-the-Growth</a>
−
        <a data-scroll data-options='{ "easing": "linear" }' href="#users" class="buttonblack">Users</a>
+
−
        <a data-scroll data-options='{ "easing": "linear" }' href="#developers" class="buttonblack">Developers</a>
+
 
     </div>
 
     </div>
  
Line 374: Line 417:
 
<div id="members">
 
<div id="members">
  
−
<div style="height: 100px"></div>
+
<div id="mark" style="height: 50px"></div>
  
  
−
<div class="memberwrapper" id="mark">
+
<div class="memberwrapper">
 
<h2>Mind-the-Mark</h2>
 
<h2>Mind-the-Mark</h2>
 
<br><br><span style="text-align: center; margin: 0 auto; display: block;"><img src="https://static.igem.org/mediawiki/2015/d/d6/UCL_Mind_the_Mark_icon_small.png"/></span><br>
 
<br><br><span style="text-align: center; margin: 0 auto; display: block;"><img src="https://static.igem.org/mediawiki/2015/d/d6/UCL_Mind_the_Mark_icon_small.png"/></span><br>
−
   <div class="editorGit">
+
   
−
     <a href="https://github.com/ucligem2015/Mind-The-Mark">
+
 
−
      <span class="overlayx">
+
 
−
        <img src="https://static.igem.org/mediawiki/2015/3/32/UCLGitHubLogo.png" size="50%"/>
+
 
−
        <div>GitHub Repository</div>
+
   <div style="width:90%;padding:5%;border:1px solid grey;">
−
      </span>
+
     <h3 style="margin-top:40px;">The Tool</h3>
−
    </a>
+
    <p style="margin:0 0 0 20px;">By taking advantage of Google's easy to use extension system for the Chrome Browser, we devised a powerful
−
  </div>
+
       and lightweight extension that transforms the iGEM wiki editor on whatever page you choose to edit; be it in the
−
    <h3>Summary</h3>
+
      future in 2020 or now in 2015. The extension is easily downloaded and then drag-and-dropped into the Chrome browser,
−
       <p>
+
      to install, or installed with a click from the chrome store. Then its working!</p>
−
            The Mind-the-Mark tool takes the bland and boring wiki input box and transforms it into a proper code editor with several
+
    <table style="width:100%; margin:20px auto; z-index:999;">
−
        interactive and assistive features. Having talked to several iGEM teams this year, and years past, one of the  
+
−
        issues they lamented over was the issue of entering code into the wiki. The bland and simple text input on each
+
−
        page made developing interactive and pretty wikis a real hassle. Due to this many teams developed their code
+
−
        externally and then transfered it in, costing them time and effort. We have changed that.
+
−
      </p>
+
−
      <table style="width:100%; margin:0 auto; border:1px solid grey; z-index:999;">
+
 
       <tr>
 
       <tr>
 
         <td><div class="bigCenterText">Before</div></td>
 
         <td><div class="bigCenterText">Before</div></td>
Line 404: Line 441:
 
         <td>
 
         <td>
 
           <div class="centerRize">
 
           <div class="centerRize">
−
             <img src="https://static.igem.org/mediawiki/2015/9/91/UCLSoft2.png"  width="100%"/>
+
             <img src="https://static.igem.org/mediawiki/2015/9/91/UCLSoft2.png"  width="100%" style="margin:0 auto;"/>
 
           </div>
 
           </div>
 
         </td>
 
         </td>
 
         <td>
 
         <td>
 
           <div class="centerRize">
 
           <div class="centerRize">
−
             <img src="https://static.igem.org/mediawiki/2015/b/b3/UCLBit_6.png" width="100%"/>
+
             <img src="https://static.igem.org/mediawiki/2015/b/b3/UCLBit_6.png" width="100%" style="margin:0 auto;"/>
 
           </div>
 
           </div>
 
         </td>  
 
         </td>  
Line 415: Line 452:
 
     </table>
 
     </table>
  
−
      <p>By taking advantage of Google's easy to use extension system for the Chrome Browser, we devised a powerful
+
    <h3>Description</h3>
−
       and lightweight extension that transforms the wiki editor on whatever page you choose to edit; be it in the
+
    <p>
−
       future in 2020 or now in 2015. The extension is easily downloaded and then drag-and-dropped into the Chrome browser,
+
      The Mind-the-Mark tool takes the bland and boring wiki input box and transforms it into a proper code editor with several
−
       to install. Then its working!</p>
+
       interactive and assistive features. Having talked to several iGEM teams this year, and years past, one of the
−
       <img src="https://static.igem.org/mediawiki/2015/d/df/UCLSoft3.png"/>
+
      issues they lamented over was the issue of entering code into the wiki. The bland and simple text input on each
−
        
+
      page made developing interactive and pretty wikis a real hassle. Due to this many teams developed their code
−
   
+
       externally and then transfered it in, costing them time and effort. We have changed that.
−
       <p>For more information, the source code, and the extension go to <a href="https://github.com/ucligem2015/Mind-The-Mark" style="color:red;">
+
    </p>
−
         Our Github Page</a>.</p>
+
    <h3>Features</h3>
−
 
+
    <ul>
−
 
+
      <li>Syntax Markup for HTML, XML, CSS, Javascript</li>
−
       <h3>Construction</h3>
+
      <li>Customized Layout and Design</li>
 +
      <li>Tag Highlighting and linking</li>
 +
      <li>Line Count</li>
 +
      <li>Ctrl-F for Finding, replacing, and searching with RegExp</li>
 +
       <li>Open Source and Fully Changeable</li>
 +
      <li>Much More!</li>
 +
    </ul>
 +
    <p>For a more indepth update history and singular repository see the following <a href='https://github.com/ucligem2015/Mind-The-Mark' style="color:blue;"> link</a> beside the one below</p>
 +
    <div style="font-weight:bold;font-size:20px;width:20%;margin:30px auto;text-alignment:center;">Download the Tool!</div>
 +
    <div style="width:100%;display:inline-flex;">
 +
       <div style="width:50%;">
 +
        <a href="https://github.com/igemsoftware/UCL2015">
 +
          <!--https://github.com/ucligem2015/Mind-The-Mark-->
 +
          <img src="https://static.igem.org/mediawiki/2015/3/32/UCLGitHubLogo.png" width="20%" style="margin:0 40%;"/>
 +
        </a>
 +
       </div>
 +
       <div style="width:50%;">
 +
        <a href="https://chrome.google.com/webstore/detail/mind-the-mark/jkagocihmkabhekcmdgiloihalnoliai?utm_campaign=en&utm_source=en-et-na-us-oc-webstrhm&utm_medium=et">
 +
          <img src="https://static.igem.org/mediawiki/2015/1/10/UCLAppicns_Chrome.png" width="20%" style="margin:0 40%;"/>
 +
         </a>
 +
      </div>
 +
    </div>
 +
    <div style="width:100%;display:inline-flex;margin-bottom:20px;">
 +
       <div style="width:50%;text-align:center;font-size:20px;">
 +
        <div>GitHub</div>
 +
      </div>
 +
      <div style="width:50%;text-align:center;font-size:20px;">
 +
        <div>Chrome Store</div>
 +
      </div>
 +
    </div>
 +
  </div>
 +
   
 +
   
 +
   
 +
    <h3>Construction</h3>
  
−
      <p>The spirit of the tool is to make editing and working on the iGEM wiki easier and more interactive for all.
+
    <p>The spirit of the tool is to make editing and working on the iGEM wiki easier and more interactive for all.
 
       It was with this spirit that we built the tool. Although the code is part of chrome extension, it is really
 
       It was with this spirit that we built the tool. Although the code is part of chrome extension, it is really
 
       a lightweight javascript tool.</p>
 
       a lightweight javascript tool.</p>
−
     
+
 
−
      <h3>What is a Chrome Extension?</h3>
+
    <h3>What is a Chrome Extension?</h3>
−
      <p>A chrome extension at its base is a <b>.json</b> file called the "Manifest" file that contains the file
+
    <p>A chrome extension at its base is a <b>.json</b> file called the "Manifest" file that contains the file
 
       reference's and basic information about the tool. When used this tells the browser to load a piece of javascript or other files  
 
       reference's and basic information about the tool. When used this tells the browser to load a piece of javascript or other files  
 
       on to specified pages. These then interact with the DOM (Document Object Model) of the page.</p>
 
       on to specified pages. These then interact with the DOM (Document Object Model) of the page.</p>
−
     
+
 
−
      <h3>Why use a Chrome Extension?</h3>
+
    <h3>Why use a Chrome Extension?</h3>
−
      <p>Chrome is one of the most modern and widely used browser on the internet and has an easy to use and develop
+
    <p>Chrome is one of the most modern and widely used browser on the internet and has an easy to use and develop
 
       extension system, on top of a very rich API. When loading files that interact with the DOM chrome extensions
 
       extension system, on top of a very rich API. When loading files that interact with the DOM chrome extensions
 
       also make sure that there is no interaction with any of the loaded scripts of libraries from the page, protecting
 
       also make sure that there is no interaction with any of the loaded scripts of libraries from the page, protecting
 
       the user. To top it all off, the chrome extensions are very easy to install and distribute.</p>
 
       the user. To top it all off, the chrome extensions are very easy to install and distribute.</p>
−
     
+
 
−
      <h3>How did we Implement it?</h3>
+
    <h3>How did we Implement it?</h3>
−
      <p>Our tool uses the commonly implemented "Content_Scripts" method for loading our extension. This allows
+
    <p>Our tool uses the commonly implemented "Content_Scripts" method for loading our extension. This allows
 
       chrome to load specific js and css files whenever a URL, defined by a certain patern, is loaded. In our case
 
       chrome to load specific js and css files whenever a URL, defined by a certain patern, is loaded. In our case
 
       we load both js and css whenever an iGEM edit page is loaded. The javascipt that is loaded
 
       we load both js and css whenever an iGEM edit page is loaded. The javascipt that is loaded
Line 452: Line 523:
 
       to then load the script file is that it allows for a cleaner separation of files as well as a faster loading solution
 
       to then load the script file is that it allows for a cleaner separation of files as well as a faster loading solution
 
       when the scipt is large.</p>
 
       when the scipt is large.</p>
−
      <p>The script.js file contains the source code and several add-on pieces of code from a js library called CodeMirror.
+
    <p>The script.js file contains the source code and several add-on pieces of code from a js library called CodeMirror.
 
       This provides the majority of functions that alter the page. It also contains the final function that runs when the  
 
       This provides the majority of functions that alter the page. It also contains the final function that runs when the  
 
       Document OnLoad call is made. This final function finds the textarea tag by its ID and makes the call to CodeMirror
 
       Document OnLoad call is made. This final function finds the textarea tag by its ID and makes the call to CodeMirror
Line 458: Line 529:
 
       and applies the css. As well as defining and instigating a few other features, this performs the majority of the  
 
       and applies the css. As well as defining and instigating a few other features, this performs the majority of the  
 
       work</p>
 
       work</p>
−
      <p>By packing the majority of the js into one file it reduces the overall space required and time neaded to load.
+
    <p>By packing the majority of the js into one file it reduces the overall space required and time neaded to load.
 
       That being said it is well commented and laid out so that it is easily editable in the future. The same runs
 
       That being said it is well commented and laid out so that it is easily editable in the future. The same runs
 
       true for the css.</p>
 
       true for the css.</p>
−
     
+
 
−
      <h3>Future Work</h3>
+
    <h3>Future Work</h3>
−
      <p>There are several features we would like to implement in the future to make this the best tool, and the only
+
    <p>There are several features we would like to implement in the future to make this the best tool, and the only
 
       as far as we know, for editing the iGEM wiki. Javascipt, CSS, and HTML are all currently supported but providing  
 
       as far as we know, for editing the iGEM wiki. Javascipt, CSS, and HTML are all currently supported but providing  
 
       syntax for SCSS and other CSS variants, as well as PHP would complete the language mark up types. Providing  
 
       syntax for SCSS and other CSS variants, as well as PHP would complete the language mark up types. Providing  
 
       code suggestion as well as auto complete would make this a tool to rival the best code editors out there.</p>
 
       code suggestion as well as auto complete would make this a tool to rival the best code editors out there.</p>
−
      <p>Another project we have begun work on is developing a larger tool coaltes our tool with other team's
+
    <p>Another project we have begun work on is developing a larger tool coaltes our tool with other team's
 
       to create a complete IDE for developing iGEM wikis.</p>
 
       to create a complete IDE for developing iGEM wikis.</p>
−
      <p>This tool will and can make a massive difference to teams current and futrue by making the process of creating  
+
  <div id="growth"style="height:1px;background-colour:transparent;"> </div> 
 +
  <p>This tool will and can make a massive difference to teams current and future by making the process of creating  
 
       a wiki infinitely more easy and enjoyable to do!</p>
 
       a wiki infinitely more easy and enjoyable to do!</p>
 +
 +
 +
 +
  <h2>Mind-the-Growth</h2>
 +
  <span style="text-align: center; margin: 0 auto; display: block;"><img src="https://static.igem.org/mediawiki/2015/5/5c/Mind_the_Growth_icon.png" width="15%" style="margin:50px 0;"/></span>
 +
  <div style="width:90%;padding:5%;border:1px solid grey;">
 +
    <h3>The Tool</h3>
 +
    <p>When we first discussed adding a probiotic bacteria into the human gut one of the questions
 +
      that come up was what effect would it have on the human’s microbiome. 
 +
      In order to understand and gain some insight into the functioning of the
 +
      human microbiome we decided to model it! </p>
 +
<p>Many of the current models that model the human microbiome are descriptive, and use
 +
      mathematical models and other logical operations to create a system that mimics the
 +
      gut loosely.
 +
 +
<span class="content"><span class="tooltip"><a href="http://www.sciencedirect.com/science/article/pii/S0022283614001788" target="_blank"><b>[Link]</b></a>Bucci v. and Xavier J. Towards Predictive Models of the Human Gut Microbiome, Journal of Molecular Biology Volume 426, Issue 23, 25 November 2014, Pages 3907–3916
 +
</span><b>[1]</b></span>
 +
 +
One of the challenges is that although there exist complex models of single cell
 +
      dynamics, that use operations like mean-field partial differential equations, the
 +
      computational power needed to expand any discrete models to a population is very high.
 +
</p>
 +
    <img src="https://static.igem.org/mediawiki/2015/0/0f/UCLGifSoft.gif" width="100%"/>
 +
    <p>A potential solution to this is using metabolic analysis as a descriptive tool
 +
      for modelling the activity of the populations. What we have done is built a lightweight
 +
      framework in both C++ and in C# to enable researchers to expand and build upon this
 +
      concept in the future. Not only does this tool render cell population graphics in a physics
 +
      engine but it also has been used to examine the effect that consuming probiotics and prebiotics
 +
      (inulin in this case) has on the gut microbiome. </p>
 +
   
 +
    <p>For a more indepth update history and singular repository see the following <a href='https://github.com/ucligem2015/Mind-The-Growth'  style="color:blue;"> link</a> beside the one below</p>
 +
   
 +
    <div style="font-weight:bold;font-size:20px;width:20%;margin:30px auto;text-alignment:center;">Download the Tool!</div>
 +
    <div style="width:100%;display:inline-flex;">
 +
      <div style="width:100%;">
 +
        <a href="https://github.com/igemsoftware/UCL2015">
 +
          <!--https://github.com/ucligem2015/Mind-The-Growth-->
 +
          <img src="https://static.igem.org/mediawiki/2015/3/32/UCLGitHubLogo.png" width="10%" style="margin:0 45%;"/>
 +
        </a>
 +
      </div>
 +
    </div>
 +
    <div style="width:100%;display:inline-flex;margin-bottom:20px;">
 +
      <div style="width:100%;text-align:center;font-size:20px;">
 +
        <div>GitHub</div>
 +
      </div>
 +
    </div>
 +
  </div>
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
  <h3>Construction</h3>
 +
<p>
 +
Cellular automata are discrete models used across a variety of disciplines. The model consists of a grid of cells that are assigned one of several possible states which can be thought of as the identity of the cell. Each of these possible states has a set of rules which determine if and how the state of the that cell will change as time progresses. The model operates on discrete time, so all the states at t+1 are determined by how the grid looks at time t.
 +
  </p><p>
 +
The purpose of the creation of this particular model was to determine the optimum way in which a combination of probiotics and prebiotics can be used to change an initial microbiome profile to a pre-determined one.
 +
  </p><p>
 +
This model is a simplification that offers a framework to which more variables can be added, as well as experimental data.
 +
  </p><p>
 +
The states 1-5 represent different five different bacterial phyla, with state 6 representing all other phyla.
 +
  </p><p>
 +
The bacteria were randomly generated on a grid of cells according to a pre-determined proportion using a random number generator. As time progressed the state of each cell on the grid changed according to a set of rules that took into account the following variables:
 +
  </p>
 +
  <ul>
 +
  <li>
 +
The states of the eight cells that surround it.</li>
 +
  <li>
 +
  Durability and strength constants that were defined for each of the phyla
 +
  </li><li>
 +
  A cooperation/competition constant that take into account the proportion of the overall population that belongs to the same phyla
 +
  </li><li>
 +
  A constant to take into account each phylum’s response to the prebiotic (inulin)
 +
  </li>
 +
  </ul>
 +
  <p>
 +
Each of these factors is set to zero or one in the source code, so as to eliminate its influence on the model. Each user can then set the constants as he or she sees fit.
 +
  </p><p>
 +
The system is disrupted periodically by the addition of a dose of Prokao containing inulin and bacteria of different phyla, whose values can also be adjusted as needed.
 +
  </p>
 +
 
 +
  <h3>Future Work</h3>
 +
  <p>
 +
Given the amount of variables involved we would need to incorporate machine learning, such as a genetic algorithm, in order to come up with a composition of Prokao that’s even close to the ideal. </p>
 +
 +
<p>Quorum sensing could be incorporated by having particular actions at a distance between cells, and have those effects diminish with the distance between them.</p>
 +
 
 +
<p>More complex functions based on particular limiting nutrients could be used to define the nature of cooperation and competition between different states.</p>
 +
 +
<p>Experimental data could be interpreted in the context of the model and used to make the simulation more accurate. Current theoretical frameworks could also be incorporated in future versions of this model.</p>
 +
 +
<p>More possible states could be represented, in this case going down to the genus or even species level. With overarching characteristics that defining a phyla and particular characteristics to each genus and so on. Non-bacterial actors such as archaea, fungi and parasites could also be considered.</p>
 +
 +
<p>The “other” state could be more accurately modelled by having each of it’s cells behave in a different way and thus eliminating any competition or cooperation between them.</p>
 +
 +
<p>Empty space can be considered as one of the possible states, thereby making it possible to model initial colonisation.</p>
 +
 +
<p>Limiting factors which increase periodically such as carbon sources or specific nutrients which are essential for the growth of particular bacteria.</p>
 +
 +
<p>Cellular products could be produced, consumed and accumulated leading to different effects.
 +
  </p>
 +
 
 +
 +
 
 
   </div>
 
   </div>
 
    
 
    
Line 481: Line 660:
 
   <style>
 
   <style>
 
     .bigCenterText {
 
     .bigCenterText {
−
     margin:0 auto;
+
     margin:10px auto;
 
     font-size:20px;
 
     font-size:20px;
 +
    width:25%;
 +
    text-align:center;
 +
   
 
     }
 
     }
 
     .editorGit {
 
     .editorGit {
 
     margin:0 auto;
 
     margin:0 auto;
−
     display:inline;
+
     float:left;
 +
    width:80%;
 
     }
 
     }
 
     .overlayx {
 
     .overlayx {
Line 503: Line 686:
 
<div style="clear:both;"></div>
 
<div style="clear:both;"></div>
  
−
</div>
+
 
  
 
</html>
 
</html>

Latest revision as of 23:58, 18 September 2015

'



Software

We have developed two incredible tools to help not only our project but all of iGEM!
▼

Mind-the-Mark




The Tool

By taking advantage of Google's easy to use extension system for the Chrome Browser, we devised a powerful and lightweight extension that transforms the iGEM wiki editor on whatever page you choose to edit; be it in the future in 2020 or now in 2015. The extension is easily downloaded and then drag-and-dropped into the Chrome browser, to install, or installed with a click from the chrome store. Then its working!

Before
After

Description

The Mind-the-Mark tool takes the bland and boring wiki input box and transforms it into a proper code editor with several interactive and assistive features. Having talked to several iGEM teams this year, and years past, one of the issues they lamented over was the issue of entering code into the wiki. The bland and simple text input on each page made developing interactive and pretty wikis a real hassle. Due to this many teams developed their code externally and then transfered it in, costing them time and effort. We have changed that.

Features

  • Syntax Markup for HTML, XML, CSS, Javascript
  • Customized Layout and Design
  • Tag Highlighting and linking
  • Line Count
  • Ctrl-F for Finding, replacing, and searching with RegExp
  • Open Source and Fully Changeable
  • Much More!

For a more indepth update history and singular repository see the following link beside the one below

Download the Tool!
GitHub
Chrome Store

Construction

The spirit of the tool is to make editing and working on the iGEM wiki easier and more interactive for all. It was with this spirit that we built the tool. Although the code is part of chrome extension, it is really a lightweight javascript tool.

What is a Chrome Extension?

A chrome extension at its base is a .json file called the "Manifest" file that contains the file reference's and basic information about the tool. When used this tells the browser to load a piece of javascript or other files on to specified pages. These then interact with the DOM (Document Object Model) of the page.

Why use a Chrome Extension?

Chrome is one of the most modern and widely used browser on the internet and has an easy to use and develop extension system, on top of a very rich API. When loading files that interact with the DOM chrome extensions also make sure that there is no interaction with any of the loaded scripts of libraries from the page, protecting the user. To top it all off, the chrome extensions are very easy to install and distribute.

How did we Implement it?

Our tool uses the commonly implemented "Content_Scripts" method for loading our extension. This allows chrome to load specific js and css files whenever a URL, defined by a certain patern, is loaded. In our case we load both js and css whenever an iGEM edit page is loaded. The javascipt that is loaded is the background.js file which adds a script refecence to the page, loads the script, and then deletes it. In this instance the script in question is the script.js file. The extension also has the ability to access other js and css file which are referenced in the Manifest file. The reason the background.js file is used to then load the script file is that it allows for a cleaner separation of files as well as a faster loading solution when the scipt is large.

The script.js file contains the source code and several add-on pieces of code from a js library called CodeMirror. This provides the majority of functions that alter the page. It also contains the final function that runs when the Document OnLoad call is made. This final function finds the textarea tag by its ID and makes the call to CodeMirror to change the textarea into the new snazzy code editor. CodeMirror then alters the shape of the divs in the tag and applies the css. As well as defining and instigating a few other features, this performs the majority of the work

By packing the majority of the js into one file it reduces the overall space required and time neaded to load. That being said it is well commented and laid out so that it is easily editable in the future. The same runs true for the css.

Future Work

There are several features we would like to implement in the future to make this the best tool, and the only as far as we know, for editing the iGEM wiki. Javascipt, CSS, and HTML are all currently supported but providing syntax for SCSS and other CSS variants, as well as PHP would complete the language mark up types. Providing code suggestion as well as auto complete would make this a tool to rival the best code editors out there.

Another project we have begun work on is developing a larger tool coaltes our tool with other team's to create a complete IDE for developing iGEM wikis.

This tool will and can make a massive difference to teams current and future by making the process of creating a wiki infinitely more easy and enjoyable to do!

Mind-the-Growth

The Tool

When we first discussed adding a probiotic bacteria into the human gut one of the questions that come up was what effect would it have on the human’s microbiome. In order to understand and gain some insight into the functioning of the human microbiome we decided to model it!

Many of the current models that model the human microbiome are descriptive, and use mathematical models and other logical operations to create a system that mimics the gut loosely. [Link]Bucci v. and Xavier J. Towards Predictive Models of the Human Gut Microbiome, Journal of Molecular Biology Volume 426, Issue 23, 25 November 2014, Pages 3907–3916 [1] One of the challenges is that although there exist complex models of single cell dynamics, that use operations like mean-field partial differential equations, the computational power needed to expand any discrete models to a population is very high.

A potential solution to this is using metabolic analysis as a descriptive tool for modelling the activity of the populations. What we have done is built a lightweight framework in both C++ and in C# to enable researchers to expand and build upon this concept in the future. Not only does this tool render cell population graphics in a physics engine but it also has been used to examine the effect that consuming probiotics and prebiotics (inulin in this case) has on the gut microbiome.

For a more indepth update history and singular repository see the following link beside the one below

Download the Tool!
GitHub

Construction

Cellular automata are discrete models used across a variety of disciplines. The model consists of a grid of cells that are assigned one of several possible states which can be thought of as the identity of the cell. Each of these possible states has a set of rules which determine if and how the state of the that cell will change as time progresses. The model operates on discrete time, so all the states at t+1 are determined by how the grid looks at time t.

The purpose of the creation of this particular model was to determine the optimum way in which a combination of probiotics and prebiotics can be used to change an initial microbiome profile to a pre-determined one.

This model is a simplification that offers a framework to which more variables can be added, as well as experimental data.

The states 1-5 represent different five different bacterial phyla, with state 6 representing all other phyla.

The bacteria were randomly generated on a grid of cells according to a pre-determined proportion using a random number generator. As time progressed the state of each cell on the grid changed according to a set of rules that took into account the following variables:

  • The states of the eight cells that surround it.
  • Durability and strength constants that were defined for each of the phyla
  • A cooperation/competition constant that take into account the proportion of the overall population that belongs to the same phyla
  • A constant to take into account each phylum’s response to the prebiotic (inulin)

Each of these factors is set to zero or one in the source code, so as to eliminate its influence on the model. Each user can then set the constants as he or she sees fit.

The system is disrupted periodically by the addition of a dose of Prokao containing inulin and bacteria of different phyla, whose values can also be adjusted as needed.

Future Work

Given the amount of variables involved we would need to incorporate machine learning, such as a genetic algorithm, in order to come up with a composition of Prokao that’s even close to the ideal.

Quorum sensing could be incorporated by having particular actions at a distance between cells, and have those effects diminish with the distance between them.

More complex functions based on particular limiting nutrients could be used to define the nature of cooperation and competition between different states.

Experimental data could be interpreted in the context of the model and used to make the simulation more accurate. Current theoretical frameworks could also be incorporated in future versions of this model.

More possible states could be represented, in this case going down to the genus or even species level. With overarching characteristics that defining a phyla and particular characteristics to each genus and so on. Non-bacterial actors such as archaea, fungi and parasites could also be considered.

The “other” state could be more accurately modelled by having each of it’s cells behave in a different way and thus eliminating any competition or cooperation between them.

Empty space can be considered as one of the possible states, thereby making it possible to model initial colonisation.

Limiting factors which increase periodically such as carbon sources or specific nutrients which are essential for the growth of particular bacteria.

Cellular products could be produced, consumed and accumulated leading to different effects.