-
Notifications
You must be signed in to change notification settings - Fork 399
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
Selecting a directed edge #68
Comments
We don't have bidirectional connections so this isn't a use case we have thought about. Would definitely welcome a PR for something like this though! |
My use case involves bi-directional data flow. Vizceral out of the box will show particles traveling in both directions simultaneously. It is subtle to see the particles flying in both directions if one direction has a significantly higher volume than the other with respect to the If you want to prove to yourself that both directions are flowing/producing particles change the metric of one direction to something different so that the particles will have different colors, e.g. "connections": [
{"source": "A", "target": "B", "metrics": {"normal": 117}},
{"source": "B", "target": "A", "metrics": {"warning": 12}}
] I would be wary of hiding the traffic on a bi-directional connection. If one direction is so much more important that you would hide the very existence of the reverse flow... do you even need the connection you are willing to hide? |
Again, thank you for the well written response @aSqrd-eSqrd. |
I am unable to find a way to specify the direction when selecting an edge. If there is traffic from A -> B, and also from B -> A, looks like it chooses the direction with more traffic.
How about adding the capability to specify the direction depending upon which half of the edge was clicked?
The text was updated successfully, but these errors were encountered: