Software
From ung.igem.org
Contents |
Welcome to iGEM Software Tools Development
iGEM software development is based on an ecosystem of four concepts:
- A repository of open source software tools.
- Community driven data exchange standards.
- Specific software frameworks built explicitly for synthetic biology.
- Part information in the Registry of Standard Biological Parts.
These four concepts find a home in a revamped iGEM competition software track. The software track now complements the other tracks in iGEM with new goals, medal criteria, and awards to reflect the distinct requirements of tools in this domain.
The first concept will be supported by archiving each team's software in a centralized location. This will increase software reuse, interoperability, and collaboration. Ideally software will be reused in much the same way that the BioBrick parts are used by wet labs.
The second concept finds a home in the Synthetic Biology Open Language (SBOL) and the BioBricks Foundation Request for Comments (RFC) infrastructure.
Software frameworks include such efforts as Clotho. These tools aim to create open source, community driven software applications with a rapid development and deployment cycles.
Finally, the foundation of all of these efforts requires a steady stream of biological data and available parts. The Registry of Standard Biological Parts provides this function.
Concepts
The Registry of Software Tools
The Registry of Software Tools is the computational analog to the Registry of Biological Parts. Driven by the large library of software tools generated by iGEM teams annually, the Registry of Software Tools will be a central location to store and access this growing resource.
Synthetic Biology Open Language (SBOL)
Synthetic Biology Open Language (SBOL) is a language for the description and the exchange of synthetic biological components and systems. You can start using SBOL by checking out this tutorial.
The BBF is a public-benefit organization which looks to promote the standardizing of BioBrick parts. One such effort is through the Request for Comments (RFC) mechanism. RFCs are static documents or digital objects like videos intended to get an idea, proposed standard, or method out to the rest of the community for comment. RFCs are numbered, for ease of referencing, and the numbers are assigned by the BBF.
There are a number of software efforts which look to make the specification, design, assembly, simulation, and data management activities in synthetic biology more efficient, automated, predictive, collaborative, and standardized. These efforts will allow us to develop more complex systems and incorporate advanced modeling methodologies. These frameworks are created by small research groups. iGEM provides an opportunity to improve upon these tools.
The Registry of Standard Biological Parts
The Registry is a continuously growing collection of genetic parts that can be mixed and matched to build synthetic biology devices and systems. Founded in 2003 at MIT, the Registry is part of the Synthetic Biology community's efforts to make biology easier to engineer. It provides a resource of available genetic parts to iGEM teams and academic labs.
Starting in 2011 it is our intention to elevate the development of software tools for synthetic biology to the same level of community support and participation currently experienced by the general iGEM competition. To this end, it is our goal to re-energize the software development of iGEM participants by:
- Reducing the amount of redundant code development.
- Increasing the size and scope of software development by leveraging previous projects and experiences.
- More closely couple the development of software with the experimental techniques and requirements of the wetlab.
This page will serve as the starting point for these efforts. So join us and help create the tools, algorithms, and infrastructure to power the next generation of Synthetic Biology. We can't wait to see what you create!!
Douglas Densmore, Boston University
Randy Rettberg, iGEM Central
Software Competition Overview
iGEM traditionally has been a venue for teams to create designs in wetlabs. Starting in 2008, area awards for software tools were introduced. These efforts produced a number of truly unique software projects. However, there were a number of aspects which could be improved. Our goal is to begin the process of making the software aspects of iGEM more fully featured. This will include a centralized repository for the software tools developed. This will help to not only preserve the projects but also allow others to avoid building existing tools as well as extend them. Second, we hope to help create a community of users around specific design frameworks and community standards.
This page is the beginning of this process!
Organizing Committee
The Chairs of the iGEM Software track are: Douglas Densmore and Randy Rettberg. Due to the truely international nature of the 2011 iGEM competition, each region will have a separate, local organizing committee. These members are listed in the table below:
Calendar of Events
Note: Dates in grey have not been finalized yet. Make sure to check the calendar periodically for any changes!
| March | IGEM 2011 registration opens | ||
| March 31 | IGEM 2011 registration closes; Team registration fee due | ||
| May - June | Teachers Workshops | ||
| July 15 | Team project descriptions due | ||
| July 15 | Safety proposal due (if your software team has a wet lab component) | ||
| September 2 | Regional Jamboree attendance fee due at 11:59pm, EDT | ||
| September 2 | Track selection due | ||
| Project abstracts due | |||
| Team rosters due | |||
| Safety questions due (if your software team has a wet lab component) | |||
| Europe | Americas | Asia | |
| Sep 21 | Sep 28 | Oct 5 | Project documentation due, including all medal criteria. Upload software to Registry of Software Tools. |
| Sep 21 | Sep 28 | Oct 5 | BioBrick Part DNA due to the Registry (if you created new BioBricks as part of your software team) |
| Sep 21 | Sep 28 | Oct 5 | Judging form due |
| Sep 21 | Sep 28 | Oct 5 | Wiki FREEZE at 11:59pm, EDT |
| October 1-2 | iGEM 2011 Regional Jamborees: Europe | ||
| October 8-10 | iGEM 2011 Regional Jamborees: Americas | ||
| October 15-16 | iGEM 2011 Regional Jamborees: Asia | ||
| October | World Championship Jamboree attendance fee due | ||
| November 5-7 | iGEM 2011 World Championship Jamboree, MIT |
Software Competition Judging
Judging for the Software Tools track will have area-specific requirements for medals as detailed below. Software Tools teams are also eligible for selection as Finalists, Grand Prizes, and Special Prizes. It is possible that the medals in the software track will be replaced with "Mousepads", which are of equivalent significance. This will depend on available funds and interest.
Bronze Medal
- Register the team, have a great summer, and have fun attending the Jamboree.
- Create and share a description of the team's project via the iGEM wiki.
- Present a Poster and Talk at the iGEM Jamboree.
- Develop and make available via the The Registry of Software Tools an open source software tool that supports synthetic biology based on BioBrick standard biological parts (remember, the iGEM judges will be looking for substantial team-based software projects).
Silver Medal
To earn a Silver Medal, in addition to the Bronze Medal requirements, a team must do ONE of the following:
- Provide a detailed, draft specification for the next version of your software tool
- Provide a second, distinct software tools project.
In addition the team must:
- Provide a demonstration of their software either as a textual or video tutorial made available on their wiki. This tutorial should explain all the features of the tool as well as provide sample input and output as appropriate.
Gold Medal
To earn a Gold Medal, in addition to the Silver Medal requirements, a team must:
1. Have another team utilize the software developed by your team. You must clearly show how your software was used and the results that were obtained.
2. Outline and detail how your software effects Human Practices in Synthetic Biology. Such topics include: safety, security, ethics, or ownership, sharing, and innovation.
PLUS
3a. Develop and document a new technical standard that supports the:
- design of BioBrick Parts or Devices
- construction of BioBrick Parts or Devices
- characterization of BioBrick Parts or Devices
- the analysis, modeling, and simulation of BioBrick Parts or Devices
- the sharing of BioBrick Parts or Devices, either via physical DNA or as information via the internet.
OR
3b. In place of requirement two, a team may instead use SBOL in your software documentation.
Software Competition Special Awards
In addition to the best software tool overall award, three additional awards may be presented provided that enough qualified entries are received.
Best Clotho App
Clotho is for engineering synthetic biological systems and managing the data which is used to create them. It also provides a mechanism to begin the process of creating standardized data, algorithms, and methodologies for synthetic biology. You can find out more about Clotho here.
In order to qualify for this award you must:
- Create a Clotho App which runs in Clotho v2.0 or higher. This will be written in Java and be fully documented both in the source code along with a user manual added to clothohelp.org. For more information on making a Clotho app read this.
- Fully illustrate how that App uses the Clotho data model by retrieving, manipulating, and then storing data back in to a Clotho based database.
- Make the Clotho App available and its source code to the larger Clotho project (details TBA).
If you are interested in creating a Clotho App, please see www.clothohelp.org for more information. In particular check out the pages related to "Developer Information". If you have further questions please contact dougd@bu.edu.
Best SBOL Based Tool
Synthetic Biology Open Language (SBOL) is a language for the description and the exchange of synthetic biological components and systems.
In order to qualify for this award you must:
- Adopt SBOL in your software to enable synthetic biology information sharing. To show that you are using SBOL-semantic you must demonstrate that the data you output conforms to the standard (as appropriate). For example, to demonstrate that it does conform, you could show that another SBOL compliant tool can read it (or vise-versa). If you are using SBOL-visual, your software application should demonstrate its use in synthetic biology practice. For example, that your wet-lab team or another (wet-lab or software)team made use of the output of your SBOL-visual compliant tool in their project.
- Document your use of SBOL by describing how it was used to perform information exchange. Be very clear to describe what was exchanged or communicated so the judges can assess your contribution.
- Describe any challenges you faced in conforming to the SBOL standard. Tell the judges how SBOL should be changed to meet those challenges. SBOL is extensible, community driven, and evolving; consider writing a BBF RFC proposing an extension to overcome the challenges you faced.
Best Interaction with the Parts Registry
The Registry is a continuously growing collection of genetic parts that can be mixed and matched to build synthetic biology devices and systems. Founded in 2003 at MIT, the Registry is part of the Synthetic Biology community's efforts to make biology easier to engineer. It provides a resource of available genetic parts to iGEM teams and academic labs.
In order to qualify for this award you must do one of the following:
- Provide a new software interface to both retrieve information from and store information to the Parts registry. You should clearly demonstrate how this approach is superior to using the Parts web site directly.
- Develop a methodology to quantify BioBrick performance which is supported by a software tool. Characterization, user reviews, and formally tracking parts used successfully in designs are all examples. Users should be able to both query this information as well as add it themselves. This should complement what is in the registry.
- Propose an alternate interaction with the registry. Clearly document this on your wiki in a page explicitly dedicated to this aspect of your tool. You should clearly show how to use this tool in a design flow used by experimental iGEM teams.
Software Resources
- Parts Registry
- Clotho and Clotho Help
- Synthetic Biology Open Language (SBOL)
- The Registry of Software Tools
Industrial Partners
For more information contact: Prof.Douglas Densmore - dougd@bu.edu


