Skip to content

jung.algorithms.scoring.BetweennessCentrality seems to be wrong #224

@darkclouder

Description

@darkclouder

Hey there,
the implementation of jung.algorithms.scoring.BetweennessCentrality seems to be wrong.
Initially, I came across this because I was so surprised that the JUNG implementation is so much faster than my own.

Tested with this graph:
http://www.cs.utah.edu/~lifeifei/research/tpq/OL.cedge
(Edge list of Edge ID, Start Node ID, End Node ID, L2 Distance)
I used the L2 distance as an edge length.

I compared the vertex betweenness of JUNG with the betweenness that I get with my own implementation and then compared both with the implementation of Visone, a graphical graph tool from the chair of research of Ulrik Brandes (the creator of that particular betweenness algorithm in the first place). http://www.visone.info/html/download.html

Simply looking at node 0 shows a huge difference.
JUNG returns a betweenness of 0.0, my implementation and the one of Visone returns 38,924.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions