iGEM 2018 — Team BostonU

[![](https://static.igem.org/mediawiki/2018/8/8b/HQ_page_logo.jpg)](https://2018.igem.org)

# Team:BostonU/Notebook

# Project LEO

![An image of a male lion, with a red/blue split down the middle. Our team logo for Project Leo.](https://static.igem.org/mediawiki/2018/2/2c/T--BostonU--LOGO.png)

[JUDGING](https://igem.org/2018_Judging_Form?team=BostonU)

[Medals](https://2018.igem.org/Team%3ABostonU/Medals)
[Judging Form](https://igem.org/2018_Judging_Form?team=BostonU)

[HUMAN PRACTICES](https://2018.igem.org/Team%3ABostonU/Human_Practices)

[Integrated Human Practices](https://2018.igem.org/Team%3ABostonU/Human_Practices)
[Public Engagement](https://2018.igem.org/Team%3ABostonU/Public_Engagement)
[GreenGEM](https://2018.igem.org/Team%3ABostonU/GreenGEM)
[2018 Sustainable Labs Challenge](https://2018.igem.org/Team%3ABostonU/Challenge)
[Safety](https://2018.igem.org/Team%3ABostonU/Safety)

[PROJECT](https://2018.igem.org/Team%3ABostonU/Description)

[Motivation](https://2018.igem.org/Team%3ABostonU/Description)
[Design](https://2018.igem.org/Team%3ABostonU/Design)
[Measurement](https://2018.igem.org/Team%3ABostonU/Measurement)
[Characterization](https://2018.igem.org/Team%3ABostonU/Experiments)
[Modeling](https://2018.igem.org/Team%3ABostonU/Model)
[Submitted Parts](https://2018.igem.org/Team%3ABostonU/Parts)
[Notebook](https://benchling.com/s/etr-tAKlAtAknVaj3nnihozY)
[InterLab](https://2018.igem.org/Team%3ABostonU/InterLab)

[PEOPLE](https://2018.igem.org/Team%3ABostonU/Team)

[Team](https://2018.igem.org/Team%3ABostonU/Team)
[Attributions](https://2018.igem.org/Team%3ABostonU/Attributions)
[Collaborations](https://2018.igem.org/Team%3ABostonU/Collaborations)

[HOME](https://2018.igem.org/Team%3ABostonU)

# Notebook

Document the dates you worked on your project. This should be a detailed account of the work done each day for your project.

### What should this page have?

* Chronological notes of what your team is doing.
* Brief descriptions of daily important events.
* Pictures of your progress.
* Mention who participated in what task.

### Inspiration

You can see what others teams have done to organize their notes:

* [2014 ATOMS-Turkiye](https://2014.igem.org/Team%3AATOMS-Turkiye/Notebook)
* [2014 Tec Monterrey](https://2014.igem.org/Team%3ATec-Monterrey/ITESM14_project.html#tab_notebook)
* [2014 Kyoto](https://2014.igem.org/Team%3AKyoto/Notebook/Magnetosome_Formation#title)
* [2014 Cornell](https://2014.igem.org/Team%3ACornell/notebook)


[![](https://static.igem.org/mediawiki/2018/8/8b/HQ_page_logo.jpg)](https://2018.igem.org)

# Team:BostonU/Experiments

# Project LEO

![An image of a male lion, with a red/blue split down the middle. Our team logo for Project Leo.](https://static.igem.org/mediawiki/2018/2/2c/T--BostonU--LOGO.png)

[JUDGING](https://igem.org/2018_Judging_Form?team=BostonU)

[Medals](https://2018.igem.org/Team%3ABostonU/Medals)
[Judging Form](https://igem.org/2018_Judging_Form?team=BostonU)

[HUMAN PRACTICES](https://2018.igem.org/Team%3ABostonU/Human_Practices)

[Integrated Human Practices](https://2018.igem.org/Team%3ABostonU/Human_Practices)
[Public Engagement](https://2018.igem.org/Team%3ABostonU/Public_Engagement)
[GreenGEM](https://2018.igem.org/Team%3ABostonU/GreenGEM)
[2018 Sustainable Labs Challenge](https://2018.igem.org/Team%3ABostonU/Challenge)
[Safety](https://2018.igem.org/Team%3ABostonU/Safety)

[PROJECT](https://2018.igem.org/Team%3ABostonU/Description)

[Motivation](https://2018.igem.org/Team%3ABostonU/Description)
[Design](https://2018.igem.org/Team%3ABostonU/Design)
[Measurement](https://2018.igem.org/Team%3ABostonU/Measurement)
[Characterization](https://2018.igem.org/Team%3ABostonU/Experiments)
[Modeling](https://2018.igem.org/Team%3ABostonU/Model)
[Submitted Parts](https://2018.igem.org/Team%3ABostonU/Parts)
[Notebook](https://benchling.com/s/etr-tAKlAtAknVaj3nnihozY)
[InterLab](https://2018.igem.org/Team%3ABostonU/InterLab)

[PEOPLE](https://2018.igem.org/Team%3ABostonU/Team)

[Team](https://2018.igem.org/Team%3ABostonU/Team)
[Attributions](https://2018.igem.org/Team%3ABostonU/Attributions)
[Collaborations](https://2018.igem.org/Team%3ABostonU/Collaborations)

[HOME](https://2018.igem.org/Team%3ABostonU)

![lions cubs being cute af](https://static.igem.org/mediawiki/2018/7/74/T--BostonU--charban.jpg)

Characterization

Strain Screening

The first step in characterizing LOV2 and PhiReX was validating that our yeast strains had functionally integrated. In order to minimize resource consumption, we screened our strains using a reusable culture block and a red or blue photography lamp in our shaking incubator.

![white light shaker expt](https://static.igem.org/mediawiki/2018/5/56/T--BostonU--WhiteLight.png)
Figure 1:
mRuby expression driven by LOV2 exposed to white light in the shaking incubator.

Figure 1 is from a LOV2 induction experiment using white light instead of blue (the preferred induction spectrum). It was necessary to efficiently validate our transformed strains before running long-term eVOLVER experiments. Reviewing relevant literature indicated that white light activates LOV2, albeit to lower levels than blue. . We determined that lower activation levels were sufficient for screening colonies and confirmed white light activation of LOV2 in the shaker experiment in Figure 1.
We later ordered a red light bulb for use in testing our PhiReX strains and blue to further test LOV2.

![white light shaker expt](https://static.igem.org/mediawiki/2018/b/b0/T--BostonU--PhiReXRLSHK.png)
Figure 2:
mRuby expression driven by PhiReX under red light in the shaking incubator.

Our red light shaker experiment revealed unexpected fluorescence from several negative controls. We determined that the measured fluorescence in negative control strains was due to a mutation in our strains which forms a pink pigment in the presence of adenine in media. This pink color was interpreted as fluorescence during flow cytometry measurements, leading us to refine our experimental protocol to dilute cells every hour, halting the accumulation of pink color. Nonetheless, we observed an increase in mRuby expression in the PhiReX strain that indicated successful induction.

eVOLVER Experiments

Using the eVOLVER, we were able to rapidly obtain data on induction of our two systems. By characterizing the induction capabilities of our systems across integration into different yeast loci, we found that the most reliable and active configurations were LOV2 integrated in the HO locus, and a PhiReX design with chromophores in the HO locus and PhyBNT and PIF3 in the URA3 locus.

![white light shaker expt](https://static.igem.org/mediawiki/2018/c/cf/T--BostonU--LOV2_first_order_step.png)
Figure 3:
mRuby expression driven by LOV2 in response to a unit step blue light input in eVOLVER, plotted with a first order model for the step response of LOV2.

The above graph shows the response of LOV2 to a unit step input of blue light in the eVOLVER. Using control theory, we were able to fit a first order control system model to this dataThe first order model is overlaid on top of the step data in Figure 3. This first order model allowed us to predict how LOV2 would react under different light inputs Experimental analysis of OD and temperature of vials during our initial LOV2 eVOLVER experiments indicated these were not parameters that heavily influenced the functionality of the promoters. Further, light programs are easier to manipulate on the eVOLVER; thus we decided to focus our characterization of LOV2 and PhiRex over different pulsatile light inputs.We used our model to predict the response of LOV2 to different blue light pulsing programs, and then performed an eVOLVER experiment to test our model. The results are shown below.

![white light shaker expt](https://static.igem.org/mediawiki/2018/5/56/T--BostonU--LOV2_PWM_1st_ord.png)
Figure 4:
mRuby expression vs. time under varying pulsatile blue light inputs, with the first order model overlaid on top.

The first order model was not within one standard deviation of the data; we revisited our step data and changed our assumption that the system could be represented by a first order model to a second order model.
The model is fitted to the step data as seen below (see <Model> for more details):

![white light shaker expt](https://static.igem.org/mediawiki/2018/a/a2/T--BostonU--LOV2_second_order_step.png)
Figure 5:
mRuby expression vs. time under varying pulsatile blue light inputs, with the second order model overlaid on top.

We reapplied the second order model onto data from our pulsatile input experiment. While it does not track the data perfectly, the second order model estimates the data better than the first order model, particularly as the duty cycle approaches 100%. The
results of this second order model overlay are displayed below:

![white light shaker expt](https://static.igem.org/mediawiki/2018/4/47/T--BostonU--LOV2_PWM_2nd_ord.png)
Figure 6:
LOV2 blue light pulse data with second order model overlaid.

Concurrently with our experiments with LOV2, we applied pulsatile inputs to PhiReX to see if it behaved similarly to LOV2.

![white light shaker expt](https://static.igem.org/mediawiki/parts/8/86/T--BostonU--PhiReX_PWM.png)
Figure 7:
mRuby expression driven by PhiReX under several different pulsatile red light inputs.

Figure 7 outlines the output of PhiReX in response to pulsatile red light inputs of different duty cycles. Light pulse programs can be tuned and adjusted to achieve a desired expression level output.
The second order model does not fit PhiReX as well as LOV2 because the model was trained on PhiReX step input data; in our pulsatile experiment, PhiReX did not induce as highly as we anticipated, and therefore did not fit the model well.
In the future, we plan to run this experiment again, and either alter the model to fit the data or determine that this data is anomalous. Further, we found LOV2 is induced more reliably and generated data that was better suited to our modeling.

![white light shaker expt](https://static.igem.org/mediawiki/2018/d/d4/T--BostonU--PhiReX_PWM_linear_expression.png)
![white light shaker expt](https://static.igem.org/mediawiki/2018/c/ce/T--BostonU--LOV2_PWM_linear_expression.png)
Figure 8:
Steady State mRuby expression vs. Pulse duty cycle is plotted, showing a linear relationship in which longer duty cycles increase reporter expression.

Light pulse duty cycle is a readily tunable parameter, so we sampled a range of inputs for optimal activation levels with PhiReX and LOV2.
Thus, modulation of light pulse dynamics as inputs to LOV2 and PhiReX allows precise control of transcription without having to test inducer dose responses as small molecule inducers require.
Further, modeling of light inducible system responses provides an opportunity to predict outputs generated in response to tunable pulsatile inputs.
We have demonstrated that steady-state gene expression increases linearly as duty cycle approaches a step function. Our results indicate that steady-state gene expression under the control of LOV2 and PhiReX in a bioreactor can be controlled using tunble light programs.

Orthogonality of LOV2 & PhiReX

In order to exact layered transcriptional control, we aimed to demonstrate that our blue- and red-light inducible systems could be used simultaneously in the same cells to multiplex control. We therefore needed to demonstrate that their activation spectra were functionally orthogonal when co-expressed *in vivo*.

![Absorbance spectra for LOV2 and PhiReX](https://static.igem.org/mediawiki/2018/8/80/T--BostonU--spectra.png)

Figure 9: Absorbance spectra of LOV2 and PhiReX. LOV2 peaks at 450-490 nm and PhiReX peaks at 640-670 nm.

As the peak absorbance wavelengths of PhiReX and LOV2 lie on opposite ends of the visible spectrum, the systems are theoretically orthogonal. To confirm this hypothesis, we tested PhiReX and LOV2 orthogonality with both batch culture shaking incubator experiments and eVOLVER experiments.

![orthogonality data](https://static.igem.org/mediawiki/parts/7/77/T--BostonU--ortho.png)
Figure 10: Average mRuby expression in a.u. of PhiReX and LOV2 under different experimental conditions.

The data in Figure 10 confirms that LOV2 is not activated by red light, and PhiReX is not activated by blue light. Thus, the systems are indeed orthogonal and could be used to implement layered control over gene expression.

![blue orthogonality data](https://static.igem.org/mediawiki/parts/8/8c/T--BostonU--blue_ortho_bar.png)
Figure 11: mRuby expression under PhiReX and LOV2 in a blue light eVOLVER experiment for orthogonality, as well as fold change from negative control strain.

Examining the fold change from negative control for each system in orthogonality experiments, we found that LOV2-driven mRuby expression is significantly activated under blue light while PhiReX-driven expression mirrors control expression values. Conversely, PhiReX-driven mRuby expression is responsive to red light while LOV2-driven expression remains at baseline levels. Although PhiReX expression is slightly elevated over the negative control in the above figure 11, this less than 2-fold activation can be reconciled as likely due to either transient activation of PhiReX by ambient white light in the lab, or due to a low-level basal "leakiness" in the promoter system.

[![](https://static.igem.org/mediawiki/2018/8/8b/HQ_page_logo.jpg)](https://2018.igem.org)

# Team:BostonU/Results

# Project LEO

![An image of a male lion, with a red/blue split down the middle. Our team logo for Project Leo.](https://static.igem.org/mediawiki/2018/2/2c/T--BostonU--LOGO.png)

[JUDGING](https://igem.org/2018_Judging_Form?team=BostonU)

[Medals](https://2018.igem.org/Team%3ABostonU/Medals)
[Judging Form](https://igem.org/2018_Judging_Form?team=BostonU)

[HUMAN PRACTICES](https://2018.igem.org/Team%3ABostonU/Human_Practices)

[Integrated Human Practices](https://2018.igem.org/Team%3ABostonU/Human_Practices)
[Public Engagement](https://2018.igem.org/Team%3ABostonU/Public_Engagement)
[GreenGEM](https://2018.igem.org/Team%3ABostonU/GreenGEM)
[2018 Sustainable Labs Challenge](https://2018.igem.org/Team%3ABostonU/Challenge)
[Safety](https://2018.igem.org/Team%3ABostonU/Safety)

[PROJECT](https://2018.igem.org/Team%3ABostonU/Description)

[Motivation](https://2018.igem.org/Team%3ABostonU/Description)
[Design](https://2018.igem.org/Team%3ABostonU/Design)
[Measurement](https://2018.igem.org/Team%3ABostonU/Measurement)
[Characterization](https://2018.igem.org/Team%3ABostonU/Experiments)
[Modeling](https://2018.igem.org/Team%3ABostonU/Model)
[Submitted Parts](https://2018.igem.org/Team%3ABostonU/Parts)
[Notebook](https://benchling.com/s/etr-tAKlAtAknVaj3nnihozY)
[InterLab](https://2018.igem.org/Team%3ABostonU/InterLab)

[PEOPLE](https://2018.igem.org/Team%3ABostonU/Team)

[Team](https://2018.igem.org/Team%3ABostonU/Team)
[Attributions](https://2018.igem.org/Team%3ABostonU/Attributions)
[Collaborations](https://2018.igem.org/Team%3ABostonU/Collaborations)

[HOME](https://2018.igem.org/Team%3ABostonU)

# Results

Here you can describe the results of your project and your future plans.

### What should this page contain?

* Clearly and objectively describe the results of your work.
* Future plans for the project.
* Considerations for replicating the experiments.

### Describe what your results mean

* Interpretation of the results obtained during your project. Don't just show a plot/figure/graph/other, tell us what you think the data means. This is an important part of your project that the judges will look for.
* Show data, but remember all measurement and characterization data must be on part pages in the Registry.
* Consider including an analysis summary section to discuss what your results mean. Judges like to read what you think your data means, beyond all the data you have acquired during your project.

### Project Achievements

You can also include a list of bullet points (and links) of the successes and failures you have had over your summer. It is a quick reference page for the judges to see what you achieved during your summer.

* A list of linked bullet points of the successful results during your project
* A list of linked bullet points of the unsuccessful results during your project. This is about being scientifically honest. If you worked on an area for a long time with no success, tell us so we know where you put your effort.

### Inspiration

See how other teams presented their results.

* [2014 TU Darmstadt](https://2014.igem.org/Team%3ATU_Darmstadt/Results/Pathway)
* [2014 Imperial](https://2014.igem.org/Team%3AImperial/Results)
* [2014 Paris Bettencourt](https://2014.igem.org/Team%3AParis_Bettencourt/Results)