hi,
i use the part of the functionality of the graph package within my
packages qpgraph and VariantFiltering. I mostly use the 'graphBAM' class
that provides a memory-efficient representation of the graph and the
possiblity to store data associated with nodes and edges via the
'nodeData()'
Possibly of interest on this topic, though it implements a different sort of
(interactive) solution, are two Bioc packages: RCyjs and RCy3.
RCyjs renders to the browser, using the cytoscape.js javascript library and
websockets:
http://js.cytoscape.org/
RCy3 renders to Cytoscape, the
Dear Thomas
thank you for asking about this.
The main information in a graphNEL is, of course, the vector of nodes
(character) and a list of edges. That information can for sure go into an
igraph.
Then there is the slot `renderInfo`, which afaIu is (or can be) used to control
how the graph
>From my perspective Rgraphviz now has a quite good (cross-platform) access
to the Graphviz layout routines. But how to actually use these routines
from R is certainly something I think could be vastly improved upon. Right
now, Rgraphviz basically has two different interfaces to graph layout and
I’m in the process of developing ggraph (https://github.com/thomasp85/ggraph) -
An extensive plotting framework for graph/tree/network data based on ggplot2.
Currently the class support is focused on igraph and dendrogram, but the idea
is to extend it with support for additional graph
