Difference between revisions of "Team:Edinburgh UG/Lexicon Encoding"
F1yingFish (Talk | contribs) |
F1yingFish (Talk | contribs) |
||
| (20 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script> | <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script> | ||
</head> | </head> | ||
| + | |||
| + | <style type="text/css"> | ||
| + | |||
| + | #contentSub, #footer-box, #catlinks, #search-controls, #p-logo, .printfooter, .firstHeading,.visualClear | ||
| + | |||
| + | { | ||
| + | |||
| + | display: none; | ||
| + | |||
| + | } | ||
| + | |||
| + | #top_menu_under | ||
| + | { | ||
| + | height: 0; | ||
| + | } | ||
| + | |||
| + | #top-section { | ||
| + | height: 0px; | ||
| + | border-top: 0; | ||
| + | border-left: none; | ||
| + | border-right: none; | ||
| + | } | ||
| + | #globalWrapper | ||
| + | { | ||
| + | width: 100%; | ||
| + | height: 100%; | ||
| + | border: 0px; | ||
| + | background-color: #ffffff; | ||
| + | margin: 0px; | ||
| + | padding: 0px; | ||
| + | font-size: 100% | ||
| + | } | ||
| + | |||
| + | #content | ||
| + | { | ||
| + | width: 100%; | ||
| + | height: 100%; | ||
| + | margin-left: auto; | ||
| + | margin-right: auto; | ||
| + | background-color: #ffffff; | ||
| + | padding: 0px; | ||
| + | font-size: 100%; | ||
| + | } | ||
| + | |||
| + | |||
| + | } | ||
| + | |||
| + | section { | ||
| + | padding: 75px 0; | ||
| + | } | ||
| + | |||
| + | .section-heading { | ||
| + | margin: 30px 0; | ||
| + | font-size: 4em; | ||
| + | } | ||
| + | |||
| + | .section-lead { | ||
| + | margin: 30px 0; | ||
| + | } | ||
| + | |||
| + | .section-paragraph { | ||
| + | margin: 30px 0; | ||
| + | } | ||
| + | |||
| + | .headline { | ||
| + | padding: 120px 0; | ||
| + | } | ||
| + | |||
| + | @media(max-width:768px) { | ||
| + | .container { | ||
| + | margin: 0 15px; | ||
| + | } | ||
| + | } | ||
| + | |||
| + | </style> | ||
<div id="custom-bootstrap-menu" class="navbar navbar-default navbar-fixed-top" role="navigation"> | <div id="custom-bootstrap-menu" class="navbar navbar-default navbar-fixed-top" role="navigation"> | ||
| − | <div class="container-fluid"> | + | <div class= "container-fluid"> |
| − | + | <!-- Navigation --> | |
| − | + | <nav class="navbar navbar-inverse navbar-fixed-top" role="navigation"> | |
| − | + | <div class="container"> | |
| − | + | <!-- Brand and toggle get grouped for better mobile display --> | |
| − | + | <div class="navbar-header"> | |
| − | + | <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"> | |
| − | + | <span class="sr-only">Toggle navigation</span> | |
| − | + | <span class="icon-bar"></span> | |
| − | + | <span class="icon-bar"></span> | |
| − | + | <span class="icon-bar"></span> | |
| − | + | </button> | |
| − | + | <a class="navbar-brand" href="https://2016.igem.org/Team:Edinburgh_UG"> | |
| − | + | <img src="https://static.igem.org/mediawiki/2016/9/92/Edinburgh_logo2_MINI.png" alt=""> | |
| − | + | </a> | |
| − | + | </div> | |
| − | + | ||
| − | + | <!-- Collect the nav links, forms, and other content for toggling --> | |
| − | + | <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"> | |
| − | + | <ul class="nav navbar-nav"> | |
| − | + | <li> | |
| − | + | <a href="https://2016.igem.org/Team:Edinburgh_UG">Home</a> | |
| − | + | </li> | |
| − | + | <li class="dropdown"> | |
| − | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Team<span class="caret"></span></a> | |
| − | + | <ul class="dropdown-menu" role="menu"> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Team">Team</a></li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Attribution">Attribution</a></li> | |
| − | + | </ul> | |
| − | + | </li> | |
| − | + | <li class="dropdown"> | |
| − | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Human Practices<span class="caret"></span></a> | |
| − | + | <ul class="dropdown-menu" role="menu"> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Overview">Overview</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/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/Engagement">Engagement</a> </li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Ethics">Ethics</a> </li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Mary_Queen_of _Scots">Mary Queen of Scots</a> </li> | |
| − | + | </ul> | |
| − | + | </li> | |
| − | + | <li class="dropdown"> | |
| − | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Project<span class="caret"></span></a> | |
| − | + | <ul class="dropdown-menu" role="menu"> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Description">Description</a></li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Design">Design</a></li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Proof">Proof of Concept</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/Protocols">Protocols</a></li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Limitations">Advantages and Limitations</a></li> | |
| − | + | </ul> | |
| − | + | </li> | |
| − | + | <li class="dropdown"> | |
| − | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Informatics<span class="caret"></span></a> | |
| − | + | <ul class="dropdown-menu" role="menu"> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Lexicon_Encoding">Lexicon Encoding</a></li> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Error_Correction">Error Correction</a></li> | |
| − | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/ | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Encryption">Encryption</a></li> |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Files">Files</a></li> | |
| − | + | </ul> | |
| − | + | </li> | |
| − | + | <li class="dropdown"> | |
| − | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Parts<span class="caret"></span></a> | |
| − | + | <ul class="dropdown-menu" role="menu"> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Basic_Part">Basic Parts</a></li> | |
| − | <li><a href=" | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Composite_Part">Composite Parts</a></li> |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Part_Collection">Part Collection</a> </li> | |
| − | + | </ul> | |
| − | + | </li> | |
| − | + | <li> | |
| − | + | <a href="https://2016.igem.org/Team:Edinburgh_UG/Collaboration">Collaboration</a> | |
| − | + | </li> | |
| − | + | <li class="dropdown"> | |
| − | + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Awards<span class="caret"></span></a> | |
| − | + | <ul class="dropdown-menu" role="menu"> | |
| − | + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Software">Software</a> </li> | |
| − | + | </ul> | |
| − | + | </li> | |
| + | <li class="dropdown"> | ||
| + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Safety<span class="caret"></span></a> | ||
| + | <ul class="dropdown-menu" role="menu"> | ||
| + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Safety/Biological Safety">Biological Safety</a></li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | <li class="dropdown"> | ||
| + | <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Interlab<span class="caret"></span></a> | ||
| + | <ul class="dropdown-menu" role="menu"> | ||
| + | <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Plate_Reader">Plate Reader</a></li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | </ul> | ||
| + | </div> | ||
| + | <!-- /.navbar-collapse --> | ||
| + | </div> | ||
| + | <!-- /.container --> | ||
| + | </nav> | ||
</div> | </div> | ||
</div> | </div> | ||
| + | <!-- End of menu --> | ||
| − | + | ||
| − | + | <div class="row"> | |
| − | + | <div class="col-sm-12"> | |
| − | + | <img src="https://static.igem.org/mediawiki/2016/9/9f/EdiGEM16UGLexEncodingHeader.png" class="img-responsive center-block"> | |
| − | + | ||
| − | + | ||
| − | + | ||
</div> | </div> | ||
| − | </ | + | </div> |
| + | <br> | ||
| + | <br> | ||
<div class="container-fluid"> | <div class="container-fluid"> | ||
<div class="row full-size"> | <div class="row full-size"> | ||
| − | <div class="col-sm- | + | <div class="col-sm-3"></div> |
| − | <div class="col-sm- | + | <div class="col-sm-6"> |
| + | <p></p> | ||
<centre style="font-size:160%;">To create BabblED we needed the capacity to rapidly design and process the information contained in a large lexicon of BabbleBricks. This would have been practically impossible to accomplish by hand and hence required the creation of a software tool with the functionality to encode and decode BabbleBlocks and BabbleBlocks.</centre> | <centre style="font-size:160%;">To create BabblED we needed the capacity to rapidly design and process the information contained in a large lexicon of BabbleBricks. This would have been practically impossible to accomplish by hand and hence required the creation of a software tool with the functionality to encode and decode BabbleBlocks and BabbleBlocks.</centre> | ||
<centre style="font-size:160%;">You can read more about all these mechanisms below or jump straight into the code at our <a href="https://github.com/Edinburgh-iGEM2016/Lexicon-Encoding-and-Decoding" target="_self">Github</a></centre> | <centre style="font-size:160%;">You can read more about all these mechanisms below or jump straight into the code at our <a href="https://github.com/Edinburgh-iGEM2016/Lexicon-Encoding-and-Decoding" target="_self">Github</a></centre> | ||
| + | <p></p> | ||
</div> | </div> | ||
| − | <div class="col-sm- | + | <div class="col-sm-3"></div> |
</div> | </div> | ||
</div> | </div> | ||
| − | + | ||
| + | <br> | ||
| + | <br> | ||
<div class="container-fluid"> | <div class="container-fluid"> | ||
| − | <div class="col-cm- | + | <div class="col-cm-3"></div> |
| − | <div class="col-cm- | + | <div class="col-cm-6"> |
<div id="accordian" class="panel-group"> | <div id="accordian" class="panel-group"> | ||
<div class="panel panel-default"> | <div class="panel panel-default"> | ||
| Line 130: | Line 227: | ||
<div id="collapseOne" class="panel-collapse collapse"> | <div id="collapseOne" class="panel-collapse collapse"> | ||
<div class="panel-body"> | <div class="panel-body"> | ||
| − | <p> | + | <p>To encode the BabbleBricks that make up a lexicon we begin by taking a list of information units, for example words. We then enumerate this list first in decimal and then in base 4. This conversion enables us to encode numbers using digits 0-3 instead of the normal 0-9 in decimal. We convert these base 4 numbers into their DNA equivalent using the schema; A is 0, T is 1, G is 2, C is 3 and pad them all up to 5 base pairs. Now we have these variable sequences we must ensure that no illegal |
| − | <img src="https://static.igem.org/mediawiki/2016/ | + | restriction sites can occur so we add gap sequences. Finally we append a stop codon region, restriction site preventing gapped error correcting region and hangs in each BabbleBrick form. For example:</p> |
| − | + | <img src="https://static.igem.org/mediawiki/2016/c/c9/EdiGEM16UGlex_encoding.png" class="img-responsive center-block"> | |
</div> | </div> | ||
</div> | </div> | ||
| Line 144: | Line 241: | ||
<div id="collapseTwo" class="panel-collapse collapse"> | <div id="collapseTwo" class="panel-collapse collapse"> | ||
<div class="panel-body"> | <div class="panel-body"> | ||
| − | <p> | + | <p>When we assemble our BabbleBricks together to create BabbleBlocks its vital we know what the sequence will be for both verification purposes, so that we can instruct the user exactly which BabbleBricks to use and so we can work out our checksum and address values. We start by appending our word coding BabbleBricks together:</p> |
| − | < | + | <p></p> |
| − | + | <centre>5' GGAGACCAAAATAGCTAATCACTTATGAAAGGAATTAAGGAATTAA + GGAGACCAAATTAGCTAATCACTTATGAAAGGATTTAAGGATTTAA</centre> | |
| + | <p></p> | ||
| + | <centre>5' GGAGACCAAAATAGCTAATCACTTATGAAAGGAATTAAGGAATTAAGGAGACCAAATTAGCTAATCACTTATGAAAGGATTTAAGGATTTAA</centre> | ||
| + | <p></p> | ||
| + | <p>We then look at the word coding regions spaced at regular intervals and use them to calculate a checksum as described in the error correction section <a href="https://2016.igem.org/Team:Edinburgh_UG/Error_Correction" target="_self">here</a>. Finally, we append an address BabbleBlock which acts like a line number telling the decoding program where this BabbleBlock lies in the overall archive.</p> | ||
</div> | </div> | ||
</div> | </div> | ||
| Line 158: | Line 259: | ||
<div id="collapseThree" class="panel-collapse collapse"> | <div id="collapseThree" class="panel-collapse collapse"> | ||
<div class="panel-body"> | <div class="panel-body"> | ||
| − | <p> | + | <p>In order to decode a BabbleBlock we first look at our checksum and use it to verify whether or not error correction needs to be done - if some mistakes are flagged we use our error correcting apparatus and return their results (what our sequence was before the change) back to the decoding program. The error correcting program will look at each word coding region, convert it back to its numerical values and use it as an index to look up the information value of that BabbleBrick in the lexicon. Having decoded all the BabbleBlocks in a batch these will then be sorted in order using the address found at the end of each sequence before the decoded information is returned to the user.</p> |
| − | + | ||
| − | + | ||
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
</div> | </div> | ||
| − | <div class="col-cm- | + | <div class="col-cm-3"></div> |
</div> | </div> | ||
</div> | </div> | ||
| + | |||
| + | <br> | ||
| + | <br> | ||
<div class="row"> | <div class="row"> | ||
| Line 173: | Line 275: | ||
<div class="col-lg-12"> | <div class="col-lg-12"> | ||
<hr> | <hr> | ||
| − | <h2 class="intro-text text-center"> | + | <h2 class="intro-text text-center">Follow |
<strong>Us</strong> | <strong>Us</strong> | ||
</h2> | </h2> | ||
<hr> | <hr> | ||
<div class="intro-text text-center"> | <div class="intro-text text-center"> | ||
| − | |||
| − | |||
<ul class="list-inline banner-social-buttons"> | <ul class="list-inline banner-social-buttons"> | ||
<li> | <li> | ||
| − | <a href="https://twitter.com/EdiGEM2016"><img src="https://static.igem.org/mediawiki/2016/ | + | <a href="https://twitter.com/EdiGEM2016"><img src="https://static.igem.org/mediawiki/2016/9/94/Edinburgh2_t2.jpg"></img></a> |
</li> | </li> | ||
<li> | <li> | ||
| − | <a href="https://www.facebook.com/EdiGEM2016"><img src="https://static.igem.org/mediawiki/2016/c/ | + | <a href="https://www.facebook.com/EdiGEM2016"><img src="https://static.igem.org/mediawiki/2016/c/ce/Edinburgh2_f2.png"></img></a> |
</li> | </li> | ||
<li> | <li> | ||
| − | <a href="https://www.instagram.com/edigem2016/"><img src="https://static.igem.org/mediawiki/2016/ | + | <a href="https://www.instagram.com/edigem2016/"><img src="https://static.igem.org/mediawiki/2016/6/64/Edinburgh2_insta2.png"></img></a> |
</li> | </li> | ||
</ul> | </ul> | ||
| Line 195: | Line 295: | ||
</div> | </div> | ||
</div> | </div> | ||
| + | <br> | ||
| + | <br> | ||
| + | |||
| + | |||
</body> | </body> | ||
</html> | </html> | ||
Latest revision as of 00:27, 20 October 2016
To encode the BabbleBricks that make up a lexicon we begin by taking a list of information units, for example words. We then enumerate this list first in decimal and then in base 4. This conversion enables us to encode numbers using digits 0-3 instead of the normal 0-9 in decimal. We convert these base 4 numbers into their DNA equivalent using the schema; A is 0, T is 1, G is 2, C is 3 and pad them all up to 5 base pairs. Now we have these variable sequences we must ensure that no illegal restriction sites can occur so we add gap sequences. Finally we append a stop codon region, restriction site preventing gapped error correcting region and hangs in each BabbleBrick form. For example:
When we assemble our BabbleBricks together to create BabbleBlocks its vital we know what the sequence will be for both verification purposes, so that we can instruct the user exactly which BabbleBricks to use and so we can work out our checksum and address values. We start by appending our word coding BabbleBricks together:
We then look at the word coding regions spaced at regular intervals and use them to calculate a checksum as described in the error correction section here. Finally, we append an address BabbleBlock which acts like a line number telling the decoding program where this BabbleBlock lies in the overall archive.
In order to decode a BabbleBlock we first look at our checksum and use it to verify whether or not error correction needs to be done - if some mistakes are flagged we use our error correcting apparatus and return their results (what our sequence was before the change) back to the decoding program. The error correcting program will look at each word coding region, convert it back to its numerical values and use it as an index to look up the information value of that BabbleBrick in the lexicon. Having decoded all the BabbleBlocks in a batch these will then be sorted in order using the address found at the end of each sequence before the decoded information is returned to the user.
Follow Us
