55 | | ==== <links> ... </links> ==== |
56 | | The links section defines how many independent sets of connections objects in the simulator may have (eg. multi-homing). It can be thought of in terms of [wiki:foo Sandbox 4] as the number of available attenuator matrices. Each matrix (ie. each link set) is independent of the other. The default attenuation per matrix (link set) is defined in this section and used in cases where maximum attenuation is calculated between a pair of objects or an object pair is not defined. The maximum number of objects per matrix (link set) is also defined here for proper generation of the trace file. |
| 57 | '''<links> ... </links>''' |
| 58 | |
| 59 | The links section defines how many independent sets of connections objects in the simulator may have (eg. multi-homing). It can be thought of in terms of [wiki:foo Sandbox 4] as the number of available attenuator matrices. Each matrix (ie. each link set) is independent of the other. The default attenuation (dB) per matrix (link set) is defined in this section and used in cases where maximum attenuation is calculated between a pair of objects or an object pair is not defined. The maximum number of objects per matrix (link set) is also defined here for proper formatting of the generated trace file. |
| 60 | |
| 61 | {{{ |
| 62 | <objects> |
| 63 | <object name="1" type="Car" id="12"> |
| 64 | <link name="1">2,3</link> |
| 65 | <link name="2">3,4</link> |
| 66 | </object> |
| 67 | <object name="2" type="Bus" id="4"> |
| 68 | <link name="1">5,6</link> |
| 69 | <link name="2">3,5</link> |
| 70 | </object> |
| 71 | |
| 72 | ... |
| 73 | |
| 74 | </objects> |
| 75 | }}} |
| 76 | |
| 77 | '''<objects> ... </objects>''' |
| 78 | |
| 79 | This section defines the objects that the user wishes to track (and generate trace data for). The object "name" is a number used to map the object to the corresponding trace output values. In the case of Sandbox 4... The "type" determines the subset of objects to which the object of interest belongs and the "id" corresponds to the specific object in that subset. |
| 80 | |
| 81 | ||='''Object Type'''=||= '''Valid Id''' =|| |
| 82 | || Building || ''none'' || |
| 83 | || Car || 0 - 404 || |
| 84 | || Bus || 0 - 5 || |
| 85 | || Pedestrian || 0 - 115 || |
| 86 | || Microcell || 0 - 5 || |
| 87 | || Macrocell || 0 - 3 || |
| 88 | || Sensor || 0 - 9 || |
| 89 | |
| 90 | {{{ |
| 91 | <attenuations> |
| 92 | <attn factor="3" type="Bus" /> |
| 93 | <attn factor="2" type="Car" /> |
| 94 | <attn factor="1" type="Building" /> |
| 95 | <attn factor="2" type="Pedestrian" /> |
| 96 | <attn factor="6" type="Antenna" /> |
| 97 | </attenuations> |
| 98 | <sim_parameters max_time="180" time_int="1000" frequency = "100"/> |
| 99 | </config> |
| 100 | }}} |
| 101 | |
| 102 | '''<attenuations> ... </attenuations>''' |
| 103 | |
| 104 | Path loss attenuations of different objects in the simulation are defined here. These are the attenuations of objects obstructing line of sight between the two objects for which the pairwise attenuation is being calculated. These factors are not taken into account for the pair of objects themselves. |
| 105 | |
| 106 | ||= '''Type''' =||='''Description''' =|| |
| 107 | || Bus || Path loss attenuation of a bus || |
| 108 | || Car || Path loss attenuation of a car || |
| 109 | || Building || Path loss attenuation of a building || |
| 110 | || Pedestrian || Path loss attenuation of a pedestrian || |
| 111 | || Antenna || Path loss attenuation of a rooftop antenna || |
| 112 | |
| 113 | '''<sim_parameters> ... </sim_parameters>''' |
| 114 | |
| 115 | This section contains additional trace related simulation parameters. |
| 116 | |
| 117 | ||='''Parameter'''=||='''Description''' =|| |
| 118 | || max_time || Number of seconds to run the simulation || |
| 119 | || time_int || Number of miliseconds between calculating pairwise attenuations || |
| 120 | || frequency || Frequency (in MHz) to use as a baseline for attenuation calculations || |
| 121 | |
| 122 | [[BR]] |
| 123 | === Trace Output CSV File === |
| 124 | |
| 125 | The output trace file generated at the end of a simulation run is formatted in accordance with the requirements of the Instrumentation AM service for trace replay. |