getEdges.ggobi {Rggobi} | R Documentation |
These functions allow the user to establish and query connections between points in a GGobi instance and use this information to show edge connections on displays.
getEdges.ggobi(edgeset = 1, .data = NULL, .gobi=getDefaultGGobi()) setEdges.ggobi(src, dest, edgeset, .gobi=getDefaultGGobi())
edgeset |
an identifier for the dataset within the GGobi instance,
given as an index or an object of class the ggobiDataset |
.data |
an identifier for the dataset within the GGobi instance,
given as an index or an object of class the ggobiDataset |
.gobi |
an identifier for the GGobi instance which can be
omitted if .data is a ggobiDataset object.
Otherwise this should be an integer identifying the GGobi instance
or a ggobi object.
|
src |
a vector identifying the source of the edges by index or a 2 column matrix giving the source and destination |
dest |
a vector giving the indeces of the destination nodes of the
edges used together with x
|
A matrix giving the edge pairs before the call.
Should no edges return NULL or an empty matrix?
The edge mechanism in GGobi is very powerful and supports a very general form of linking. As a result, simple uses may appear complex. The idea with this interface is to try to hide the complexity. However, you are advised to read the GGobi and RGGobi manuals to get a better understanding of edges and linking.
Duncan Temple Lang
createEdgeData.ggobi
setDisplayEdges.ggobi
## Not run: #XXX ggobi(file.path(ggobi.home(), "datasets", "snetwork.xml")) # Find ggobi.home getEdges.ggobi(2, 1) getEdges.ggobi(2) ## End(Not run)