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

Port Gelly Graph methods to GraphStreams #3

Open
balidani opened this issue Mar 30, 2015 · 4 comments
Open

Port Gelly Graph methods to GraphStreams #3

balidani opened this issue Mar 30, 2015 · 4 comments

Comments

@balidani
Copy link
Collaborator

All relevant Gelly methods should be ported. Some of these are:

  • Graph creation
    • fromRandomEdgeStream()
    • fromIncidenceStream()
  • Graph stream properties
    • getVertices(), getEdges()
    • getVertexIds(), getEdgeIds()
    • inDegrees(), outDegrees(), getDegrees()
    • numberOfVertices(), numberOfEdges()
  • Graph stream transformations
    • mapVertices(), mapEdges()
    • filterOnVertices(), filterOnEdges()
    • subgraph()
    • reverse()
    • undirected()
    • union()
  • Neighborhood methods

Each of these have to be considered for both normal streams and (tumbling?) windows.

@vasia
Copy link
Owner

vasia commented Apr 1, 2015

I'd like to implement some of these to also start getting a bit familiar with the streaming API.
On which branch are you planning to work on these? Shall we create individual issues for each method or just leave a comment here on what we're working on?

@balidani
Copy link
Collaborator Author

balidani commented Apr 1, 2015

Right now I'm working on a test branch called graph-representation or something. Should I move to master? Is there a point of having an interface for GraphStream?

I think we can comment here about the functions we want to implement.

@senorcarbone
Copy link
Collaborator

I will work on the merge trees on a different branch probably and merge later ^^

@vasia
Copy link
Owner

vasia commented Apr 2, 2015

@balidani, now that we have a clearer model in mind, let's move what we have in the master.
And I don't see a point in the interface, since we're going for edge representation only. We could add this later if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants