"
Team:UC Davis
From 2011.igem.org
| Line 7: | Line 7: | ||
<div class="floatbox2"> | <div class="floatbox2"> | ||
<h1>Welcome</h1> | <h1>Welcome</h1> | ||
| - | <p>Welcome to our page! Our team is comprised of 6 dedicated individuals: 4 undergraduates and 2 advisors. This will be the third year that iGEM @ UC Davis participates in the competition. We are hard at work and are looking forward towards the completion of our project.<br><br>This year, we're making libraries of mutant promoters and repressors. We would like to contribute well characterized mutants to the registry along with characterization of the wildtype parts that we're mutating. We believe that in order for the parts registry to thrive, characterization must be a top priority when adding new parts. This will ensure that the fundamentals of the registry remain, namely that parts are universal and composable. Along with making mutants, we would like to model their behavior when placed in different simple circuits which could give different behavior (i.e. a switch vs. an oscillator). Once characterized, we will make a predictive algorithm so new mutant interactions can be predicted without the need to physically measure each interaction combination. Read more about it <a href="https://2011.igem.org/Team:UC_Davis/Project | + | <p>Welcome to our page! Our team is comprised of 6 dedicated individuals: 4 undergraduates and 2 advisors. This will be the third year that iGEM @ UC Davis participates in the competition. We are hard at work and are looking forward towards the completion of our project.<br><br>This year, we're making libraries of mutant promoters and repressors. We would like to contribute well characterized mutants to the registry along with characterization of the wildtype parts that we're mutating. We believe that in order for the parts registry to thrive, characterization must be a top priority when adding new parts. This will ensure that the fundamentals of the registry remain, namely that parts are universal and composable. Along with making mutants, we would like to model their behavior when placed in different simple circuits which could give different behavior (i.e. a switch vs. an oscillator). Once characterized, we will make a predictive algorithm so new mutant interactions can be predicted without the need to physically measure each interaction combination. Read more about it <a href="https://2011.igem.org/Team:UC_Davis/Project">here.</a><br><br>Stay tuned for the upcoming results!</p> |
</div> | </div> | ||
Revision as of 23:20, 16 September 2011
Our Sponsors
Start a Family
Got a favorite BioBrick? Check our our process for expanding basic parts into part families.Criteria
View our judging criteria for iGEM 2011 here.
Welcome
Welcome to our page! Our team is comprised of 6 dedicated individuals: 4 undergraduates and 2 advisors. This will be the third year that iGEM @ UC Davis participates in the competition. We are hard at work and are looking forward towards the completion of our project.
This year, we're making libraries of mutant promoters and repressors. We would like to contribute well characterized mutants to the registry along with characterization of the wildtype parts that we're mutating. We believe that in order for the parts registry to thrive, characterization must be a top priority when adding new parts. This will ensure that the fundamentals of the registry remain, namely that parts are universal and composable. Along with making mutants, we would like to model their behavior when placed in different simple circuits which could give different behavior (i.e. a switch vs. an oscillator). Once characterized, we will make a predictive algorithm so new mutant interactions can be predicted without the need to physically measure each interaction combination. Read more about it here.
Stay tuned for the upcoming results!
Notebook
See what we did on a daily basis in lab. In here you'll find a detailed description of each day's work. Read more.
Want to know how we did our wet work? You can see our protocols here.
Safety
Attributions
We've found that there is an inverse relationship between number of team members and amount of work. For a breakdown of what we worked on, check out our Attributions page.
