Difference between revisions of "Team:Edinburgh UG"

Line 1: Line 1:
−
{{EdigemUG16_Home}}
+
{{Example}}
 
<html>
 
<html>
  
−
    <head>
+
<div class="column full_size" >
−
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
+
<img src="http://placehold.it/800x300/d3d3d3/f2f2f2">
−
<link href="http://fonts.googleapis.com/css?family=Pacifico" rel="stylesheet" type="text/css">
+
</div>
  
−
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>
+
<div class="column full_size" >
−
    </head>
+
<h2> Welcome to iGEM 2016! </h2>
 +
<p>Your team has been approved and you are ready to start the iGEM season! </p>
  
−
  <!-- menu -->
+
</div>  
−
<div id="custom-bootstrap-menu" class="navbar navbar-default navbar-fixed-top" role="navigation">
+
 
−
    <div class="container-fluid">
+
<div class="column half_size" >
−
        <div class="navbar-header">
+
<h5>Before you start: </h5>
−
            <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-menubuilder"><span class="sr-only">Toggle navigation</span><span class="icon-bar"></span><span class="icon-bar"></span><span class="icon-bar"></span>
+
<p> Please read the following pages:</p>
−
            </button>
+
<ul>
−
        </div>
+
<li> <a href="https://2016.igem.org/Requirements">Requirements page </a> </li>
−
        <div class="collapse navbar-collapse navbar-menubuilder">
+
<li> <a href="https://2016.igem.org/Wiki_How-To">Wiki Requirements page</a></li>
−
            <ul class="nav navbar-nav navbar-right">
+
</ul>
−
              <li class="active">
+
−
                  <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/Collaborations">Collaboration</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">Project</a></li>
+
−
                      <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/Experiments">Experiments</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/Results">Results</a></li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Notebook">Notebook</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/Parts">Team Parts</a></li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Basic_Part">Basic Parts</a></li>
+
−
                      <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 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">Safety</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/Human_Practices">Human Practices</a></li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Silver">Silver</a> </li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Gold">Gold</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>
+
−
                    </ul>
+
−
                  </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/Entrepreneurship">Entrepreneurship</a></li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Hardware">Hardware</a> </li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Software">Software</a> </li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Measurement">Measurement</a> </li>
+
−
                      <li><a href="https://2016.igem.org/Team:Edinburgh_UG/Model">Model</a> </li>
+
−
                    </ul>
+
−
                  </li>
+
−
            </ul>
+
−
        </div>
+
−
    </div>
+
 
</div>
 
</div>
  
 +
<div class="column half_size" >
 +
<div class="highlight">
 +
<h5> Styling your wiki </h5>
 +
<p>You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.</p>
 +
<p>While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.</p>
 +
</div>
 +
</div>
  
−
    <!-- End of menu  -->
+
<div class="column full_size" >
 +
<h5> Wiki template information </h5>
 +
<p>We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the <a href="https://2016.igem.org/Judging/Pages_for_Awards/Instructions">Pages for awards</a> link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!</p>
  
−
<body>
+
</div>
 +
 
 +
 
 +
 
 +
 
 +
<div class="column half_size" >
 +
<h5> Editing your wiki </h5>
 +
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>
 +
<p> <a href="https://2016.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
 +
 
 +
</div>
 +
 
 +
 
 +
<div class="column half_size" >
 +
<h5>Tips</h5>
 +
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
 +
<ul>
 +
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
 +
<li>Be clear about what you are doing and how you plan to do this.</li>
 +
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
 +
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
 +
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
 +
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2016.igem.org/Calendar">iGEM 2016 calendar</a> </li>
 +
<li>Have lots of fun! </li>
 +
</ul>
 +
</div>
 +
 
 +
 
 +
<div class="column half_size" >
 +
<h5>Inspiration</h5>
 +
<p> You can also view other team wikis for inspiration! Here are some examples:</p>
 +
<ul>
 +
<li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
 +
<li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
 +
<li> <a href="https://2014.igem.org/Team:LMU-Munich">2014 LMU-Munich</a> </li>
 +
<li> <a href="https://2014.igem.org/Team:Michigan"> 2014 Michigan</a></li>
 +
<li> <a href="https://2014.igem.org/Team:ITESM-Guadalajara">2014 ITESM-Guadalajara </a></li>
 +
<li> <a href="https://2014.igem.org/Team:SCU-China"> 2014 SCU-China </a></li>
 +
</ul>
 +
</div>
 +
 
 +
<div class="column half_size" >
 +
<h5> Uploading pictures and files </h5>
 +
<p> You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
 +
When you upload, set the "Destination Filename" to <br><code>T--YourOfficialTeamName--NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
 +
 
 +
 
 +
<div class="button_click"  onClick=" parent.location= 'https://2016.igem.org/Special:Upload '"> 
 +
UPLOAD FILES
 +
</div>
 +
 
 +
</div>
  
−
  <div class="jumbotron text-centre">
 
−
    <img src="https://static.igem.org/mediawiki/2016/4/4c/EdiGEM16UGhomeheader.jpeg" class="img-responsive">
 
−
  </div>
 
  
−
  <div class="container-fluid">
 
−
    <div class="row full-size">
 
−
      <div class="col-sm-6">
 
−
        <p></p>
 
−
        <h3 style="font-size:250%;">By 2040, we will run out of the materials needed to store digital data.</h3>
 
−
        <p style="font-size:180%;">If this happens, there will be no capacity for Twitter, </p>
 
−
        <p style="font-size:180%;">Facebook or iGEM to function online. Last year, data </p>
 
−
        <p style="font-size:180%;">centres worldwide used more electricity than the entire </p>
 
−
        <p style="font-size:180%;">United Kingdom. By 2020, it will cost more than $13.7 </p>
 
−
        <p style="font-size:180%;">billion to power data centres per year. </p>
 
−
      </div>
 
−
      <div class="col-sm-6">
 
−
        <p></p>
 
−
        <img src="https://static.igem.org/mediawiki/2016/4/44/EdiGEM16UGppie.png" class="img-responsive center-block">
 
−
      </div>
 
−
    </div>
 
−
  </div>
 
  
−
  <div class="container-fluid">
 
−
    <div class="row full-size">
 
−
      <div class="col-sm-6">
 
−
      </div>
 
−
      <div class="col-sm-6">
 
−
        <p></p>
 
−
        <h3 style="font-size:250%;">We have a solution: DNA Text Encoding</h3>
 
−
      </div>
 
−
    </div>
 
−
  </div>
 
  
−
  <div class="container-fluid">
 
−
    <div class="row full-size">
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <img src="https://static.igem.org/mediawiki/2016/5/55/EdiGEM16UGdensity.png" class="img-responsive center-block">
 
−
      </div>
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <img src="https://static.igem.org/mediawiki/2016/2/26/EdiGEM16UGdollar.png" class="img-responsive center-block">
 
−
      </div>
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <img src="https://static.igem.org/mediawiki/2016/1/1f/EdiGEM16UGhourglassResize.png" class="img-responsive center-block">
 
−
      </div>
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <img src="https://static.igem.org/mediawiki/2016/a/a4/EdiGEM16UGpuzzleResize.png" class="img-responsive center-block">
 
−
      </div>
 
−
    </div>
 
−
  </div>
 
  
−
  <div class="container-fluid">
 
−
    <div class="row full-size">
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <h3 style="font-size:200%;" class="text-center">Density</h3>
 
−
        <p class="text-center">DNA has 1000 times</p>
 
−
        <p class="text-center">greater storage density</p>
 
−
        <p class="text-center">than flash memory</p>
 
−
      </div>
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <h3 style="font-size:200%;" class="text-center">Affordability</h3>
 
−
        <p class="text-center">All our encoding programmes </p>
 
−
        <p class="text-center">are open source and initial </p>
 
−
        <p class="text-center">synthesis of the lexicon is done </p>
 
−
        <p class="text-center">for you providing significant </p>
 
−
        <p class="text-center">cost reductions on existing </p>
 
−
        <p class="text-center">methods</p>
 
−
      </div>
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <h3 style="font-size:200%;" class="text-center">Longevity</h3>
 
−
        <p class="text-center">DNA can last for </p>
 
−
        <p class="text-center">thousands of years </p>
 
−
        <p class="text-center">without consuming </p>
 
−
        <p class="text-center">resources; modern  </p>
 
−
        <p class="text-center">hard drives can only </p>
 
−
        <p class="text-center">last 50</p>
 
−
      </div>
 
−
      <div class="col-sm-3">
 
−
        <p></p>
 
−
        <h3 style="font-size:200%;" class="text-center">Modularity</h3>
 
−
        <p class="text-center">Assembly of our BabbleBricks </p>
 
−
        <p class="text-center">is unrestricted and completely </p>
 
−
        <p class="text-center">customisable </p>
 
−
      </div>
 
−
    </div>
 
−
  </div>
 
  
−
  <div class="container-fluid">
 
−
    <div class = "row full-size">
 
−
        <div class="col-sm-12">
 
−
          <p></p>
 
−
          <h3 style="font-size:250%;" class="text-center">Abstract</h3>
 
−
          <p>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.</p>
 
−
          <p>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.</p>
 
−
          <p>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.</p>
 
−
          <p>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.</p>
 
−
            <p>References:</p>
 
−
            <p>1.http://www.nature.com/nmat/journal/v15/n4/full/nmat4594.html#supplementary-information</p>
 
−
            <p>2.http://www.greenpeace.org/international/Global/international/publications/climate/2011/
 
−
            Cool%20IT/dirty-data-report-greenpeace.pdf/</p>
 
−
    </div>
 
−
  </div>
 
  
−
</body>
 
 
</html>
 
</html>

Revision as of 13:42, 20 July 2016

MENU ▤

Welcome to iGEM 2016!

Your team has been approved and you are ready to start the iGEM season!

Before you start:

Please read the following pages:

Styling your wiki

You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.

While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.

Wiki template information

We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the Pages for awards link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!

Editing your wiki

On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world!

Use WikiTools - Edit in the black menu bar to edit this page

Tips

This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started:

  • State your accomplishments! Tell people what you have achieved from the start.
  • Be clear about what you are doing and how you plan to do this.
  • You have a global audience! Consider the different backgrounds that your users come from.
  • Make sure information is easy to find; nothing should be more than 3 clicks away.
  • Avoid using very small fonts and low contrast colors; information should be easy to read.
  • Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the iGEM 2016 calendar
  • Have lots of fun!
Inspiration

You can also view other team wikis for inspiration! Here are some examples:

Uploading pictures and files

You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name.
When you upload, set the "Destination Filename" to
T--YourOfficialTeamName--NameOfFile.jpg. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)

UPLOAD FILES