"
Team:Newcastle University/Software
From 2008.igem.org
| Line 1: | Line 1: | ||
{{:Team:Newcastle University/Header}} | {{:Team:Newcastle University/Header}} | ||
{{:Team:Newcastle University/Template:UnderTheHome|page-title=[[Team:Newcastle University/Dry Lab|Dry Lab]]}} | {{:Team:Newcastle University/Template:UnderTheHome|page-title=[[Team:Newcastle University/Dry Lab|Dry Lab]]}} | ||
| + | |||
| + | Our software consists of four main modules which communicate via Web services. One person was Lead Developer for each module, but the developers worked in the same lab, and had frequent formal and informal discussions in order to develop software which works together and provides the necessary functionality. | ||
==Components== | ==Components== | ||
| + | |||
| + | ===Parts Repository (Megan)=== | ||
| + | The Parts Repository stores information from the literature and various databases about biological parts such as promoters, ribosomal binding sites and protein coding regions. | ||
'''[[Team:Newcastle University/Parts Repository|Parts Repository]]''' | '''[[Team:Newcastle University/Parts Repository|Parts Repository]]''' | ||
| + | |||
| + | ===Constraints Repository (Nina)=== | ||
| + | The Constraints Repository stores information about how parts work together, and associated parameters such as binding affinities, POPS, etc., where these are known. Populated from the literature and hard-won knowledge from advisors. | ||
'''[[Team:Newcastle University/Constraints Repository|Constraints Repository]]''' | '''[[Team:Newcastle University/Constraints Repository|Constraints Repository]]''' | ||
| + | |||
| + | ===Evolutionary Algorithm (Mark)=== | ||
| + | The EA takes parts from the Parts Repository, assembles them randomly, but using constraints from the Constraints Repository, and evaluates the "fitness" of the resulting circuit depending on a desired input:output mapping. Equivalent parts with different parameters are swapped in and out at random, and fitter circuits selected in an iterative manner. | ||
'''[[Team:Newcastle University/Evolutionary Algorithm|Evolutionary Algorithm]]''' | '''[[Team:Newcastle University/Evolutionary Algorithm|Evolutionary Algorithm]]''' | ||
| + | |||
| + | ===Workbench (Morgan)=== | ||
| + | The Workbench is a graphical front end that allows circuits to be designed by hand, using drag-and-drop of icons, and drawing upon the Parts Repository and the Constraints Repository. The designed circuits can then be sent to the EA to be further refined. | ||
| + | |||
'''[[Team:Newcastle University/Workbench|Workbench]]''' | '''[[Team:Newcastle University/Workbench|Workbench]]''' | ||
Revision as of 12:45, 25 October 2008
Newcastle University
GOLD MEDAL WINNER 2008
| Home | Team | Original Aims | Software | Modelling | Proof of Concept Brick | Wet Lab | Conclusions |
|---|
Our software consists of four main modules which communicate via Web services. One person was Lead Developer for each module, but the developers worked in the same lab, and had frequent formal and informal discussions in order to develop software which works together and provides the necessary functionality.
Components
Parts Repository (Megan)
The Parts Repository stores information from the literature and various databases about biological parts such as promoters, ribosomal binding sites and protein coding regions.
Constraints Repository (Nina)
The Constraints Repository stores information about how parts work together, and associated parameters such as binding affinities, POPS, etc., where these are known. Populated from the literature and hard-won knowledge from advisors.
Evolutionary Algorithm (Mark)
The EA takes parts from the Parts Repository, assembles them randomly, but using constraints from the Constraints Repository, and evaluates the "fitness" of the resulting circuit depending on a desired input:output mapping. Equivalent parts with different parameters are swapped in and out at random, and fitter circuits selected in an iterative manner.
Workbench (Morgan)
The Workbench is a graphical front end that allows circuits to be designed by hand, using drag-and-drop of icons, and drawing upon the Parts Repository and the Constraints Repository. The designed circuits can then be sent to the EA to be further refined.
