Difference between revisions of "Team:Edinburgh UG"
| Line 1: | Line 1: | ||
| − | + | ||
<html> | <html> | ||
<head> | <head> | ||
Revision as of 13:15, 15 July 2016
Team:Edinburgh UG
<!doctype html> Untitled Page body { background-color: #FFFFFF; color: #000000; font-family: Arial; font-weight: normal; font-size: 13px; line-height: 1.1875; margin: 0; padding: 0; } #Image1 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #wb_Text1 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text1 div { text-align: center; } #wb_Text2 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text2 div { text-align: center; } #wb_Text3 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text3 div { text-align: center; } #wb_Text4 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text4 div { text-align: left; } #wb_Text5 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text5 div { text-align: left; } #Image2 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #Button1 { border: 1px #000000 solid; -moz-border-radius: 4px; -webkit-border-radius: 4px; border-radius: 4px; background-color: transparent; background-image: none; color: #101010; font-family: Verdana; font-weight: normal; font-size: 13px; } #Line1 { border-width: 0; height: 12px; width: 1407px; } #wb_Text6 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: right; } #wb_Text6 div { text-align: right; } #Image3 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #Image4 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #Image5 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #Image7 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #Image6 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #wb_Text7 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text7 div { text-align: left; } #wb_Text8 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text8 div { text-align: center; } #wb_Text9 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text9 div { text-align: center; } #wb_Text10 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text10 div { text-align: center; } #wb_Text11 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text11 div { text-align: center; } #wb_Text12 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text12 div { text-align: center; } #wb_Text13 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text13 div { text-align: center; } #wb_Text14 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text14 div { text-align: center; } #wb_Text15 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: center; } #wb_Text15 div { text-align: center; } #Line2 { border-width: 0; height: 12px; width: 1407px; } #Image8 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #wb_Text16 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text16 div { text-align: left; } #wb_Text17 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text17 div { text-align: left; white-space: nowrap; } #Line3 { border-width: 0; height: 12px; width: 1407px; } #Line4 { border-width: 0; height: 12px; width: 1407px; } #Image9 { border: 0px #000000 solid; padding: 0px 0px 0px 0px; left: 0; top: 0; width: 100%; height: 100%; } #wb_Text18 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text18 div { text-align: left; } #wb_Text19 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text19 div { text-align: left; } #Button3 { border: 1px #000000 solid; -moz-border-radius: 4px; -webkit-border-radius: 4px; border-radius: 4px; background-color: transparent; background-image: none; color: #101010; font-family: Verdana; font-weight: normal; font-size: 13px; } #Button4 { border: 1px #000000 solid; -moz-border-radius: 4px; -webkit-border-radius: 4px; border-radius: 4px; background-color: transparent; background-image: none; color: #101010; font-family: Verdana; font-weight: normal; font-size: 13px; } #wb_Text20 { background-color: transparent; background-image: none; border: 0px #000000 solid; padding: 0; margin: 0; text-align: left; } #wb_Text20 div { text-align: left; white-space: nowrap; }
BabblED
The University of Edinburgh Undergraduate iGEM Team 2016 presents:
The next generation of information storage
By 2040, we will run out of the materials needed to store digital data.
If this happens, there will be no capacity for Twitter, Facebook or iGEM to function online. Last year, data centres worldwide used more electricity than the entire United Kingdom. By 2020, it will cost more than $13.7 billion to power data centres per year.
We have a solution.
DNA Text Encoding
Density
Longevity
Affordability
Modularity
DNA has 1000 times greater storage density than flash memory
DNA can last for thousands of years without consuming resources; modern hard drives can only last 50
All our encoding programmes are open source and initial synthesis of the lexicon is done for you providing significant cost reductions on existing methods
Assembly of our BabbleBricks is unrestricted and completely customisable
Abstract
The last decade has seen an exponential increase in data and information generation, creating a storage demand that will soon outweigh supply. By 2040, global data storage demand will reach 3×10^24 (3 million billion billion) bits1.. Considering the amount of energy required to run a data centre (about 2% of global energy consumption2.) and the limited supply of raw materials like silicon for manufacturing memory devices, it is clear that novel storage methods are of the utmost importance in meeting demand and providing a sustainable, long term solution to the data storage problem. The University of Edinburgh 2016 undergraduate iGEM team held these considerations in mind when we set out to create a new DNA-based storage system.
Over the course of weeks 1 and 2 our team explored and researched ideas for a project utilising DNA as an information storage device. Our brainstorming process evolved through discussions about the advantages and disadvantages of DNA synthesis and encoding digital information into nucleotide sequences. Major points of debate were cost, fidelity and efficiency of data storage. Following some constructive feedback from our supervisors, our team focused on developing a method that is accessible, sustainable and fits the iGEM format.
Over the course of weeks 1 and 2 our team explored and researched ideas for a project utilising DNA as an information storage device. Our brainstorming process evolved through discussions about the advantages and disadvantages of DNA synthesis and encoding digital information into nucleotide sequences. Major points of debate were cost, fidelity and efficiency of data storage. Following some constructive feedback from our supervisors, our team focused on developing a method that is accessible, sustainable and fits the iGEM format.
Medal Criteria
We've created a wiki page dedicated to outlining how we fulfilled each of the gold medal requirements.
Our project, given the name BabblED, is based on a simple idea: develop a modular system for encoding text, or any other unit of information, into DNA. We will prove the validity of our concept by encoding Ogden’s Basic English (a collection of 850-1,000 words that can be used to express most concepts in the English language). Each encoded word-a BabbleBrick -will be stored in a different PhytoBrick. Sentence assembly and unidirectionality is ensured by the stepwise addition of BabbleBricks that have alternating types of sticky ends; this also prevents repeats and minimizes the occurrence of missing words. The whole sentence construct can be melted off for easy retrieval and assembled back into a PhytoBrick for storage. Since the value that is assigned to each BabbleBrick is arbitrary, each one can be reused with any library or language. In this way, our encoding and assembly method can be optimized for many types of data. Furthermore, using tools such as checksums, optimal rectangular codes and, when appropriate, natural language processing techniques, we are able to ensure that each BabbleBrick sentence can be decoded with 100% accuracy.
As of week 4, we have developed the computer program that converts our vocabulary to BabbleBrick sequences. We have designed the DNA sequences for error-correcting codes and researched the benefits and potential ways to utilize encryption in our method. We are in the process of ordering our first BabbleBricks in the form of gBlocks from IDT and testing our assembly method for efficiency. We have commenced the 2016 Interlab study and are pursuing another exciting project on bacterial growth-based logic. We have already had some fascinating discussions with data specialists and librarians; their feedback and expertise are vital to how we are shaping our project. We have also been in touch with other iGEM teams, such as Newcastle and Dundee, and are hosting a Scottish team meet-up in the beginning of July.
References:
1.http://www.nature.com/nmat/journal/v15/n4/full/nmat4594.html#supplementary-information
2.http://www.greenpeace.org/international/Global/international/publications/climate/2011/Cool%20IT/dirty-data-report-greenpeace.pdf/
As of week 4, we have developed the computer program that converts our vocabulary to BabbleBrick sequences. We have designed the DNA sequences for error-correcting codes and researched the benefits and potential ways to utilize encryption in our method. We are in the process of ordering our first BabbleBricks in the form of gBlocks from IDT and testing our assembly method for efficiency. We have commenced the 2016 Interlab study and are pursuing another exciting project on bacterial growth-based logic. We have already had some fascinating discussions with data specialists and librarians; their feedback and expertise are vital to how we are shaping our project. We have also been in touch with other iGEM teams, such as Newcastle and Dundee, and are hosting a Scottish team meet-up in the beginning of July.
References:
1.http://www.nature.com/nmat/journal/v15/n4/full/nmat4594.html#supplementary-information
2.http://www.greenpeace.org/international/Global/international/publications/climate/2011/Cool%20IT/dirty-data-report-greenpeace.pdf/
