View source for Team:Carnegie Mellon/Description

{{:Team:Carnegie_Mellon/navbar}}
<html>
<head>
<style src = "" type = "text/css">

/*Tried to make the content border-color:width the whole page... Not the stupid box*/
body {
  border: 0px;
}

/* makes the white boxes go away */
#content{
				background: white;
				border: 0px;
				float: center;
                                width: 100%;
				margin-left:auto;
                                margin-right:auto;
				padding-top: 0px;
                                min-height: 700px;
			}


.jumbotron {
  background-image:url('https://static.igem.org/mediawiki/2015/0/0f/IGEM_Fort_Pitt_Bridge.png');
  /* background-image:url('http://cdn.mysitemyway.com/etc-mysitemyway/backgrounds/legacy-previews/backgrounds/nightlights/nightlights-000890-light-orange-moss-green.jpg'); */
  height: 600px;
  background-repeat: no-repeat;
  background-size: cover;
  margin-top: 15px;
}

.jumbotron .container {
  position: relative;
  top:220px;
}

.jumbotron .container .title {
  color: orange;
  font-size: 100px;  
  font-family: Georgia, serif;
  font-weight: bold;
  text-align: center;
}

.jumbotron p {
  font-size: 50px;
  color: #fff;
  background-color: rgba(0,0,0,.5);
  margin-top: 30px;
  text-align: center;
  font-family: "Palatino Linotype", "Book Antiqua", Palatino, serif;
}

.jumbotron a {
  text-decoration: none;
  background-color: #40e6ee;
  font-size: 25px;
  color: #fff;
  padding: 10px 15px 10px 15px;
  margin: 0px 10px 0px 10px;
}

.jumbotron a:hover {
  /* background-color: #fcf95a; */
    background-color: #40e6ee;
}

/* /jumbotron code */



.container {
  text-align: center;
}

.words {
    font-family:"Palatino Linotype";
    font-size: 20px;
    line-height: 25px;
    width: 85%;
    margin-left: 50px;
}

.title {
    color: #40e6ee;
    font-size: 50px;
    font-weight: bold;
    font-family: Palatino Linotype;
    padding-top: 20px;
    padding-bottom: 20px;
}

</style>
</head>

<body>
    <div class="jumbotron">
      <div class="container">
        <div class = "title">Project.</div>
        <p>We built a light.</p>
       <!--  <a href = "https://2015.igem.org/Team:Carnegie_Mellon/game">Game</a>
        <a href = "#">Maker Movement</a>
        <a href = "https://2015.igem.org/Team:Carnegie_Mellon/Interviews">Interviews</a> -->
      </div>
    </div>  

<div class = "title">Project Description.</div>
    <div class="words">
      Engineered sensors are all around us. Biological systems contain natural biosensors that can be utilized to monitor the environment and health of ecosystems and the individuals within them. A critical part of building a sensor is the ability to detect and measure the output. To enable the design and fabrication of DIY biosensors, we are creating instructions on how to build a low cost luminometer and fluorimeter. The precision, accuracy, and sensitivity of the instrument will be demonstrated using a set of luciferase and fluorescent protein reporters. <br></br>
      The luminometer is a simple photodiode detector with the signal being integrated using an Arduino and output data being processed with open source software. The fluorimeter is an extension that includes an LED light source and emission/excitation filters appropriate for the fluorescent protein to be analyzed. The entire light path is encased in a 3D printed shell. <br></br>
      To test the luminometer, the luciferases from <i>Gaussia princeps</i>, <i>Renilla reniformis</i> and <i>Photinus pyralis</i> were codon optimized for E. coli  and expressed from a strong constitutive promoter. The Gaussia luciferase was extracellularly targeted. Fluorescent proteins including blue, green, yellow, orange, and red with different promoter strengths and an estrogen biosensor are used to calibrate the fluorometer. <br></br>
      To engage the public about synthetic biology and iGEM, we have developed a BioLight powered by luciferase. For education purposes, a light (with parts) and plans for the fluorimeter were provided to the “The Citizen Science Lab” in Pittsburgh and we are hopeful that this will excite the community to start building.
    </div>
</body>












<!-- 
<h2> Project Description </h2>

<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
<br />

<h5>What should this page contain?</h5>
<ul>
<li> A clear and concise description of your project.</li>
<li>A detailed explanation of why your team chose to work on this particular project.</li>
<li>References and sources to document your research.</li>
<li>Use illustrations and other visual resources to explain your project.</li>
</ul>


<br />
<h4>Advice on writing your Project Description</h4>

<p>
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements. 
</p>

<p>
Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
</p>


<br />
<h4>References</h4>
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you though about your project and what works inspired you.</p>



<h4>Inspiration</h4>
<p>See how other teams have described and presented their projects: </p>

<ul>
<li><a href="https://2014.igem.org/Team:Imperial/Project"> Imperial</a></li>
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> UC Davis</a></li>
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">SYSU Software</a></li>
</ul>

</div>
-->


</html>