From OpenWetWare
Jump to: navigation, search


<link rel="stylesheet" href=",100&subset=latin"> <script src="//" ></script>

<script type"text/javascript"> $(function () { $("style[media*='screen']").remove(); $("link[href*='favicon']").remove(); //fix heading var h1 = $(".firstHeading").text().split("/"); $(".firstHeading").text(h1[h1.length-1]); $("tr:odd").addClass("odd"); }); $('link[rel="shortcut icon"]').attr('href',''); </script> <link rel="icon" type="image/png" href="">

<style type="text/css"> /**** Base styles ****/ /*#column-one, */

  1. content {
   font-weight: bold;


  1. footer, div#sidebar-main, #contentSub, .firstHeading, #siteSub, #jump-to-nav, .printfooter, #p-cactions {
   display: none;


/*only show edit button - also remove p-cactions from previous style*/

  1. ca-nstab-main, #ca-talk, #ca-history, #ca-move, #ca-watch, #ca-link, #p-personal{
   display: none;


  1. ca-edit{

} /*Make text on edit buttons visible for easier editing*/ .editButtons, #wpSummary{ color: black; }


<meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>EchiDNA 2014</title>

<link href="" rel="stylesheet">

<style type="text/css">

@font-face { font-family: BIOMOD_font; src: url(; }

@font-face { font-family: HEADING_font; src: url(; }

@font-face { font-family: HEADING_ACTIVE_font; src: url(; }

@font-face { font-family: FOOTER_font; src: url(; }

/*Alter default header*/

.navbar-default .navbar-nav > li > a { font-family: HEADING_font, Arial, sans-serif; }

.navbar-default .navbar-nav > li > ul > li > a { font-family: HEADING_font, Arial, sans-serif; font-size: 10pt; }

.navbar-default .navbar-right > li { color: #f8f8f8; } .navbar-default .navbar-nav > .active > a, .navbar-default .navbar-nav > .active > a:hover, .navbar-default .navbar-nav > .active > a:focus { color: #F7941E; background-color: #F8F8F8; font-family: HEADING_ACTIVE_font, Arial, sans-serif; }

a[href^="mailto"] { color: white; }

a[href^="mailto"]:hover { color: #f7941e; text-decoration: none; }

a#vccri, a#edit-link { color:white; }

a#vccri:hover, a#edit-link:hover { color: #f7941e; text-decoration: none; }

body { background-image: url(; background-repeat: repeat; color:white; font-family: BIOMOD_font, Arial, sans-serif; }

.col-centered { display:inline-block; float:none; text-align:left; /* inline-block space fix */ margin-right:-4px; }

h4 { color: #f7941e; font-family: HEADING_font, Arial, sans-serif; }

/*Footer stuff*/

html { position: relative; min-height: 100%; }

body { margin-bottom: 35px; }

.footer { position: absolute; bottom: 0; width: 100%; height: 35px; background-color: #0c2850; }

/*Fix OpenWetWare Editing Box*/

  1. wpTextbox1 {

color: #000; font-family: Arial; width: 100%; }


<html lang="en">


<script type="text/javascript"> $('#lab_book_link').addClass('active'); </script>

<style type="text/css">

  1. next-link {

color: #0F3264; text-decoration: none; margin-left: auto; margin-right: auto; font-size: 12pt; }

  1. next-link:hover {

color: #F7941E; }

.col-centered { display:inline-block; float:none; text-align:left; /* inline-block space fix */ margin-right:-4px; }

#LAB-BOOK-TITLE { font-family: HEADING_font, Arial, sans-serif; color: black; font-size: 16pt; padding-top: 35px; }

h2 { font-family: HEADING_font, Arial, sans-serif; color: #0F3264; font-size: 14pt; }

img { margin: 10px 15px; }

orange { color: #F7941E; }

#LAB-BOOK-TOP { display:block; width: 766px; height: 76px; margin-left: auto; margin-right: auto; margin-bottom: 0px; background-image: url(; }

#LAB-BOOK-REPEAT { display:block; position: relative; width: 766px; height: auto; margin-left: auto; margin-right: auto; margin-bottom: 0px; padding-bottom: 30px; padding-left: 60px; padding-right: 20px; background-image: url(; background-repeat: repeat-y; background-position: top; }

#LAB-BOOK-TEXT { position: relative; padding-top: 15px; color: black; text-align: justify; }

.image-left { font-size: 9pt; width: 50%; float: left; text-align: center; padding: 10px 15px; }

.image-right { font-size: 9pt; width: 50%; float: right; text-align: center; padding: 10px 15px; }

.image-center { font-size: 9pt; width: 100%; float: left; text-align: center; padding: 10px 15px; }

.image-right img, .image-left img { max-width: 91%; }

.image-center img { max-width: 95%; }



<div class="container" style="text-align: center; margin-top: 100px;">

<div id="LAB-BOOK-TOP"> <div id="LAB-BOOK-TITLE" style="padding-left:60px; text-align: justify;">Re-designing the Molecular Beacon</div> </div> <div id="LAB-BOOK-REPEAT"> <div id="LAB-BOOK-TEXT">

<!-- ************************************************************************************************************************************************ --> <!-- ************************************************ START EDITING ********************************************************************************* --> <!-- ************************************************************************************************************************************************ -->

<h2>Aim</h2> To design a new kind of molecular beacon which is modular and capable of being tethered to its neighbours in our cooperative biosensor. <h2>Background</h2> <a href="" target="_blank"> Molecular beacons</a> are a simple DNA-based probe for detecting the presence of a specific sequence of DNA or RNA in a sample. The mechanism of detection is via a conformational change in the beacon that occurs upon hybridising with the target DNA or RNA. This change in conformation alters the distance between two fluorescent moieties, thus changing the strength of Förster resonance energy transfer (FRET) and resulting in a fluorescent readout. <br><br> Structurally, molecular beacons contain four domains:

<div class="image-left"> <div class="image-centre"> <div style="height:auto"><img src="" /></div> Fig.1 The basic principles of a molecular beacon. </div> &nbsp;

</div><br> <br> <ul> <li><orange>Sensor:</orange> A domain that is the reverse complement of the target DNA or RNA; usually around 25 nucleotides in length.</li> <li><orange>Stem:</orange> Two complementary domains (around 5bp) on either side of the sensor domain, forming a hairpin structure. <li><orange>Fluorophore:</orange> Typically a 5' nucleotide modified with fluorescent dye. <li><orange>Quencher:</orange> Typically a 3' nucleotide modified with a molecule that quenches fluorescent emission from the fluorophore. The efficiency of quenching is distance-dependent. </ul> <br><br> <h2>Considerations</h2> We identified the following parameters to be important in molecular beacon: <br> <ul> <li> <orange>Sensor sequence</orange> defines the target signal the molecular beacon detects. Ideally it should have not self-complimentary regions that compete with the hairpin structure.</li>

 				<li> <orange> Sensor length </orange>defines the accuracy of detection as well as providing the free energy required to cause the conformational change and produce a signal.</li>
 				<li> <orange>Stem length</orange> defines the free energy cost that must be overcome to activate the fluorescent moiety.</li>


We knew we would have to optimise our cooperative biosensor by exploring these parameters in our molecular beacon. But synthesising DNA with quencher- and fluorophore-modifications is expensive, has a low yield, and a slow turn around in synthesis. Therefore we wanted to avoid synthesising a new molecular beacon every time we needed to vary any of the components of the system. <br><br> We deconstructed the four domains of conventional molecular beacons and reconstructed them as an assembly of four oligos, each representing a separate domain. This modular design allowed us to quickly, easily, and cheaply generate different molecular beacon-like sensors by swapping out the different versions of each domain.

<h2>Single Switch Design #1</h2> <div class="image-center"> <div><img src="" /></div> Fig 2. A conventional molecular beacon (left) and their <br>corresponding strands in our redesigned switch (right). </div><br> To generate sequences for our first molecular beacon, we used a mix of random and pre-defined sequences. Our lab already had a 20nt AlexaFluor488 modified oligo - we used this and in combination with random sequences for the remaining domains. We plugged these into NUPACK for analysis, and iterated analysis until we achieved<a href= ""> high theoretical yields of assembly</a>. We then truncated the clip by increments, thus generating variations in 'clip strength' by altering the free energy of hybridisation with the loop of the molecular beacon. This allowed us to find the optimal clip strength for observing a clear change in fluorescence before we proceeded to construct our cooperative biosensor. <br><br> Check out how this design performed in the lab <a href=>HERE</a>, or for the nitty gritty sequences and protocols head to our <a href="" target="_blank">rough lab book</a>.

<h2>Single Switch Design #2</h2> The initial <a href=>experimental data</a> led to improvements in our designs. From our experiments we developed two hypotheses about our first single switch: <br> <ul> <li> It occurred to us that our first design may allow both the clip and signal strands to be hybridised at the same time, forming a trianglular rather than linear conformation. This means that even though signal binds the fluorophore may remain quenched. </li>

 				<li> We also observed unexpected results for shorter clips. In molecular beacons with shorter clips a region of the sensor was left unhybridised. Through a strand-by-strand analysis of homo- and hetero-dimers we found that this region resulted in an array of secondary structures that counfound our expectations even in this simple system. </li>

</ul> <br> <div class="image-center"> <div><img src="" /></div> Fig 3. A potential triangular confirmation of single switch #1. <br> The signal strand binds without triggering a change in fluorescence. </div> <br> To overcome these problems we flipped the positions of the fluorophore and quencher strands. Additionally, we altered the clip so that it would compete with the signal to hybridise to the molecular beacon, removing the unhybrised nucleotides that caused secondary structures in our single switch #1. Finally, though our design is entirely modular and could detect any arbitrary sequence of DNA, we decided to make our molecular beacon relevant by altering the specificity of our sensor strand for a conserved sequence en the Ebola virus genome that has been used in a <a target="_blank" href=>Reverse Transcriptase PCR detection method</a>.

<div class="image-center"> <div><img src="" /></div> Fig. 4. Single switch #2 </div> <br> The new position of the clip removed the possibility of the alternate triangular conformation, while also removing unhybridised nucleotides and providing a simpler method to tether multiple switches together in our <a target="_blank"href="">cooperative molecular biosensor</a>. Check out how this design performed in the lab compared to our first design <a target="_blank" href=>here</a>, or for the nitty gritty sequences and protocols head to the <a target="_blank" href="">rough lab book</a>.


We have built on the proven biosensing technology of molecular beacons by teasing apart the different components of the system into separate, variable domains. This design has allowed our team to fully characterise the molecular beacon with a range of different clip strengths with different concentrations of the target strand of DNA. Furthermore, the redesigned molecular beacon is entirely compatible with the <a target="_blank"href="">design of our cooperative molecular biosensor</a>, which will allow direct comparison of independently vs. cooperatively functioning molecular beacons.

<!-- ************************************************************************************************************************************************ --> <!-- ************************************************ STOP EDITING ********************************************************************************* --> <!-- ************************************************************************************************************************************************ -->

</div> <br><br> <a id="next-link" href="">Click here to go back to the Lab Book Overview</a> </div> </div>




   <script src=""></script>
   <script src=""></script>

<script type="text/javascript"> var pathArray = window.location.pathname.split( '/' ); var newPathname = ""; for (i = 2; i < pathArray.length; i++) { newPathname += pathArray[i]; newPathname += "/"; } newPathname=newPathname.slice(0,-1); document.getElementById('edit-link').setAttribute('href', ''+newPathname+String.fromCharCode(38)+'action=edit'); </script>