Cytoscape Wiki|
← Revision 5 as of 2006-11-17 20:35:17
Size: 3095
Comment:
|
← Revision 6 as of 2007-05-30 23:09:09 →
Size: 4263
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 68: | Line 68: |
| [[PageComment2]] |
---- AllanKuchinsky - 2006-11-26 05:41:17 Do compartments need to be aware of what components are in them? For example, if a compartment is moved or resized, do positions of components need to move with them or shift arrangement to accommodate resizing? This requires further discussion, as there are a number of alternative ways that compartments could be represented: 1. as Groups, in which case components would be members. This raises the issue of whether Groups can intersect, e.g. for trans-membrane proteins. Since Groups are networks, this ought to be feasible, since nodes and edges can be shared across groups. But how would it affect intersecting groups if, for example, a compartment is moved or resized? 2. as arbitrary graphical annotations. Flexible, but doesn't accommodate the association of components with the compartment. 3. as a specialized type of Cytoscape Node. This seems as if it would require extensive changes and specialized processing in the Cytoscape core, probably not advisable. ---- MiritAladjem - 2007-02-01 08:53:38 Yes. Subcompartments and anything in the compartment needs to move when compartments are moved or resized. |
Summary
A user wants to describe a membrane-enclosed compartment
Step-by-Step User Action
- User specifies a boundary to partition the compartments
- User optionally specifies a label for the compartments
Visual Aides
A membrane boundary is represented with a thick, double-walled line. It can either partition the entire map, as in this example:
attachment:compartment1_061115_dwk.png
Alternately, the compartment can completely enclose a region on a map, as in this example:
attachment:compartment2_061115_dwk.png
Requirements for Cytoscape
TBD
We are unsure to what degree components in the map need to be aware of what compartments they appear in.
Importance
Compartments play an important role in describing transportation functions. They also interact with other elements in the ../ShowTransport and ../ProteinDomains use cases.
Variations
Some earlier maps used a pattern instead of shading to describe the membrane as in this example:
attachment:compartment3_061117_dwk.png
Other Examples
Comments
Shared ../MimEditorUseCaseComments
It is not clear how to represent the compartments in BioPax.
AllanKuchinsky - 2006-11-26 05:41:17
Do compartments need to be aware of what components are in them? For example, if a compartment is moved or resized, do positions of components need to move with them or shift arrangement to accommodate resizing?
This requires further discussion, as there are a number of alternative ways that compartments could be represented: 1. as Groups, in which case components would be members. This raises the issue of whether Groups can intersect, e.g. for trans-membrane proteins. Since Groups are networks, this ought to be feasible, since nodes and edges can be shared across groups. But how would it affect intersecting groups if, for example, a compartment is moved or resized? 2. as arbitrary graphical annotations. Flexible, but doesn't accommodate the association of components with the compartment. 3. as a specialized type of Cytoscape Node. This seems as if it would require extensive changes and specialized processing in the Cytoscape core, probably not advisable.
MiritAladjem - 2007-02-01 08:53:38
Yes. Subcompartments and anything in the compartment needs to move when compartments are moved or resized.