Difference between revisions of "Team:Heidelberg/Sandbox"

(Blanked the page)
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  
<html lang="en" dir="ltr" class="client-nojs">
 
<head>
 
<meta charset="UTF-8" />
 
<title>Team:Heidelberg/Sandbox - 2017.igem.org</title>
 
<meta name="generator" content="MediaWiki 1.24.1" />
 
<link rel="alternate" type="application/x-wiki" title="Edit" href="/wiki/index.php?title=Team:Heidelberg/Sandbox&amp;action=edit" />
 
<link rel="edit" title="Edit" href="/wiki/index.php?title=Team:Heidelberg/Sandbox&amp;action=edit" />
 
<link rel="shortcut icon" href="/favicon.ico" />
 
<link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="2017.igem.org (en)" />
 
<link rel="EditURI" type="application/rsd+xml" href="https://2017.igem.org/wiki/api.php?action=rsd" />
 
<link rel="alternate" hreflang="x-default" href="/Team:Heidelberg/Sandbox" />
 
<link rel="copyright" href="http://creativecommons.org/licenses/by/3.0/" />
 
<link rel="alternate" type="application/atom+xml" title="2017.igem.org Atom feed" href="/wiki/index.php?title=Special:RecentChanges&amp;feed=atom" />
 
<link rel="stylesheet" href="https://2017.igem.org/wiki/load.php?debug=false&amp;lang=en&amp;modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.content.externallinks%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.igem.styles&amp;only=styles&amp;skin=igem&amp;*" />
 
<!--[if IE 6]><link rel="stylesheet" href="/wiki/skins/Igem/IE60Fixes.css?303" media="screen" /><![endif]-->
 
<!--[if IE 7]><link rel="stylesheet" href="/wiki/skins/Igem/IE70Fixes.css?303" media="screen" /><![endif]--><meta name="ResourceLoaderDynamicStyles" content="" />
 
<style>a:lang(ar),a:lang(kk-arab),a:lang(mzn),a:lang(ps),a:lang(ur){text-decoration:none}
 
/* cache key: 2017_igem_org:resourceloader:filter:minify-css:7:faeec198b704588e6c9afc1a44274438 */</style>
 
<script src="https://2017.igem.org/wiki/load.php?debug=false&amp;lang=en&amp;modules=startup&amp;only=scripts&amp;skin=igem&amp;*"></script>
 
<script>if(window.mw){
 
mw.config.set({"wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"Team:Heidelberg/Sandbox","wgTitle":"Team:Heidelberg/Sandbox","wgCurRevisionId":127748,"wgRevisionId":127748,"wgArticleId":20811,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":"Lukas Adam","wgUserGroups":["*","user","autoconfirmed"],"wgCategories":[],"wgBreakFrames":false,"wgPageContentLanguage":"en","wgPageContentModel":"wikitext","wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy","wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgMonthNamesShort":["","Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec"],"wgRelevantPageName":"Team:Heidelberg/Sandbox","wgUserId":2048,"wgUserEditCount":45,"wgUserRegistration":1496761953000,"wgUserNewMsgRevisionId":null,"wgIsProbablyEditable":true,"wgRestrictionEdit":[],"wgRestrictionMove":[],"wgWikiEditorEnabledModules":{"toolbar":false,"dialogs":false,"hidesig":true,"preview":false,"previewDialog":false,"publish":false}});
 
}</script><script>if(window.mw){
 
mw.loader.implement("user.options",function($,jQuery){mw.user.options.set({"ccmeonemails":0,"cols":80,"date":"default","diffonly":0,"disablemail":0,"editfont":"default","editondblclick":0,"editsectiononrightclick":0,"enotifminoredits":0,"enotifrevealaddr":0,"enotifusertalkpages":1,"enotifwatchlistpages":1,"extendwatchlist":0,"fancysig":0,"forceeditsummary":0,"gender":"unknown","hideminor":0,"hidepatrolled":0,"imagesize":2,"math":1,"minordefault":0,"newpageshidepatrolled":0,"nickname":"","norollbackdiff":0,"numberheadings":0,"previewonfirst":0,"previewontop":1,"rcdays":7,"rclimit":50,"rows":25,"showhiddencats":0,"shownumberswatching":1,"showtoolbar":1,"skin":"igem","stubthreshold":0,"thumbsize":5,"underline":2,"uselivepreview":0,"usenewrc":1,"watchcreations":1,"watchdefault":1,"watchdeletion":0,"watchlistdays":3,"watchlisthideanons":0,"watchlisthidebots":0,"watchlisthideliu":0,"watchlisthideminor":0,"watchlisthideown":0,"watchlisthidepatrolled":0,"watchmoves":0,"watchrollback":0,
 
"wllimit":250,"useeditwarning":1,"prefershttps":1,"language":"en","variant-gan":"gan","variant-iu":"iu","variant-kk":"kk","variant-ku":"ku","variant-shi":"shi","variant-sr":"sr","variant-tg":"tg","variant-uz":"uz","variant-zh":"zh","searchNs0":true,"searchNs1":false,"searchNs2":false,"searchNs3":false,"searchNs4":false,"searchNs5":false,"searchNs6":false,"searchNs7":false,"searchNs8":false,"searchNs9":false,"searchNs10":false,"searchNs11":false,"searchNs12":false,"searchNs13":false,"searchNs14":false,"searchNs15":false});},{},{});mw.loader.implement("user.tokens",function($,jQuery){mw.user.tokens.set({"editToken":"d6d69b00ab30efe5a1f725d9c914f093+\\","patrolToken":"ddc2a3f05785304f59bfc51c3ad82ce7+\\","watchToken":"29fae7c7f7f201274ef0b7981621fd79+\\"});},{},{});
 
/* cache key: 2017_igem_org:resourceloader:filter:minify-js:7:37c143da26853a066e85a046a3d37eb5 */
 
}</script>
 
<script>if(window.mw){
 
mw.loader.load(["mediawiki.page.startup","mediawiki.legacy.wikibits","mediawiki.legacy.ajax"]);
 
}</script>
 
</head>
 
<body class="mediawiki ltr sitedir-ltr ns-0 ns-subject page-Team_Heidelberg_Sandbox skin-igem action-view">
 
 
        <script type='text/javascript'        src ='/common/tablesorter/jquery.tablesorter.min.js'></script>
 
        <link rel='stylesheet' type='text/css' href='/common/tablesorter/themes/groupparts/style.css' />
 
        <link rel='stylesheet' type='text/css' href='/common/table_styles.css' />
 
 
        <script type='text/javascript'        src ='/wiki/skins/Igem/resources/2017_skin.js'></script>
 
 
 
    <div id='globalWrapper'>
 
        <div id='top_menu_under' class='noprint'></div>
 
        <div id='top_menu_14' class='noprint'>Loading menubar.....</div> <!-- Will be replaced with the jQuery.load -->
 
<script>jQuery('#top_menu_14').load('https://2017.igem.org/cgi/top_menu_14/menubar_reply.cgi',
 
    {  t:"Team%3AHeidelberg%2FSandbox",
 
a:"View+%2FTeam%3AHeidelberg%2FSandbox++Edit+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AHeidelberg%2FSandbox%26action%3Dedit++History+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AHeidelberg%2FSandbox%26action%3Dhistory++Move+%2FSpecial%3AMovePage%2FTeam%3AHeidelberg%2FSandbox++Unwatch+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AHeidelberg%2FSandbox%26action%3Dunwatch%26token%3Def7f6bb9c65b431962b83d897d41b161%252B%255C++Page+%2FTeam%3AHeidelberg%2FSandbox++Discussion+%2Fwiki%2Findex.php%3Ftitle%3DTalk%3ATeam%3AHeidelberg%2FSandbox%26action%3Dedit%26redlink%3D1++" });
 
</script>
 
 
        <!-- Content div contains HQ_page for HQ styles, Logo and title div, and USER CONTENT -->
 
<div id="content" class="mw-body" role="main">
 
    <a id="top"></a>
 
 
            <div id="top_title">
 
                <div class="logo_2017">
 
                    <a href="https://2017.igem.org">
 
                    <img src="https://static.igem.org/mediawiki/2017/8/8b/HQ_page_logo.jpg" width="100px">
 
                    </a>
 
                </div>
 
 
        <h1 id="firstHeading" class="firstHeading">
 
            <span dir="auto">Team:Heidelberg/Sandbox</span>
 
        </h1>
 
            </div>
 
 
            <div id="HQ_page">
 
                <div id="bodyContent">
 
            <div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><p><br />
 
</p><p>
 
<head>
 
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
<meta name="generator" content="MediaWiki 1.16.5" />
 
<link rel="shortcut icon" href="/favicon.ico" />
 
<link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="2014.igem.org (en)" />
 
<link title="Creative Commons" type="application/rdf+xml" href="/wiki/index.php?title=WikitemplateA_home&amp;action=creativecommons" rel="meta" />
 
<link rel="copyright" href="http://creativecommons.org/licenses/by/3.0/" />
 
<link rel="alternate" type="application/atom+xml" title="2014.igem.org Atom feed" href="/wiki/index.php?title=Special:RecentChanges&amp;feed=atom" /> <title>WikitemplateA home - 2014.igem.org</title>
 
<style type="text/css" media="screen, projection">/*<![CDATA[*/
 
@import "/wiki/skins/common/shared.css?270";
 
@import "/wiki/skins/igem/main.css?270";
 
/*]]>*/</style>
 
<link rel="stylesheet" type="text/css" media="print" href="/wiki/skins/common/commonPrint.css?270" />
 
<!--[if lt IE 5.5000]><style type="text/css">@import "/wiki/skins/igem/IE50Fixes.css?270";</style><![endif]-->
 
<!--[if IE 5.5000]><style type="text/css">@import "/wiki/skins/igem/IE55Fixes.css?270";</style><![endif]-->
 
<!--[if IE 6]><style type="text/css">@import "/wiki/skins/igem/IE60Fixes.css?270";</style><![endif]-->
 
<!--[if IE 7]><style type="text/css">@import "/wiki/skins/igem/IE70Fixes.css?270";</style><![endif]-->
 
<!--[if lt IE 7]><script type="text/javascript" src="/wiki/skins/common/IEFixes.js?270"></script>
 
<meta http-equiv="imagetoolbar" content="no" /><![endif]-->
 
           
 
<script type="text/javascript" src="/wiki/skins/common/wikibits.js?270"><!-- wikibits js --></script>
 
<!-- Head Scripts -->
 
<script src="/wiki/skins/common/ajax.js?270"></script>
 
<script src="/wiki/skins/common/mwsuggest.js?270"></script>
 
<script type="text/javascript" src="/wiki/index.php?title=-&amp;action=raw&amp;gen=js&amp;useskin=igem"><!-- site js --></script>
 
<!-- jQuery Javascript -->
 
<script type='text/javascript'        src ='/common/jquery-latest.min.js'></script>
 
<script type='text/javascript'        src ='/common/tablesorter/jquery.tablesorter.min.js'></script>
 
        <link rel='stylesheet' type='text/css' href='/common/tablesorter/themes/groupparts/style.css' />
 
        <link rel='stylesheet' type='text/css' href='/common/table_styles.css' />
 
        <link rel='stylesheet' type='text/css' href='/forum/forum_styles.css' />
 
<script type='text/javascript'        src ='/forum/forum_scripts.js'></script>
 
</head>
 
 
<body>
 
 
 
 
    <div id="top-section">
 
 
<script type="text/javascript"> if (window.isMSIE55) fixalpha(); </script>
 
 
 
 
 
 
<div class="right-menu noprint" id="menubar">
 
    <ul>
 
                <li id="pt-login"><a href="/wiki/index.php?title=Special:UserLogin&amp;returnto=WikitemplateA_home" title="You are encouraged to log in; however, it is not mandatory [o]" accesskey="o">Log in</a></li>     </ul>
 
</div><!-- end right menubar -->
 
 
<div id="search-controls" class="noprint">
 
<form action="/Special:Search" id="searchform">
 
<input id="searchInput" name="search" type="text" title="Search 2014.igem.org [f]" accesskey="f" value="" />
 
<input type='submit' name="go" class="searchButton" id="searchGoButton" value="Go" title="Go to a page with this exact name if exists" />&#160;
 
      <input type='submit' name="fulltext" class="searchButton" id="mw-searchButton" value="Search" title="Search the pages for this text" />
 
</form>
 
</div> <!-- close search controls -->
 
    </div> <!-- close top-section-->
 
    <div id="content">
 
<a name="top" id="top"></a>
 
<h1 class="firstHeading">WikitemplateA home</h1>
 
<div id="bodyContent">
 
<h3 id="siteSub" class='noprint'>From 2014.igem.org</h3>
 
<div id="contentSub"></div>
 
<!--
 
<div id="jump-to-nav">Jump to:                        <a href="#column-one">navigation</a>, <a href="#searchInput">search</a></div>-->
 
<!-- start content -->
 
<p>
 
 
 
<!-- this section changes the default wiki template to a
 
white full width background -->
 
<style type="text/css">
 
#contentSub, #footer-box, #catlinks, #search-controls, #p-
 
 
logo, #sideMenu, #menubar, .logo_2017, .printfooter, .firstHeading,.visualClear {display:
 
 
none;} /*-- hides default wiki settings --*/
 
 
#top-section { /*-- styling for default menu bar (edit, page,
 
 
history, etc.) --*/
 
 
border: 0 none;
 
height: 14px;
 
z-index: 100;
 
top: 0;
 
position: fixed;
 
width: 975px;
 
left: 50%;
 
margin-left: -487px;
 
}
 
 
#globalWrapper, #content { /*-- changes default wiki settings
 
 
--*/
 
width: 100%;
 
height: 100%;
 
border: 0px;
 
background-color: transparent;
 
margin: 0px;
 
padding: 0px;
 
}
 
 
html, body, .wrapper { /*-- changes default wiki settings --
 
 
*/
 
width: 100%;
 
height: 100%;
 
background-color: transparent;
 
}
 
</style>
 
<style>
 
h1,h2,h3,h4,h5,h6{font-weight:100 !important; color: #393939 !important;font-family: 'Josefin Sans' !important;line-height: 70px !important;}
 
    p {font-family: 'Roboto' !important; font-size: 18px !important; color: #393939 !important;}
 
    #Abstract {
 
    font-size: 24px;
 
    color: #393939;
 
}
 
#Abstract:hover {
 
    color: black;
 
}
 
   
 
    #footer-sec h4 {
 
        color: white !important;
 
        font-size: 26px !important;
 
    }
 
 
#footer-sec p {
 
color: grey !important;
 
font-size: 16px !important;
 
font-family: 'Josefin Sans' !important;
 
}
 
    h3 {
 
        font-size: 40px !important;
 
    }
 
    h4 {
 
        font-size: 30px !important;
 
    }
 
    .inline_table {
 
        font-size: 18px !important;
 
        font-family: 'Roboto' !important;
 
    }
 
   
 
    span {
 
        font-size: 18px !important;
 
    }
 
   
 
    .col-lg-1, .col-lg-2, .col-lg-3, .col-lg-4,.col-lg-5, .col-lg-6, .col-lg-7, .col-lg-8, .col-lg-9, .col-lg-10, .col-lg-11, .col-lg-12{
 
      padding-top: 10px !important;
 
        padding-bottom: 50px !important;
 
    }
 
    </style>
 
 
<!-- Assets -->
 
<link rel="stylesheet" href="http://static.tildacdn.com/css/tilda-grid-3.0.min.css" type="text/css" media="all" />
 
 
<link rel="stylesheet" href="http://static.tildacdn.com/css/tilda-zoom-1.0.min.css" type="text/css" media="all" />
 
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Josefin+Sans:300,400|Roboto:300,400,500">
 
<link rel="stylesheet" href="http://azmind.com/demo/bootstrap-navbar-menu/layout-3/assets/bootstrap/css/bootstrap.min.css">
 
       
 
<link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css?action=raw&amp;ctype=text/css" type="text/css" rel="stylesheet">
 
<link rel="stylesheet" href="http://azmind.com/demo/bootstrap-navbar-menu/layout-3/assets/font-awesome/css/font-awesome.min.css">
 
 
<link rel="stylesheet" type="text/css"
 
href="https://2017.igem.org/Template:Heidelberg/navbar/CSS?action=raw&amp;ctype=text/css" />
 
 
<link rel="stylesheet" type="text/css"
 
href="https://2017.igem.org/Template:Heidelberg/table_layout/CSS?action=raw&amp;ctype=text/css" />
 
  <!-- Favicon and touch icons -->
 
  <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css" rel="stylesheet">
 
<script src="http://static.tildacdn.com/js/jquery-1.10.2.min.js"></script>
 
<script src="http://static.tildacdn.com/js/tilda-scripts-2.8.min.js"></script>
 
 
<script src="http://static.tildacdn.com/js/tilda-zoom-1.0.min.js"></script>
 
<script src="http://static.tildacdn.com/js/bootstrap.min.js"></script>
 
<script src="http://static.tildacdn.com/js/jquery.touchswipe.min.js"></script>
 
<script src="http://static.tildacdn.com/js/tilda-map-1.0.min.js"></script>
 
<script src="http://static.tildacdn.com/js/lazyload-1.3.min.js"></script>
 
 
</head>
 
<body class="t-body">
 
                        <!-- CSS -->       
 
                   
 
 
 
   
 
    <!-- Top menu -->
 
<nav class="navbar navbar-inverse navbar-fixed-top navbar-no-bg" role="navigation">
 
<div class="container">
 
<div class="navbar-header">
 
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#top-navbar-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="#"><div id="circle">
 
                    </div></a>
 
</div>
 
<!-- Collect the nav links, forms, and other content for toggling -->
 
<div class="collapse navbar-collapse" id="top-navbar-1">
 
<ul class="nav navbar-nav navbar-right">
 
<li><a href="#">Achievements</a></li>
 
<li class="dropdown"><a href="#">Project <span class="caret"></span></a>
 
             
 
                        </li>
 
<li><a href="#">Modeling</a></li>
 
<li><a href="#">Software &amp; Hardware <span class="caret"></span></a></li>
 
<li class="dropdown"><a href="#">Human Practice <span class="caret"></span></a>
 
                        <ul class="dropdown-menu">
 
                            <li><a href="">Safety &amp; Security</a></li>
 
                            <li class="divider"></li>
 
                            <li><a href="">Integrated Human Practice</a></li>
 
                            <li><a href="">Education</a></li>
 
                            <li class="divider"></li>
 
                            <li><a href="">Public Engagement</a></li>
 
                            <li><a href="">Collaborations</a></li>
 
                        </ul>
 
                       
 
                        </li>
 
<li><a href="#">People</a></li>
 
                        <li><a href="#">Toolbox</a></li>
 
</ul>
 
</div>
 
</div>
 
</nav>
 
                 
 
 
<div style="padding-top: 150px;padding-bottom:105px; background-color:white;">
 
<div class="t-container">
 
<div class="t-col t-col_12">
 
 
                                                        <h1>Project</h1>
 
                                                        <hr>
 
                                                        <div class="panel panel-default">
 
                                                        <div class="panel-heading" role="tab" id="headingOne"  style="background-color: whitesmoke;">
 
                                                          <div class="panel-title">
 
                                                            <a role="button" data-toggle="collapse" href="#collapseOne" aria-expanded="true" id="Abstract" aria-controls="collapseOne" class="trigger collapsed">
 
                                                              Abstract <span class="caret"></span>
 
                                                            </a>
 
                                                          </div>
 
                                                        </div>
 
                                                          <div class="panel-body">
 
                                                              <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sequi molestiae dolorum, soluta temporibus vero perferendis quo odit eaque cum fugiat nihil earum error vitae libero nostrum sed ipsam, beatae ea.</p>
 
                                                          </div>
 
                                                        </div>
 
                                                     
 
                                                        <p>Es gibt im Moment in diese Mannschaft, oh, einige Spieler vergessen ihnen Profi was sie sind. Ich lese nicht sehr viele Zeitungen, aber ich habe gehört viele Situationen. Erstens: wir haben nicht offensiv gespielt. Es gibt keine deutsche Mannschaft spielt offensiv und die Name offensiv wie Bayern. Letzte Spiel hatten wir in Platz drei Spitzen: Elber, Jancka und dann Zickler. Wir müssen nicht vergessen Zickler. Zickler ist eine Spitzen mehr, Mehmet eh mehr Basler. Ist klar diese Wörter, ist möglich verstehen, was ich hab gesagt? Danke. Offensiv, offensiv ist wie machen wir in Platz. Zweitens: ich habe erklärt mit diese zwei Spieler: nach Dortmund brauchen vielleicht Halbzeit Pause. Ich habe auch andere Mannschaften gesehen in Europa nach diese Mittwoch. Ich habe gesehen auch zwei Tage die Training. Ein Trainer ist nicht ein Idiot! Ein Trainer sei sehen was passieren in Platz. In diese Spiel es waren zwei, drei diese Spieler waren schwach wie eine Flasche leer! Haben Sie gesehen Mittwoch, welche Mannschaft hat gespielt Mittwoch? Hat gespielt Mehmet oder gespielt Basler oder hat gespielt Trapattoni? Diese Spieler beklagen mehr als sie spielen! Wissen Sie, warum die Italienmannschaften kaufen nicht diese Spieler? Weil wir haben gesehen viele Male solche Spiel! Haben</p>
 
                                                      <div class="inline_table">
 
 
                                                         
 
                                                          <!-- Table starts here -->
 
                                                          <table id="table" class="table table-hover table-mc-light-blue">
 
                                                              <thead>
 
                                                                <tr>
 
                                                                  <th>ID</th>
 
                                                                  <th>Name</th>
 
                                                                  <th>Link</th>
 
                                                                  <th>Status</th>
 
                                                                </tr>
 
                                                              </thead>
 
                                                              <tbody>
 
                                                                <tr>
 
                                                                  <td>1</td>
 
                                                                  <td>Material Design Color Palette</td>
 
                                                                  <td>
 
                                                                    <a href="#" target="_blank">GitHub</a>
 
                                                                  </td>
 
                                                                  <td>Completed</td>
 
                                                                </tr>
 
                                                                <tr>
 
                                                                  <td>2</td>
 
                                                                  <td>Material Design Color Palette</td>
 
                                                                  <td>
 
                                                                    <a href="#" target="_blank">GitHub</a>
 
                                                                  </td>
 
                                                                  <td>Completed</td>
 
                                                                </tr>
 
                                                                <tr>
 
                                                                  <td>3</td>
 
                                                                  <td>Material Design Color Palette</td>
 
                                                                  <td>
 
                                                                    <a href="#" target="_blank">GitHub</a>
 
                                                                  </td>
 
                                                                  <td>Completed</td>
 
                                                                </tr>
 
                                                              </tbody>
 
                                                            </table>
 
                                                         
 
                                                          Tab1: Description on what the table is about
 
                                                        </div>
 
                                                <p>Es gibt im Moment in diese Mannschaft, oh, einige Spieler vergessen ihnen Profi was sie sind. Ich lese nicht sehr viele Zeitungen, aber ich habe gehört viele Situationen. Erstens: wir haben nicht offensiv gespielt. Es gibt keine deutsche Mannschaft spielt offensiv und die Name offensiv wie Bayern. Letzte Spiel hatten wir in Platz drei Spitzen: Elber, Jancka und dann Zickler. Wir müssen nicht vergessen Zickler. Zickler ist eine Spitzen mehr, Mehmet eh mehr Basler. Ist klar diese Wörter, ist möglich verstehen, was ich hab gesagt? Danke. Offensiv, offensiv ist wie machen wir in Platz. Zweitens: ich habe erklärt mit diese zwei Spieler: nach Dortmund brauchen vielleicht Halbzeit Pause. Ich habe auch andere Mannschaften gesehen in Europa nach diese Mittwoch. Ich habe gesehen auch zwei Tage die Training. Ein Trainer ist nicht ein Idiot! Ein Trainer sei sehen was passieren in Platz. In diese Spiel es waren zwei, drei diese Spieler waren schwach wie eine Flasche leer! Haben Sie gesehen Mittwoch, welche Mannschaft hat gespielt Mittwoch? Hat gespielt Mehmet oder gespielt Basler oder hat gespielt Trapattoni? Diese Spieler beklagen mehr als sie spielen! Wissen Sie, warum die Italienmannschaften kaufen nicht diese Spieler? Weil wir haben gesehen viele Male solche Spiel!</p>
 
                                                <div class="container-fluid">
 
                                                <div class="row"> 
 
<div class="pull-right col-lg-12 col-md-12 col-sm-12 col-xs-12">
 
                                               
 
                                                  <a href="#" target="_blank" ><img src="https://static.igem.org/mediawiki/2014/e/e7/Heidelberg_full_BBa_K1362000.png"  alt="#"></a>
 
                                                  <span>NpuDnaE intein RFC [i] circularization construct</span>
 
                                                </div>
 
                                                </div>
 
                                                </div>
 
                                                <p>Es gibt im Moment in diese Mannschaft, oh, einige Spieler vergessen ihnen Profi was sie sind. Ich lese nicht sehr viele Zeitungen, aber ich habe gehört viele Situationen. Erstens: wir haben nicht offensiv gespielt. Es gibt keine deutsche Mannschaft spielt offensiv und die Name offensiv wie Bayern. Letzte Spiel hatten wir in Platz drei Spitzen: Elber, Jancka und dann Zickler. Wir müssen nicht vergessen Zickler. Zickler ist eine Spitzen mehr, Mehmet eh mehr Basler. Ist klar diese Wörter, ist möglich verstehen, was ich hab gesagt? Danke. Offensiv, offensiv ist wie machen wir in Platz. Zweitens: ich habe erklärt mit diese zwei Spieler: nach Dortmund brauchen vielleicht Halbzeit Pause. Ich habe auch andere Mannschaften gesehen in Europa nach diese Mittwoch. Ich habe gesehen auch zwei Tage die Training. Ein Trainer ist nicht ein Idiot! Ein Trainer sei sehen was passieren in Platz. In diese Spiel es waren zwei, drei diese Spieler waren schwach wie eine Flasche leer! Haben Sie gesehen Mittwoch, welche Mannschaft hat gespielt Mittwoch? Hat gespielt Mehmet oder gespielt Basler oder hat gespielt Trapattoni? Diese Spieler beklagen mehr als sie spielen! Wissen Sie, warum die Italienmannschaften kaufen nicht diese Spieler? Weil wir haben gesehen viele Male solche Spiel!</p>
 
                                                <h2>OptoPACE</h2>
 
 
                                                <p>Enzymes represent a major tool for many branches of the chemical industry, including food, brewing, paper, detergent or biofuel. Millions of years of evolution have allowed these proteins to performed extremely specific chemical modifications that are not only essential for living organisms but can also be of great benefit to produce useful molecules for our life, efficiently and at low cost. A major limitation of the use of enzyme for industrial application and in general out of their natural environment is their stability. They can be destroyed by other enzymes and they can unfold and take non-functional conformation when exposed to non-physiological temperature and pH. Such limitations has motivated research in species that can grow at extreme temperatures . Another major area of chemical research is the design of strategies to stabilize enzymes, and more generally proteins and peptides. Protein circularization, meaning ligation of the N- and C-terminal ends of a protein, represents a promising way to achieve this stabilization. While conserving the functionality of their linear counterpart, circular proteins can be superior in terms of thermostability, resistance against chemical denaturation and protection from exopeptidases . Moreover, a circular backbone can improve <i>in vivo</i> stability of therapeutical proteins and peptides. All these remarkable properties motivated us to develop new tools to circularize any protein of interest.
 
                                                Our <a href="#References" title="#"> Toolbox Guide</a> provides a step-by-step strategy to clone a circularization linker and express it in <i>E. coli</i>. Moreover, in case of complex structures where the protein extremities are far from each other, we have developed the software tool <a href="#" title="#"> CRAUT </a>that will design the appropriate rigid linkers.
 
                                                </p><p><i>Please find more information about the circularization of proteins and the theory that laid the foundation for the circularization kit of the toolbox on the <a href="https://2014.igem.org/Team:Heidelberg/Toolbox/Circularization" class="external text" rel="nofollow">Circularization pages</a></i>.
 
                                                </p>
 
                                                <h2>Circularization Constructs</h2>
 
                                                <p>The most promising approaches to <a href="/Team:Heidelberg/Toolbox/Circularization" title="Team:Heidelberg/Toolbox/Circularization"> circularize</a> proteins are protein trans-splicing using <a href="/Team:Heidelberg/Project/Background" title="Team:Heidelberg/Project/Background"> split inteins</a> and Sortase A-catalyzed cyclization. Both methods require the addition of specific proteins domains or peptides to the protein to be circularized. Consequently, on DNA level, creating circular proteins is equivalent to creating fusion proteins. However, existing protein fusion standards like <a href="http://parts.igem.org/Help:Standards/Assembly/RFC23" class="external text" rel="nofollow">RFC[23</a>] cause scars. Those scars on protein level may affect protein function and further complicate 3D-structure modeling.
 
                                                Therefore, we decided to create the new RFC[i] that allows scarless cloning of inteins. Our intein circularization constructs apply to this standard, while our sortase constructs are closely related and can be used similarly. Detailed instructions on how to use our constructs are provided in our <a href="/Team:Heidelberg/Toolbox_Guide" title="Team:Heidelberg/Toolbox Guide"> Toolbox Guide</a>.
 
                                                </p>
 
                                                <h2> Split Intein Circularization</h2>
 
                                                <p>
 
                                                <div class="pull-right col-lg-12 col-md-12 col-sm-12 col-xs-12">
 
                                                      <a href="#" target="_blank" ><img src="https://static.igem.org/mediawiki/2014/e/e7/Heidelberg_full_BBa_K1362000.png"  alt="#"></a>
 
                                                    <span>NpuDnaE intein RFC [i] circularization construct</span>
 
                                                       
 
 
                                                </div>
 
                                                <p>Between the coding sequences of the <i>Npu</i> DnaE C-intein and the N-intein we placed. Exteins, RFC [i] standard overhangs and BsaI sites have to be added to the coding sequence of the protein to be circularized without start- and stop codons by PCR. By Golden Gate assembly, the mRFP selection marker has to be replaced with the protein insert. After addition of an inducible promotor the circular protein is ready to be expressed. For detailed step-by-step instructions please use our <a href="/Team:Heidelberg/Toolbox_Guide" title="Team:Heidelberg/Toolbox Guide">Toolbox Guide</a>.
 
                                                </p><p>Upon expression of the fusion protein, the split intein domains reassemble to the active <a href="/Team:Heidelberg/Project/Background" title="Team:Heidelberg/Project/Background">intein</a> and thus ligate the termini of the protein to be circularized in trans-splicing reaction.
 
                                                </p><p>These constructs were successfully used to circularize <a href="/Team:Heidelberg/Project/Linker_Screening" title="Team:Heidelberg/Project/Linker Screening">lambda lysozyme</a> and <a href="/Team:Heidelberg/Project/Xylanase" title="Team:Heidelberg/Project/Xylanase">xylanase</a> and probably <a href="/Team:Heidelberg/Project/PCR_2.0" title="Team:Heidelberg/Project/PCR 2.0">DNMT1</a>.
 
                                                </p>
 
                                                <h2>Sortase Circularization</h2>
 
                                                <p>
 
                                                <div class="pull-right col-lg-12 col-md-12 col-sm-12 col-xs-12">
 
                                                   
 
                                                      <a  href="https://static.igem.org/mediawiki/2014/7/70/Heidelberg_orig_BBa_K1362002.png" target="_blank" ><img src="https://static.igem.org/mediawiki/2014/e/e7/Heidelberg_full_BBa_K1362002.png" alt="Figure 2) <a href='http://parts.igem.org/Part:BBa_K1362002'> BBa_K1362002</a>"></a>
 
 
                                                        <span>Sortase A circularization construct (with His6)</span>
 
                                                       
 
 
                                                   
 
                                                </div>
 
                                                <p>An mRFP selection marker <a href="http://parts.igem.org/Part:BBa_J04450" class="external text" rel="nofollow">BBa_J04450</a>, which can be removed by restriction with BsaI, is flanked by TEV protease cleavage site (left) and a sorting signal (right) with a His6 tag.
 
                                                </p><p>BsaI sites and overhangs corresponding to the sortase A circularization construct have to be added to the coding sequence of the protein to be circularized without start- and stop codons by PCR. By Golden Gate assembly, the mRFP selection marker has to be replaced with the protein insert. After addition of an inducible promotor protein is ready to be expressed. The protein has to be purified and treated with TEV protease  and sortase A. The sortase A catalyzes the transpeptidation reaction that leads to backbone circularization.
 
                                                </p><p><i>Please find more information about our the toolkit for cirularization on the <a href="https://2014.igem.org/Team:Heidelberg/Toolbox/Circularization_Constructs" class="external text" rel="nofollow">Circularization Construct pages</a></i>.
 
                                                </p><p>
 
                                                    <div class="linie"></div>
 
 
 
                                                <h1>Oligomerization</h1>
 
                                                <p>Split inteins constitute a useful tool to produce huge polymers in vivo: Hauptmann et al. managed to fabricate synthetic spider silk with microfiber structure. The results using an easy-to-handle split intein system were stunning: The polymers had a molecular weight of 250 kDa and more <a href="#References">[7]</a>. Further application of oligomerization by inteins includes the posttranslational complexation of multi-domain proteins, after their domains have been expressed individually. This approach is very valuable considering great difficulities of expressing large eukaryotic proteins in <i>E.coli</i>.
 
                                                </p>
 
                                                <h4> Standardization of oligomerization </h4>
 
                                                <p>The valuable properties of spider silk, for example its exceptional strength and elasticity, result from numerous repeats of certain protein motifs. Convenitonal methods to multimerize these motifs bear a lot of difficulties: Often genetic and mRNA instability constitute a barrier for the production of multimers as fusion proteins <a href="#References">[1]</a>. Posttranslational assembly through split inteins is therefore the solution to overcome these problems. The successfull polimerization of spider silk potein motifs demonstrates the potential of split inteins to be a useful tool for the production of new biomaterials by performing oligomerization reactions with split inteins. The iGEM team Heidelberg standardized (lik to toolbox guide) the oligomerization procedure with split inteins to allow easy handling with different proteins.
 
                                                </p><p>The use of non-orthogonal split inteins can further be exploited to direct the oligomerisation of several protein domains at once.
 
                                                </p>
 
                                                <h4>The mechanism</h4>
 
                                                <p>
 
                                                <div class="pull-right col-lg-6 col-md-6 col-sm-8 col-xs-12">
 
                                                   
 
                                                      <a href="https://static.igem.org/mediawiki/2014/0/0e/Heidelberg_orig_Oligomerization.png" target="_blank" ><img src="https://static.igem.org/mediawiki/2014/3/34/Heidelberg_half_Oligomerization.png"  alt="Oligomerization with inteins."></a>
 
                                                    <span>Oligomerization with inteins</span>
 
                                                   
 
 
                                                    </div>
 
                                                </div>
 
 
                                                <p>Oligomerization reactions require the same constructs as the ones used for protein circularization.</p><p>Circularization is achieved by bringing the N and C terminus of a protein very close together, so both intein parts can asseble, cut out off the protein and thereby circularize it. In contrast, oligomerization occurs when both termini of a protein cannot reach each other and the intein parts of two neighbouring proteins assemble.</p>
 
                                                <h1>Fusion and Tagging</h1>
 
                                                <h4>Introduction</h4>
 
                                                <p>Post-translational modifications are present in nature in great numbers.Synthetic Biology, however, has not yet made use of the innumerable possibilities nature has developed. With our collection of intein assembly constructs we expand the arsenal of synthetic biology by enabling unlimited changes of a protein's amino acid sequence even after translation.
 
                                                </p>
 
                                                <h4> Standard Construction</h4>
 
                                                <p>To be able <b>to fuse</b> any two halves of a protein together can have many different uses. We therefore saw the need for a standardised construct, the intein assembly part. This BioBrick part allows the user to clone two DNA-sequences coding for two parts of a peptide into a plasmid prepared with selection markers and standardised overhangs. Those parts were all send in with additional hexahistidine-tags to enable quick analysis on a western blot, however there are highly customisable parts available as well.Visit our <a href="https://2014.igem.org/Team:Heidelberg/Parts#allParts" class="external text" rel="nofollow">parts page</a> to get an overview of our assembly constructs.
 
                                                In an extensive assay we proved the principle behind split protein assembly by showing that GFP can be artificially split into two halves and thereafter be reassembled so the fluorescence is restored. Visit the <a href="https://2014.igem.org/Team:Heidelberg/Project/Reconstitution" class="external text" rel="nofollow">split Fluorescent Protein</a>.
 
                                                </p>
 
                                                <div class="container-fluid">
 
                                                <div class="row"> 
 
                                                <div class=" col-lg-6 col-md-6 col-sm-8 col-xs-12">
 
                                                   
 
                                                      <a class="img-enlarge" href="https://static.igem.org/mediawiki/2014/d/d3/Heidelberg_orig_AssemblyConstructforN-Intein%281%29.png" target="_blank" ><img src="https://static.igem.org/mediawiki/2014/d/d1/Heidelberg_half_AssemblyConstructforN-Intein%281%29.png" class="img-responsive" alt="N-intein fusion construct."></a>
 
                                                   
 
                                                    <span>N-intein fusion construct</span>
 
                                                 
 
                                                 
 
                                                </div>
 
 
 
                                                <div class="col-lg-6 col-md-6 col-sm-8 col-xs-12">
 
                                                   
 
                                                      <a  href="#" target="_blank" ><img src="https://static.igem.org/mediawiki/2014/3/37/Heidelberg_half_AssemblyConstructforC-Intein%281%29.png" alt="#"></a>
 
 
                                                      <span>C-intein fusion construct</span>
 
 
 
                                                   
 
                                                </div>
 
                                                    </div> </div>
 
                                                <h1> Posttranslational Modifications</h1>
 
                                                <h4> Introduction</h4>
 
                                                <p>Posttranslational modifications are highly prevalent in nature: Almost every protein in a cell is modified after having been translated, adding numerous varieties of the protein to the mere protein backbone.
 
                                                Synthetic Biology, however, can expand the possibilities offered by nature and introduce synthetic posttranslational modifications or attachments, such as biophysical probes. As the two parts of a split intein assemble in a highly specific manner, the modifications are introduced controllable a certain locus.
 
                                                There are different publications on intein-based introduction of posttranslational modifications, including phosphorylation, lipidation, glycosylation, acetylation and ubiquitination <a href="#References">[4]</a>.
 
                                                Phosphorylation, for example has been applied with tyrosine kinase C-terminal Src kinase (Csk) in order to be able to study the structure and function of this specifically modified protein <a href="#References">[5]</a>.
 
                                                </p>
 
                                                <h4> Standard construction</h4>
 
                                                <p>Applying the intein assembly constructs the iGEM team Heidelberg provides a tool for all kinds of natural as well as synthetic posttranslational modifications by chemoselective addition of a peptide to a recombinant protein.
 
                                                The principle is based on intein-mediated protein fusion using the <a href="http://parts.igem.org/wiki/index.php?title=Part:BBa_K1362141" class="external text" rel="nofollow">SspDnaB</a> split intein for N-terminal modifications and SspDnaX-S11 for C-terminal ones. The split SspDnaB intein has a very short N-terminal part, consisting of only 11 amino acids intein and 5 amino acids extein sequence and a much longer C-terminal part. By contrast, <a href="http://parts.igem.org/wiki/index.php?title=Part:BBa_K1362110" class="external text" rel="nofollow">SspDnaX-S11</a> has a C-terminal part consisting of only 6 amino acids intein and 3 amino acids extein sequence, but a much longer N-terminal part.
 
                                                The short part including the desired modification is easy to obtain by chemical synthesis. This  offers the possibility to introduce this modification at a specific locus.
 
                                                </p><p><br />
 
                                                <i>In general, split inteins are powerful tools to easily introduce all kinds of posttranslational modifications in a highly chemoselective manner.</i>
 
                                                Use our <a href="https://2014.igem.org/Team:Heidelberg/Toolbox_Guide" class="external text" rel="nofollow">toolbox guide</a> to attach posttranslational modifications and attachments to your protein of interest!
 
                                                </p>
 
                                                <h3>Translocation</h3>
 
                                                <h4> Introduction</h4>
 
                                                <p>Adding and removal of translocation tags is one application example for split intein-mediated fusion of two protein domains. Translocation tags offer the possibility to transfer proteins to a certain locus inside the cell by attaching a short tag sequence to the terminus of one's protein of interest. Expressed fused to the protein, which is the conventional way, such a tag is neither removable nor attachable to a protein at a certain time point. Usage of split inteins for tagging offers new dimensions of mobility and control: Tags can be attached (using fusion constructs) or removed (using the intein protease) posttranslationally at a specific time point.
 
                                                        </p>
 
                                               
 
                                            <h1 id="References">References</h1>
 
                                            <p>[1] McGinness, KE et al.: Engineering controllable protein degradation. Molecular Cell
 
                                            22, 701–707, June 9, 2006. DOI 10.1016/j.molcel.2006.04.027
 
                                            </p><p>[2] Volkmann, G. et al: Controllable protein cleavages through intein fragment complementation. Protein Sci, 18 (2009), pp. 2393–2402. DOI: 10.1002/pro.249
 
                                            </p><p>[3] Volkmann, Gerrit et al.: Site-specific protein cleavage in vivo by an intein-derived protease.   
 
                                            FEBS Letters 586 (2012) 79–84. doi:10.1016/j.febslet.2011.11.028.
 
                                            </p><p>[4] Vila-Perello, Miquel et al.: Biological Applications of Protein Splicing. Cell 143. October 15, 
 
                                            2010. DOI 10.1016/j.cell.2010.09.031.
 
                                            </p><p>[5] Muir, Tom W. et al.: Expressed protein ligation: A general method for protein engineering. Proc. 
 
                                            Natl. Acad. Sci. USA 95 (1998).
 
                                            </p><p>[6] Lu, Wei et al.: Split intein facilitated tag affinity purification for recombinant proteins with controllable tag removal by inducible auto-cleavage. J. Chromatogr. A 1218 (2011)
 
                                            </p><p>[7] Hauptmann, V. et al.: Native-sized spider silk proteins synthesized in planta via intein-based multimerization. Transgenic Res (2013) 22:369–377. DOI 10.1007/s11248-012-9655-6.
 
                                            </p><p>[8/D] Vila-Perello, Miquel et al.: Biological Applications of Protein Splicing. Cell 143. October 15, 
 
                                            2010. DOI 10.1016/j.cell.2010.09.031.
 
                                            </p><p>[9/E] Muir, Tom W. et al.: Expressed protein ligation: A general method for protein engineering. Proc. Natl. Acad. Sci. USA 95 (1998).
 
                                            </p><p>[10] McGinness, KE et al.: Engineering controllable protein degradation. Molecular Cell
 
                                            22, 701–707, June 9, 2006. DOI 10.1016/j.molcel.2006.04.027
 
                                            </p><p>[11] Volkmann, G. et al: Controllable protein cleavages through intein fragment complementation. Protein Sci, 18 (2009), pp. 2393–2402. DOI: 10.1002/pro.249
 
                                            </p><p>[12] Volkmann, Gerrit et al.: Site-specific protein cleavage in vivo by an intein-derived protease.   
 
                                            FEBS Letters 586 (2012) 79–84. doi:10.1016/j.febslet.2011.11.028.
 
                                                      </div>
 
                                                    </div>
 
                                       
 
                                            <section id="footer-sec">
 
        <div class="container">
 
            <div class="row" style="padding-top: 30px;">
 
                <div class="col-md-3">
 
                    <h4>About us</h4>
 
                    <p>"We are an extremely motivated team of young students competing in the worlds biggest synthetic biology competition"</p>
 
 
                </div>
 
                <div class="col-md-3">
 
                    <h4> Useful <strong>Links</strong> </h4>
 
 
<li>
 
<a href="#">
 
<i class="fa fa-angle-right">
 
</i>
 
Special pages
 
</a>
 
</li>
 
<li>
 
<a href="#">
 
<i class="fa fa-angle-right">
 
</i>
 
Main Page
 
</a>
 
</li>
 
</div>
 
                <div class="col-md-3">
 
                    <h4> Follow us on </h4>
 
                    <a href="#" target="_blank" id="facebook"><i class="fa fa-facebook-square fa-3x"></i></a> 
 
                    <span style="color: grey">&amp;</span>
 
                    <a href="#" target="_blank" id="twitter"><i class="fa fa-twitter-square fa-3x"></i></a>
 
                </div>
 
                <div class="col-md-3">
 
                    <h4> Contact us </h4>
 
                    <li>
 
<i class="fa fa-map-marker fa-lg">
 
</i>
 
Im Neuenheimer Feld 267
 
<br>
 
69120 Heidelberg
 
</li>
 
<li>
 
<i class="fa fa-phone">
 
</i>
 
1 -234 -456 -7890
 
</li>
 
 
<li>
 
<a href="mailto:info@yourdomain.com">
 
<i class="fa fa-envelope">
 
</i>
 
bioquant@uni-heidelberg.de
 
</a>
 
</li>
 
                </div>
 
            </div>
 
        </div>
 
    </section>
 
        <script src="http://azmind.com/demo/bootstrap-navbar-menu/layout-3/assets/bootstrap/js/bootstrap.min.js"></script>
 
 
 
 
<!-- Saved in parser cache with key 2014_igem_org:pcache:idhash:224-0!1!0!!en!2!edit=0 and timestamp 20170831072851 -->
 
<div class="printfooter">
 
Retrieved from "<a href="https://2014.igem.org/WikitemplateA_home">https://2014.igem.org/WikitemplateA_home</a>"</div>
 
<div id="catlinks"><div id='catlinks' class='catlinks catlinks-allhidden'></div></div> <!-- end content -->
 
<div class="visualClear"></div>
 
</div>
 
    </div>
 
<!-- PAGE FOOTER -- ITEMS FROM COLUMN ! HAVE BEEN MOVED HERE  -- RDR  -->
 
<div class="visualClear"></div>
 
    <div id='footer-box' class='noprint'>
 
        <div id="footer">
 
              <div id="f-poweredbyico"><a href="http://www.mediawiki.org/"><img src="/wiki/skins/common/images/poweredby_mediawiki_88x31.png" height="31" width="88" alt="Powered by MediaWiki" /></a></div>       <div id="f-copyrightico"><a href="http://creativecommons.org/licenses/by/3.0/"><img src="http://i.creativecommons.org/l/by/3.0/88x31.png" alt="Attribution 3.0 Unported" width="88" height="31" /></a></div>     <ul id="f-list">
 
 
 
  <!-- Recentchanges is not handles well DEBUG -->
 
    <li id="t-recentchanges"><a href="/Special:RecentChanges"
 
      title='Recent changes'>Recent changes</a></li>
 
 
    <li id="t-whatlinkshere"><a href="/Special:WhatLinksHere/WikitemplateA_home"
 
      title="List of all wiki pages that link here [j]" accesskey="j">What links here</a></li>
 
 
                        <li id="t-recentchangeslinked"><a href="/Special:RecentChangesLinked/WikitemplateA_home"
 
                          title="Recent changes in pages linked from this page [k]" accesskey="k">Related changes</a></li>
 
 
 
 
                <li id="t-specialpages"><a href="/Special:SpecialPages"
 
                  title="List of all special pages [q]" accesskey="q">Special pages</a>
 
                </li>
 
                <li><a href='/Special:Preferences'>My preferences</a></li>
 
            </ul>
 
        </div> <!-- close footer -->
 
        <div id='footer'>
 
    <ul id="f-list">
 
 
            <li id="t-print"><a href="/wiki/index.php?title=WikitemplateA_home&amp;printable=yes"
 
              title="Printable version of this page [p]" accesskey="p">Printable version</a>
 
            </li>
 
 
            <li id="t-permalink"><a href="/wiki/index.php?title=WikitemplateA_home&amp;oldid=145279"
 
              title="Permanent link to this revision of the page">Permanent link</a>
 
            </li>
 
 
 
        <li id="privacy"><a href="/2014.igem.org:Privacy_policy" title="2014.igem.org:Privacy policy">Privacy policy</a></li>
 
        <li id="disclaimer"><a href="/2014.igem.org:General_disclaimer" title="2014.igem.org:General disclaimer">Disclaimers</a></li>
 
    </ul>
 
</div> <!-- close footer -->
 
    </div> <!-- close footer-box -->
 
 
<script>if (window.runOnloadHook) runOnloadHook();</script>
 
</div>
 
</body>
 
 
 
</p>
 
<!--
 
NewPP limit report
 
CPU time usage: 0.004 seconds
 
Real time usage: 0.004 seconds
 
Preprocessor visited node count: 4/1000000
 
Preprocessor generated node count: 24/1000000
 
Post‐expand include size: 0/2097152 bytes
 
Template argument size: 0/2097152 bytes
 
Highest expansion depth: 2/40
 
Expensive parser function count: 0/100
 
-->
 
 
<!-- Saved in parser cache with key 2017_igem_org:pcache:idhash:20811-0!*!*!*!*!*!* and timestamp 20170919171929 and revision id 127748
 
-->
 
</div>             <div class="visualClear"></div>
 
            </div>
 
    </div>
 
 
        </div>
 
 
        <!-- Side Menubar -->
 
        <div id="sideMenu">
 
            <a href="https://2017.igem.org">
 
                <div id="home_logo" >
 
                <img src="https://static.igem.org/mediawiki/2017/b/bf/HQ_menu_logo.jpg">
 
                </div>
 
            </a>
 
 
            <div style="clear:both; height:5px;"></div>
 
 
            <div id="menuDisplay"></div>  <!- Menu will be loaded here ->
 
        </div>
 
 
        <!-- Pop_Why Div is definded here -->
 
        <div class="pop_why_cover"></div>
 
 
        <div class="pop_why_box" >
 
            <div class="pop_close">× </div>
 
            <div class="pop_why_content"><h3> Loading ... </h3></div>
 
        </div>
 
 
    </div>
 
</html>
 

Latest revision as of 00:34, 16 December 2017