You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the functions from booleannet.network I get an error that networkx
is not present. However this is false as I do have networkx properly installed.
I found the source of the problem: in booleannet's 'network.py' file it uses
-----------------
from networkx import component
-----------------
However, networkx has no "component" name, but it does have "components". I am
running the latest version of networkx (as of late October), so perhaps they
have changed it recently. Anyway, the first is simple
-----------------
from networkx import components as component
-----------------
and then I reinstalled booleannet to python and everything worked fine.
Jason Wittenbach
PhD Candidate
Department of Physics
Penn State Unviersity
juw217@psu.edu
Original issue reported on code.google.com by Jason.Wi...@gmail.com on 11 Nov 2011 at 6:53
The text was updated successfully, but these errors were encountered:
Yes I am aware of this, the networkx library has changed its API several times
and we need to play catchup.
We usually fix things up in spurts, once every half year. Probably early 2012.
Original comment by istvan.a...@gmail.com on 11 Nov 2011 at 12:10
When the script "BooleanNet-1.2.8/examples/samples/singlepick.py" is run the
following error occurs,
"*** error: networkx is missing, install it from https://networkx.lanl.gov/"
I tried to fix this bug by using,
"from networkx import components as component" in the network.py script and
reinstall BooleanNet.
But this doesn't solve the issue.
Could some one advise on how to get rid of this bug?
PS. I removed some of my previous comments and edit this one.
Original comment by gabbyt...@gmail.com on 26 Feb 2015 at 2:09
Original issue reported on code.google.com by
Jason.Wi...@gmail.com
on 11 Nov 2011 at 6:53The text was updated successfully, but these errors were encountered: