manual.txt

These mobility generator tools are used to generate a rich set of mobility scenarios used to evalua

%--------------------------------------------------------------------------------------------------%

%--------------------------------------------------------------------------------------------------%







Appendix A: The format of Checkpoint file for RPGM model



[Format:]

===============================================================

<ini_x0> <ini_y0>

<destination_x1> <destination_y1> <duration_time_t1>

<destination_x2> <destination_y2> <duration_time_t2>

<destination_x3> <destination_y3> <duration_time_t3>

<destination_x4> <destination_y4> <duration_time_t4>

...

...

...

<destination_x(n)> <destination_y(n)> <duration_time_t(n)>

================================================================



Here, <ini_x> and <ini_y> are the initial positions of the group leader at the beginning of simulation.

<destination_x1> and <destination_y1> are the position of the destinations at the next movement, 

<duration_t1> is the time to move from current location (x0,y0) to (x1,y1). 



Similarly, <destination_x2> and <destination_y2> are the position of the destinations of next movement

after it reaches the position (x1,y1), <duration_t2> is the time to move from current location 

(x1,y1) to (x2,y2). 



This procedure is repeated until the simulation is finished. 

 

Please refer to the samples in /rpgm/checkpoint1 and /rpgm/checkpoint2.







%--------------------------------------------------------------------------------------------------%

%--------------------------------------------------------------------------------------------------%







Appendix B: The format of Map file for FW model



[Format:]

=============================================================

FREEWAY

FREEWAY_NUM <total_number_of_freeways>

LANE_NUM <total_number_of_lanes>

LANE_BEGIN <freeway_id> <lane_id_in_this_freeway> <lane_id_in_all_freeway> <direction> <number_of_phases_of_this_lane>

PHASE <phase_id> (<phase_start_x0,phase_start_y0>) (<phase_end_x1,phase_end_y1>) <v_min> <v_max>

PHASE <phase_id> (<phase_start_x1,phase_start_y1>) (<phase_end_x2,phase_end_y2>) <v_min> <v_max>

...

...

LANE_BEGIN <freeway_id> <lane_id_in_this_freeway> <lane_id_in_all_freeway> <direction> <number_of_phases_of_this_lane>

PHASE <phase_id> (<phase_start_x0,phase_start_y0>) (<phase_end_x1,phase_end_y1>) <v_min> <v_max>

PHASE <phase_id> (<phase_start_x1,phase_start_y1>) (<phase_end_x2,phase_end_y2>) <v_min> <v_max>

...

...

LANE_BEGIN <freeway_id> <lane_id_in_this_freeway> <lane_id_in_all_freeway> <direction> <number_of_phases_of_this_lane>

PHASE <phase_id> (<phase_start_x0,phase_start_y0>) (<phase_end_x1,phase_end_y1>) <v_min> <v_max>

PHASE <phase_id> (<phase_start_x1,phase_start_y1>) (<phase_end_x2,phase_end_y2>) <v_min> <v_max>

...

...

==============================================================



In FW model, several freeways co-exist in the simulation field and mobile nodes are moving on 

the lanes of the freeways. For each freeway, it has several lanes in both directions. (certainly,

 users are able to define a freeway with only one direction). Please note, each lane should be 

seperated with other lanes by some distance. That is to say, when design the map file, the lanes 

are not supposed to be overlapping. For each lane which is not necessary to be a straight line, 

so it may have several phases while each phase is a straight line. By connecting several phases 

together, the users are able to define a non-straight freeway in the simulation field.



the map starts with required word 'FREEWAY', then some parameters are placed.

<total_number_of_freeways> is used to define how many freeways exist in the simulation field, 

<total_number_of_lanes> is used to count totally how many lanes exist in the field. 



For each lane, it begins with keyword 'LANE_BEGIN',and then several parameters are listed here,

<freeway_id> is the id of the freeway where this specific lane belongs,

<lane_id_in_this_freeway> is the id of this lane on this freeway,

<lane_id_in_all_freeway> is the id of this lane in the overall simulation field, please note, 

these two parameters are not same. 

<direction> is the direction of this lane. For example, if one direction of a lane is defined 

as positive value 1, then the lane on the opposite direction must be defined as the negative 

value -1. 

