SaveLEDA Functionality #162
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are a few network packages/methods out there that require a LEDA-formatted file as input (for example, Graphlet-based network comparison distances). It's obviously not impossible to code up yourself a LEDA file from the raw edge outputs that SNAP provides, but it would be nice to have saving to a LEDA-format file built in to the SNAP functionality. So I wrote a function that does that. I'm not sure exactly what all needs to happen to make that part of the make file/namespace/documentation, but I'm happy to help where I can.
SUNetID: scottyf