Team:Berkeley Software/Eugene Implementation

From 2009.igem.org

Revision as of 21:14, 19 October 2009 by Adam z liu (Talk | contribs)



Contents:
  • Introduction
  • Language Definition
  • Examples
  • Implementation
  • Results
  • Conclusions
    		•            
    Eugene.png

    Implementation

    Figure 1: Eugene Flow Diagram


    Header File Creation
    Header files give the language the functionality to access many already predefined Parts in the databases. For the purpose of convenient data exchange over the Internet, XML could be used to read information from a database. Then the data is converted into Eugene syntax to represent the header files. As a result the language definitions are not just abstract statements but are tied to existing designs. There are three main header files: PropertyDefintion.h, PartDefiniton.h and PartDeclaration.h shown in Figure 1.

    back to Contents

    Eugene Main File

    The main .eug file can include the header files, which need to be specified at the top: 

    include PropertyDefintion.h, PartDefinition.h, PartDeclaration.h;

    The main file will generally consist of custom Part definitions/declarations, device constructs, rule implementations and control statements.

    back to Contents

    Retrieved from "http://2009.igem.org/Team:Berkeley_Software/Eugene_Implementation"