"

From 2011.igem.org

Life = 42

jtferns

--Jtferns 15:47, 7 June 2011 (CDT)

To-Do List

• read through Doug's Algorithm paper [http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2860133/]
• read through AssemblyManager code
• read through ClothoHelp [http://wiki.bu.edu/ece-clotho/index.php/Main_Page]
  • edit main page to allow for click-able images
  • break main page
  • fix link-caption centering issue
• read through kirigami/TB paper
• read through Friedland abstract/paper [6/7/2011]

• PuppetShow Thought Project
  • read through Puppeteer/PuppetShow powerpoint [6/7/2011]
    • PuppetShow takes some version of the protocol graph produced via the Assembly Planner
      • The relationships between parts within the protocol graphs are assumed to be labeled with protocol names
      • The PuppetShow itself should link the protocol names to libraries and help generate the necessary Puppeteer code
  • read through Puppeteer/related abstract [6/7/2011]
  • peruse GroovyScripter code/structure
    • read up on JEditorPane first!!
    • attempt to mimic GUI and incorporate Python-parsing?
  • figure out how to seamlessly integrate Python script-compiling within fluid GUI
  • design aforementioned fluid GUI

Using the Clotho platform [4], we develop two
applications for specifying and executing biological protocols.
The Assembly Planner [5] is the end-point of an endto-
end design workflow [3] that produces an assembly plan
for synthetic biological devices, with each assembly step
annotated with the name of a biological protocol. Each
such protocol itself may be fully specified using another
Clotho application called PuppetShow, which provides an
environment for writing, testing, debugging, and executing
biological protocols.
--A Software Stack for Specification and Robotic Execution of Protocols for Synthetic Biological Engineering

The Backburner

• Protocol Graphs Thought Project
  • Ideally, we should have a protocol graph that would be a generic form of managing an arbitrary combination of protocols.
  • The protocol graph should contain vertices, which are either operands or protocols/operations.
  • The graph should also connect operands to protocols.
  • Given access to a library of protocol specifications, one should be able to give an expression or an explicit protocol graph for parsing purposes.
  • One should be able to use PuppetShow (see powerpoint) to create an implicit protocol graph.
  • One should be able to reconfigure protocol graphs for optimization, etc.
  • Questions
    1. How do we want to construct this graph?
    2. Does the user input an expression?
    3. Should we have an interactive GUI to help user create custom protocol graphs?