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.

Sign up for GitHub

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

Jump to bottom

GEXF Output #103

Closed
ianmilligan1 opened this issue Oct 25, 2017 · 5 comments
Closed

GEXF Output #103

ianmilligan1 opened this issue Oct 25, 2017 · 5 comments
Labels
enhancement

Comments

@ianmilligan1
Copy link
Member

Right now, we export networks in CSV and GDF.

I think we should explore exporting to GEXF as it would play nicer with Ryan's Sigma.js format. GDF import into Gephi seems a bit wonky too.

For Gephi users, recent CSV importer enhancements make having a native file format for them less important. The new importer is great.
@greebie
Copy link
Contributor

greebie commented Oct 25, 2017 •
edited
Loading

Just to point out a use case for this tool. Because Sigma.js is primarily a visualisation tool, it would be nice to have a Gexf output that includes a large number of attributes for the nodes and edges.

For example, "x" & "y" attributes would offer default positions on a canvas, web archive attributes (.com vs .org), page rank or if we are feeling ambitious, some NER responses based on the text in the record.

Edge examples would be less common, but one example might be urls found inside <head> vs those inside <body>.

In an ideal world, I would be able to build a node and edge data frame, filter via these kinds of values and output both to a gexf. More discussion at #13 .

If pyspark plays nicely with networkx or igraph, it would be nice to include some algorithm values like eigenvector centrality. If not, we will have to settle for the Sparkx Scala library.

@ianmilligan1
Copy link
Member Author

Thanks @greebie, so you think this might wait until #13 is implemented and come out of that nicely? Do you want me to assign this to you to take on once we have DataFrames implemented?

@greebie
Copy link
Contributor

greebie commented Oct 27, 2017

I think it would be worth it to check. It is also related to the discussion about maintaining Scala vs Python code.

@ianmilligan1
Copy link
Member Author

I'm circling back to this – now that it is clear that we'll be keeping the Scala version, I think it's important to try to have GEXF output.

@greebie greebie mentioned this issue Dec 5, 2017
Merged
ianmilligan1 pushed a commit that referenced this issue Dec 5, 2017
@greebie @ianmilligan1
Include script to write to GEXF. (#103) (#137)
6b761b9 
* Include script to write to GEXF.

* Fix typographical errors (gdfPath for gexfPath)
@ianmilligan1
Copy link
Member Author

Closed with #137

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@greebie @ianmilligan1