|
From: | Bob Pap |
Subject: | Re: [igraph] smooth interaction between igraph/R and networkx/python |
Date: | Thu, 6 Dec 2012 15:11:46 +0100 |
> g_new <- read.graph(MyFile("folder", "data", "g_new.gml"),"gml")
Error in read.graph.gml(file, ...) :
At foreign.c:1114 : Parse error in GML file, line 1 (syntax error, unexpected LISTCLOSE, expecting KEYWORD), Parse error
> g_new <- read.graph(MyFile("folder", "data", "g_new.net"),"pajek")
Error in read.graph.pajek(file, ...) :
At foreign.c:578 : Parse error in Pajek file, line 1 (syntax error, unexpected ALNUM), Parse error
> g_new <- read.graph(MyFile("interbank", "data", "g_new.graphml"),"graphml")
> forth (incidentally, igraph is not able to read the gml and pajek graphsCan you please send me a few example graphs produced by NetworkX that cannot
> exported from networkx).
be read by igraph?
The only trick that comes into my mind is that if you want to avoid having
> However, a bit ahead I am going to have to do the back-and-forth between
> igraph/R and networkx/python for many graphs. Is anybody familiar with
> tricks to implement this in code?
to jump back and forth between an R console and a Python console, you could
try RPy (http://rpy.sourceforge.net), which aims to bridge the gap between
the two languages. Note that R and Python still live in their separate
worlds, RPy just gives you tools to pass basic variables between them.
(Passing igraph graphs directly won't work, though).
--
T.
_______________________________________________
igraph-help mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/igraph-help
g_new.gml
Description: Binary data
g_new.graphml
Description: Binary data
g_new.net
Description: Binary data
[Prev in Thread] | Current Thread | [Next in Thread] |