I currently started using graph-tool: nice software, excellent documentation, thank you!
However, I stumbled on some (for me) unexpected behavior when using the get_edges_prob() function with a BlockState of a weighted network (graph-tool version 2.26, Python 2.7 as well as Python 3.6). When calling the get_edges_prob() function to a state, its entropy is altered, and subsequent calls of get_edges_prob() deliver different results.
"Luckily", I could reproduce the observed behavior with a dataset from the graph-tool collection (with arguably small alterations, but the introduced differences are a lot bigger in my networks).
import graph_tool as gt
import graph_tool.collection as gtc
import graph_tool.inference as gti
for i in range(10000):
state.entropy() #entropy is different from original!
edge_prob #first call of get_edges_prob() delivers other results than last
For me, this is really unexpected. What is happening there, and/or how this can be fixed?
Smaller further experiments showed that this also happens to NestedBlockStates (of course), but seems not to happen for models lacking edge covariates...
Thanks in advance!
Katharina Baum, PhD
Postdoctoral Fellow, Proteome and Genome Research Unit
Luxembourg Institute of Health
Department of Oncology
1A-B, rue Thomas Edison, L-1445 Strassen
Fax: +352 26970-719
Join us on Facebook and follow our activities on Twitter:
This message (including any attachments) is intended for the addressee only and may contain confidential and/or privileged information and/or information protected by intellectual property rights. If you have received this message by mistake, please notify the sender by return e-mail and delete this message from your system. You should not use, alter, copy or distribute this message or disclose its contents to anyone. E-mail transmission can not be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Luxembourg Institute of Health shall not be responsible nor liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system.
attachment.html (4.58 KB)