Bug 1314 – mobility helper setting of position allocator does not set the RandomWaypoint position allocator pointer

Bug 1314 - mobility helper setting of position allocator does not set the RandomWaypoint position allocator pointer


Summary:	mobility helper setting of position allocator does not set the RandomWaypoint...

Status:	NEW

Product:	ns-3
Classification:	Unclassified
Component:	mobility models
Version:	pre-release
Hardware:	All All

Importance:	P5 normal
Assigned To:	Pavel Boyko

URL:
Keywords:

Duplicates:	1386 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-12-15 01:20 EST by Tom Henderson
Modified:	2012-04-25 09:11 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
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 Tom Henderson 2011-12-15 01:20:00 EST

From this thread:
http://groups.google.com/group/ns-3-users/browse_thread/thread/7b8c10503103405a

It seems like the user's code ought to work without having to resort to the way that examples/routing/manet-routing-compare does it.

Comment 1 Mathieu Lacage 2012-03-24 10:18:45 EDT

(In reply to comment #0)
> From this thread:
> http://groups.google.com/group/ns-3-users/browse_thread/thread/7b8c10503103405a
> 
> It seems like the user's code ought to work without having to resort to the way
> that examples/routing/manet-routing-compare does it.

Are you saying that it is common for users of a random waypoint model to use the same position allocator model to pick the initial position as well as the waypoints ? If so, I would suggest coming up with a RandomWaypointMobilityHelper class.

Comment 2 Mathieu Lacage 2012-03-24 10:39:03 EDT

*** Bug 1386 has been marked as a duplicate of this bug. ***

Comment 3 Tom Henderson 2012-04-25 09:11:38 EDT

(In reply to comment #1)
> (In reply to comment #0)
> > From this thread:
> > http://groups.google.com/group/ns-3-users/browse_thread/thread/7b8c10503103405a
> > 
> > It seems like the user's code ought to work without having to resort to the way
> > that examples/routing/manet-routing-compare does it.
> 
> Are you saying that it is common for users of a random waypoint model to use
> the same position allocator model to pick the initial position as well as the
> waypoints ? If so, I would suggest coming up with a
> RandomWaypointMobilityHelper class.


I'm saying (for now) that it is not intuitive that the random waypoint behaves slightly differently and requires different API calls than the other mobility models when using the helper.

There is a separate issue that we have discussed in the context of the random number generators that embedding a position allocator within the mobility helper is difficult to set its streams, and you mentioned to consider to decouple the position allocator from the mobility helper.  That may help with this as well.