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

Remove loops from graph visualization and edge count #44

Closed
albertocottica opened this issue Oct 6, 2014 · 7 comments
Closed

Remove loops from graph visualization and edge count #44

albertocottica opened this issue Oct 6, 2014 · 7 comments

Comments

@albertocottica
Copy link
Member

It is not clear that loops have meaning in a social network of comments. Removing them improves the clarity of the graph.

@luca
Copy link
Contributor

luca commented Oct 7, 2014

commenting to say that when we remove loops we'll have to do so by removing (not considering) the network edges generated by comments of a person on their own content (they are currently included in the network)

@albertocottica
Copy link
Member Author

You could also remove all edges where source == target

@luca
Copy link
Contributor

luca commented Oct 7, 2014

yep that what I meant but badly explained 😄

@jenkin
Copy link
Contributor

jenkin commented Oct 13, 2015

Simple filter in preprocessing, but with edgeryders the improvement in visualization is quite useless (loops are ~11% of total edges): Dataninja@a71f78a

@luca
Copy link
Contributor

luca commented Oct 13, 2015

@jenkin that's ok, I still think removing the loops should be done: as @albertocottica said in the there's a reason of clarity and meaning for removing them

@jenkin
Copy link
Contributor

jenkin commented Oct 21, 2015

Ok, loops removed as discussed here: #34 (comment)

@jenkin
Copy link
Contributor

jenkin commented Nov 14, 2015

Done in last PR.

@luca luca closed this as completed Nov 25, 2015
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

3 participants