Team:RHIT/Project

From 2012.igem.org

(Difference between revisions)
Line 130: Line 130:
<li>Boost each other up; don't bring anybody down.</li></ol><br />
<li>Boost each other up; don't bring anybody down.</li></ol><br />
<p>Once the group agreed on a common purpose and principles, the team brainstormed ideas for the needs of the project. These ideas were then organized into categories based on similar themes. A few examples of the categories are team practices, mathematical modeling, presentation, laboratory, wiki, and gold criteria. Ideas were then flushed out by a group discussion, resulting in modifications to ideas’ category locations. This part served as the brainstorming and organization of Allen’s method.</p><br />
<p>Once the group agreed on a common purpose and principles, the team brainstormed ideas for the needs of the project. These ideas were then organized into categories based on similar themes. A few examples of the categories are team practices, mathematical modeling, presentation, laboratory, wiki, and gold criteria. Ideas were then flushed out by a group discussion, resulting in modifications to ideas’ category locations. This part served as the brainstorming and organization of Allen’s method.</p><br />
-
<p>Then, the team identified next actions for the project based off of the brainstormed ideas. Next actions are described as steps taken by the team to complete a specific portion of the project, and Allen’s method says that a project is only considered fully developed when all portions of the project have their potential next actions assigned. Once next actions were issued, all members of the team started to research how the task could be completed.</p><br />
+
<p>Then, the team identified next actions for the project based off of the brainstormed ideas. Next actions are described as steps taken by the team to complete a specific portion of the project, and Allen’s method says that a project is only considered fully developed when all portions of the project have their potential next actions assigned. Once next actions were issued, all members of the team started to research how the task could be completed.</p><br /><br />
<p>During the research phase, Devon found out that the team’s idea was previously attempted using a different method by the 2008 Johns Hopkins iGEM team. The team then switched gears into finding out what the Johns Hopkins team accomplished by examining their wiki, presentation, and poster. After learning helpful information about the project, the team decided to stick with their original idea.</p><br />
<p>During the research phase, Devon found out that the team’s idea was previously attempted using a different method by the 2008 Johns Hopkins iGEM team. The team then switched gears into finding out what the Johns Hopkins team accomplished by examining their wiki, presentation, and poster. After learning helpful information about the project, the team decided to stick with their original idea.</p><br />
<p>Around the same time, research on possible pigment pathways, fluorescent colors, and promoters occurred. Robert then found the next big breakthrough on the project when he found a positive feedback loop in yeast cells form the work of Ajo-Franklin, Drubin, Eskin, et al. in their paper titled Rational Design of Memory in Eukaryotic Cells. Further research showed that many teams have used a very similar pathway in previous years of the iGEM competition, solidifying the part as a key component of the project design.</p><br />
<p>Around the same time, research on possible pigment pathways, fluorescent colors, and promoters occurred. Robert then found the next big breakthrough on the project when he found a positive feedback loop in yeast cells form the work of Ajo-Franklin, Drubin, Eskin, et al. in their paper titled Rational Design of Memory in Eukaryotic Cells. Further research showed that many teams have used a very similar pathway in previous years of the iGEM competition, solidifying the part as a key component of the project design.</p><br />

Revision as of 19:15, 29 September 2012

Home
Team
Project
BioBricks
Modeling
Notebook
Outreach
Overview
Planning
In-depth
Simple Science

Basic Description

The Checkmate project was designed to address a current problem in yeast genetics research. Currently, the test to determine mating type of haploid yeast takes two to three days. Our goal was to cut down that time to four hours (roughly an afternoon). This will speed up yeast genetics research by helping researchers get results more quickly.

Background

Yeast can exist stably as both a diploid and a haploid. When it is a haploid, it has one of two mating types, a and alpha. These correspond to male and female in vertebrates. Genetic manipulation in yeast is typically done to haploids. Once the genetic manipulation has been done, it is necessary to identify the mating types of the resulting haploid yeast, so that they can be mated to form a diploid strain.

Current Test

The current test for mating type takes several days. It involves mixing the unknown strain with two known tester strains, each of which have a known auxotrophic deficiency, which is different from the auxotrophic deficiency of the known strain. The mixes are then plated on media that is deficient in both substances that are unable to be produced by the haploid strains, such that neither tester strain nor unknown strain can survive as a haploid. If the cells mate, then they get a working copy of their defective gene, so the diploid can survive. Below is a graphic illustrating the current test process.


Our Test

