Hi guys,
when I import graph_tool I get an error. It complains graph filtering was disabled at compile time. Well, I can't set it enable because for some reason compiling with flag enabled drains out my memory. I have 4GB RAM and I am using Arch. I get package from AUR repository and made makepkg on it(I had to modify it slightly to get rid of openmp and graph-filtering).
My stack trace from ipython:
In [1]: from graph_tool.all import * --------------------------------------------------------------------------- RuntimeError Traceback (most recent call last) <ipython-input-1-100bbe2bc9d9> in <module>() ----> 1 from graph_tool.all import *
/usr/lib/python2.7/site-packages/graph_tool/__init__.py in <module>() 2010 e.__class__.__doc__ = _edge_doc 2011 -> 2012 init_edge_classes() 2013 2014 # some shenanigans to make it seem there is only a single edge class
/usr/lib/python2.7/site-packages/graph_tool/__init__.py in init_edge_classes() 2000 e_filter = g.new_edge_property("bool") 2001 e_filter.a = [1] -> 2002 g.set_edge_filter(e_filter) 2003 if v_filtered: 2004 v_filter = g.new_vertex_property("bool")
/usr/lib/python2.7/site-packages/graph_tool/__init__.py in set_edge_filter(self, prop, inverted) 1733 are kept. If the supplied property is ``None``, any previous filtering 1734 is removed.""" -> 1735 self.__graph.SetEdgeFilterProperty(_prop("e", self, prop), inverted) 1736 self.__filter_state["edge_filter"] = (prop, inverted) 1737
RuntimeError: graph filtering was not enabled at compile time
Hi there,
On 05/17/2013 12:19 PM, piwonski.kris@gmail.com wrote:
Hi guys,
when I import graph_tool I get an error. It complains graph filtering was disabled at compile time.
This is a bug... It should be to import the module with graph filtering disabled. I'll submit a fix to it.
Well, I can't set it enable because for some reason compiling with flag enabled drains out my memory. I have 4GB RAM and I am using Arch. I get package from AUR repository and made makepkg on it(I had to modify it slightly to get rid of openmp and graph-filtering).
It should be possible to compile graph-tool under 4GB RAM... Did you make sure no other process was using significant amount of memory, such as the browser and such?
Optionally, you can use the clang compiler. It uses significantly less memory than GCC (around half or so).
Cheers, Tiago
Thanks Tiago for response.
When I compile there is not other significant processes in background. Before compilation there is no more than 700MB used by other processes.
Just in case I attach my configure.log.
In free time I will try to compile it with clang.
Kris
On Friday, 17 May 2013 18:37:06 UTC+2, Tiago Peixoto wrote:
Hi there,
On 05/17/2013 12:19 PM, piwons...@gmail.com javascript: wrote:
Hi guys,
when I import graph_tool I get an error. It complains graph filtering was disabled at compile time.
This is a bug... It should be to import the module with graph filtering disabled. I'll submit a fix to it.
Well, I can't set it enable because for some reason compiling with flag
enabled drains out my memory.
I have 4GB RAM and I am using Arch. I get package from AUR repository
and made makepkg on it(I had to modify it slightly to get rid of openmp and graph-filtering).
It should be possible to compile graph-tool under 4GB RAM... Did you make sure no other process was using significant amount of memory, such as the browser and such?
Optionally, you can use the clang compiler. It uses significantly less memory than GCC (around half or so).
Cheers, Tiago
-- Tiago de Paula Peixoto <ti...@skewed.de javascript:>
-
piwonski.kris＠gmail.com -
Tiago de Paula Peixoto