Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
EDITION 1
Your feedback is important to us: The TEOCO Documentation team takes many measures
in order to ensure that our work is of the highest quality.
If you found errors or feel that information is missing, please send your Documentationrelated feedback to Documentation@teoco.com
Thank you,
The TEOCO Documentation team
CONTENTS
INSTALLING MYRIAD MODEL WITH ASSET .................................................. 7
INSTALLATION ............................................................................................................................... 8
REMOVAL ......................................................................................................................................... 9
LICENCE MANAGEMENT ........................................................................................................... 10
Stand-alone License ..................................................................................................................... 10
Server floating license ................................................................................................................. 11
Borrowing floating license .......................................................................................................... 12
DISTRIBUTED PREDICTION ...................................................................................................... 15
Configuration ............................................................................................................................... 15
MYRIAD Model licenses ............................................................................................................ 15
Workstation machine configuration ......................................................................................... 15
Client machine configuration ..................................................................................................... 16
EXPORT AND IMPORT ................................................................................................................ 17
Export ............................................................................................................................................ 17
Import ............................................................................................................................................ 17
Page 5
Page 6
CHAPTER 1
In This Section
INSTALLING MYRIAD MODEL WITH ASSET .................................................. 7
INSTALLATION ............................................................................................................................... 8
REMOVAL ......................................................................................................................................... 9
LICENCE MANAGEMENT ........................................................................................................... 10
Standalone License ...................................................................................................................... 10
Server floating license ................................................................................................................. 11
Borrowing floating license .......................................................................................................... 12
DISTRIBUTED PREDICTION ...................................................................................................... 15
Configuration ............................................................................................................................... 15
MYRIAD Model licenses ............................................................................................................ 15
Workstation machine configuration ......................................................................................... 15
Client machine configuration ..................................................................................................... 16
EXPORT AND IMPORT ................................................................................................................ 17
Export ............................................................................................................................................ 17
Import ............................................................................................................................................ 17
Page 7
INSTALLATION
Launching the installer opens the following dialogue boxes:
WARNING: From this version, MYRIAD Models license server has to be run with
the Flexlm tools version 11.13 (they are installed via the setup in the folder MYRIAD
Model\MYRIAD Model430_x.x\License Manager\flexnet). Previous versions of
MYRIAD Model should be compatible with Flexlm tools v11.13, meaning that users
can run a license server with Flexlm tools v11.13 and use it with all versions of
MYRIAD Model (430 and previous ones).
Page 8
REMOVAL
You remove the MYRIAD model in the same way as other programs. From the Start
menu, select Control Panel => Add or Remove Programs.
Note: It is recommended to close ASSET during the removal of a model and to stop
the services "Distributed Predictions Agent Service".
Page 9
LICENCE MANAGEMENT
MYRIAD Model uses a software-based security system, which requires that you have
a valid license on your workstation. This requirement prevents unauthorized use of
the software. Two types of license are available:
Stand-alone license
A stand-alone license enables you to use MYRIAD Model on a single specific
workstation (as identified by that workstations MAC address). A stand-alone license
is the best option if you plan to use MYRIAD Model on only one workstation for
independent projects with no multi-user collaboration. No separate license server
needs to be installed, and no network connection is required. When you purchase a
MYRIAD Model stand-alone license, you are provided with a license file (.lic). You
must ensure that this file has a specific name (MYRIAD_Model.lic) and is placed in
the MYRIAD Model installation directory.
Note: a standalone license is not compatible whether you are logged on to a server or
whether you use a remote connection.
Floating license
A floating license enables a predefined number of users to use MYRIAD Model.
When a user starts MYRIAD Model on a workstation, a license is automatically
requested from a license server that has been configured by an administrator. If there
are available licenses, the user is assigned a license and can use MYRIAD Model.
However, when there are no more licenses available, further users will be unable to
use MYRIAD Model. Unlike a stand-alone license, a floating license is not restricted
to a specific workstation. However, a network connection is required between the
workstation of the user requesting MYRIAD Model license and the license server.
Borrowing a floating license If you want to use MYRIAD Model when you are
disconnected from the network, you can borrow (i.e., check out) a floating license for
a limited amount of time. This can be useful, for example, if you are travelling, or are
in the field, and you do not have access to the MYRIAD Model license server. Once
you have successfully borrowed a license, you can use MYRIAD Model until the
borrowing period expires.
Stand-alone License
Workflow for using MYRIAD Model with a stand-alone license
Step 1: Install MYRIAD Model on the workstation.
Step 2: Configure the stand-alone licence
Configuring Stand-alone Licenses
If you are using a stand-alone license, after you install MYRIAD Model on
your workstation, you must ensure that your license is properly configured.
Ensure that the .lic file that you were sent after purchasing your copy of the
MYRIAD Model is in the MYRIAD Model installation directory. If necessary,
copy the .lic file to that folder.
Ensure that the .lic file is named MYRIAD_Model.lic If necessary, rename
the .lic file.
Page 10
You must use the tools in the License Manager folder (in MYRIAD Model
install directory).
Double-click lmtools.exe. The LMTools dialogue box opens.
Page 11
An administrator can use the debug log file to view the reason why a user cannot get
a license (e.g., no license, licensed expired, licensed number of users already reached).
Note: On the machine which hosts the license server, in the firewall exceptions, you
must add and enable the two executables files, LICPIFT.exe and lmgrd.exe, used by
the license server.
Page 12
Page 13
In the User Variables for the given user name section, click New.
In the New User Variable dialogue box, enter LM_LICENSE_FILEin the
Variable Name box.
In the Variable Value box, enter the path of the MYRIAD_Model.lic file in the
MYRIAD Model installation directory and click OK.
Page 14
DISTRIBUTED PREDICTION
MYRIAD Model uses ASSETs distributed calculation server to run simultaneous
predictions in order to reduce computation time.
You have the possibility of running simultaneous predictions on several machines
and can use all processors or cores of these machines (for example, if you have two
machines with two cores or processors, you can run four threads (one per prediction)
at the same time).
Please contact ASSET product support for distributed prediction licensing.
To use ASSETs distributed calculation server, you need:
a workstation with ASSET and MYRIAD Model (the ASSET coordinator has
to be configured on this machine)
one or several client machines running ASSETs Agent and MYRIAD Model
Configuration
First of all, the ASSET administrator has to enable the distributed prediction option
in the user profile settings.
To use ASSETs distributed calculation server with MYRIAD Model, you must set all
file paths in the MYRIAD Model settings to UNC mode (i.e., the network path).
Page 15
More information is available in the ASSET online help and/or in the ASSET
documentation.
Note: due to the MYRIAD Model licence system, it is not possible to run
simultaneously two different versions in a multithreads/multi-machines context.
Page 16
Export
Click the Export button to export the settings of the propagation model
Import
Click the Import button to import the settings of another propagation model. Both
possibilities:
You can directly import the export of another MYRIAD propagation model. If
both versions are not equivalent, parameters which were not defined in the
imported version will be automatically set to their default values
You can import the file MODEL-LIST001.xml which was beforehand exported
from ASSET. In this case, the list of MYRIAD Model available in the project
and compatible with this option appears and you have the possibility to
import one of them (this option is compatible from MYRIAD Model v390). If
both versions are not equivalent, parameters which were not defined in the
imported version will be automatically set to their default values
Note: it is recommended to check the clutter settings after having imported a model,
especially if the source project does not contain the same clutter themes as the target
project.
Page 17
Page 18
CHAPTER 2
Page 19
CONTEXT
In the current context of the growth of mobile telecommunication networks,
operators face innumerable technical and economic problems during the planning,
deployment, and optimization phases of mobile radio networks. To address these
issues, operators use dedicated engineering tools that offer solutions to problems
such as the calculation of coverage, determining hand-over zones, interference,
frequency allocation, antenna optimization, traffic localization, and so on.
Among the most indispensable tools for mobile radio engineering are the field
prediction models. Also called wave propagation models, they are incorporated in
engineering tools and allow mobile radio network creators to determine the coverage
zones of emitting stations and, in turn, infer the interference zones. Providing the
indispensable information to numerous tools for further treatment and exploiting the
predicted fields, they occupy a privileged place in cellular engineering.
Strongly dependent on geographic data that allow the extraction of a vertical crosssection of the terrain (called a profile), a propagation model is a mathematical
simulation of a physical phenomenon between two points. Performing preliminary
processing of the cross-section of the terrain in order to check the calculation
hypotheses, the propagation model combines theory with profile information before
statistically adjusting the results using field measurements.
Programmable according to different needs, a propagation model is developed with
for objective to always respect significant constraints in domains such as: speed,
precision, strength, and versatility.
Page 20
Figure 10: Reflection + diffraction + guided propagation = the MYRIAD Model trilogy
Page 21
The first operation, then, consists of elaborating the profile from the vectors
geographical data or raster geographic data representing the surface (clutter and/or
building raster) and the raster geographic data of the relief (height).
The solution chosen to construct the diffraction profile with the vectors geographic
data is to add the profile of the heights of the vectors to the altitude profile taken
from the height as follows:
For a building contour, the diffraction profile consists of ridges of equal
heights. All the height ridges supporting the buildings, modified so that the
buildings rooftop stays flat, are increased to the height of the building. The
profile is then completed with the two ridges framing the building.
For a forest contour, the diffraction profile is formed from the height ridges
under the forest contour to which the height of the contour is added. The
profile is then completed with the two frame ridges of the contour where the
height portion is determined by interpolation.
Page 22
Once the profile is obtained so that the diffraction loss is not over-estimated, it is best
to delete certain diffraction edges; therefore every diffraction edge less than one
hundred meters away from a positive or negative diffraction edge is deleted. This
means that a succession of diffraction edges that are so close to each other that they
in fact represent only one ridge is not taken into consideration.
Deygouts method is chosen to calculate the diffraction loss. The model also
calculates different variables related to the profile. The loss of the profile component
results in a linear combination of these variables for which the coefficients are
determined by adjusting the smallest squares with the calibration tool.
Page 23
points of the vertical planes (or the horizontal planes if >=45) passing through the
centre of the pixels with the transmitter-receiver segment. The height of each ridge is
equal to the height of the bin containing the point of intersection.
Pixels
Profile extract
E
X
E
R
P2
P1
P2
P0
P2
P1
P2
E
3
2
4
1
6
5
7
Ordre
de lobtension
despositive
artesedges
engages
positives
Figure
16: Order
of obtaining the
committed
Page 25
Page 26
Page 27
Page 28
When the antenna is well under the rooftops, the electro-magnetic propagation
occurs principally along the streets which act as street canyons. There is a guiding
phenomenon of the electro-magnetic waves by the street which implies that the
major propagation phenomena are situated in the horizontal plane and no longer the
vertical plane, as is the case with the profile models. Thus, we benefit from the
canalization effect to increase propagation.
To model this guiding phenomenon of the electro-magnetic waves by the streets, the
model uses a graph of the street axes. A graph is formed by arcs representing the
axes of the streets capable of acting as a wave guide.
Page 29
Searching the graphs is done using the graphs index parameter in which are defined
the files that contain the relative information used to model the route maintenance.
Page 30
Transmitter
Receiver
Best path considered for the
graphs component
Paths considered by the
graphs component
Figure 20: Examples of paths for the graphs component
The profile loss is calculated and is added to the graphs component loss to form the
total loss of the MYRIAD Model.
Page 31
Page 32
CHAPTER 3
In This Section
CONFIGURING MYRIAD MODEL WITH ASSET ............................................ 33
THE PARAMETERS TAB ........................................................................................................... 34
General parameters ..................................................................................................................... 34
Geographical data ........................................................................................................................ 35
Output directory .......................................................................................................................... 37
THE TIME OPTIM TAB .............................................................................................................. 38
Prediction parameters ................................................................................................................. 38
Radial............................................................................................................................................. 39
Inner/Outer area resolution ....................................................................................................... 40
Optimized calculation area ........................................................................................................ 41
THE RADIO TAB.......................................................................................................................... 42
Radio optimization ...................................................................................................................... 42
Typologies effects ........................................................................................................................ 44
Depenetration ............................................................................................................................... 44
Building calculation..................................................................................................................... 45
Computed data ............................................................................................................................ 48
THE ADVANCED TAB ................................................................................................................ 51
Key features .................................................................................................................................. 51
Train option .................................................................................................................................. 53
Page 33
In this window, you can check the MYRIAD Model parameters which are:
General parameters
In this section, you can define the frequency and the mobile height.
The frequency, two possibilities:
If you select the Use antenna frequency
checkbox, the model uses the frequency
defined for the antenna (except if the
antenna is not defined or if the antenna
frequency is set to 0)
The default frequency is used when Use
antenna frequency is not selected and/or
when the antenna is not defined (unassociated measurements for example)
Page 34
Geographical data
In this section, you select the geographical data you want to use. There are four
options:
Heights: this type of data is compulsory for the model.
Building raster
Clutter: If you select this type of data, the Clutter settings assignment
window appears:
In this window, the list of clutter classes appears. You must determine whether the
clutter is a Building type (this information is used for the Buildings calculation
option), Water type (this information is used for the maritime optimization), a Forest
type (this information is used for the forest optimization) or an Undefined type
(meaning there is no data). You also have to indicate the height information and the
buildings calculation losses for Building class(es). In most cases, the clutters have a
default height value which is an example; it is recommended to check that each value
corresponds to the project reality.
Note: All the themes contained in the clutter file(s) have to be referenced in the
clutter description file (including No_data)
For raster geographical data, you have other options
Page 35
If you did not select the Use advanced accuracy checkbox, the model uses less
detailed calculations in order to decrease processing time. Otherwise, the model
exploits the accuracy of the geographical data with the goal of generating more exact
output.
If you have selected Use highest resolution checkbox, the model uses the highest
resolution available. Otherwise, the model uses the resolution closest to the
prediction resolution.
If there is no surface data (neither vectors, nor clutter and nor building raster), you
can set an average surface height using the Clutter height parameter.
Vectors: If you select this type of data, the Vectors type assignment window
appears:
In this window, the list of vectors names appears. You must determine
whether the vector is a BUILDING type, a FOREST type, a WATER type, a
BRIDGE type or an UNDEFINED type. This configuration creates or
modifies a file, named 'menu.xml', containing vectors type specifications in
the same directory as the vectors index file.
This feature use the attribute NAME of tag VECTOR in the "index.xml" file to
determine the vector name. The vectors files which are under the same tag VECTOR
must have a single type of vector.
This feature also generates a file "indexOptim.xml" which optimizes the vectors
access and so improves the calculation time (this file is not compulsory for the
model).
If MYRIAD Model encounters a vector description that is not defined in the menu.xml
file while loading the vectors index file, you are informed of the issue and the
UNDEFINED type is assigned to the corresponding geographic data file.
Page 36
If the menu.xml file contains non standard MYRIAD Model vector type, you are
informed of the issue and geographic data file relating to that unknown vector type
is assigned an UNDEFINED type.
If the vectors index file was updated, you are informed of the issue and you have to
update files "menu.xml" (and "indexOptim.xml") with the settings.
Output directory
In this section, you have to select a writing directory (required by the model). This
directory hosts the file MYRIAD_LOG.txt which contains all the messages returned
by the model. It is also used to store temporary files and specific propagation files
which can be re-used by the model in multi sectors context (under certain conditions)
to decrease the computation time. The number of temporary files is limited to 100.
Page 37
Prediction parameters
In this section, you have the possibility to set the resolution of the calculation.
If you select the radio button Use
pathloss prediction manager resolution,
the model uses the prediction resolution
If you select the radio button Userdefined resolution, the model always
uses the resolution defined in the
associated field (100 meters in this
example).
Note: the calculation resolution of the model has to be superior to the one of the
platform.
The Circular calculation areas parameter allows you to indicate whether the model
has to consider the calculation areas as circular areas.
Page 38
Radial
The Use Radial mode parameter allows you to activate radial calculation. During a
coverage calculation, this mode allows you to reuse a profile extracted on the
perimeter of the calculation area, approximating for the distance. The radial mode is
approximately three times as efficient. In fact, in a square calculation zone of n pixels
long, in normal mode n profiles are extracted, while in radial mode only 4n-4
profiles are extracted.
Radial mode works as follows:
- MYRIAD Model associates a profile at several points (depending of the
resolution) of the calculation area perimeter, while determining the closest
profile by orthogonal projection
- MYRIAD Model extracts the first profile of the perimeter and uses it for each
calculation point along the profile, and so on
In the diagram below, the resolution corresponds to the transmitter resolution.
Profile A
dA
dB
Profile B
Transmitter
Extraction point of the profiles
Profiles of the perimeter of the calculation area
Calculation point
Orthogonal projections
Figure 26: MYRIAD Model - Radial mode
You can define the extraction resolution (in meters) of the profiles on the perimeter of
the calculation area when you use radial mode.
If you select Use calculation radial
resolution, the model uses the
calculation resolution
If you select User-defined radial
resolution is activated, the model uses
resolution you define (100 meters in
this example)
Note: If the User-defined radial resolution is greater than the transmitter resolution,
the transmitter resolution is used.
Page 39
Page 40
If you select Automatic backwards distance, the model automatically adjusts the
value of the recoil distance, starting from which the model no longer calculates
behind the transmitter. Limited to 30% of the distance along the azimuth, it is used
by the model as described in the following equation:
20 log( DIST _ AZIM ) ADIR _ MIN
ln(10)
20
Recoil distance = e
Where:
- Recoil distance: The maximal distance calculated behind the station at 30% of the
distance along the azimuth
- DIST_AZIM: The distance between the transmitter and the edge of the influence
area according to the direction of the azimuth
- ADIR_MIN: The smallest directional loss of the antenna behind the station.
Calculated pixels
Non calculated pixels
Boundary of the zone to be calculated
Azimuth
DIST_AZIM
Recoil distance
If you select User-defined backwards distance, the model uses the defined recoil
distance (50 meters in this example) starting from which it no longer calculates
behind the transmitter.
Note: This distance is limited to 30% of the distance along the azimuth
Page 41
Radio optimization
The Loss correction parameter indicates the value of the correction (in dB, 0 by
default) to add to the total loss of the model.
For example, Loss correction = 3dB means 3dB more loss.
Note: this parameter does not affect the tuning.
The Additional extraction distance parameter indicates the additional extraction
distance (in meters, 0 by default, the value must be contained in the interval [0-300])
of vectors above the receiver (to the right of the receiver on the cross-section of
terrain). This parameter is only available if vectors are available.
The Graphs extraction radius parameter indicates the distance (in meters, 1500 by
default, the value must be contained in the interval [0-2000]) beyond which the
graphs component is no longer used. This parameter is only available if graphs are
available.
The Free space in line of sight parameter indicates the maximal distance to apply
free space attenuation for pixels that are in Line Of Sight of the transmitter without
taking into account any model calibration. This can be useful when calculation
resolution is low and especially when receivers are fixed like in Machine to Machine.
Page 42
The Calculate on water parameter allows you to indicate whether the model should
calculate on water.
The Horizontal propagation parameter allows you to activate or deactivate
horizontal propagation. If activated, when the models finds an obstacle between the
transmitter and the receiver, if the height of this obstacle is greater than the smallest
apparent width of it, then the height is replaced by the apparent width on the profile.
The purpose of this is to avoid taking into account the diffraction on the top of the
obstacle in the calculations carried out when the electro-magnetic field is mainly
diffracted on the side of the obstacle.
In the above example, if the height is greater than the right apparent width (to the
right of the Transmitter-Receiver axis when looking at the receiver), then this height
is replaced by the right apparent width.
The Used weighted tuning coefficients parameter allows you to use a weighting
between tuning coefficients used for vectors and for raster data (included in case of
default tuning); this weighting will take into account the distance crossed over
vectors and raster data.
In the example below, both tuning coefficients are taken into account after weighting
them according to the distance over each area type.
Vectors
Page 43
The Use clutter type parameter allows you, in case of forest/maritime optimization
or building calculation, to indicate to the model to retrieve the clutter classes
information in case of building raster data. In others words, Clutter types, which
have to be configured in the Clutter settings assignment window, allow the model
to determine if building raster data is located in building/forest/water area. Any
building raster located within pixels of such clutter classes will be considered as
building/forest/water.
Note: For vectors, the model uses the parameters BUILDINGS, FOREST or
WATER configured in the Vectors type assignment window.
Typologies effects
The Forest optimization parameter allows you to activate the forest optimization. If
activated, the vegetation is not consider as an obstacle but as a transmission
phenomenon which will be associated with specifics losses properties
Note: The using this parameter slightly increases calculation time.
The Maritime optimization parameter allows you to activate maritime optimization.
If activated, a statistic optimization will be applied in the case of propagation over
water.
Note: The using this parameter slightly increases calculation time.
Depenetration
The Depenetration option allows you to activate the depenetration feature.
Depenetration works as follows: for an antenna located in a building, the model
applies a specific treatment to take into account the propagation inside this building.
The model identifies several virtual transmitters and considers the one which
generates the lowest losses.
In addition to the propagation phenomena between the virtual transmitter and the
receiver, the model estimates the losses from the real transmitter (RT) to the virtual
transmitter (VT) with the following formula:
Loss (from RT to VT) = d * loss( Inside Inside) Maxh 3;0 3 *
Page 44
loss( InsideOutside)
3
Where:
- d: the distance between the real transmitter and the virtual transmitter
- h: the difference of height between the real transmitter and the virtual transmitter
- loss(Inside->Outside): corresponds to the Inside Outside parameter which allows you
to set the value in dB (the default is 10 dB) of the assigned additional loss to the
transmitter inside a building while the signal passes through the building.
- loss(Inside->Inside): corresponds to the Inside Inside parameter which allows you to
set the value in dB/m (the default is 0.66 dB/m) of the assigned additional loss to the
transmitter inside a building, while the signal is propagated inside the building.
Note: the transmitter-receiver angle is considered as the incidence angle
MYRIAD Model is able to take into account a specific loss correction for each
building vector via the Losses from vectors data parameter. In order to do so, valid
vector files (.tab) must contain additional fields (float type) with the following
headings:
- Dep_In_Out_xxxxx_yyyyy_Mhz (example: Dep_In_Out_800_1200_Mhz) Valid values include the assigned additional loss (in dB) to the transmitter
inside a building for frequency range [xxxxx Mhz ; yyyyy Mhz] while the
signal passes through the building. The value must be from 0 to 100.
- Dep_In_In_xxxxx_yyyyy_Mhz (example: Dep_In_In_2200_2600_Mhz) - Valid
values include the assigned additional loss (in dB/m) to the transmitter
inside a building for frequency range [xxxxx Mhz ; yyyyy Mhz] while the
signal is propagated inside the building (the value must be from 0 to 5).
If the antennas frequency is compatible with several fields, the model considers only
the first one. If there is no compatible field (no compatible frequency range), the
model searches the fields Dep_Inside_Outside and/or Dep_Inside_Inside which are
compatible with all frequencies.
Note: The spelling of the key words and values are important: if the Losses from
vectors data parameter is activated and when there is no valid additional loss (no
compatible frequency range and/or no valid value), the model automatically switches
to the values defined in the MYRIAD parameters settings without any message.
Building calculation
The Do not calculate in building parameter allows you to deactivate the penetration
feature.
The Model-defined penetration parameter allows you to activate the penetration
feature. If activated, the model calculates only the outdoor pixels in a first pass, and
then it calculates indoor pixels that border on at least one pixel calculated during the
previous pass. Among the bordering pixels, the model selects the one with the
smallest loss and adds a correction to get the loss on the new pixels. It carries on until
there are no more uncalculated pixels left. The correction is automatically calculated
by the model according to the frequency, the penetration angle and the distance with
regard to the outside of the building.
Page 45
pass)
Building
Second pass
Third pass
The User-defined penetration parameter also allows you to activate penetration, but
for penetration, you manually set the correction.
The Outside Inside parameter allows you to set the value (in dB, 10 by default) of
the additional loss to a pixel located inside a building, while at least one of the eight
surrounding pixels is found on the street.
The Inside Inside parameter allows you to set the value (in dB/m, 0.66 by default)
of the additional loss to a pixel situated inside a building, while all of the eight
surrounding pixels are found inside the building.
Note: Penetration calculation can increase calculation time for very high resolutions.
MYRIAD Model is able to take into account a specific loss correction for each
building vector via the Losses from vectors data parameter. In order to do so, valid
vector files (.tab) must contain additional fields (float type) with the following
headings:
- Out_In_xxxxx_yyyyy_Mhz (example: Out_In_800_1200_Mhz) - Valid values
include the assigned additional loss (in dB) to the receivers inside a building
for frequency range [xxxxx Mhz ; yyyyy Mhz] while at least one of the eight
surrounding pixels is found on the street. The value must be from 0 to 30.
- In_In_xxxxx_yyyyy_Mhz (example: In_In_2200_2600_Mhz) - Valid values
include the assigned additional loss (in dB/m) to the receivers inside a
building for frequency range [xxxxx Mhz ; yyyyy Mhz] while all of the eight
surrounding pixels are found in the building. The value must be from 0 to 5.
If the antennas frequency is compatible with several fields, the model considers only
the first one. If there is no compatible field (no compatible frequency range), the
model searches the fields Outside_Inside and/or Inside_Inside which are
compatible with all frequencies.
To sum up, in case of vectors, the model will automatically apply penetration losses
when the receiver is located in a building vector except if you enable Do not
calculate in building (in this case, there is no calculation when the receiver is located
in a building vector). If Do not calculate in building is not enabled:
- If Losses from vectors data is enabled, the model uses the penetration defined
in the vectors files
- If Losses from vectors data is enabled and the penetration losses defined in
the vectors files are not set or not valid, the model uses the Model-defined
penetration or User-defined penetration according to the model settings
Page 46
If Losses from vectors data is not enabled, the model uses the Model-defined
penetration or User-defined penetration according to the model settings
MYRIAD Model is able to take into account a specific loss correction for each clutter
class via the Losses from clutter settings parameter. In order to do so, in the clutter
classes settings, the clutter class has to be assigned to the Building type and the two
dedicated columns have to be set:
Outside inside (dB) - Valid values include the assigned additional loss (in dB)
for all frequencies to the receivers inside a building, while at least one of the
eight surrounding pixels is found on the street. The value must be from 0 to 30.
Inside inside (dB/m) - Valid values include the assigned additional loss (in
dB/m) for all frequencies to the receivers inside a building, while all of the
eight surrounding pixels are found inside the building. The value must be from
0 to 5.
To sum up, in case of clutter, when you select one or several clutter types as Building,
the model will automatically apply penetration losses when the receiver is located in
one of these clutter types, except if you enable Do not calculate in building (in this
case, there is no calculation when the receiver is located in one of these clutter types).
If Do not calculate in building is not enabled:
- If Losses from clutter settings is enabled, the model uses the penetration
defined in the Clutter settings assignment window
- If Losses from clutter settings is enabled and the penetration losses
defined in the Clutter settings assignment window are not set, the model
uses the Model-defined penetration or User-defined penetration according
to the model settings
- If Losses from clutter settings is not enabled, the model uses the Modeldefined penetration or User-defined penetration according to the model
settings
The only way to not apply penetration losses for a specific clutter type is to not select
this clutter type as Building.
Note: The buildings calculation coverage option can return incoherent results in case
of raster data with low resolution and or in case of raster data with generic clutter
type (as urban for example)
Note: The spelling of the key words and values are important: if the Losses from
vectors data and/or Losses from clutter settings parameter is activated and when
there is no valid additional loss (no compatible frequency range and/or no valid
value), the model automatically switches to the selected building calculation option
(meaning Model-defined penetration or User-defined penetration) without any
message.
Note: In case of point to point simulation (analyse, tuning, etc.), the model applies an
internal algorithm which allows to relocate the receiver outside the building (the
closest outside place or, if the distance is too important, in front of the building
(transmitter-receiver direction) and to apply internal penetration losses.
Page 47
The Mobile on top of buildings parameter allows you to enable MYRIAD Model to
consider the height of the receiver from the top of the building (or from the ground if
there is no building). No penetration is available with this parameter.
The Calculate indoor only parameter allows you to enable MYRIAD Model to
calculate only in the buildings (other calculation points will not be calculated).
Computed data
The Tuning index parameter allows you to access a specific optimization for the
different components of the model. This option is only available if you have already
tuned the model using survey data (See chapter for more information about the
MYRIAD Model automatic tuning).
If the parameter is not assigned, MYRIAD Model uses its default tuning.
The Morphology index parameter allows you to access the morphology geographic
data type. If the parameter is not assigned, the model uses the default morphology.
To generate these data, you click on the Morphologies Index tool (
) button.
The morphologies generator creates the morphologies on the intersection of the
height and the clutter data. The morphologies are used by the model to determine in
which geographical context the prediction is performed, and depending on context,
special optimizations are applied. You have to set the name of the index file that is
generated and map each clutter class to one of 5 basic clutter classes. A morphologies
file and morphologies index file are created.
Note: All the themes contained in the clutter file(s) have to be referenced in the
clutter classes description file (including No_data)
Page 48
Page 49
The Graph index parameter allows you to access to the graphs geographic data type.
If the parameter is not assigned, the model will calculate without taking this into
consideration. To generate these data, you click on the Graph index tool (
)
button:
The graphs generator creates the graphs on the project. These data are useful to help
the model to compute 'guided' propagation for micro cells. You set the name of the
index file to be generated. The graphs generator automatically detects the dense
urban areas and decides if it has to generate the graphs in each case.
Note: Depending to the size of the project area, the calculation time can be significant.
By default, the Vectors index parameter contains the vectors index of the project.
You have the possibility of using another vectors index to generate the graphs on
another region.
If the project area is not considers as a microcell environment, the model will
consider that the guided propagation component is not significant and the graphs
generator will display the message: No microcell environment detected. Graphs
will not be generated..
Page 50
Key features
The Antenna correction option allows you to determine whether the model verifies
the coordinates of the antenna in an urban environment.
Antenna correction works as follows: For an antenna located in a building, the model
calculates the new DX, DY or the height so that the antenna is on the exterior of the
building (DX and DY correspond to the displacement in the direction of the azimuth
according to the axis of the Xs and the Ys in the horizontal plane in relation to the
transmitter).
After that, you can move the antenna to the facade by applying DX and DY to the
transmitter coordinates or on the rooftop (by modifying the transmitters height).
Roof distance
Roof distance
Facade
distance
Facade distance
Page 51
A
text
file
(which
can
be
opened in
a
spreadsheet),
called
AntennaCorrectionFile.txt, summing up the different correction parameters and
the obtained results, is generated in the Result directory (the correction will appear
only for poorly located transmitters).
You can make an automatic update of the antenna location (roof or facade correction).
For that, you have to make an ASSET xml export:
GSM case: the selected xml file is GSM-CELL-LIST001.xml
GSM repeater case: the selected xml files are REPEATER-LIST001.xml and
PROPERTY-LIST001.xml
UMTS case: the selected xml file is NODEB-LIST001.xml
UMTS repeater case: the selected xml files are UMTS-REPEATERLIST001.xml and PROPERTY-LIST001.xml
CDMA2000 case: the selected xml file is CDMA-BS-LIST001.xml
CDMA2000 repeater case: the selected xml files are CDMA-REPEATERLIST001.xml and PROPERTY-LIST001.xml
Fixed WIMAX case: the selected xml file is WiMAX-NODE-LIST001.xml
Fixed WIMAX repeater case: the selected xml files are WiMAX-REPEATERLIST001.xml and PROPERTY-LIST001.xml
Mobile WIMAX case: the selected xml file is MOBILE-WiMAX-NODELIST001.xml
Mobile WIMAX repeater case: the selected xml files are MOBILE-WiMAXREPEATER-LIST001.xml and PROPERTY-LIST001.xml
LTE case: the selected xml file is LTE-NODE-LIST001.xml
LTE repeater case: the selected xml files are LTE-REPEATER-LIST001.xml
and PROPERTY-LIST001.xml
Note: In case of repeater(s), do not forget to select Option Grid (Easting-Northing)
during the export of the property .xml file.
You have to run the antenna correction tool (called AntennaCorrectionTool.exe)
available in the MYRIAD Model installation directory.
You need to choose between Antenna Roof Correction and Antenna Facade
Correction and to select the directories where input xml files and
AntennaCorrectionFile.txt are located and where output xml files will be created.
Finally, you have to make an xml import ("Replace" has to be selected to erase older
location):
Page 52
Note: The use of this option implies that the result files of the model are not assigned;
it means that there is no calculation; the model only creates the
AntennaCorrectionFile.txt file.
The Minimal distance between antenna and faade parameter allows you to set the
minimum distance (in meters) between the antenna and the building facade that
supports it.
The Minimal distance between antenna and roof parameter allows you to set the
minimum distance (in meters) between the height of the antenna and the roof of the
building that supports it.
The Result directory parameter allows you to select the directory where the file
AntennaCorrectionFile.txt will be generated. If it is assigned to "NULL", the results
files are generated in the directory 'tmp' under the MYRIAD Model output directory.
Train option
The Use railway tracks parameter allows you to indicate whether the train option is
used by the model.
If you select this type of data, the Railway vectors assignment window appears:
In this window, the list of vectors names appears. You must determine whether the
railway is a TRAIN type, a TRAIN_EXCAVATION type, a TRAIN_TUNNEL type,
a TRAIN_SOUNDPROOF, a TRAIN_EMBANKMENT type, a TRAIN_ VIADUCT
type or an UNDEFINED type. This configuration creates or modifies a file, named
'menu.xml', containing building and railway types specifications in the same
directory as the vectors index file.
Page 53
The railway tracks data is vector linear data with only 2 points. The railway files,
which are in vector MapInfo format (TAB file), have to be registered in the same xml
index file as the vectors files (index.xml).
The type of railway is stored under the attribute NAME of tag VECTOR. The
railways files which are under the same tag VECTOR must have a single type of
railway.
If MYRIAD Model encounters a vector name that is not defined in the menu.xml file
while loading the vectors (or/and linear) index file, you are informed of the issue
and the UNDEFINED type is assigned to the corresponding geographic data file.
If the menu.xml file contains non standard MYRIAD Model vector type, you are
informed of the issue and geographic data file relating to that unknown vector type
is assigned an UNDEFINED type.
If the vectors (or/and linear) index file was updated, you are informed of the issue
and you have to update files "menu.xml" with the settings.
The Calculate only along the railway tracks parameter defines whether the model
calculates only along the railway tracks (other calculation points will not be
calculated).
The Train type parameter indicates the type of train on the railways: single-decker,
double-decker-low or double-decker-high.
The Track width parameter defines the area where the model will apply the train
correction. For example, for 20 meters, the model will consider an area of 20 meters
along the railway track (i.e., 10 meters on either side) and every calculation point in
this zone will be considered as being on the railway track.
Page 54
CHAPTER 4
MULTI-SECTORS OPTIMIZATION
In the case of a multi-sectors site, the model is able of re-using the results of the first
sector to decrease the computation time of the others sectors.
This optimization, available under certain conditions (same position, same antenna
height ...) is not active in micro-cellular (graphs utilisation) and mountainous (facets
utilisation) contexts and is not compatible with the parameters 'Antenna correction'
and 'Optimized calculation area'.
Page 55
Page 56
CHAPTER 5
By using the 'Analyse' button, you can run a validation of the model along further
measurements. By using 'Auto Tune' button, you can calibrate the model, with
specific tuning parameters dialog.
Page 57
In the Files section, you have to select the index and the name of the
optimization file. After the tuning, MYRIAD Model uses the index file that
contains the optimization file.
Note: An index file can include one or several optimization files. For example, it is
possible to have an optimization file for the northern part of a country and another
optimization file for the Southern. The first optimization file that matches the
calculation area will be taken into account.
The optimization file that you select should not exist, if it exists, you must make sure
you do not use the file anymore. With respect the index file, if the selected file
already exists, the new optimization file will be automatically placed at the
beginning of the index.
Configuration: MYRIAD Model allows you to check the index optimization files by
clicking on the Index file tool (
) button which makes it possible to check
whether the different calibration files of the calibration index recover all the project
area.
On this window, you can visualize a summary of the index optimization files:
In blue: name and coordinates of the different optimization area of the index
optimization file
In red: coordinates of the area(s) which is (are) not covered by the index
optimization file
On the first column, you can select the area you want to visualize.
Page 58
You can modify the index optimization file. The modifications can be made by
changing the value of the coordinates of the calibration area on the grid (double click
on the case of the grid that you want to modify) or by directly moving the calibration
area on the picture.
You can also change the order of the calibration files in the calibration index. You can
select the line of the calibration file and move up or move down the selected
calibration file with up and down button.
In the Calibration type section, you can define the survey filtering and the
calibration type:
You select the Use automatic filtering checkbox to filter out surveys where
inconsistent values have been found. These surveys can generate inconsistency in the
tuning coefficients.
Note: When this option is selected, the log displays filtered surveys and a number
between 0 and 100 indicates the level of quality (i.e., a value close to 95 indicates that
the survey points are of a good quality)
You select the Do not consider indoor pixels for raster areas checkbox to filters out
surveys which are located inside Building clutter classes. When it is not enabled,
surveys which are located inside Building clutter classes are not considered as
indoor, it means that tuning engine automatically sets the clutter classes type
Building to Other.
During the tuning process, the calibration tool optimizes coefficients for each type of
morphology. Note that if the morphology option is not selected, the model will only
use the default morphology meaning a unique optimization for all environments.
MYRIAD Model User Reference Guide
MYRIAD v430; ASSET v9.0
Page 59
Before starting the tuning process, the calibration tool will separate the
measurements points in different categories (boxes) according to the morphology
they belong to.
Please note that for both options, there is an initial checking based on min. number of
points: a min of 1000 measurements points per box are required to start optimization
otherwise the model uses default parameters for the box(es).
You can choose between two types of tuning:
When using the Standard calibration, the calibration tool performs specific
tuning for each box without any control, it means that, for each box, it just
tries to associate the variables calculated along the profile with the best
coefficients to reduce the average and the standard deviation.
Note: the calibration tool optimizes all parameters (provided enough points
are available), which means the model can show very good stats against the
set of measurements used, but will probably be less robust when using the
same model in other type of environment.
When using the Advanced calibration, the calibration tool performs specific
calibration for each box but it first checks the distribution of each variable
calculated along the profile, it means that the calibration tool will associate
the variables calculated along the profile with the best coefficients to reduce
the average and the standard deviation but only the variables considered as
representative of the reality, the other variables will be associated to a default
coefficient ('representative of the reality' means in adequacy with what the
model learnt during all steps of its development)
Note: the calibration tool optimizes certain parameters (provided enough
points are available), which means the model can show very good stats, but
according if the set of measurements used, the results can be a little less good
than with the other option but it will be more robust when using the same
model in other type of environment
Note: the transmitters and the receivers located inside a building are not considered
during the MYRIAD Models Analysis/Tuning process
In the Calibration Area section, you can select the optimization area. After the
tuning of MYRIAD Model, the model uses the new optimization for the stations
located in this optimization area. Three cases are possible:
Surveys extent: the optimization area is formed by the rectangle including the
whole of the measurement points
Project extent (default value): the optimization area is equal to the ASSET
project area
User-defined extent: you define the optimization area manually
Tuning the model starts after you click Start tuning. You can follow the progress of
the tuning in the progress bar and in the message log.
Depending on your choice, you can run several tunings and compare the differences
performance displayed in the different Tuning performances tab.
Page 60
At the end of the tuning, you can view the global results, by morphology and by
survey. You can export these result in a CSV or Excel file with the option of exporting
the performance per pixel data.
Finally, depending on the results, you can choose whether you want to keep this new
MYRIAD Model tuning by clicking on Select (if there is more than one tuning) and
Ok to apply it automatically to the next predictions.
Warning: during the Analyse or the Auto Tune functions, the MYRIAD Model
parameters are always taken into account, for example for the frequency:
If you select the Use antenna frequency
checkbox, the model uses the frequency
defined for the antenna (database or header,
depending on whether measurements are
associated or not)
The default frequency is used when Use
antenna frequency is not selected and/or
when the antenna is not defined (unassociated measurements for example)
Page 61
TABLE OF ILLUSTRATIONS
Figure 1: Installation of the MYRIAD Model for ASSET .................................................................. 8
Figure 2: Uninstalling the Myriad Model for ASSET........................................................................ 9
Figure 3 : LMTools - Service/License File tab ................................................................................. 11
Figure 4 : LMTools - Borrowing tab .................................................................................................. 13
Figure 5 : Environment Variables ...................................................................................................... 14
Figure 6 : New User Variable ............................................................................................................. 14
Figure 7 : Distribution Coordinator Options ................................................................................... 16
Figure 8 : Coordinator Hostname ...................................................................................................... 16
Figure 9 : MYRIAD Model parameters import ................................................................................ 17
Figure 10: Reflection + diffraction + guided propagation = the MYRIAD Model trilogy ......... 21
Figure 11: Profile example (without vectors) ................................................................................... 22
Figure 12: Profile example (with vectors) ......................................................................................... 22
Figure 13: Profile construction for vectors ....................................................................................... 22
Figure 14: Extraction of a profile ....................................................................................................... 24
Figure 15: Profile example of obstacles in thin ridges .................................................................... 25
Figure 16: Order of obtaining the positive edges committed ........................................................ 25
Figure 17: Example of facets ............................................................................................................... 28
Figure 18: Profile example for the graphs component ................................................................... 29
Figure 19: Example of a graph (PARIS) ............................................................................................ 30
Figure 20: Examples of paths for the graphs component ............................................................... 31
Figure 21: MYRIAD Model - Parameters tab ................................................................................... 34
Figure 22: MYRIAD Model - Clutter settings assignment window .............................................. 35
Figure 23 : MYRIAD Model - Raster options ................................................................................... 35
Figure 24: MYRIAD Model - Vectors type assignment window ................................................... 36
Figure 25: MYRIAD Model - Time Optim tab ................................................................................. 38
Figure 26: MYRIAD Model - Radial mode ....................................................................................... 39
Figure 27: MYRIAD Model - Inner/outer area resolution mode .................................................. 40
Figure 28: MYRIAD Model - Optimized calculation area mode ................................................... 41
Figure 29: MYRIAD Model - Radio tab ............................................................................................ 42
Figure 30: MYRIAD Model - Horizontal propagation .................................................................... 43
Figure 31: MYRIAD Model - Used weighted tuning coefficients ................................................. 43
Figure 32: MYRIAD Model - Depenetration .................................................................................... 44
Figure 33: MYRIAD Model - Building penetration ......................................................................... 46
Figure 34: MYRIAD Model - Morphologies generator window ................................................... 48
Figure 35: MYRIAD Model - Facets generator window ................................................................. 50
Figure 36: MYRIAD Model - Graphs generator window ............................................................... 50
Figure 37: MYRIAD Model - Advanced tab ..................................................................................... 51
Figure 38: MYRIAD Model - Antenna correction ........................................................................... 51
Figure 39: Automatic antenna correction tool ................................................................................. 52
Figure 40 : MYRIAD Model - Railway vectors assignment window............................................ 53
Figure 41: Measurement toolbox ....................................................................................................... 57
Figure 42: MYRIAD Model - Auto Tune window ........................................................................... 58
Figure 43: MYRIAD Model - Index Optim File Configuration...................................................... 59
Figure 44: CW Measurement Analysis - Tuning performances window .................................... 61
Page 62