F1yingFish (Talk | contribs) |
F1yingFish (Talk | contribs) |
||
(3 intermediate revisions by 3 users not shown) | |||
Line 124: | Line 124: | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Silver">Silver</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Silver">Silver</a> </li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Gold">Gold</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/HP/Gold">Gold</a> </li> | ||
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Medal_Criteria">Medal Criteria</a> </li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Integrated_Practices">Integrated Practices</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Integrated_Practices">Integrated Practices</a> </li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Engagement">Engagement</a> </li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Engagement">Engagement</a> </li> | ||
Line 138: | Line 139: | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Demonstrate">Demonstrate</a></li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Demonstrate">Demonstrate</a></li> | ||
<li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</a></li> | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</a></li> | ||
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Protocols">Protocols</a></li> | ||
+ | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Limitations">Advantages and Limitations</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
Line 188: | Line 191: | ||
+ | <!-- End of menu --> | ||
− | + | ||
− | + | <div class="row"> | |
− | + | <div class="col-sm-12"> | |
− | + | <img src="https://static.igem.org/mediawiki/2016/8/8c/EdiGEM16UGsoftware1.jpeg" class="img-responsive center-block"> | |
− | + | </div> | |
− | + | </div> | |
− | <img src="https://static.igem.org/mediawiki/2016/8/8c/EdiGEM16UGsoftware1.jpeg" | + | |
− | + | ||
− | + | ||
− | + | ||
− | </div | + | |
− | + | ||
<br> | <br> | ||
Line 209: | Line 207: | ||
<div class="col-sm-8"> | <div class="col-sm-8"> | ||
<p> </p> | <p> </p> | ||
− | <centre style="font-size:160%;">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 <a href="https://github.com/Edinburgh-iGEM2016/" target="_self">github</a>or on our <a href="https://2016.igem.org/Team:Edinburgh_UG/Files" target="_self">dedicated wiki page</a>), 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.</centre> | + | <centre style="font-size:160%;">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 <a href="https://github.com/Edinburgh-iGEM2016/" target="_self">github</a>or on our <a href="https://2016.igem.org/Team:Edinburgh_UG/Files" target="_self">dedicated wiki page</a>), 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.</centre> |
<p> </p> | <p> </p> | ||
</div> | </div> | ||
Line 281: | Line 279: | ||
<centre style="font-size:160%;">Python is high-level, general purpose language designed for quick creation of highly readable code. As a result of libraries such as BioPython it has becoming increasingly used in Bioinformatics and Computational Biology in recent years this made it the obvious choice for the BabblED software. We made the decision to use Python 2.7 to increase accessibility as this is the Python version commonly pre-installed on Linux distributions such as Ubuntu.</centre> | <centre style="font-size:160%;">Python is high-level, general purpose language designed for quick creation of highly readable code. As a result of libraries such as BioPython it has becoming increasingly used in Bioinformatics and Computational Biology in recent years this made it the obvious choice for the BabblED software. We made the decision to use Python 2.7 to increase accessibility as this is the Python version commonly pre-installed on Linux distributions such as Ubuntu.</centre> | ||
<p> </p> | <p> </p> | ||
− | <centre style="font-size:160%;">Why avoid a web app?</centre> | + | <centre style="font-size:160%;">Why avoid a web app?</centre> |
<p> </p> | <p> </p> | ||
<centre style="font-size:160%;">When developing our software we carefully considered how it should be deployed. Should we create a web app using Django (the commonly used Python web framework)? Or simply make all our code easily downloadable with documentation on how to run it? Despite the minor drawbacks in accessibility we eventually settled on the later option for two main reasons. Firstly BabblED was designed for encoding large amounts of archival data - such large amounts that sending these volumes over the web would be very impracticable. Secondly having put a lot of work into the data security angle of the project we deemed that the web app approach had a much higher chance to introduce unforeseen security flaws that we knew (not being computer security experts) we would not have the capabilities to protect against.</centre> | <centre style="font-size:160%;">When developing our software we carefully considered how it should be deployed. Should we create a web app using Django (the commonly used Python web framework)? Or simply make all our code easily downloadable with documentation on how to run it? Despite the minor drawbacks in accessibility we eventually settled on the later option for two main reasons. Firstly BabblED was designed for encoding large amounts of archival data - such large amounts that sending these volumes over the web would be very impracticable. Secondly having put a lot of work into the data security angle of the project we deemed that the web app approach had a much higher chance to introduce unforeseen security flaws that we knew (not being computer security experts) we would not have the capabilities to protect against.</centre> |
Latest revision as of 00:08, 20 October 2016