Comment 7 for bug 713617

Hi Dimitris,

Thanks for the info. If I remember correctly in my case the edge all had
the same weight so it wouldn't matter which one you took. But I agree that
in the general case it is not obvious. I think that as you said it is an
edge case (pun intended) and you could simply print an error or warning
message saying that there are duplicate edges and let the user decide how
to fix the graph.

Cheers,

Tom

On Mon, Sep 1, 2014 at 3:10 PM, Dimitris Kalamaras <
<email address hidden>> wrote:

> FWIW for such an old bug report, the problem didn't have anything to do
> with Edge::makeReciprocal(). Rather, it was that the metro.xml declared
> multiple edges between nodes. For instance, the edge 15->16 is
> declared twice, first in line 316 (edge id "15 M1") and then again in
> line 391 (edge id "87 M11"). SocNetV up to version 1.3 does not support
> multiple edges between nodes. And if wee need to support that feature
> there would be problems such as: when we would need to create and
> display the adjacency sociomatrix (or count distances) what value should
> we use in the (15,16) element? The weight of the first edge (id "15 M1")
> or the weight of the other edge (id "87 M11") ? The only thing I can do
> at the moment is to catch these exceptions and silently unifying the
> multiple edges to a single edge...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/713617
>
> Title:
> Segmentation fault when loading GraphML file
>
> Status in Social Networks Visualizer:
> In Progress
> Status in SocNetV 1.x series:
> In Progress
>
> Bug description:
> Hi,
>
> The segmentation fault seems to occur in Edge::makeReciprocal(). It's
> not the first call to that method and I don't see anything special
> with that edge. Maybe I am missing something.
>
> Cheers,
>
> Tom
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/socnetv/+bug/713617/+subscriptions
>