Implement Laplacian centrality

Bug #1116657 reported by Jan Katins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
igraph
Confirmed
Wishlist
Unassigned
Revision history for this message
Jan Katins (jasc) wrote :

This is a algorithm with O(v) time complexity, but similar results than closeness/betweenes...

Tamás Nepusz (ntamas)
Changed in igraph:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Tamás Nepusz (ntamas) wrote :

Seems quite simple. Not sure if it will ever make it into the C core because it is fairly easy to implement it in Python or R without significant speed loss. A Python implementation is now provided here:

http://igraph.wikidot.com/python-recipes#toc4

Revision history for this message
Jan Katins (jasc) wrote :

Nice, thanks! Would you take a patch which adds this to the python graph class?

Revision history for this message
Tamás Nepusz (ntamas) wrote :

Sure, that would be awesome. A complete patch should include:

- The function itself of course ;)
- A proper docstring for the function
- A corresponding test case in igraph.test.structural or wherever else it fits the best

Note that we are in the process of moving the igraph repositories to Github, so if you feel more comfortable with Github, you can fork the 'develop' branch of the igraph repo on Github (http://github.com/igraph/igraph) and then send us a pull request with the changes. Alternatively, you can attach a patch to this bug report, that's also fine, I'll just commit it to the Github repo and it will be synchronized here by Launchpad itself.

Revision history for this message
Jan Katins (jasc) wrote : Re: [Bug 1116657] Re: Implement Laplacian centrality

Hi!

On 5 March 2013 22:55, Tamás Nepusz <email address hidden> wrote:
> Sure, that would be awesome. A complete patch should include:
> - The function itself of course ;)
> - A proper docstring for the function
> - A corresponding test case in igraph.test.structural or wherever else it fits the best

Ok, will do!

> Note that we are in the process of moving the igraph repositories to
> Github, so if you feel more comfortable with Github, you can fork the
> 'develop' branch of the igraph repo on Github
> (http://github.com/igraph/igraph) and then send us a pull request with
> the changes.

Great! Will you also move all bugreports?

I've forked the repository and will send you a PR. This could take a
while because I have to first figure out how to build this beast under
windows and MS compilers.

Jan

Revision history for this message
Gábor Csárdi (gabor.csardi) wrote :

We will move the bug reports as well, but this will take some time, and you'll get an email about it, assuming this bug is not closed before that.

To build on windows, it is easiest to just download the MSVC zip file from the homepage and then you can send a patch against that.

Revision history for this message
Gábor Csárdi (gabor.csardi) wrote : Continue on github

The development of igraph has moved to github, so please do not comment on this bug here. You are of course welcome to comment on github, here:
https://github.com/igraph/igraph/issues/363

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.