Thursday, January 19, 2012

[ns] problem with - setdest - command

Hi people,

I will be really grateful if someone can help me with the
setdest command,

SCENARIO:
I am trying to use a Manhattan scenario using these
mobility generators: bonnmotion2.0 and IMPORTANT.
I am testing a clustering algorithm with mobile nodes that
broadcast packets every 2 seconds.

PROBLEM:
Every time that i run the simulation it stops before it
should, giving not any outcome or exception.
Nodes are moving withing the area defined, no segmentation
faults.

WHAT I FOUND OUT:
I think that this happens because sometimes there is a
"setdest" command that changes the destination of a node
before this node reaches its current destination.

Is there any way to change the setdest to allow this?
Or should I look for other generators?
btw, has someone worked with this before and can recommend
me a good generator for Manhattan Scenario?

EXAMPLE:

this does not work:

$ns_ at 194.2469962641935 "$node_(0) setdest 110.0 10.0
0.8914828790957766"
$ns_ at 201.98659742338714 "$node_(0) setdest
133.10027807554906 10.0 0.8914828790957625"

but, if i increase the trillionth decimal
(201.98659742338--7--14 for 201.98659742338--8--14) then
it works well :S

Very thanks!

No comments:

Post a Comment

Counter

blogger analytics