Bug 1705 – ns2-mobility-helper.cc found to behave absurdly

Bug 1705 - ns2-mobility-helper.cc found to behave absurdly


Summary:	ns2-mobility-helper.cc found to behave absurdly

Status:	NEW

Product:	ns-3
Classification:	Unclassified
Component:	mobility models
Version:	ns-3.17
Hardware:	PC Linux

Importance:	P5 major
Assigned To:	Pavel Boyko

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-06-18 00:23 EDT by gaurav jain
Modified:	2013-07-05 15:46 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
this is the .cc file (8.12 KB, text/x-c++src) 2013-06-18 00:23 EDT, gaurav jain	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description gaurav jain 2013-06-18 00:23:03 EDT

Created attachment 1616 [details]
this is the .cc file

While working with ns2-mobiliyt-helper, I noticed something very absurd in its behavior. The ns2-mobility-trace.cc file has this line :
       
      ns2.Install();
// the install function over here calls Install(begin(),end()) which has a call to ConfigNodesMovement() in ns2-mobility-helper.cc

on debugging it with gdb, it came to light that once the install method is called, all the destinations for each node is calculated and the method runs till the end of .tcl file. So we call the Install() method and create a server-client application on any two different nodes, the block executes, all the nodes reach their final destinations even before the client-server communication begins.

I am attaching a .cc file and a .tcl file. Please let me know if it is actually some error on my part. I followed the example given in ns3 documentation.

Comment 1 Mitch Watrous 2013-07-05 15:46:32 EDT

Can you please attach the ns2 mobility trace file you used, mobility.tcl?

If the events in the ns2 mobility trace file happen before the client-server relationship is set up, you will have to change the times for the client and the server to match times in your trace file.