Revision as of 22:41, 18 October 2009

Miscellaneous

This page covers a number of different topics which did not fit nicely within any of the other pages in this wiki. Here we provide a draft specification/roadmap for the next version of many of the projects here (who knows these could be a part of iGEM 2010). In addition we discuss our collaborations, efforts in standardization, and how our project relates to human practices.

Draft Specification

This section details a draft specification for the next version of Eugene, Spectacles, and the Clotho environment. These specification descriptions assume the reader is familiar with the current state of the projects (i.e. has read the appropriate pages on this wiki). The specs involve an ordered list of tasks along with approximate dates when these should be completed by.

Eugene

Add a way to express the relationship of parts in a device to resulting transcripts - December 2009
- Currently there is no clean way to say which parts are associated to a particular transcript after transcription. It would be ideal to have a way to do this so that rules can be applied on a transcript based level. Often interactions are on a per transcript basis.
Add support for rules over part definitions (i.e. not just part instances) - December 2009
- Current rules are constructed as such: Rule r1(partInstance1 WITH partInstance2). It would be very powerful if we could state: Rule r1(partDef1 WITH partDef2). This would remove a lot of repetition in rule creation when one wants to state something abstract regarding a whole set of parts.
More completely support [http://openwetware.org/wiki/Endy:Notebook/Synthetic_Biology_Data_Transfer_Process SB/DTP (Synthetic Biology Data Transfer Process)] with XML export and import - Spring 2010
- Current we can produce a limited XML file from Eugene's interpreter. Ideally we can make this fully compliant with the SB/DTP protocol being developed.
Add support for a completely expressive control statement set (e.g. if, while, for) - Spring 2010
- Eugene currently only has if-statements. We will be adding the needed control statements to provide a fully expressive control flow.

Spectacles

More advanced testing which is more integrated with the completion of whole design flows - December 2009
- Spectacles current exports device information to the algorithm manager and the sequence view. It would be nice to more closely couple this with other tools such as the parts manager. This would make complete design flows much more easy to create.
Expansion of visual cues - December 2009
- The current Spectacles tool offers visual cues related to the status of abstract functional parts related to assignment of physical data as well as part adherence to rules. The visual cue system should be expanded and made more user flexible.
More advanced database support of assignment of physical parts - December 2009
- Now the user can specify what criteria they wish to use to search for parts in the database. For example one can search for all parts which say "promoter" as part of the short description or those which contain "bba" in the name. However, this system can be expanded to offer more robust search capabilities as well as more insight into the repository where the parts are located.
Visual rule enforcement - Spring 2010
- Support should be added which visually enforces the rules specified by Eugene in Spectacles. This can restrict the movement of icons, the editing or property information, or the visual cues present.

Clotho

Complete/Test flow for basic part creation - Fall 2009
Complete/Test flow for full device creation - Fall 2009
Integrate Clotho with JBEI's registry - Fall 2009
Complete SPAM tool's oligo coverage designer and golden gate part packager - Fall 2009
Test data model with Davidson University's GCATalog based registry - Spring 2010

Collaboration

Valencia Suvery Participation Gold Medal

For all of our projects, we worked with a number of different groups both to make our tools more visible, as well as get valuable feedback. This section discusses some of these collaborations.

UC Berkeley iGEM team - we worked very closely with our wet team counter parts to tie our Kepler based assembly workflows with the Beckman Coulter BioMek 3000 liquid handling robot that they used. In addition we beta tested our software with them, incorporated their feedback, and ran tutorial sessions on Clotho use and how to write Clotho plug-ins.

Stanford iGEM team - we provided early versions of Spectacles to the Stanford iGEM team so that they could test it out. In addition we worked with them to incorporate new iconography as they added it to the SBOL Visual effort.

University of Minnesota - Emma Weeding worked with us

Joint BioEnergy Institute (JBEI) -

Valencia - In addition to many other iGEM teams, we filled out their survey and received a gold medal (100% team participation).

Support for New Technical Standard

This entire project is very tied to the [http://openwetware.org/wiki/The_BioBricks_Foundation:Standards/Technical/Exchange Synthetic Biology Open Language] (SBOL) effort. This is a set of three activities related to the standardization of a number of required synthetic biology concepts with the goal of facilitating software development. We contributed in the following ways.

SBOL Visual Constitutive Promoter

SBOL Visual Open Reading Frame

SBOL Visual- We worked with Suzie Bartram and Cesar Rodriquez at Stanford to make sure that Spectacles was 100% compliant with the the SBOL Visual standard. This included support to assign functional concepts to the icons as well as providing a very smooth upgrade path in the event the images evolve.

SBOL Semantic Proposal

SBOL Semantic - By revamping the Clotho data model we have enabled the internal structure of Clotho to adapt to new ideas regarding the representation of biological data. Bing Xia and Douglas Densmore participated in the SB Data Exchange working group meeting at Stanford on 26/07/2009. Clotho as a project is committed to the support of this standard.

SBOL Script - SBOL scriupt is an effort to develop a human readable specific. Eugene has been created to be a super-set of the eventual SBOL script. A key piece that we added support for in Eugene is the exporting of Eugene as an XML description. This will lead to the manipulation of Eugene by other tools as well as translating Eugene into a more restricted form which will be SBOL script.

@@ Line 21: / Line 21: @@
 ===Spectacles===
-# Advanced testing more integrated with the completion of whole design flows - Fall 2009
+# More advanced testing which is more integrated with the completion of whole design flows - December 2009
-# More advanced database support of assignment of physical parts - Fall 2009
+#* Spectacles current exports device information to the ''algorithm manager'' and the ''sequence view''. It would be nice to more closely couple this with other tools such as the ''parts manager''. This would make complete design flows much more easy to create.
+# Expansion of visual cues - December 2009
+#* The current Spectacles tool offers visual cues related to the status of abstract functional parts related to assignment of physical data as well as part adherence to rules. The visual cue system should be expanded and made more user flexible.
+# More advanced database support of assignment of physical parts - December 2009
+#* Now the user can specify what criteria they wish to use to search for parts in the database. For example one can search for all parts which say "promoter" as part of the short description or those which contain "bba" in the name. However, this system can be expanded to offer more robust search capabilities as well as more insight into the repository where the parts are located.
 # Visual rule enforcement - Spring 2010
+#*Support should be added which visually enforces the rules specified by Eugene in Spectacles. This can restrict the movement of icons, the editing or property information, or the visual cues present.
 ===Clotho===

Team:Berkeley Software/Misc

From 2009.igem.org