-
-
Save rtbs-dev/1349864212b25cce91dbe5e336d794b4 to your computer and use it in GitHub Desktop.
Wow, I had no idea there were comments here! Thanks to all for checking out the example. For those of you with issues/ideas (especially networkx v2 problems), check out the repository that automates a lot of the underlying mechanical/boilerplate code in this example. This notebook was really just a proof-of-concept for that repository.
I haven't gone back to the code for a while, but if there's interest I would be happy to update things to newer pymc3 features. Please see if your above issues persist in the more mature repository. Thanks!
@NelisW certainly, and like I said, feel free to open an issue if something works unexpectedly on that repo (as I said, it's been a while).
If you are having issues with BN.edges['C3']['D4']['bin']
, substitute for BN.edges['C3','D4']['bin']
.
As described in the migration guide mentioned before
G.edge have been removed in favor of using G.nodes[n] and G.edges[u, v]
Do you have any example for dynamic BN simulated on PYMC3?
Thanks to all above!
I have about four hours experience in pymc3, so the above comments are much appreciated.
Using networkx 2.3 and pyMC3 3.7, cpu on Windows.
Fixed the
dict_keyiterator
problem.When
print(BN.__dict__)
I see noedge
attribute.The edges seem to be embedded in
_adj
,_pred
and_succ
.D1
is a predecessor forC1
.C1
is a successor forD1
.But
C1
is also adjacent toD1
?My bigger issue is what to do with the error on line 32/33 above.
I have no idea how to handle this. Any help will be appreciated!