Size: 1275
Comment:
|
Size: 1919
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
In many cases, biologists are interested in relationship between functional modules first. Then, they look into the details inside the modules, i.e., actual interactions. Cytoscape can partially handle this problem using Group API and some related plugins, but it's not a standard feature. Also, there is no simple file format to represent hierarchy/substructures. | In many cases, biologists are interested in relationship between functional modules first. Then, they look into the details inside the modules, i.e., actual interactions. Cytoscape can partially handle this problem using Group API and some related plugins, but it's not a standard feature. Also, there is no simple file format to represent hierarchy/substructures. In this project, we are going to implement a mechanism to handle output of module finding algorithms as a hierarchy of subnetworks and make Cytoscape core module-aware. |
Line 8: | Line 8: |
=== Module Finding Plugins === Currently, there are several plugins finding functional modules from large networks. In some cases, they produce subnetworks, but there is no universal UI or function to keep the structure in the session or other files. === Pathway Overview === Cytoscape has function to import KEGG/Reactome data as attributes. |
|
Line 27: | Line 32: |
This package does not have its own file format to represents subgraph. Instead, supporting GraphML and dot. | |
Line 28: | Line 34: |
= Unified UI for Module Finding Plugins and New Network Browser = |
=== Cytoscape New File Format for Subgraphs === === User Interface === |
Support for Modules in Cytoscape
Introduction
In many cases, biologists are interested in relationship between functional modules first. Then, they look into the details inside the modules, i.e., actual interactions. Cytoscape can partially handle this problem using Group API and some related plugins, but it's not a standard feature. Also, there is no simple file format to represent hierarchy/substructures. In this project, we are going to implement a mechanism to handle output of module finding algorithms as a hierarchy of subnetworks and make Cytoscape core module-aware.
Usecases
Module Finding Plugins
Currently, there are several plugins finding functional modules from large networks. In some cases, they produce subnetworks, but there is no universal UI or function to keep the structure in the session or other files.
Pathway Overview
Cytoscape has function to import KEGG/Reactome data as attributes.
Implementation
File Formats
Most of popular XML graph file formats support hierarchical structure.
DOT
This is a standard file format in graphviz. It has XML-like structure in the text file, and can represent substructure.
Pajek
This program has 3 types of files to represent substructure:
- Partitions – they tell for each vertex to which class vertex belong. Default extension: .clu.
- Clusters – subset of vertices (e.g. one class from partition). Default extension: .cls.
- Hierarchies – hierarchically ordered vertices. Default extension: .hie.
Therefore, user needs to load 4 files (network, partition, cluster, hierarchy) to reconstruct the saved substructures.
igraph
This package does not have its own file format to represents subgraph. Instead, supporting GraphML and dot.
Cytoscape New File Format for Subgraphs