hsc-coop wrote:Unfortunately, the name is not really used for much in this method -
> Thanks for all the input, the problem that I have is not nodes in the
> same network but rather in different networks. For example I have a
> gene in 2 networks, in one I want it to be a primary node and in
> another a secondary node. If I want to use vizmapper to color the node
> according to whether is is primary or secondary it must be mapped to an
> attribute. But this value must be different for the gene in the 2
> networks since it is primary in one and secondary in the other. This
> was solved by giving a unique identifier and changing the canonicalName
> which I believe is what the label is mapped to currently.
> Now, I have come across a similar problem. My program creates a network
> So far I have mostly worked with the NodeViews so the problems have not
> I tried using:
this needs to be fixed in a future version. The way to force a
different edge is to set a different interaction_type e.g. pp1, pp2,
etc. A general solution to this would be to create network specific
attributes, but that might not happen for a while, so this is the best
workaround right now.
Hope that helps,
> Any ideas for getting around this? I was thinking I would need to
> iterate through the nodes/edges in my original networks and then create
> nodes with unqiue names that have the same attributes and graph index.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.