Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modularity output different depending on the order of importing nodes and edges table #2888

Open
ubique123 opened this issue Feb 20, 2024 · 0 comments

Comments

@ubique123
Copy link

Expected Behavior

Stable results of the modularity measure and identified communities

Current Behavior

When importing a .csv file, formatted as a Nodes table (Id, Label columns only) and then appending another .csv file, formatted as na Edges table (source, target, weight columns only) I get lower modularity scores and more communities (the decomposition is stable when repeated).
When I first import the edges table and then append the nodes table (or do not append it at all), I get higher modularity scores with less communities, and, again, the result is stable when I repeat the importing and computation.
The graph is weighted and directed, and modularity options are: randomize - yes, use weights - yes, resolution - 1.0, classes start at - 0.

I have also generated a similar graph from fake data, and the problem remains - the order of importing data files changes modularity scores.

Attached is the study data (assortNodes.csv is the nodes table, outbreak.csv is the edges table) and the fake data (nodesTest.csv and edgesTest.csv)
assortNodes.csv
edgesTest.csv
nodesTest.csv
outbreak.csv

Possible Solution

Steps to Reproduce

Context

Your Environment

  • Version used: Gephi 0.10.1
  • Operating System: Win 11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant