Team:Imperial College London/Modelling/Experiments
From 2010.igem.org
(Difference between revisions)
m |
(spelling mistakes fixed) |
||
Line 21: | Line 21: | ||
2. Influence of design on modelling and vice versa: | 2. Influence of design on modelling and vice versa: | ||
*All modelling was meant to give answers to questions that arose during the design phase. | *All modelling was meant to give answers to questions that arose during the design phase. | ||
- | *Once the designs were chosen, they were modelled. It was found that | + | *Once the designs were chosen, they were modelled. It was found that 3-step amplification is not likely to be efficient, so it was decided that only 2-step amplification will be taken forward to assembly. This was a significant conclusion as it would take weeks in the laboratory to reach this conclusion. |
*The question whether a sufficient AIP gradient could be established in the extracellular space to set off receptor was answered by modelling. The model allowed to determine under which conditions the system would work. | *The question whether a sufficient AIP gradient could be established in the extracellular space to set off receptor was answered by modelling. The model allowed to determine under which conditions the system would work. | ||
3. Influence of modelling on assembly and vice versa: | 3. Influence of modelling on assembly and vice versa: | ||
*The results from modelling allowed to progress with the assembly. | *The results from modelling allowed to progress with the assembly. | ||
4. Influence of assembly on testing and vice versa: | 4. Influence of assembly on testing and vice versa: | ||
- | *Testing has been planned ahead, so assembly | + | *Testing has been planned ahead, so assembly constructs have been modified to allow some testing methods, e.g. purification or negative control. |
5. Influence of testing on specifications and vice versa: | 5. Influence of testing on specifications and vice versa: | ||
*This step has not been implemented yet. However, if the specifications were not met by the results, we would need to try to redesign the system or change the specifications (in case there was no other alternatives). | *This step has not been implemented yet. However, if the specifications were not met by the results, we would need to try to redesign the system or change the specifications (in case there was no other alternatives). | ||
6. Influence of components which are not adjacent to each other in the cycle: | 6. Influence of components which are not adjacent to each other in the cycle: | ||
- | * | + | *Visibility threshold concentration of muconic acid was determined in the labs and fed back to modellers. |
- | *Many experiments were designed specifically on the request of the modelling team in order to find the necessary parameters for the models. Obtaining these | + | *Many experiments were designed specifically on the request of the modelling team in order to find the necessary parameters for the models. Obtaining these parameters would increase the reliability of the models. |
|} | |} | ||
Revision as of 10:46, 25 October 2010
Modelling | Overview | Detection Model | Signaling Model | Fast Response Model | Interactions |
A major part of the project consisted of modelling each module. This enabled us to decide which ideas we should implement. Look at the Fast Response page for a great example of how modelling has made a major impact on our design! |
Interaction between Dry-Lab and Wet-Lab | ||
Engineering approach to the project 1. Influence of specification on the design and vice versa:
2. Influence of design on modelling and vice versa:
3. Influence of modelling on assembly and vice versa:
4. Influence of assembly on testing and vice versa:
5. Influence of testing on specifications and vice versa:
6. Influence of components which are not adjacent to each other in the cycle:
|
Wet-Lab Experiments for Dry-Lab |
Output Amplification Model
Protein Display Model
|