IGEM:IMPERIAL/2006/project/popsblocker: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
 
(11 intermediate revisions by one other user not shown)
Line 10: Line 10:
<br style="clear:both">
<br style="clear:both">


'''[[IGEM:IMPERIAL/Methodology/Part_documentation_template | Use this template]]'''
===Cre-LoxP System===


==Cre-LoxP System==
==Motivations==
==Motivations==


The use of Cre recombinase to excise regions of DNA between two loxP sites could be incorporated into part [http://parts.mit.edu/registry/index.php?title=Part:BBa_J37015 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.  
*We wanted a way of controlling the activation of the positive-feedback loop in our predator-prey based oscillator. The idea was to use some kind of switch, and seeing as the available switches in the registry all had certain drawbacks, we went about designing our own and what we came up with was the Cre-LoxP system
*The use of Cre recombinase to excise regions of DNA between two loxP sites could be incorporated into part [http://parts.mit.edu/registry/index.php?title=Part:BBa_J37015 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/Pops blocker controlled by the activity of the promoter in front of the Cre enzyme.
 
*In theory, using Cre recombinase as a switch/Pops blocker appears to be a very efficient and solid method.


*Using Cre recombinase as a switch appears to be, in theory, a very efficient and solid method.
==Part interface==


==Part interface==


(describe your black-box approach, define properties of inputs/outputs)
{| border="0" width="100% align="center"
{| border="0" width="100% align="center"
|-
|-
Line 29: Line 29:
! style="background:#66CC99"| INPUTS !!style="background:#FF3333"| OUTPUTS  
! style="background:#66CC99"| INPUTS !!style="background:#FF3333"| OUTPUTS  
|-
|-
| input 1 || output 1
| Cre ||rowspan = "2"| Reporter
|-
| input 2 ||rowspan = "2" | output 2
|-
|-
| input 3
| Pops
|}
|}
||
||
[[Image:iGEM_IMPERIAL_Methodology_Specifications.png|right|350px]]
[[Image:IGEM_IMPERIAL_Methodology_Specifications_Cre.PNG|right|350px]]
|}
|}
(don't forget to insert a relevant image of your black box.)
==Expected behavior and performances==


(try to write your specifications in tables. Here are just 2 examples)
<html>
{| border="1" width="100%"
<!-- Start of StatCounter Code -->
Interface specifiactions
<script type="text/javascript" language="javascript">
|-
var sc_project=1999441;
! style="background:lightgrey"|Characteristics !! Input 1 !! Input 2 !! Input 3 !! Output 1 !! Output 2
var sc_invisible=1;
|-
var sc_partition=18;
| Range || [X1,Y1] || [X2,Y2] || [X3,Y3] || [X4,Y4] || [X5,Y5]
var sc_security="18996820";
|-
</script>
| Tolerance || T1 ||T2 || T3 || T4|| T5
|-
| Transfer function ||  n/a  ||  n/a    ||  n/a  ||  insert image    || insert image
|-
| Latency||      ||      ||      ||        ||
|}
 
 
{| border="1" width="100%"
System level specifications
|-
! style="background:lightgrey" width="100pt" |Properties !! Comments
|-
| Range||
|-
| Transfer function ||
|-
| Latency ||
|-
| Robustness || 
|-
| Variability  || 
|-
| properties 3 || 
|-
| properties 4 || 
 
|}


==Open issues==
<script type="text/javascript" language="javascript" src="http://www.statcounter.com/counter/frames.js"></script><noscript><a href="http://www.statcounter.com/" target="_blank"><img  src="http://c19.statcounter.com/counter.php?sc_project=1999441&amp;java=0&amp;security=18996820&amp;invisible=1" alt="website statistics" border="0"></a> </noscript>
<!-- End of StatCounter Code -->
</html>

Latest revision as of 09:47, 30 October 2006


Cre-LoxP System

Motivations

  • We wanted a way of controlling the activation of the positive-feedback loop in our predator-prey based oscillator. The idea was to use some kind of switch, and seeing as the available switches in the registry all had certain drawbacks, we went about designing our own and what we came up with was the Cre-LoxP system
  • 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/Pops blocker controlled by the activity of the promoter in front of the Cre enzyme.
  • In theory, using Cre recombinase as a switch/Pops blocker appears to be a very efficient and solid method.

Part interface

INPUTS OUTPUTS
Cre Reporter
Pops

<html> <!-- Start of StatCounter Code --> <script type="text/javascript" language="javascript"> var sc_project=1999441; var sc_invisible=1; var sc_partition=18; var sc_security="18996820"; </script>

<script type="text/javascript" language="javascript" src="http://www.statcounter.com/counter/frames.js"></script><noscript><a href="http://www.statcounter.com/" target="_blank"><img src="http://c19.statcounter.com/counter.php?sc_project=1999441&amp;java=0&amp;security=18996820&amp;invisible=1" alt="website statistics" border="0"></a> </noscript> <!-- End of StatCounter Code --> </html>

Retrieved from "https://openwetware.org/mediawiki/index.php?title=IGEM:IMPERIAL/2006/project/popsblocker&oldid=83911"