-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add children property to CompositeNode #189
Comments
Is this property meant to link names or objects? I.e. ABQM level 2 will have Node objects reflecting individual workers and then CompositeNode object reflecting sites where those are? If it is that the more likely solution is that we need a new relationship type. Please let me know @kthare10 |
ABQM level 2 has two kinds of nodes:
Need a way to traverse both sites as well as workers within each. Agree that having an additional relationship would help. For now, I have the following hack:
|
So having looked at ABQM code, I'm not sure we can do much better than what we have. If we add a new relationship type to connect worker Nodes to site CompositeNodes you are still left with using get_first_neighbor() to get them. A property on a graph has to have a simple type, so we can add a property 'Children' (or similar) that will be a list of names of worker nodes, but I'm not sure it gives you anything on top of what you already have (?) When you say 'traverse', which direction are you traversing in? From CompositeNode of the site down to worker nodes or vice versa? |
Composite node to worker nodes, I think just encapsulating the above code snipped in |
…urns a dictionary of Node objects attached via has relationship
There is now a
|
Add
nodes
property toCompositeNode
infim/user/compsite_node.py
to list all the worker nodes embedded inside a composite node. This is needed for ABQM with level=2.The text was updated successfully, but these errors were encountered: