Difference between revisions of "Team:Cornell/Demonstrate"

Line 1: Line 1:
 
<!DOCTYPE html>
 
<!DOCTYPE html>
 
<html class="no-js">
 
<html class="no-js">
    <style> /********************************* WIKI RESET  ********************************/
+
<style> /********************************* WIKI RESET  ********************************/
        #sideMenu, #top_title {
+
@import url('https://fonts.googleapis.com/css?family=Crimson+Text:400,700%7CSource+Sans+Pro:400,700%7CMontserrat:500');
            display:none;
+
  #sideMenu, #top_title {
        }
+
    display:none;
        #content {
+
  }
            padding:0px;
+
  #content {
            width:100% !important;
+
    padding:0px;
            margin-top:-26px;
+
    width:100% !important;
            margin-left:0px ;
+
    margin-top:-26px;
            font-family:"Raleway", "Helvetica Neue", Helvetica, Arial, sans-serif; !important;
+
    margin-left:0px ;
        }
+
    font-family:"Raleway", "Helvetica Neue", Helvetica, Arial, sans-serif; !important;
        body {
+
  }
            background-color: black;
+
  body {
            font-family:"Raleway", "Helvetica Neue", Helvetica, Arial, sans-serif; !important;
+
    background-color: black;
        }
+
    font-family:"Crimson Text", "Source Sans Pro", Montserrat, sans-serif; !important;
        #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 {
+
  }
            font-family:"Raleway", "Helvetica Neue", Helvetica, Arial, sans-serif; !important;
+
  #bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 {
        }
+
    font-family:"Raleway", "Helvetica Neue", Helvetica, Arial, sans-serif; !important;
    </style>
+
  }
    <head>
+
#HQ_page .bios-banner-caption {
        <meta charset="UTF-8">
+
text-align: center; !important;
        <meta http-equiv="X-UA-Compatible" content="IE=edge">
+
font-family: 'Crimson Text', serif; !important;
        <title>Demonstrate</title>
+
font-size: 65px; !important;
        <meta name="description" content="Attributions">
+
}
        <meta name="viewport" content="width=device-width, initial-scale=1">
+
 
        <!--Stylesheets-->
+
#HQ_page p {
        <link rel="stylesheet" href="styles/bootstrap.min.css">
+
font-family:"Crimson Text", "Helvetica Neue", Helvetica, Arial, sans-serif; !important;
        <link rel="stylesheet" href="styles/styles.css"> <!--For nav bar text-->
+
font-size: 16px; !important;
        <link rel="stylesheet" href="styles/main.css">
+
text-align: left; !important;
        <!-- JavaScript Files-->
+
 
        <script src="js/jquery-1.11.2.min.js" type="text/javascript"></script>
+
}
        <script src="js/main.js" type="text/javascript"></script>
+
 
     </head>
+
#HQ_page .bio-title {
 +
font-size: 36px; !important;
 +
}
 +
 
 +
#HQ_page .bio-subtitle {
 +
font-size: 24px; !important;
 +
}
 +
 
 +
#HQ_page .sponsors-title {
 +
margin: 100px 0; !important;
 +
text-align: center; !important;
 +
font-size: 65px; !important;
 +
}
 +
 
 +
a:visited {
 +
color: #000000;
 +
}
 +
 
 +
</style>
 +
<head>
 +
    <meta charset="UTF-8">
 +
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
 +
    <title>Demonstrate</title>
 +
    <meta name="description" content="Bios">
 +
    <meta name="viewport" content="width=device-width, initial-scale=1">
 +
    <!--Stylesheets-->
 +
    <link rel="stylesheet" href="https://2017.igem.org/Team:Cornell/bootstrapCSS?action=raw&ctype=text/css">
 +
    <link rel="stylesheet" href="https://2017.igem.org/Team:Cornell/styles?action=raw&ctype=text/css"> <!--For nav bar text-->
 +
    <link rel="stylesheet" href="https://2017.igem.org/Team:Cornell/animateCSS?action=raw&ctype=text/css"> <!--For slide show text animation-->
 +
    <link rel="stylesheet" type="text/css" href="https://2017.igem.org/Team:Cornell/slickCSS?action=raw&ctype=text/css">
 +
    <link rel="stylesheet" href="https://2017.igem.org/Team:Cornell/mainCSS?action=raw&ctype=text/css">
 +
    <!-- JavaScript Files-->
 +
    <script src="https://2017.igem.org/Team:Cornell/jquerymin?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
    <script src="https://2017.igem.org/Team:Cornell/modernizrJS?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
    <script src="https://2017.igem.org/Team:Cornell/slickJS?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
     <script src="https://2017.igem.org/Team:Cornell/stellar?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
    <script src="https://2017.igem.org/Team:Cornell/mainJS?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
