Bug 145 - waypoint list mobility model
waypoint list mobility model
Status: RESOLVED INVALID
Product: ns-3
Classification: Unclassified
Component: network
pre-release
All All
: P3 enhancement
Assigned To: ns-bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-03 06:32 UTC by Gustavo J. A. M. Carneiro
Modified: 2008-04-15 16:34 UTC (History)
0 users

See Also:


Attachments
patch (11.54 KB, patch)
2008-03-03 06:32 UTC, Gustavo J. A. M. Carneiro
Details | Diff
patch v2 (fixes bad copy-paste of copyright) (11.56 KB, patch)
2008-03-03 06:39 UTC, Gustavo J. A. M. Carneiro
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo J. A. M. Carneiro 2008-03-03 06:32:30 UTC
I made a new "waypoint list" mobility model, to help a student working with NS-3.  It's similar to the random waypoint model, but in this case the waypoints are deterministic and taken from a list given by the programmer.  Let me know if there is interest in including this model in ns-3-dev.
Comment 1 Gustavo J. A. M. Carneiro 2008-03-03 06:32:52 UTC
Created attachment 113 [details]
patch
Comment 2 Gustavo J. A. M. Carneiro 2008-03-03 06:39:51 UTC
Created attachment 114 [details]
patch v2 (fixes bad copy-paste of copyright)
Comment 3 Mathieu Lacage 2008-04-15 12:44:11 UTC
I wonder if this patch is superseded by the current src/mobility/position-allocator.h code, more specifically: ListPositionAllocator.

If so, can you confirm so I can close this bug as INVALID ?
Comment 4 Gustavo J. A. M. Carneiro 2008-04-15 15:16:03 UTC
(In reply to comment #3)
> I wonder if this patch is superseded by the current
> src/mobility/position-allocator.h code, more specifically:
> ListPositionAllocator.
> 
> If so, can you confirm so I can close this bug as INVALID ?
> 

Correct me if I'm wrong, but I think ListPositionAllocator is used to assign preset positions from a list to _different nodes_.  WaypointListMobilityModel has a list of positions through which a single node has to travel.

So, no, I don't think they overlap. 
Comment 5 Mathieu Lacage 2008-04-15 15:47:15 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > I wonder if this patch is superseded by the current
> > src/mobility/position-allocator.h code, more specifically:
> > ListPositionAllocator.
> > 
> > If so, can you confirm so I can close this bug as INVALID ?
> > 
> 
> Correct me if I'm wrong, but I think ListPositionAllocator is used to assign
> preset positions from a list to _different nodes_.  WaypointListMobilityModel

yes.

> has a list of positions through which a single node has to travel.

But RandomWaypointMobilityModel now uses another PositionAllocator object to allocate each destination position.
Comment 6 Gustavo J. A. M. Carneiro 2008-04-15 16:29:10 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > I wonder if this patch is superseded by the current
> > > src/mobility/position-allocator.h code, more specifically:
> > > ListPositionAllocator.
> > > 
> > > If so, can you confirm so I can close this bug as INVALID ?
> > > 
> > 
> > Correct me if I'm wrong, but I think ListPositionAllocator is used to assign
> > preset positions from a list to _different nodes_.  WaypointListMobilityModel
> 
> yes.
> 
> > has a list of positions through which a single node has to travel.
> 
> But RandomWaypointMobilityModel now uses another PositionAllocator object to
> allocate each destination position.

Hmm... OK.  Then RandomWaypointMobilityModel becomes a misnomer, since it may not be random at all :)

But, yes, in this case, which is news to me, WaypointListMobilityModel becomes redundant.
Comment 7 Mathieu Lacage 2008-04-15 16:34:44 UTC
(In reply to comment #6)
> > But RandomWaypointMobilityModel now uses another PositionAllocator object to
> > allocate each destination position.
> 
> Hmm... OK.  Then RandomWaypointMobilityModel becomes a misnomer, since it may
> not be random at all :)
> 
> But, yes, in this case, which is news to me, WaypointListMobilityModel becomes
> redundant.


marking INVALID then.