IGEM:IMPERIAL/2006/project/popsblocker: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 22: | Line 22: | ||
==Part interface== | ==Part interface== | ||
{| border="0" width="100% align="center" | {| border="0" width="100% align="center" | ||
|- | |- | ||
Line 30: | Line 30: | ||
! style="background:#66CC99"| INPUTS !!style="background:#FF3333"| OUTPUTS | ! style="background:#66CC99"| INPUTS !!style="background:#FF3333"| OUTPUTS | ||
|- | |- | ||
| | | Cre ||rowspan = "2"| Reporter | ||
| Pops | |||
| | |||
|} | |} | ||
|| | || | ||
[[Image:IGEM_IMPERIAL_Methodology_Specifications_Cre.PNG|right|350px]] | [[Image:IGEM_IMPERIAL_Methodology_Specifications_Cre.PNG|right|350px]] | ||
|} | |} | ||
==Expected behavior and performances== | ==Expected behavior and performances== | ||
Line 79: | Line 76: | ||
|} | |} | ||
Revision as of 00:20, 23 October 2006
Cre-LoxP System
Motivations
The use of Cre recombinase to excise regions of DNA between two loxP sites could be incorporated into part J37015. Our aim is to insert two loxP sites into this part, which, when in place, would block the synthesis of any genes downstream of it, and when removed would allow their synthesis. Thus the Cre-loxP system would effectively act as a switch controlled by the activity of the promoter in front of the Cre enzyme.
- Using Cre recombinase as a switch appears to be, in theory, a very efficient and solid method.
Part interface
|
Expected behavior and performances
(try to write your specifications in tables. Here are just 2 examples)
Interface specifiactionsCharacteristics | Input 1 | Input 2 | Input 3 | Output 1 | Output 2 |
---|---|---|---|---|---|
Range | [X1,Y1] | [X2,Y2] | [X3,Y3] | [X4,Y4] | [X5,Y5] |
Tolerance | T1 | T2 | T3 | T4 | T5 |
Transfer function | n/a | n/a | n/a | insert image | insert image |
Latency |
Properties | Comments |
---|---|
Range | |
Transfer function | |
Latency | |
Robustness | |
Variability | |
properties 3 | |
properties 4 |