-
Notifications
You must be signed in to change notification settings - Fork 3
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
Decorated graphs #37
Decorated graphs #37
Conversation
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #37 +/- ##
==========================================
+ Coverage 80.29% 80.92% +0.62%
==========================================
Files 20 21 +1
Lines 878 907 +29
==========================================
+ Hits 705 734 +29
Misses 173 173
|
For the current version of |
Maybe |
Currently the vertex |
Oh I see, I was picturing that each vertex neighbor would get connected to unique vertices of the decorated graph getting inserted onto the vertex, that's why I thought it would be random to some extent. In that case, I agree it isn't random (though still somewhat arbitrary and restricted) since the user can choose which is the first vertex of the decorated vertex graph. In that case it seems fine to leave it for future work to give more control to the users over how the edges to the neighbors get specified. |
This PR, which addresses #36, adds functionality for decorating graphs by adding additional graphs on their edges or vertices.
Two functions are provided
decorate_graph_edges(g::NamedGraph; edge_map::Function=e -> named_grid((1,)))
and
decorate_graph_vertices(g::NamedGraph; vertex_map::Function=v -> named_grid((1,)))
Currently there are defaults for which vertices of the decoration are connected to the edges/vertices original graph but we will add keyword arguments for this in the future.
Testing is included. This PR also fixed an ambiguity issue with function
a_star
when passed aNamedGraph
with Integer labelling.