wrong group closeness centrality

Bug #504037 reported by Dimitris Kalamaras
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
SocNetV
Fix Released
High
Dimitris Kalamaras
0.x
Fix Released
High
Dimitris Kalamaras

Bug Description

Group closeness results in negative numbers

Revision history for this message
Dimitris Kalamaras (dimitris-kalamaras) wrote :

All the results I got for GCC(Group Closeness Centralisation) are negative numbers, not in the GCC range: 0 < GCC < 1.

--Haiyue Jin

summary: - wrong standardized closeness centrality
+ wrong group closeness centrality
Revision history for this message
Dimitris Kalamaras (dimitris-kalamaras) wrote :

The bug was in createDistanceMatrix() method, in line 1210. We needed to call minmax with std CC not plain CC:

minmax( (*it)->SCC(), (*it), maxCC, minCC, maxNodeCC, minNodeCC) ;

Fix commited

Changed in socnetv:
importance: Undecided → High
assignee: nobody → Dimitris Kalamaras (dimitris-kalamaras)
milestone: none → 0.80
description: updated
Changed in socnetv:
status: New → Fix Committed
Changed in socnetv:
status: Fix Committed → Fix Released
Changed in socnetv:
milestone: 0.80 → 0.81
Revision history for this message
Jin Haiyue (haiyue-j) wrote :

Version 0.81: wrong closeness centrality (CC') and group closeness centrality (GCC);
The GCC now are positive numbers, but still out of the range of 0<GCC<1; and also the CC' out of range of 0<CC'<1.

Revision history for this message
Dimitris Kalamaras (dimitris-kalamaras) wrote :

Jin, I thought this bug was fixed. :(

Are you using directed data?

Have you tested this with undirected data?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.