Difference between revisions of "Team:Munich"

(Undo revision 19368 by Lici (talk))
Line 1: Line 1:
−
{{CGU_Taiwan}}
+
{{Munich}}
 +
 
 +
 
 
<html>
 
<html>
 +
<style>
 +
* {margin: 0; padding: 0;
 +
 
 +
}
 +
body{
 +
  font-family: Helvetica;
  
 +
}
  
−
<div class="column full_size" >
 
−
<img src="http://placehold.it/2000x300/d3d3d3/f2f2f2">
 
−
</div>
 
  
 +
#container {
 +
width: 80%;
 +
overflow: hidden;
 +
margin: 50px auto;
 +
}
  
 +
h2{
 +
  text-align: center;
 +
}
  
−
<div class="column full_size" >
+
.banner > img{
−
<h1> Welcome to iGEM 2017! </h1>
+
  margin-left:50px;
−
<p>Your team has been approved and you are ready to start the iGEM season! </p>
+
}
−
</div>
+
  
−
<div class="clear"></div>
+
.banner {
 +
  width:5000px;
 +
  overflow: hidden;
 +
  height: 233px;
 +
}
  
−
<div class="column half_size" >
+
/*keyframe animations*/
−
<h5>Before you start: </h5>
+
.first {
−
<p> Please read the following pages:</p>
+
-webkit-animation: bannermove 20s linear infinite;
−
<ul>
+
  -moz-animation: bannermove 20s linear infinite;
−
<li>  <a href="https://2017.igem.org/Competition">Competition Hub</a> </li>
+
    -ms-animation: bannermove 20s linear infinite;
−
<li> <a href="https://2017.igem.org/Competition/Deliverables/Wiki">Wiki Requirements page</a></li>
+
    -o-animation: bannermove 20s linear infinite;
−
<li> <a href="https://2017.igem.org/Resources/Template_Documentation">Template documentation</a></li>
+
        animation: bannermove 20s linear infinite;
−
</ul>
+
}
−
</div>
+
  
