Team:USTC
Project Description
hasn't been finished yet!
Work in the past
Brainstorming and Brain"mist"
Coming up with a fancy idea is easy, however, coming up with a promising as well as feasible one is hard, harder than we imagined.
Our leader encouraged every member to think about ideas, and we successfully did that. Initially, we acquired about 10 ideas and discussed each one of them. After 2 weeks, three ideas left to be further determined whether they are appropriate or not. They were:
1. Bacteria feeds on plastic
2. EEEEE(Extremely Enhanced Expessing Engineered E.coli )
3. Prion and its aggregating
Our criteria for ideas are as follow:Will our team members have fun? Is our time enough for it? Is our experiment equipment enough? Does it meet iGEM safety requirements? Is it innovative enough?
Final Selection
We finally decided to select "Prion and its aggregating" as our project carrier. Information found is as below:
1. Background
In yeast cell, there is a non-Mendelian inheritance system.
Figure 1: The effect of [PSIC] on Sup35 and translational termination.
(A) A complex of Sup35 (see legend at bottom) and Sup45 binds ribosomes at stop codons and mediates translational termination. Sup35 is composed of two regions, a prion-determining-domain (PrD, rectangle) and a termination domain (Sup35C, sphere). In non-prion [ psi¡] strains, translational termination occurs efficiently at stop codons at the ends of open reading frames, and the completed protein is released from the ribosome.
(B) In [PSIC] cells, most Sup35 proteins adopt the prion conformation and self-assemble into an aggregated, possibly amyloid structure (depicted as large cylinder). This conformational change impairs Sup35’s ability to participate in translational termination and consequently, stop codons are read through occasionally, producing proteins with a C-terminal extension.
Moreover, it shows that the PrD can be modularized, which means we can combine this domain to another protein we want to make them aggregate, and even impair its function.
Here is the most magical part ,not only can we make them aggregate, we can also cure our yeast by a great variety of chemical, environmental, and protein-based agents. Then these proteins will be depolymerized, and spread uniformly in the cell once again.
2. Application
We design three gene lines.
In the first design (figure 2), we just use R9 to depolymerize the SUP35’s aggregation to allow the yeast to produce functional GFP. Then we can calculate the concentration of R9 through the fluorescent brightness.
In the second design (figure 3), we build a double direction switch.
In the third design (figure 4), GFP1 and GFP2 are not able to give out light separately. However, when they touch each other physically, they will reconstruct and give out light.
Goals in the future
We hope to construct a bio-reaction controller, which functions directly on protein level rather than on DNA level in advance. Such strategy is highly possible to reduce the time it takes for the controlling effect to appear, as DNA->Protein process is skipped.
(End of project description)
Welcome to iGEM 2016!
Your team has been approved and you are ready to start the iGEM season!
Before you start:
Please read the following pages:
Styling your wiki
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.
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.
Wiki template information
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 Pages for awards 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!
Editing your wiki
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!
Tips
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:
- State your accomplishments! Tell people what you have achieved from the start.
- Be clear about what you are doing and how you plan to do this.
- You have a global audience! Consider the different backgrounds that your users come from.
- Make sure information is easy to find; nothing should be more than 3 clicks away.
- Avoid using very small fonts and low contrast colors; information should be easy to read.
- 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 iGEM 2016 calendar
- Have lots of fun!
Inspiration
You can also view other team wikis for inspiration! Here are some examples:
Uploading pictures and files
You can upload your pictures and files to the iGEM 2016 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.
When you upload, set the "Destination Filename" to Team:YourOfficialTeamName/NameOfFile.jpg. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)
