(Boeing r1758)
update user manual with text on distributed controlnets; replace PER with Loss; add note about UTM zones
This commit is contained in:
parent
898a8c6c76
commit
5bda784128
2 changed files with 85 additions and 11 deletions
|
@ -184,6 +184,19 @@ is running generates location events for EMANE. To view or change the
|
|||
geographic location or scale of the canvas use the *Canvas Size and Scale*
|
||||
dialog available from the *Canvas* menu.
|
||||
|
||||
.. index:: UTM zones
|
||||
|
||||
.. index:: UTM projection
|
||||
|
||||
Note that conversion between geographic and Cartesian
|
||||
coordinate systems is done using UTM
|
||||
(Universal Transverse Mercator) projection, where
|
||||
different zones of 6 degree longitude bands are defined.
|
||||
The location events generated by
|
||||
CORE may become inaccurate near the zone boundaries for very large scenarios
|
||||
that span multiple UTM zones. It is recommended that EMANE location scripts
|
||||
be used to achieve geo-location accuracy in this situation.
|
||||
|
||||
Clicking the green *Start* button launches the emulation and causes TAP
|
||||
devices to be created in the virtual nodes that are linked to the EMANE WLAN.
|
||||
These devices appear with interface names such as eth0, eth1, etc. The EMANE
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue