Read and respond to this message at:
It now seems clear that you have three different networks defined on the same
set of individuals. This could get into a long discussion, but depending on
what you want to do, there are a few different ways that you could represent
Some preliminary notes/questions:
* Are you _analyzing_ (calculating distances, clustering, ranking, etc.) this
network, _visualizing_ it, or both? The answer to this question will influence
how you want to represent the data. Hopefully considering this question will
clear up the "little doubt" you mentioned at the end of your post: when I talk
about "algorithms", I usually am referring to methods for analysis rather than
* I hope that this discussion will help you, and other JUNG users, to understand
the importance of clearly stating your requirements and the context for your
problem. This whole issue does not, in my opinion, really have much to do with
arrowheads at all--it's larger than that--and the edges themselves are not changing
at all, which is the impression that I'd received earlier. This post to which
I'm replying, however, is a good example of how to let us know what you're trying
Some options for representation include:
(1) A single graph in which each edge is 'tagged' with its variable (in user
data or elsewhere, it doesn't matter). You can use the built-in subset support
(see PredicateUtils and SubsetManager) to maintain an edge set for each variable,
but this is not required.
If you just want to visualize the network, one relation (var1, var2, or var3)
at a time, this is probably easiest; you would supply an edge display predicate
that would allow the user to specify which relation they wanted to see. This
may also be best if you want to analyze the network in ways that use all relations,
rather than considering just one relation at a time.
(2) Create a separate graph for each relation. Then if you want to view a different
relation, you just visualize the appropriate network. If you want to analyze
the network one relation at a time, this may be best.
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: