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

Is there an efficient way to read a GraphML file and produce a MetaGraph? #54

Open
ArtHarg opened this issue Mar 29, 2023 · 2 comments
Open
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@ArtHarg
Copy link

ArtHarg commented Mar 29, 2023

Is there an efficient way to read a GraphML file and produce a MetaGraph?

My use case: I have a file with vertices and edges, all with metadata. I can succesfully read the graph using

g = loadgraph(“calcGraph.graphml”,“graph”, GraphMLFormat())

but that ignores the key and data nodes. MetaGraphNext.jl doesn’t seem to have a function to read GraphML files.

Is there a way to read the GraphML, apart from using EzXML to read the GraphML file and building the MetaGraph myself? If not, what would be the most efficient and/or most Julian way to approach this?

@gdalle gdalle added enhancement New feature or request help wanted Extra attention is needed labels Mar 30, 2023
@filchristou
Copy link
Contributor

Hi. To my knowledge there is nothing for MetaGraphsNext.jl. However if you want to read in a MetaGraphs.jl, you can use https://github.com/UniStuttgart-IKR/NestedGraphsIO.jl. NestedGraphsIO.jl can read both NestedGraphs and MetaGraphs.MetaGraph from GraphML. However it's not registered because a PR at GraphsIO.jl is pending.

@filchristou
Copy link
Contributor

right now the whole GraphsIO.jl thing is a bit of a mess. With julia v1.9 and package extensions things will improve noticeably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants