Difference between revisions of "Team:Edinburgh UG/Software"

Line 12: Line 12:
 
     </head>
 
     </head>
  
 
+
<header class="image-bg-fluid-height">
 
+
      <img class="img-responsive img-center" src="https://static.igem.org/mediawiki/2016/8/8c/EdiGEM16UGsoftware1.jpeg" alt="">
<div class="row full-size">
+
  </header>
    <div class="col-sm-12">
+
          <img src="https://static.igem.org/mediawiki/2016/8/8c/EdiGEM16UGsoftware1.jpeg" alt="img-responsive center-block">
+
    </div>
+
</div>
+
  
 
   <div class="container-fluid">
 
   <div class="container-fluid">

Revision as of 12:47, 15 October 2016

To create BabblED, we needed to rapidly design and process the information in a lexicon of over 2000 BabbleBricks. This would have been a practically impossible task without a novel computational approach. In order to make BabblED accessible our software needed to be open source (our code can be found on githubor on our dedicated wiki page), have an easy to use and elegant user interface and run under reasonable time constraints (it's possible to encode entire lexicons practically instantly). In addition, to the easy and fast encoding and decoding of our BabbleBricks we needed to automate our unique DNA error correction system; adapting a number of computer science techniques to new and creative applications in DNA storage. Finally, with data security an ever growing concern we implemented a highly secure DNA encryption system to safeguard against unauthorised access.

To read more about how the BabblED software works behind the scenes check out our pages on lexicon encoding, error correction and encryption