</head>
  
 
     <!------------------------NAV BAR------------------------>
 
     <!------------------------NAV BAR------------------------>

Revision as of 16:07, 30 October 2017

<!DOCTYPE html> Demonstrate

Demonstrate

The strength of OxyPonics lies in the integration of genetic engineering with optical engineering. A redox-sensitive fluorescent protein signals an external LED device, which can regulate the expression of an optogenetic cassette. We demonstrate the efficacy of this novel feedback system:

pDawnIntegratedTesting

We provide evidence that the camera from our external LED device can interpret the ratiometric fluorescence changes in response to different levels of oxidative stress.

While we were not able to perform tests on rxRFP, we were able to conduct feasibility tests using mRFP.

First, we confirm that our setup is capable of detecting and quantifying the fluorescence produced. We use an LED with a 572 nm peak emission wavelength for excitation,and we used a 600 nm long-pass filter on our camera to preclude excess undesirable emission. For details on the setup, see Applied Design. Due to the broad emission of our LEDs, however, some of the excitation light is also detected. This effect was assumed to be linear. Next, we confirmed a linear relationship between excitation intensity and observed average emission intensity. This means there will be a constant scaling factor between our ratios for rxRFP and the documented absorption ratios, but our measurements will be internally consistent. In addition, the contribution of the excitation light is incorporated into our model.

After confirming that we can collect data, we sought to determine data quality. There is inherent noise associated with the camera, which compounds with the natural noise present in biological fluorescence [13]. To isolate in the camera, we took a generic red LED and recorded the average intensity across all of those samples. The resulting distribution reveals significant variation, with a smaller spread than a Gaussian of the same mean and standard deviation. This is shown in the following figure.

Figure 1

Figure 1: Distribution of observed emission levels for assessment of camera noise in well lit environment

Figure 2

Figure 2: Distribution of observed emission levels for assessment of camera noise in dark

To obtain information on the biological noise, we also recorded the average fluorescence intensity at 42% of maximum excitation intensity (a duty cycle of 42%).

We noticed another peculiarity in our data; over a 1 hour time period with the same ambient light conditions, there was a clear upwards trend in the average intensity recorded. While we were unable to determine the cause, we hypothesize this may be due to bacterial sedimentation within the test tube. Since we illuminate and image from the bottom, this would increase the fluorescence we measured. For ratiometric readings, this will not be a problem, as this gradual increase will cancel out when we take a ratio. However, it is something to consider during practical application of our bacteria, and we envision a system that applies mechanical agitation to homogenize the culture.

We are ultimately interested in determining the oxidative stress of the environment by measuring fluorescence. The first step in doing this is determining the “true” fluorescence of our system based on our noisy values by using a Kalman filter. A Kalman filter is an estimator that combines predictions from a known model (in our case, the linear regression we obtained) with observed measurements in order to determine the true state of the measured system. The prediction provided by the Kalman filter is also the theoretical optimal prediction if the underlying process is linear [14,15]. A further advantage is that the Kalman filter can also predict its internal model parameters, allowing for greater flexibility if baselines cannot be obtained.

We compared the Kalman filter to a simple running average for our data at a 42% duty cycle. The predictions are very similar, varying slightly based on choice of parameters of the Kalman filter. Why is this the case?

It turns out that the expression for a running average is also a special case of a Kalman filter. For the case of estimating a constant, the running average is in fact the optimal configuration of the Kalman filter. However, in a real-world environment, our state is constantly changing, such as when we excite pDawn in order to alter the ROS level, or due to diffusion of ROS throughout the system. This can all be modeled theoretically and used as the model for a higher-order, more generalized Kalman filter, which would allow us to more accurately estimate the true ROS level in our system.

Kalman-Results