Importing and exporting functions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Currrently Raphtory slicing is very useful for handling temporal multilayer networks, especially temporal slicing and layer selection. However, we are lacking export functions to continue our analysis when Raphtory is not enough. Cases include:
- analysis algorithms like common centralities ...
- deep learning libraries like deep graph library, pytorch geometric and pytorch geometric temporal.
Solution: offer exporting functions to common formats edgelist + nodelist, gml etc as well as the generation of networkx or networkit graphs to continue the analysis. An example of conversion, although probably slow is currently in the visualization module, to_networkx function.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the visualization module's existing to_networkx conversion and review how Raphtory slicing and layer selection are represented. Define the supported edgelist, nodelist, GML, NetworkX, and downstream graph-library outputs before implementation. Done means the agreed export and conversion cases are available for continued analysis outside Raphtory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch, rust
- Domain
- data, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100