Bug 1301

Summary:	Ns2MobilityHelper causes Node GetPosition() to return NaN
Product:	ns-3	Reporter:	Nicholas Loulloudes <loulloudes.n>
Component:	mobility models	Assignee:	Pavel Boyko <boyko>
Status:	VERIFIED FIXED
Severity:	major	CC:	andreev, ns-bugs
Priority:	P5
Version:	ns-3.11
Hardware:	Other
OS:	Linux
Attachments:	Compressed Mobilty traces generated by SUMO

Description Nicholas Loulloudes 2011-11-22 06:09:27 UTC

Hi all, 

I am using mobility traces in NS2 format generated from SUMO (0.13.0) for some VANET simulations I am performing.

While the simulations are running I get the following exception from the propagation-loss model:

distance >= 0", file=../src/propagation/model/propagation-loss-model.cc, line=643
terminate called without an active exception

I tracked it down via debug and it is because the MobilityModel::GetPosition () of a node returns NaN.

I am attaching the mobility trace file generated by SUMO (to be more specific generated by traceExporter tool in SUMO), in order to reproduce the bug.

The exception takes place around simulation time 132s

Comment 1 Nicholas Loulloudes 2011-11-22 06:11:46 UTC

Created attachment 1273 [details]
Compressed Mobilty traces generated by SUMO

Comment 2 Kirill Andreev 2011-12-12 06:50:36 UTC

(In reply to comment #0)


Hi!
> Hi all, 
> 
> I am using mobility traces in NS2 format generated from SUMO (0.13.0) for some
> VANET simulations I am performing.
> 
> While the simulations are running I get the following exception from the
> propagation-loss model:
> 
> distance >= 0", file=../src/propagation/model/propagation-loss-model.cc,
> line=643
> terminate called without an active exception
> 
> I tracked it down via debug and it is because the MobilityModel::GetPosition ()
> of a node returns NaN.

This bug can not be reproduced now and can be reproduced with earlier versions of ns-3-dev.
This problem seems to be fixed here:
https://www.nsnam.org/bugzilla/﷒0﷓

Please, check that you have no problem with the latest ns-3-dev or apply the patch provided in 1219 fix
> 
> I am attaching the mobility trace file generated by SUMO (to be more specific
> generated by traceExporter tool in SUMO), in order to reproduce the bug.
> 
> The exception takes place around simulation time 132s

Comment 3 Kirill Andreev 2011-12-14 11:02:07 UTC

Changeset 3da1c746cb06