Cytoscape Wiki|
← Revision 3 as of 2008-09-09 00:01:41
Size: 671
Comment:
|
← Revision 4 as of 2008-09-09 03:20:43 →
Size: 1282
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| * Gary opinion, Sep8 - Re: groups. Groups definitely belong in the model, but they should be kept separate from the core network model. There should be a CyGroups API similar to the one that exists that keeps track of all group information. Algorithms that work on simple graphs (most of the existing Cytoscape and plugin code) will not need to know about groups and those that need groups will be able to access the information using the CyGroups API. Group views on the other hand will likely need a lot of custom node shape functionality in the view layer. This is how Hyperedges should work as well. |
Mini-Retreat One
- September 12-13, 2008
[http://www.ucsd.edu/maps/index.jsp?mapid=601&wid=601&iws=false&cat=&t=m&z=15&opacity=50&ll=32.88178563936398,-117.23437786102295 "Department of Bioengineering"] (Powell-Focht Bioengineering Hall), UC San Diego, Room 291
Topics for Discussion
Progress on merging the new CyNetwork and CyAttributes model with the 3.0 branch.
- Discussion of how Groups will fit in to the model package.
Discussion of how HyperEdges will be handled.
Goal
Get the application and at least one core plugin working with the new CyNetwork and CyAttribute models.
Meeting Notes
Gary opinion, Sep8 - Re: groups. Groups definitely belong in the model, but they should be kept separate from the core network model. There should be a CyGroups API similar to the one that exists that keeps track of all group information. Algorithms that work on simple graphs (most of the existing Cytoscape and plugin code) will not need to know about groups and those that need groups will be able to access the information using the CyGroups API. Group views on the other hand will likely need a lot of custom node shape functionality in the view layer. This is how Hyperedges should work as well.