Our test would involve mixing the unknown strain with each of our tester strains and then plating on YPD media. If mating occurs, the pheromone response pathway will initiate transcription of a fluorescent protein with a DNA-binding domain that binds to its own promoter, effectively forming a positive feedback loop. Our system is also known as a “latch circuit”, one that responds to an initial stimulus and then maintains its response indefinitely. Over several hours, fluorescence will become visible under a fluorescence microscope, thus signaling that mating occurred. Two different fluorescent proteins were used, one for each mating type, so that results would be unambiguous if the plates got mixed up. Below is a graphic illustrating how our test improves upon the current test.


Documentation: Planning Process


Under the leadership of advisor Dr. Yosi Shibberu, Rose-Hulman’s iGEM team started off the year with an iterative process of project planning. The method using the five steps found in chapter three of David Allen’s book, “Getting Things Done”, titled Getting Projects Creatively Under Way: The Five Phases of Project Planning. Allen proposes a five step process to focus all members on the same goal of the project: defining a purpose, visioning, brainstorming, organizing, and identifying next actions. The group went through three iterations of this method, resulting in the purpose and principles that follow.

Purpose


Determine the mating type of yeast, Saccharomyces Cerevisiae, through fluorescence measurements more easily and quickly than the current method, with a goal time of four hours or less. In addition, constitutively label A and a test strains. Go for the Gold!

Principles


  1. Execute work that produces quality long-term information with the goal of being open source.
  2. Learn from past teams' mistakes.
  3. Boost each other up; don't bring anybody down.

Once the group agreed on a common purpose and principles, the team brainstormed ideas for the needs of the project. These ideas were then organized into categories based on similar themes. A few examples of the categories are team practices, mathematical modeling, presentation, laboratory, wiki, and gold criteria. Ideas were then flushed out by a group discussion, resulting in modifications to ideas’ category locations. This part served as the brainstorming and organization of Allen’s method.


Then, the team identified next actions for the project based off of the brainstormed ideas. Next actions are described as steps taken by the team to complete a specific portion of the project, and Allen’s method says that a project is only considered fully developed when all portions of the project have their potential next actions assigned. Once next actions were issued, all members of the team started to research how the task could be completed.



During the research phase, Devon found out that the team’s idea was previously attempted using a different method by the 2008 Johns Hopkins iGEM team. The team then switched gears into finding out what the Johns Hopkins team accomplished by examining their wiki, presentation, and poster. After learning helpful information about the project, the team decided to stick with their original idea.


Around the same time, research on possible pigment pathways, fluorescent colors, and promoters occurred. Robert then found the next big breakthrough on the project when he found a positive feedback loop in yeast cells form the work of Ajo-Franklin, Drubin, Eskin, et al. in their paper titled Rational Design of Memory in Eukaryotic Cells. Further research showed that many teams have used a very similar pathway in previous years of the iGEM competition, solidifying the part as a key component of the project design.


The next step in the process was finding DNA sequences that correlated to each component of the scheme. At this time, a modification from the initial layout occurred. All references and teams previously used a two-tiered system for the positive feedback loop, found in Figure 1. The team proposed to combine the two tiers into one, found in Figure 2.




Figure 1: Example fluorescence pathway based off literature and previous projects.



Figure 2: Proposed fluorescence pathway for RHIT’s iGEM 2012 competition.


The switch was driven by three major factors: cost, ease, and simplification of the pathway. The cost of production decreased proportionally as the size of the sequence was reduced. Also, by having a shorter sequence, less ligations were necessary. Finally, by decreasing the number of components, the sequence was simplified.


During this discussion, some possible problems were brought up. The spacing of the STE 12 binding site compared to the position of LexA-Regulation promoter was called into question as well as the concern of competition between STE12 and LexA once the process was activated. The spatial concerns were addressed when laying out the DNA sequence by modifying the space between the components. The team hypothesized that the inhibition, if it occurs, would not greatly affect the positive feedback loop, resulting in no action taken regarding this concern.


After all portions of the DNA sequences were assembled, Adam created a program in MATLAB that codon optimized the sequences for yeast. The sequences were then manually compared to their reference sources to ensure correct amino acids.


Two nearly identical constructs were planned by the RHIT iGEM team. The differences between them were in the specific fluorescent domain; one coded for a red domain and the other coded for a blue domain. Both constructs were synthesized by GeneArt using sequence information provided by the RHIT iGEM team. Due to some miscommunication, the red construct sequence was optimized for synthesis, during which several additional EcoRI sites were introduced. The team was unaware of this when the construct was received, so numerous attempts at digestion, ligation and transformation were made, all of which were unsuccessful. Due to the added EcoRI sites, the red construct DNA is unusable both as a BioBrick and in the intended system without extensive changes being made, which time and cost prohibit. The blue construct was not similarly changed, however.

Simple science text

Retrieved from "http://2012.igem.org/Team:RHIT/Project"