<number_of_phases_of_this_lane> represents how many phases this lane has. 



Once the general parameters of the lane has been desribed, the map file will describe the 

parameter for each phase. It starts with keyword 'PHASE', and the meaning of parameters are

described as follow:

<phase_id> is the id of this phase on this lane of this freeway.

<phase_start_x0,phase_start_y0> describes the position of starting points of this phase 

<phase_end_x1,phase_end_y1> describes the position of the ending points of this phase. Please note, 

generally speaking, the starting point of next phase should be the ending point of this phase.

<v_min> <v_max> defines the maximum and minimum allowed velocity on this phase. 



For each lane, several phases are defined. For each freeway, several lanes are defined; For the

whole simulation field, several freeways are defined. 



For more questions, please refer to the samples in directory /fwy/mapset1 and /fwy/mapset2.









%--------------------------------------------------------------------------------------------------%

%--------------------------------------------------------------------------------------------------%





Appendix C: The format of Map file for MH model



[Format:]

=============================================================

MANHATTAN

HOR_STREET_NUM <num_of_horizontal_street>

VER_STREET_NUM <num_of_vertical_street>

LANE_NUM <overall_num_of_lanes>

LANE <street_id> <lane_id> <direction> <start_x0> <start_y0> <end_x0> <end_y0> <total_number_of_crosspoints_in_this_lane> <vmin> <Vmax>

CROSSPOINT <crosspoint_id> <street_id> <lane_id> <direction> <position_x> <position_y>

CROSSPOINT <crosspoint_id> <street_id> <lane_id> <direction> <position_x> <position_y>

...

...

LANE <street_id> <lane_id> <direction> <start_x0> <start_y0> <end_x0> <end_y0> <total_number_of_crosspoints_in_this_lane> <vmin> <Vmax>

CROSSPOINT <crosspoint_id> <street_id> <lane_id> <direction> <position_x> <position_y>

CROSSPOINT <crosspoint_id> <street_id> <lane_id> <direction> <position_x> <position_y>

...

...

LANE <street_id> <lane_id> <direction> <start_x0> <start_y0> <end_x0> <end_y0> <total_number_of_crosspoints_in_this_lane> <vmin> <Vmax>

CROSSPOINT <crosspoint_id> <street_id> <lane_id> <direction> <position_x> <position_y>

CROSSPOINT <crosspoint_id> <street_id> <lane_id> <direction> <position_x> <position_y>

...

...

==============================================================





In MH model, several horizontal and vertical streets co-exist in the simulation field and mobile 

nodes are moving on the lanes of the streets. For each street, it has several lanes in both directions. 

(users can also define a street with only one direction). Please note, each lane should 

be  seperated from other lanes by some distance. That is to say, while designing the map file, 

the lanes are not supposed to overlap. However, the vertical and horizontal streets may 

cross with each other at the crosspoints. At the crosspoints, the mobile nodes are suppose to 

move ahead, turn left or turn right with certain probability.  



Similar to Map file of freeway model, the map file of Manhattan model starts with keyword 

'MANHATTAN'. Then, <num_of_horizontal_street> and <num_of_vertical_street> give the number of

horizontal and vertical streets in the simulation field. 



For each lane street, it starts with the keyword 'LANE', and the meaning of the parameters 

are described as follow:

<street_id> is the id of the street where this lane belongs,

<lane_id> is the unique id of this lane,

<direction> is the direction of this lane, for example, if lane is towards right and up, its value

is 1; otherwise, it is -1,

<start_x0> <start_y0> are the position of the starting point of this lane,

<end_x0> <end_y0> are the position of the ending point of this lane,

<total_number_of_crosspoints_in_this_lane> indicates how many crosspoints exist in this lane,

<vmin> <Vmax> defines the max and min allowed velocity of nodes on this lane. Please note, the 

values here should be consistent with the input parameters. 



For each crosspoint, it starts with keyword 'CROSSPOINT', the parameters are described as 

<crosspoint_id> is the unique id of this crosspoint

<street_id> is the unique id of the street to which this crosspoint belongs

<lane_id> is the unique id of the lane to which this crosspoint belongs

<direction> is the direction of the street to which this crosspoint belongs

<position_x> <position_y> is the exact position of this crosspoint.