Dear list,
what is the role of vweight in the constructor to BlockState? In particular, I'm trying to understand how the result of minimize_(nested_)blockmodel_dl will be different if certain vertices are assigned higher weights in the graph.
I believe that if the eweight between a pair of nodes is increased, then the two nodes are more likely to end up in the same block (more or less). Would the opposite be true if their vweight is increased?
Many thanks in advance,
Peter
On 13.03.2017 08:12, Peter Straka wrote:
Dear list,
what is the role of vweight in the constructor to BlockState? In particular, I'm trying to understand how the result of minimize_(nested_)blockmodel_dl will be different if certain vertices are assigned higher weights in the graph.
As stated in the documentation, like eweight, vweight denotes multiplicity. So a node v with vweight[v] == 2 counts as two nodes.
These parameters are useful for working with summarized versions of the network, which are used by some algorithms in graph-tool. It is meant mostly for internal use, not as a means of introduction arbitrary weights to nodes and edges.
I believe that if the eweight between a pair of nodes is increased, then the two nodes are more likely to end up in the same block (more or less). Would the opposite be true if their vweight is increased?
No, this interpretation is not correct. Increasing the edge or node multiplicity can have varied effects, it depends on the rest of the network.
Best, Tiago