−
<div class="column half_size" >
+
@keyframes "bannermove" {
−
<div class="highlight">
+
0% {
−
<h5> Styling your wiki </h5>
+
    margin-left: 0px;
−
<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>
+
100% {
−
</div>
+
    margin-left: -2000px;
−
</div>
+
}
  
−
<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://2017.igem.org/Judging/Pages_for_Awards">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>
+
  
−
</div>
+
@-moz-keyframes bannermove {
 +
0% {
 +
  margin-left: 0px;
 +
}
 +
100% {
 +
  margin-left: -2000px;
 +
}
  
 +
}
  
 +
@-webkit-keyframes "bannermove" {
 +
0% {
 +
  margin-left: 0px;
 +
}
 +
100% {
 +
  margin-left: -2000px;
 +
}
  
 +
}
  
−
<div class="column half_size" >
+
@-ms-keyframes "bannermove" {
−
<h5> Editing your wiki </h5>
+
0% {
−
<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>
+
  margin-left: 0px;
−
<p> <a href="https://2017.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
+
}
 +
100% {
 +
  margin-left: -2000px;
 +
}
  
−
</div>
+
}
  
 +
@-o-keyframes "bannermove" {
 +
0% {
 +
  margin-left: 0px;
 +
}
 +
100% {
 +
  margin-left: -2000px;
 +
}
  
−
<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://2017.igem.org/Calendar">iGEM 2017 calendar</a> </li>
+
−
<li>Have lots of fun! </li>
+
−
</ul>
+
−
</div>
+
  
  
−
<div class="column half_size" >
+
h1{
−
<h5>Inspiration</h5>
+
  text-align: center;
−
<p> You can also view other team wikis for inspiration! Here are some examples:</p>
+
  color: black;
−
<ul>
+
  font-size: 50px;
−
<li> <a href="https://2014.igem.org/Team:SDU-Denmark/"> 2014 SDU Denmark </a> </li>
+
  border-radius:12px;
−
<li> <a href="https://2014.igem.org/Team:Aalto-Helsinki">2014 Aalto-Helsinki</a> </li>
+
  background-color: #92D4EF;
−
<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" >
+
  margin: 20px;
−
<h5> Uploading pictures and files </h5>
+
}
−
<p> You can upload your pictures and files to the iGEM 2017 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!)<br><br>
+
  
−
<a href="https://2017.igem.org/Special:Upload">
+
h2{
−
UPLOAD FILES
+
text-align: center;
−
</a>
+
margin-bottom: 10px;
−
</p>
+
}
−
</div>
+
  
 +
#hola{
  
 +
}
  
 +
h3{
 +
  text-align: center;
 +
  margin: 10px;
 +
}
  
 +
.problem, .solution{
 +
  padding-left: 50px;
 +
  padding-right: 50px;
 +
  padding-top: 20px;
 +
  padding-bottom: 20px;
 +
  border-radius:50px;
 +
}
  
  
 +
.problem{
 +
  margin-right:500px;
 +
}
 +
table{
 +
  margin:auto;
 +
  border-spacing: 2.5vw 0;
 +
  margin-top: 30px;
 +
  margin-bottom: 30px;
 +
}
 +
 +
 +
.footer{
 +
  background-color: #92D4EF;
 +
  text-align: center;
 +
  margin-bottom: 0;
 +
  padding-top: 5px;
 +
 
 +
}
 +
 +
h5{
 +
  text-align: center;
 +
 +
  margin-bottom: 10px;
 +
 
 +
}
 +
 +
td{
 +
  width: 50%;
 +
  vertical-align: top;
 +
}
 +
 +
a{
 +
  text-decoration: none;
 +
  padding-left:7px;
 +
 
 +
}
 +
 +
</style>
 +
 +
<body>
 +
 +
<div id="container"> <!-- Apparently, the freaking space lines between the elements are important, so for the animation to loop seamlessly, the img elements can't have them inbetween. -->
 +
 +
  <div class="banner first"><img id="picture" src="https://static.igem.org/mediawiki/2017/9/92/T--Munich--logo.png" alt="" style="width:350px;height:233px;"/><img src="https://static.igem.org/mediawiki/2017/3/36/T--Munich--scientist.jpg" alt="" style="width:350px;height:233px" /><img src="https://static.igem.org/mediawiki/2017/f/fa/T--Munich--Explaning_MakeMunich.jpg" alt="" style="width:350px;height:233px;"/><img src="https://static.igem.org/mediawiki/2017/4/40/T--Munich--Wetlab_work.jpg" alt="" style="width:350px;height:233px;"/><img src="https://static.igem.org/mediawiki/2017/c/cd/Groupphoto_170504.jpeg" alt="" style="width:350px;height:233px;"/><img class="hola" src="https://static.igem.org/mediawiki/2017/9/92/T--Munich--logo.png" alt="" style="width:350px;height:233px;"/><img class ="hola" src="https://static.igem.org/mediawiki/2017/3/36/T--Munich--scientist.jpg" alt="" style="width:350px;height:233px" /><img src="https://static.igem.org/mediawiki/2017/f/fa/T--Munich--Explaning_MakeMunich.jpg" alt="" style="width:350px;height:233px;"/><img src="https://static.igem.org/mediawiki/2017/4/40/T--Munich--Wetlab_work.jpg" alt="" style="width:350px;height:233px;"/><img src="https://static.igem.org/mediawiki/2017/c/cd/Groupphoto_170504.jpeg" alt="" style="width:350px;height:233px;"/>
 +
    </div>
 +
  </div>
 +
                                                         
 +
 +
<div class ="projectName">
 +
  <h1> CascAID </h1>
 +
</div>
 +
 +
 
 +
 +
<div class="part2">
 +
  <table style="width:100%; text-align:justify" >
 +
  <tr>
 +
    <td bgcolor="white" class = "problem"> <h3 id="hola">Problem</h3>
 +
      <p> Although there are many diagnose tests available that can detect even the smallest traces of a pathogen, they usually require expensive lab-equipment or skilled labor. Usually, places most prone to diseases are also the ones most lacking such equipment or personal, and thus, where tests are least asequible.
 +
Many different diseases can present similar symptoms. But because the treatment for each of them can vary greatly (e.g. bacterial vs viral infetion), a quick and reliable diagnose is important to start as soon as possible with the right treatment. On the other hand, wrongly recognizing the cause of a disease not only leads to prescription of the wrong medicine, but also can contribute to the spread of resistances. <br><br>
 +
New diagnose tool must take these points into consideration and be designed with affordability, availability, simplicity and reliability in mind, and, where possible, be flexible enough to cover a wide array of diseases in order to present the user with a single, powerful product.
 +
       
 +
      </p> </td>
 +
    <td bgcolor="white" class ="solution"><h3>Solution</h3>
 +
    <p> We are working at a diagnose tool that combines the power of high sensible methods with the affordability needed for a wide application field. Our project, named CascAID, utilizes the CRISPR/Cas effector Cas13a to quickly and reliably test for different pathogens based on their RNA. By cleaverly designing a short RNA sequence, it is possible to guide Cas13a to only cleave RNA molecules belonging to a pathogen. Once the target has been digested, Cas13a becomes active and cleaves indiscriminately other RNA molecules. If the sample contained pathogen, then digested RNA will be found, where as a negative sample won't produce digestion fragments. <br><br>
 +
To provide an affordable product, CascAID will be implemented on paper-strips, using deep-freeze technologie that allows proteins and other organic molecules to remain active over long periods of time, even at room temperature. Thanks to the cheapness of paper as a material, CascAID-strips can be single use, thus reducing the risk of cross-contamination without increasing the costs of manufacture.
 +
      </p>
 +
    </td>
 +
  </tr>
 +
</table>
 +
 +
</div>
 +
  <br>
 +
 
 +
 +
<div class="footer">
 +
    <h5>Follow our progress or contact us on:</h5>
 +
<div class="logos"> <a href="https://www.facebook.com/Munich.iGEM/">
 +
<img border="0" src="https://image.flaticon.com/icons/svg/33/33702.svg" width="30px" height="30px" align="center"> </a>
 +
  <a  href="https://www.instagram.com/igem.munich.2017/">
 +
<img border="0" src="https://image.flaticon.com/icons/svg/87/87390.svg" width="30px" height="30px" align="center"> </a>
 +
<a  href="mailto:igem.munich@gmail.com"> <img  src= "https://static.igem.org/mediawiki/2017/9/97/T--Munich--mail_symbol.svg" width="30px" height="30px" align="center"> </a> </div>
 +
 
 +
 
 +
  <br>
 +
 +
</div>
  
 +
    </body>
 
</html>
 
</html>

Revision as of 14:35, 31 May 2017

HOME
TEAM
PROJECT
Description
Design
Experiments
Notebook
InterLab
Contribution
Model
Results
Demonstrate
Improve
Attributions
PARTS
Parts
Basic Parts
Composite Parts
Part Collection
SAFETY
HUMAN PRACTICES
Silver HP
Integrated and Gold
Public Engagement
AWARDS
Applied Design
Entrepreneurship
Hardware
Measurement
Model
Plant
Software
JUDGING FORM

Munich


CascAID

Problem

Although there are many diagnose tests available that can detect even the smallest traces of a pathogen, they usually require expensive lab-equipment or skilled labor. Usually, places most prone to diseases are also the ones most lacking such equipment or personal, and thus, where tests are least asequible. Many different diseases can present similar symptoms. But because the treatment for each of them can vary greatly (e.g. bacterial vs viral infetion), a quick and reliable diagnose is important to start as soon as possible with the right treatment. On the other hand, wrongly recognizing the cause of a disease not only leads to prescription of the wrong medicine, but also can contribute to the spread of resistances.

New diagnose tool must take these points into consideration and be designed with affordability, availability, simplicity and reliability in mind, and, where possible, be flexible enough to cover a wide array of diseases in order to present the user with a single, powerful product.

Solution

We are working at a diagnose tool that combines the power of high sensible methods with the affordability needed for a wide application field. Our project, named CascAID, utilizes the CRISPR/Cas effector Cas13a to quickly and reliably test for different pathogens based on their RNA. By cleaverly designing a short RNA sequence, it is possible to guide Cas13a to only cleave RNA molecules belonging to a pathogen. Once the target has been digested, Cas13a becomes active and cleaves indiscriminately other RNA molecules. If the sample contained pathogen, then digested RNA will be found, where as a negative sample won't produce digestion fragments.

To provide an affordable product, CascAID will be implemented on paper-strips, using deep-freeze technologie that allows proteins and other organic molecules to remain active over long periods of time, even at room temperature. Thanks to the cheapness of paper as a material, CascAID-strips can be single use, thus reducing the risk of cross-contamination without increasing the costs of manufacture.


Follow our progress or contact us on: