"
Team:BU Wellesley Software/Notebook/JanooNotebook
From 2011.igem.org
(Difference between revisions)
| Line 8: | Line 8: | ||
*design aforementioned fluid GUI | *design aforementioned fluid GUI | ||
| - | ==Backburner== | + | ==The Backburner== |
*Protocol/Assembly Manager | *Protocol/Assembly Manager | ||
**Ideally, we should have a protocol graph that would be a generic form of managing an arbitrary combination of protocols. | **Ideally, we should have a protocol graph that would be a generic form of managing an arbitrary combination of protocols. | ||
Revision as of 17:21, 6 June 2011
Life = 42
To-Do List
- read through Puppeteer/PuppetShow powerpoint
- read through Puppeteer/related abstract
- peruse GroovyScripter code/structure
- figure out how to seamlessly integrate Python script-compiling within fluid GUI
- design aforementioned fluid GUI
The Backburner
- Protocol/Assembly Manager
- 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
- How do we want to construct this graph?
- Does the user input an expression?
- Should we have an interactive GUI to help user create custom protocol graphs?
