MYRIAD MODEL User Reference Guide

MYRIAD MODEL
USER REFERENCE GUIDE
MYRIAD MODEL VERSION 440

ASSET VERSION 10.0.2
EDITION 1
Confidentiality, Copyright Notice & Disclaimer
Due to a policy of continuous product development and refinement, TEOCO Ltd.

(and its affiliates, together “TEOCO”) reserves the right to alter the specifications,
representation, descriptions and all other matters outlined in this publication
without prior notice. No part of this document, taken as a whole or separately, shall
be deemed to be part of any contract for a product or commitment of any kind.
Furthermore, this document is provided “As Is” and without any warranty.
This document is the property of TEOCO, which owns the sole and full rights
including copyright. TEOCO retains the sole property rights to all information
contained in this document, and without the written consent of TEOCO given by
contract or otherwise in writing, the document must not be copied, reprinted or
reproduced in any manner or form, nor transmitted in any form or by any means:
electronic, mechanical, magnetic or otherwise, either wholly or in part.
The information herein is designated highly confidential and is subject to all
restrictions in any law regarding such matters and the relevant confidentiality and
non-disclosure clauses or agreements issued with TEOCO prior to or after the
disclosure. All the information in this document is to be safeguarded and all steps
must be taken to prevent it from being disclosed to any person or entity other than
the direct entity that received it directly from TEOCO.
TEOCO is a trademark.
All other company, brand or product names are trademarks or service marks of their
respective holders.
This is a legal notice and may not be removed or altered in any way.
COPYRIGHT © 2019 TEOCO LTD

ALL RIGHTS RESERVED
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 find errors or feel that information is missing, please send your
Documentation-related 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
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
THE MYRIAD MODEL ........................................................................................... 19
CONTEXT ........................................................................................................................................ 20
THE MYRIAD MODEL .................................................................................................................. 21
THE PROFILE COMPONENT ...................................................................................................... 22
The principle behind the profile component ........................................................................... 22
Management of raster geographic data .................................................................................... 23
Profile extraction of raster geographic data ............................................................................. 24
Deygout's methods of calculating diffraction .......................................................................... 25
THE MORPHOLOGY DATA ........................................................................................................ 27
Improving propagation accuracy based on morphology ....................................................... 27
THE FACETS COMPONENT ........................................................................................................ 28
The principle behind the facets component ............................................................................. 28
The modeling and function of the facets component ............................................................. 29
THE GRAPHS COMPONENT ....................................................................................................... 30
The principle behind the graphs component ........................................................................... 30
The modeling and function of the graphs component ........................................................... 31
THE TRAIN COMPONENT .......................................................................................................... 33
THE MULTIPATH COMPONENT ............................................................................................... 34
Geographical Data ....................................................................................................................... 34
Electromagnetic Wave Model .................................................................................................... 35
Multipath Variables ..................................................................................................................... 36
CONFIGURING MYRIAD MODEL WITH ASSET ............................................ 37
THE ‘PARAMETERS’ TAB ........................................................................................................... 38
General parameters ..................................................................................................................... 38
Geographical data ........................................................................................................................ 40
Output directory .......................................................................................................................... 42
THE ‘TIME OPTIM’ TAB .............................................................................................................. 43
Prediction parameters ................................................................................................................. 43
Radial............................................................................................................................................. 44
Inner/Outer area resolution ....................................................................................................... 45
Optimized calculation area ........................................................................................................ 46
THE ‘RADIO’ TAB.......................................................................................................................... 47
Radio optimization ...................................................................................................................... 47
Typologies effects ........................................................................................................................ 49
Depenetration ............................................................................................................................... 49
Building calculation..................................................................................................................... 50
Computed data ............................................................................................................................ 53
MYRIAD Model User Reference Guide Page 5

MYRIAD v440; ASSET v10.0.2
THE ‘ADVANCED’ TAB ................................................................................................................ 56
Key features .................................................................................................................................. 56
Train option .................................................................................................................................. 59
THE ‘MULTIPATH’ TAB .............................................................................................................. 61
Advanced multipath component .............................................................................................. 61
Multipath variables ..................................................................................................................... 62
Multipath prediction settings..................................................................................................... 62
MULTI-SECTORS OPTIMIZATION .................................................................... 65
MYRIAD MODEL TUNING.................................................................................... 67
Page 6 MYRIAD Model User Reference Guide

CHAPTER 1
INSTALLING MYRIAD MODEL WITH

ASSET
The installer setup_MYRIAD_ModelAAA.BBBB.CCCCC_D.D.exe allows installing
the XXX version of the MYRIAD model (build YYYY.CCCCC) on the D.D version of
the ASSET platform.
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

INSTALLATION
Launching the installer opens the following dialogue boxes:
Figure 1: Installation of the MYRIAD Model for ASSET
The installer ensures:

- Copies of the necessary files for the MYRIAD Model in the target directory
- The modification of associated registers
- The link between the ASSET dll’s and those for the propagation model
Note 1: It is strongly recommended to keep the default installation directory

Note 2: ASSET must be closed during the installation of the MYRIAD Model
Note 3: The version of the dll must be compatible with the version of ASSET
(For example, setup_MYRIAD_Model4xx.yyyy.zzzzz_9.1.exe is only compatible
with ASSET 9.1)

REMOVAL
You remove the MYRIAD model in the same way as other programs. From the Start
menu, select Control Panel => Add or Remove Programs.
Figure 2: Uninstalling the Myriad Model for ASSET
Note: It is recommended to close ASSET during the removal of a model and to stop
the services "Distributed Predictions Agent Service".

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 workstation’s 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.
Standalone 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.

Server floating license
The workflow for using MYRIAD Model with a floating license is as follows:
 Step 1: Configure the license server.
 Step 2: Install MYRIAD Model on a workstation with access to the network on
which the license server is hosted.
 Step 3: If MYRIAD Model is to be used in a situation where continuous access
to the network on which the license server is hosted will not be available (e.g.,
when travelling), borrow a license for MYRIAD Model from the license server.
Configuring License Servers
If you are using a configuration of MYRIAD Model that uses floating licenses, an
administrator must initially configure a license server on a host server on which
MYRIAD Model has been installed. The license server can then handle MYRIAD
Model license requests from users.
 You must use the tools in the “License Manager” folder (in MYRIAD Model
install directory).
 Double-click lmtools.exe. The LMTools dialogue box opens.
Figure 3 : LMTools - Service/License File tab
 On the Service/License File tab, select Configuration Using Services.

 Select the LMTOOLS ignores license file path environment variables check
box.
 Click the Config Services tab, and enter a name for the service in the Service
Name box (for example “MYRIAD Model”).
 Click the Browse button beside the Path to the lmgrd.exe File box and
navigate to the “lmgrd.exe” file.
 Click the Browse button beside the Path to the License File box and navigate
to the “MYRIAD_Model.lic” file (the floating license).
 Click the Browse button beside the Debug Log File box, navigate to the
location where you want to save a debug log file, enter a name for the debug
log file in the File Name box, and then click Open.

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).
 Select the Use Services check box.

 Select the Start Server at Power Up check box (this option automatically
starts the license server when the host server is restarted).
 Click the Save Service button.
 When you are prompted to save the service settings, click Yes.
 Click the Start/Stop/Reread tab.
 From the FLEXnet License Services Installed on this Computer list, choose
the service that you created for the MYRIAD Model license server in step 4,
and click the Start Server button.
 You can check if the server is correctly started by reading the Debug Log File.
 Select File -> Exit.
 On the workstation, copy the “MYRIAD_Model.lic” (floating licence) file into
the MYRIAD Model installation directory. Ensure that the .lic file is named
“MYRIAD_Model.lic”.
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.
Borrowing floating license

To borrow a floating license, you must connect to the MYRIAD Model license server
and borrow a license from the license server.
After you have obtained a floating license for the MYRIAD Model, you can
disconnect from the network and use MYRIAD Model. You can use MYRIAD Model
until the end of the defined borrowing period.
You can also return a borrowed MYRIAD Model floating license before the end of
the defined borrowing period. When you return a floating license, that license
becomes available for another user.
To borrow a floating license:
 On the workstation, close ASSET.

 On the workstation, in Windows Explorer, navigate to the License Manager
folder (in MYRIAD Model installation directory), and double-click
lmtools.exe.
 The LMTools dialogue box opens.
 Click the Borrowing tab.

Figure 4 : LMTools - Borrowing tab
 In the Vendor Name box, enter LICPIFT.

 In the Return Date box, enter a date by which the license must be returned
(the return date must be in a dd-mmm-yyyy format (e.g., 01-jul-2012). The
borrowing period cannot exceed 30 days or the expiration date for the
MYRIAD Model license that was purchased).
 If you want to specify at what time the license must be returned on the return
date, enter a time in the Return Time box (the time must be in an hh:mm
format (e.g., 14:00 defines a license expiration of 2 p.m.). If no return time is
defined, the license will expire at midnight on the return date).
 Click Set Borrow Expiration.
 You must run MYRIAD Model one time in ASSET to complete borrowing
the license.
 Close ASSET and click Don't Borrow Anymore Today in LMTools.
To return a borrowed floating license:
To return a floating license before its expiration date, you must define an
environment variable that is set to the path of the license file on the license server.
You can then return the floating license to the license server.
 On the workstation, close ASSET and LMTools.

 On the workstation which currently holds the borrowed license, select Start
 Settings  Control Panel  System.
 In the System Properties dialogue box, click the Advanced tab and click
Environment Variables.
 The Environment Variables dialogue box opens.

Figure 5 : Environment Variables
 In the User Variables for the given user name section, click New.
 In the New User Variable dialogue box, enter “LM_LICENSE_FILE”in 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.
Figure 6 : New User Variable
 In the Environment Variables dialogue box, click OK.

 In the System Properties dialogue box, click OK.
 In Windows Explorer, navigate to the License Manager folder and double-
click lmtools.exe.
 The LMTools dialogue box opens.
 Click the Borrowing tab.
 In the Feature Name box, enter “MYRIAD_Model”.
 Click Return Borrowed Licenses Early.

DISTRIBUTED PREDICTION
MYRIAD Model uses ASSET’s 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 information on licensing this feature.
To use ASSET’s 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 ASSET’s 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 ASSET’s 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).
MYRIAD Model licenses

MYRIAD Model offers the possibility of running simulations on several threads
regardless of the type of license (standalone or server):
 with a standalone license, the model is limited to 4 simultaneous threads
(idem for ASSET and for agent)
 with a server license, the model is limited to 4 simultaneous threads per token
(idem for ASSET and for agent)
 For example, if the user runs a set of predictions on ASSET (6 threads) and on
two agents (2 threads by agent), the models will consume 4 licenses (2 for
ASSET (4 threads + 2 threads)) and one for each agent).
Workstation machine configuration
To configure the coordinator on the workstation machine, user has to click right on
the 'Coordinator Tray Icon', to select 'Coordinator Options…' and to set all the
information in the 'Agent' tab.
 The 'Agent Log File Path' has to be a valid path on each client machine
 The 'Agent Policy' has to be set to 'Server'

Figure 7 : Distribution Coordinator Options
Client machine configuration

On each client machine, after the installation of an ASSET agent (same version of
ASSET as the one installed on workstation) and of MYRIAD Model (same version of
MYRIAD Model as the one installed on workstation), user has to set the coordinator
hostname and to give the name of the workstation ASSET.
Figure 8 : Coordinator Hostname
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.

EXPORT AND IMPORT
You have the possibility to retrieve the settings from another MYRIAD model
(previous or same version only).
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
Figure 9 : MYRIAD Model parameters import
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.

CHAPTER 2
THE MYRIAD MODEL

In This Section
THE MYRIAD MODEL ........................................................................................... 19
CONTEXT ........................................................................................................................................ 20
THE MYRIAD MODEL .................................................................................................................. 21
THE PROFILE COMPONENT ...................................................................................................... 22
The principle behind the profile component ........................................................................... 22
Management of raster geographic data .................................................................................... 23
Profile extraction of raster geographic data ............................................................................. 24
Deygout's methods of calculating diffraction .......................................................................... 25
THE MORPHOLOGY DATA ........................................................................................................ 27
Improving propagation accuracy based on morphology ....................................................... 27
THE FACETS COMPONENT ........................................................................................................ 28
The principle behind the facets component ............................................................................. 28
The modeling and function of the facets component ............................................................. 29
THE GRAPHS COMPONENT ....................................................................................................... 30
The principle behind the graphs component ........................................................................... 30
The modeling and function of the graphs component ........................................................... 31
THE TRAIN COMPONENT .......................................................................................................... 33
THE MULTIPATH COMPONENT ............................................................................................... 34
Geographical Data ....................................................................................................................... 34
Electromagnetic Wave Model .................................................................................................... 35
Multipath Variables ..................................................................................................................... 36

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 cross-
section 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.

THE MYRIAD MODEL
Capping several years of research in domains such as: propagation, modelling,
optimization and algorithms, the MYRIAD propagation model is able to
automatically adapt itself to all engineering (micro, mini, small, and macro cells), to
all environments (dense urban, urban, suburban, mountainous, maritime, and open),
and to all systems (DVB-H, GSM, GPRS, EDGE, UMTS, WiFi, WiMAX, LTE) in a
frequency range starting from 200MHz to 5GHz.
Relying on very realistic modelling of the channel, it achieves the synergy of the
three physical elementary contributions: diffraction in the vertical plane, guided
propagation in the horizontal plane, and reflection on the relief.
Figure 10: Reflection + diffraction + guided propagation = the MYRIAD Model trilogy

THE PROFILE COMPONENT
The principle behind the profile component

The profile component is divided in two parts:
 The first one is dedicated to the environments for which the vectors’
geographical data are not available throughout the whole calculation zone or
for occasions where the user does not want to work with them.
 The second one combines the vectors’ geographic data (when available) and
the raster geographic data representing the surface with raster geographic
data of the relief.
The calculation of the loss of propagation is almost entirely determined by the relief
analysis in the vertical plane passing through the transmitter and the receiver. This
hypothesis allows to assimilate each relief obstacle to a 2D theoretically thin and
infinite horizontal plane, and to reduce it to a problem of wave diffraction calculation
on a succession of thin ridges that can be treated with Fresnel formulas.
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).
Figure 11: Profile example (without vectors)
Figure 12: Profile example (with vectors)

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
building’s 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.
Figure 13: Profile construction for vectors

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.
Deygout’s 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.
Management of raster geographic data

Raster geographical data can be of 3 different types:
Height (Digital terrain model): Description of altitudes above ground of the points
at the centre of the pixel. This is a single point and not a calculated average on the
various altitudes encountered on the pixel.
Clutter (Digital surface model): Statistical description of the surface or principal
theme on the pixel.
Building raster (Digital elevation model): Descriptions of height above the surface
of the points at the centre of the pixel.
The profile component adapts itself to all types of raster data. The management of
raster geographic data is based on the construction of a “height” representation and a
“surface” representation.

A data representation is a zone of raster data that results from the fusion of various
raster files (or from the data of one file if only one file is available) and whose
construction unfolds according to the following stages:
 Inventory of the files whose intersection with the calculation area is not zero
 Creation of a result area and positioning of each pixel to “indefinite value”.
 Reading every file and fusion in the result area. During the fusion, a pixel
from the resulting area is only affected if its previous value was “indefinite
value”.
The “height” representation is a 2D matrix that contains the description of the relief
while the “surface” representation is a 2D matrix that contains the surface height (for
clutter data, each type is associated with a height by the user).
The resolution of the “height” representation can be inferior, equal, or superior to
that of the “clutter” representation.
Profile extraction of raster geographic data

Taking into consideration the fact that propagation is principally done through
diffraction on relief, the model constructs, in a vertical transmitter-receiver plane, a
profile called “knife edge” comprised of ridges determined from the raster
geographic data. For that, it extracts the profile ridges that are at the intersection
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
R Verticals and horizontals

plane at the centre of the
bins

Y Profile extract
E
X X
Figure 14: Extraction of a profile

The profile is extracted by adding a value estimated by interpolating the distance
starting from the surface profile to the value of each point of the height profile. At
each point of the height profile, the point that provides the best frame in distance in
the surface profile is chosen, and the height of the surface ridge is estimated with a
linear interpolation starting from the heights and the distances from the transmitter
of the “framed” ridges.
Deygout's methods of calculating diffraction

The phenomenon of diffraction is one of the most important factors contributing to
the propagation of electro-magnetic waves.
Deygout’s method has been chosen for the profile component. It uses three
fundamental concepts to arrive at the calculation of diffraction losses:
a) The first Fresnel zone: It is generally understood that diffraction

phenomena due to all obstacles situated outside this zone are negligible. The first
Fresnel zone is the volume limited by the ellipsoid with starting points E and R, such
as EM + MR – ER ≤ /2 (with M points belonging to the Fresnel ellipsoid).
b) The Huyghens principle: The fundamental idea behind Deygout’s method

is to understand that, to go from transmitter to receiver, the wave must, by
diffraction, avoid a limited number of obstacles (thin ridges) taking each one into
consideration after the other in function to their importance regarding the method of
the Fresnel calculation, that is to say in relation to the Fresnel zones defined in
consequence.
Figure 15: Profile example of obstacles in thin ridges

c) The superposition principle: As with other methods, the problem of
diffraction on the multiple ridges is treated as a succession of diffractions on a single
ridge, for which the Fresnel calculation is applicable. This approach is both empirical
and intuitive.
P2 P1 P2 P0 P2 P1 P2
R
E
3 2 4 1 6 5 7
Ordre
Figure de l’obtension
16: Order despositive
of obtaining the arétesedges
engagées positives
committed
The algorithm calculates recursively by sets of three (thus with a maximum of 15

edges of diffraction), between the transmitter and the receiver, the interference
coefficient of each ridge in the Fresnel ellipsis. It conserves the ridges that have the
largest interference coefficients, as well as the number of engaged ridges, and
diffraction losses are calculated starting from these ridges.
The loss represented by the profile component, created by the accumulation of the
different diffraction losses, is then corrected by adding the weighting of the
calculated variables along the profile whose coefficients are determined by adjusting
the least squares method by the calibration tool.

THE MORPHOLOGY DATA
Improving propagation accuracy based on morphology

Morphological data is a representation of the ground specific to MYRIAD Model.
Each geographic area is stored as a classified grid, in which each point is dependant
on both the elevation and the clutter. The data point value is calculated in a
continuous way: For example, a point representing “DENSE_URBAN_RELIEF”
morphology cannot have a point representing “FOREST_FLAT” morphology as a
neighbouring point.
It is strongly recommended that you use data representing the morphology of the
area with the MYRIAD Model in order to ensure accurate results, especially for the
tuning mechanism. This data must be generated from both the clutter and elevation
data. This can be done using the MYRIAD Model interface.
There are ten different types of morphology:
 FOREST_FLAT
 FOREST_RELIEF
 OPEN_FLAT
 OPEN_RELIEF
 SUBURBAN_FLAT
 SUBURBAN_RELIEF
 URBAN_FLAT
 URBAN_RELIEF
 DENSE_URBAN_FLAT
 DENSE_URBAN_RELIEF

THE FACETS COMPONENT
The principle behind the facets component

The facets component of the MYRIAD Model allows you to evaluate the contribution
of the multi–path while the electro-magnetic connection takes place in an irregular
terrain. It allows you to predict the signal strength received by the mobile taking into
account the reflections produced on the mountain slopes. This improves the
precision in relation to the classic components that only take into consideration the
propagation phenomena in the vertical cross-section of the terrain between the
transmitter and the receiver. The consideration of reflection is very complex and
depends on numerous factors. It is suitable then to make simplified hypotheses so
that the component is usable by the operator of radio mobile networks.
 The first simplification is the consideration by the model of the paths
comprising only the reflection on a mountain. It can be assumed that this
hypothesis introduces a slight error because the received paths by multiple
reflections on the topography are strongly mitigated and not significant at the
receiver.
 The second simplification is that only the zones on the mountain slopes that
are in “height” visibility of both the transmitter and receiver are considered.
Note that there is visibility when the different obstacles do not protrude from
the axis of the Fresnel ellipsoid.
 The third hypothesis is that the determination of the reflected paths is only
performed if the direct transmitter-receiver path is obstructed by the terrain.
 The fourth hypothesis is to limit the extent of the search area for possible
reflectors by fixing a maximum delay for the consideration of the echoes. The
measurement campaigns of impulse response have allowed validation to a
value of 50μs. Because of calculation time, the value by default is fixed at 25μs,
which corresponds to a maximum distance C.∆tmax = 300 x25 = 7500 m
(where C equals the speed of light)
 Finally, the fifth hypothesis is the understanding that there is a reflection, or
diffusion, (as opposed to discrete reflection on plane surface) given the large
irregularities of mountainous slopes in relation to wavelengths. The received
signal is uniformly shone in the half-space above the slope of the mountain,
and the diffused power is inconsistent. Nevertheless, by analogy with the
radar equation, it is assumed that all the contributions of the diffused power
could be added together by the receiver. This hypothesis has been verified on
the terrain and explains why a large quantity of energy nonetheless reaches
the mobile even though there are rarely discrete reflections in the direction of
the mobile

The modeling and function of the facets component
Activating the facets component is only effective if the propagation context is hilly
enough. The search of reflection zones is performed using the facets index parameter.
The files generated with the aid of an algorithm based on the Delaunay triangulation
method are defined in this parameter. These files contain the information about the
modelling of the relief (reflection facets, visibility in relation to the reflection facets,
etc.)
Once the user has obtained the reflection zones, the facets component calculates the
loss of the reflected paths to determine the total strength received by the receiver.
The profile loss is calculated and is added to the facets component loss to form the
total loss of the MYRIAD Model.
Figure 17: Example of facets

THE GRAPHS COMPONENT
The principle behind the graphs component
The graphs component is only effective for transmitters for which the vectors
geographic data are available over the entire calculation zone.
In a micro cellular context, the emitting and receiving antennas are positioned below
the average level of the rooftops. In this case, the signal strength received by
diffraction above the rooftops is significantly inferior to that of the signal strength
received by propagation in the street and diffraction on the edges. The propagation
hypothesis above the rooftops is therefore no longer sufficient, especially when the
number of edges between the transmitter and receiver is not too great.
Figure 18: Profile example for the graphs component
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.

Figure 19: Example of a graph (PARIS)
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.
The modeling and function of the graphs component

This component is responsible for calculating all the contributions coming from the
receiver by the different paths illustrated by the graph. It calculates the loss for each
path as a result of distance, of the diffraction on the vertical ridges formed by street
corners, and of multiple reflections along the street axes. All the elementary
contributions are then added to constitute the total loss of the graphs component
representing the electro-magnetic energy that propagates along the streets.
The number of paths going from the transmitter to the receiver is not defined. Only
those paths for which the loss is less than a defined threshold, that is to say
sufficiently significant, are selected.

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.

THE TRAIN COMPONENT
The train component provides the corrections of additional losses while the receiver
is in a train. When this option is used, the losses calculated for receivers on a railway
track or very close to one are stronger than if no train were found. These additional
losses are highly dependent on the characteristics of the railway tracks (i.e.,
excavation, tunnel, embankment, viaduct, or soundproof). The losses are also
different if the train is single, double-decker-low or double-decker-high.
The Use railway tracks option must be selected for the train component to be taken
into consideration.

THE MULTIPATH COMPONENT
The multipath component aims at providing insights on the spatiotemporal nature of

electromagnetic wave propagation in dense urban environments, by the mean of
three statistical variables: the delay-spread, the angle-spread and the Rice factor. To
do so, it relies on a deterministic identification of the main propagation paths
between the transmitter and the receivers. This is achieved by simulating the
propagation of a Dirac impulse signal and its subsequent interactions with terrain
and surface features.
Figure 21: Wave propagation simulated by the multipath component
Geographical Data
The multipath component uses polygons and heights data to model a 3D
geographical environment. It cannot be activated if either is missing. The vectors are
extruded according to their class and are assigned specific material properties (no
reflection nor diffraction on forests, no transmission through water or ground).

centroid centroid
Figure 22: Extrusion of buildings Figure 23: Extrusion of bridges
Figure 24: Extrusion of forests Figure 25: Extrusion of water surfaces
Electromagnetic Wave Model

An electromagnetic wave is modelled through its electrical compound. It is a three-
dimensional vector which initial value is given by the transmitter’s antenna
configuration. The orientation in space is set by the polarization whereas the
magnitude is set by the transmitted power. Polarization, magnitude, phase and delay
are then tracked as the wave propagates.
Any interaction with a geographical feature triggers one or more of the following
phenomena: reflection, transmission and diffraction. Each one of them alters
polarization, magnitude and delay depending on the material properties of the
geographical feature and in a coherent way with the other MYRIAD Model
components.
In the end, all the identified propagation paths are combined to produce three
multipath variables that further describe how the energy is received at each receiver.

Multipath Variables
From a multipath point of view, path loss is an estimation of the overall power that is
received by a receiver. While it is the core metric behind any modern mobile network
design, it does not account for the propagation paths that are exploited by multi-
antenna technologies. Hence the three additional metrics simulated by the multipath
component.
Together with path loss, these variables can help spotting the areas where MIMO is
suitable, select the best fit between diversity and multiplexing and adjust the antenna
designs accordingly.
Rice Factor: the Rice factor is a value that indicates how close a receiver is from line
of sight conditions. A high value (usually >> -5dB) means that most of the energy is
provided by a single propagation path which is almost always the case in line of
sight conditions, but can still happen in other situations. A low value area (<< -5dB)
usually is a good candidate to deploy MIMO optimisations.
Delay-Spread: the delay-spread measures the time span during which most of the
power arrives at a receiver. Values lower than the guard interval usually mean you
can expect a significant improvement of data rates with either diversity MIMO or
multiplexing MIMO. In such areas, choose diversity MIMO to enhance low signal-to-
noise ratios and multiplexing MIMO otherwise.
Angle-Spread: the angle-spread measures the dispersion of the paths as they leave
the transmitter to a receiver. This value is especially useful to fine tune your antenna
designs. The lower the value, the more constrained the orientation is, but the more
sectors you can set up.

CHAPTER 3
CONFIGURING MYRIAD MODEL WITH

ASSET
It is very easy and fast to configure the MYRIAD Model in ASSET. When you add a
new model (Configuration => Propagation Models… => Add), you have to choose
the MYRIAD Model and the first specific window appears.
In This Section
CONFIGURING MYRIAD MODEL WITH ASSET ............................................ 37

THE ‘PARAMETERS’ TAB ........................................................................................................... 38
General parameters ..................................................................................................................... 38
Geographical data ........................................................................................................................ 40
Output directory .......................................................................................................................... 42
THE ‘TIME OPTIM’ TAB .............................................................................................................. 43
Prediction parameters ................................................................................................................. 43
Radial............................................................................................................................................. 44
Inner/Outer area resolution ....................................................................................................... 45
Optimized calculation area ........................................................................................................ 46
THE ‘RADIO’ TAB.......................................................................................................................... 47
Radio optimization ...................................................................................................................... 47
Typologies effects ........................................................................................................................ 49
Depenetration ............................................................................................................................... 49
Building calculation..................................................................................................................... 50
Computed data ............................................................................................................................ 53
THE ‘ADVANCED’ TAB ................................................................................................................ 56
Key features .................................................................................................................................. 56
Train option .................................................................................................................................. 59
THE ‘MULTIPATH’ TAB .............................................................................................................. 61
Advanced multipath component .............................................................................................. 61
Multipath variables ..................................................................................................................... 62
Multipath prediction settings..................................................................................................... 62

THE ‘PARAMETERS’ TAB
Figure 26: MYRIAD Model - Parameters tab
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 (un-
associated measurements for example)
 The mobile height (1.7 meter by default)

 Additional Mobile heights (only available from ASSET 9.1)

If you select Additional Mobile heights, the model will run different
simulations at different mobile heights according to the setting of the
Additional mobile heights window:
Figure 27: MYRIAD Model - Additional Mobile heights window

Note: this feature, which allows computing several simulation maps,
considerably increases the computation time.

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:
Figure 28: MYRIAD Model - Clutter settings assignment window
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
Figure 29 : MYRIAD Model - Raster options

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:
Figure 30: MYRIAD Model - Vectors type assignment window
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.

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.

THE ‘TIME OPTIM’ TAB
On this tab, you can choose the calculation parameters (each of which has a default
value so that you can run the model without defining any values).
Figure 31: MYRIAD Model - Time Optim tab
You can define the following MYRIAD Model parameters:
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 User-

defined 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.

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
Profile B
dB
In this case: dA < dB so profile A is kept
Transmitter
Extraction point of the profiles
Profiles of the perimeter of the calculation area
Calculation point
Orthogonal projections
Figure 32: 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.

Inner/Outer area resolution
The Use second mesh size parameter lets you activate or deactivate the Inner/outer
area resolution.
The Resolution multiplier factor parameter allows you to set the second prediction
resolution compared with the initial one (factor between 2 and 10).
The Distance Threshold parameter enables you to specify the transmitter-receiver

distance (in meters, 10,000 m by default) starting from which, during a calculation,
the model changes from a grid using the transmitter’s resolution to a larger one.
The model takes into account two different resolutions, the transmitter resolution (R1)
and the resolution assigned by the user (R2). The model checks whether
the ”transmitter/receiver” distance is greater than distance threshold (the red circle
in the diagram below). If so, it calculates the considered point and transfers the
results in the neighbouring pixels. Otherwise, the model calculates each calculation
point. For example, in the diagram below, Resolution multiplier factor is set to 4.
Transmitter
Effective calculation points
Calculation points
Figure 33: MYRIAD Model - Inner/outer area resolution mode

Optimized calculation area
The Use optimized calculation area parameter allows you to determine whether the
model reduces the calculation zone behind the antenna or not (reduction is done
orthogonally at the azimuth).
If so, you have to set the recoil distance (in meters) starting from which the model no
longer calculates behind the transmitter.
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) 
Recoil distance = e  20 
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
Figure 34: MYRIAD Model - Optimized calculation area mode
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.

THE ‘RADIO’ TAB
Figure 35: MYRIAD Model - Radio tab
You can define the following MYRIAD Model radio parameters:
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.
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.
"Left" apparent width
E R
"Right" apparent width
Figure 36: MYRIAD Model - Horizontal propagation
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 Use 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 Only raster data available
Figure 37: MYRIAD Model - Use weighted tuning coefficients

Note: this parameter does not affect the tuning.

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.
Figure 38: MYRIAD Model - Depenetration

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( InsideOutside)
Loss (from RT to VT) = d * loss( Inside Inside)  Maxh  3;0  3 *
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 antenna’s 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.

Outdoor calculation pixels
Indoor calculation pixels (second)
pass)
Indoor calculation pixels (third)
pass)
Building
First pass Second pass Third pass
Figure 39: MYRIAD Model - Building penetration
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 antenna’s 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

- 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 Model-
defined 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.

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”)
Figure 40: MYRIAD Model - Morphologies generator window

Themes used by MYRIAD Model:
 No data: This must be used for each theme for which there is no information
(it means area where no data is available)
 Dense Urban: This must be used for a high density of construction (collective
and/or individual). It can be areas with dense development where built-up
features do not appear distinct from each other (heart of city for example),
areas with group of skyscrapers or high towers, etc.
 Urban: This must be used for a mean density of construction (collective
and/or individual). It can be areas with mean development where built-up
features appear distinct from each other, area with group of mean towers,
areas including buildings with large footprints, dense industrial areas, etc.
 Suburban: This must be used for a low density of construction (collective
and/or individual). It can be areas with small constructions such as
residential areas, villages, mean industrial areas, etc.
 Forest: This must be used for each area related to vegetation (high density of
trees, dense wood/vegetation area, etc.), no distinction is made between
deciduous and coniferous
 Open: This must be used for areas with little or no construction/vegetation
such as parks, agricultural fields, open spaces, sea/water areas, etc.
Note: The map each clutter class to one of the 5 basic clutter classes depends on the
project/country, the notions of dense urban, urban and suburban is not really
important, the objective is to characterize various propagation environments in order
to apply dedicated optimisation coefficients. The morphologies generator does not
apply a basic correspondence between project’s clutter classes and model’s default
clutter classes, it is a complex process which implements several mathematical
algorithms.
The Facets index parameter allows you to access to the facets 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 associated Facets index tool
( ) button.
The facets generator creates the facets on the project. These data are useful to help the
model calculate the refection for mountainous areas. You set the name of the index
file which will be generated. The facets generator automatically detects the
mountainous areas and decides if it has to generate the facets in each case.
Note: Depending to the size of the project area, the calculation time can be significant.
By default, the Height index parameter contains the height index of the project. You
have the possibility of using another height index to generate the facets on another
region.
If the project area is not hilly enough, the model will consider that the reflection
component is not significant and the facets generator will display the message: “No
mountainous environment detected. Facets will not be generated.”.

Figure 41: MYRIAD Model - Facets generator window
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.
Figure 42: MYRIAD Model - Graphs generator window
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.”.

THE ‘ADVANCED’ TAB
Figure 43: MYRIAD Model - Advanced tab

You can set the following MYRIAD Model advanced parameters:
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 transmitter’s height).

Roof distance Roof distance Facade distance
Facade
distance
Position of the station
Correction of the station
Case of a possible difference in facade Case of an impossible difference in facade

Figure 44: MYRIAD Model - Antenna correction
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-REPEATER-
LIST001.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-REPEATER-
 Fixed WIMAX case: the selected xml file is ‘WiMAX-NODE-LIST001.xml’
 Fixed WIMAX repeater case: the selected xml files are ‘WiMAX-REPEATER-
 Mobile WIMAX case: the selected xml file is ‘MOBILE-WiMAX-NODE-
LIST001.xml’
 Mobile WIMAX repeater case: the selected xml files are ‘MOBILE-WiMAX-
REPEATER-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.

Figure 45: Automatic antenna correction tool
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):
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 façade 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:
Figure 46 : MYRIAD Model - Railway vectors assignment window
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.
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.

THE ‘MULTIPATH’ TAB
Figure 47: MYRIAD Model - Multipath tab
Note: The multipath module requires a masking algorithm that can handle multiple
paths per receiver, i.e. masking each path individually and aggregate them into the
multipath variables. Hence it is not available in unmasked computation modes. It
demands a lot of processing power and random access memory. It is advised not to
launch simulations in parallel to avoid splitting the computer resources amongst
different model instances.
Advanced multipath component

The multipath tab allows you to compute three additional map types - one per
multipath variable - complementary to the main loss map. They provide statistical
spatiotemporal descriptions of the multipath components of propagation: the delay-
spread, the angle-spread and the Rice factor. They are especially suitable for dense
urban environments or any other multipath-rich environment in general. Each map
covers a square area centered on the location of the transmitter and is exported into
output folder as an independent file.
The Use multipath component parameter allows you to activate the multipath
component.

Note: You cannot enable the multipath component without any of the multipath
variables selected.
Multipath variables
The box allows you to enable the desired variables to simulate: delay-spread, angle-
spread and/or Rice factor. Unchecking all of them is equivalent to disabling the
multipath component.
Multipath prediction settings
The Distance parameter (in meters, between 10 and 500) allows you to set the width
of the simulation area, the resulting area is a square centered on the location of the
transmitter.
Note: This parameter is the one that has most impact on the amount of random
access memory needed to perform the simulation.
The Resolution parameter allows you to set the resolution used to sample the
simulation area.
The Output file format parameter allows you to define the file format used to save
the result of the simulations. The available formats are comma separated values (.csv)
and bitmap (.bmp). The generated files are saved under Output folder and are
named after the following convention:
#1_#2_#3_#4_#5_#6_#7_#8_#9.#10,
where the #n are place holders for the following information.
1. Site name (eg. Site_1),
2. Sector number (eg. 1),
3. The transmitter’s height in meters with two decimal places (eg. 25.00),
4. The, maybe negative, antenna tilt value in degrees with one decimal place (eg. -
2.0),
5. The transmitter’s azimuth in degrees with one decimal place (eg. 5.0),
6. The distance set for the simulation in meters (eg. 200),
7. The resolution set for the simulation in meters (eg. 10),
8. The receiver’s height in meters with two decimal places (eg. 1.50),
9. The name of the exported multipath variable (eg. angle_spread, delay_spread or
rice_factor),
10. The extension of the selected file format (eg. csv or bmp).
As with any other propagation result, the generated files may overwrite previous
versions if the simulation is run twice with the same settings.

The available formats are raster-like. The specifications of the written values depend
on the multipath variable being exported:
 Delay-spread, the value is given in microseconds
 Angle-spread, the value is given in 100 x degres
 Rice factor, the value is given in 100 x decibels
Note: There may be “no data” pixels when no significant multipath contributions
were found during the simulation. The way “no data” values are written depends on
the file format.
Comma-separated value (.csv)

This file format is provided as a mean to externally process the results of the
simulations. The format is self-documented as in the following example:
Version, 1.0
Bounding box (xmin ymin xmax ymax), 66120, 1212121, 66220, 1225333
Height (m), 1.5
Resolution (m), 5
Variable name, delay-spread
X, Y, Value (ns)
66125, 1212126, 0.15
66130, 1212131, na
…
Bitmap (.bmp)
Exports an image file with the same size and resolution as the simulation area. The
color legend blends from red (smallest value) to green (greatest value) in the tone-
light-saturation color-space. The legend is automatically adjusted so as to provide no
saturation at either end of the color range.
low high
No data is exported as a white pixel.

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'.

CHAPTER 5
MYRIAD MODEL TUNING

By using Tuning, you can calibrate the model (the aim of MYRIAD Model Automatic
Tuning is to reduce the effects of imperfections and to enable MYRIAD Model to be
as close to real propagation measures as possible).
Note: the number of surveys file is limited to 3000.
First, you have to add the measurement header files (*.hd) into the "Measurements
Toolbox" window under the Tools menu in ASSET.
There are 3 different modes for loading measurement headers:

 Not associated
 Associated, but header left unchanged
 Associated and header changed
For the two first modes, header data are used for tuning (including antenna
frequency and 'Connector_Loss' value).
For the 3rd mode, data of the platform are used, including antenna frequency.
Connector_Loss is set to 0. Tuning uses the EiRP (or similar for other technologies
bar GSM).
Figure 48: Measurement toolbox
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.

Figure 49: MYRIAD Model - Auto Tune window
 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.

Figure 50: MYRIAD Model - Index Optim File Configuration
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.

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 Model’s 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.

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.
Figure 51: CW Measurement Analysis - Tuning performances window
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 (un-
associated measurements for example)

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 ....................................................................................... 23
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 ........................................................ 26
Figure 17: Example of facets ............................................................................................................... 29
Figure 18: Profile example for the graphs component ................................................................... 30
Figure 19: Example of a graph (PARIS) ............................................................................................ 31
Figure 20: Examples of paths for the graphs component ............................................................... 32
Figure 21: Wave propagation simulated by the multipath component ....................................... 34
Figure 22: Extrusion of buildings ...................................................................................................... 35
Figure 23: Extrusion of bridges .......................................................................................................... 35
Figure 24: Extrusion of forests ........................................................................................................... 35
Figure 25: Extrusion of water surfaces .............................................................................................. 35
Figure 26: MYRIAD Model - Parameters tab ................................................................................... 38
Figure 27: MYRIAD Model - Additional Mobile heights window ............................................... 39
Figure 28: MYRIAD Model - Clutter settings assignment window .............................................. 40
Figure 29 : MYRIAD Model - Raster options ................................................................................... 40
Figure 30: MYRIAD Model - Vectors type assignment window ................................................... 41
Figure 31: MYRIAD Model - Time Optim tab ................................................................................. 43
Figure 32: MYRIAD Model - Radial mode ....................................................................................... 44
Figure 33: MYRIAD Model - Inner/outer area resolution mode .................................................. 45
Figure 34: MYRIAD Model - Optimized calculation area mode ................................................... 46
Figure 35: MYRIAD Model - Radio tab ............................................................................................ 47
Figure 36: MYRIAD Model - Horizontal propagation .................................................................... 48
Figure 37: MYRIAD Model - Use weighted tuning coefficients .................................................... 48
Figure 38: MYRIAD Model - Depenetration .................................................................................... 49
Figure 39: MYRIAD Model - Building penetration ......................................................................... 51
Figure 40: MYRIAD Model - Morphologies generator window ................................................... 53
Figure 41: MYRIAD Model - Facets generator window ................................................................. 55
Figure 42: MYRIAD Model - Graphs generator window ............................................................... 55
Figure 43: MYRIAD Model - Advanced tab ..................................................................................... 56
Figure 44: MYRIAD Model - Antenna correction ........................................................................... 57
Figure 45: Automatic antenna correction tool ................................................................................. 58
Figure 46 : MYRIAD Model - Railway vectors assignment window............................................ 59
Figure 47: MYRIAD Model - Multipath tab ..................................................................................... 61
Figure 48: Measurement toolbox ....................................................................................................... 67
Figure 49: MYRIAD Model - Auto Tune window ........................................................................... 68
Figure 50: MYRIAD Model - Index Optim File Configuration...................................................... 69
Figure 51: CW Measurement Analysis - Tuning performances window .................................... 71


MYRIAD MODEL User Reference Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MYRIAD MODEL User Reference Guide

Uploaded by

Copyright:

Available Formats

MYRIAD MODEL

USER REFERENCE GUIDE

MYRIAD MODEL VERSION 440

Due to a policy of continuous product development and refinement, TEOCO Ltd.

COPYRIGHT © 2019 TEOCO LTD

The TEOCO Documentation team

MYRIAD Model User Reference Guide Page 5

Page 6 MYRIAD Model User Reference Guide

INSTALLING MYRIAD MODEL WITH

MYRIAD Model User Reference Guide Page 7

Launching the installer opens the following dialogue boxes:

Figure 1: Installation of the MYRIAD Model for ASSET

The installer ensures:

Note 1: It is strongly recommended to keep the default installation directory

Page 8 MYRIAD Model User Reference Guide

Figure 2: Uninstalling the Myriad Model for ASSET

MYRIAD Model User Reference Guide Page 9

Configuring Stand-alone Licenses

Page 10 MYRIAD Model User Reference Guide

Configuring License Servers

Figure 3 : LMTools - Service/License File tab

 On the Service/License File tab, select Configuration Using Services.

MYRIAD Model User Reference Guide Page 11

 Select the Use Services check box.

Borrowing floating license

To borrow a floating license:

 On the workstation, close ASSET.

Page 12 MYRIAD Model User Reference Guide

 In the Vendor Name box, enter LICPIFT.

To return a borrowed floating license:

 On the workstation, close ASSET and LMTools.

MYRIAD Model User Reference Guide Page 13

Figure 6 : New User Variable

 In the Environment Variables dialogue box, click OK.

Page 14 MYRIAD Model User Reference Guide

To use ASSET’s distributed calculation server, you need:

MYRIAD Model licenses

Workstation machine configuration

MYRIAD Model User Reference Guide Page 15

Client machine configuration

Figure 8 : Coordinator Hostname

Page 16 MYRIAD Model User Reference Guide

Figure 9 : MYRIAD Model parameters import

MYRIAD Model User Reference Guide Page 17

THE MYRIAD MODEL

MYRIAD Model User Reference Guide Page 19

Programmable according to different needs, a propagation model is developed with

Page 20 MYRIAD Model User Reference Guide

MYRIAD Model User Reference Guide Page 21

The principle behind the profile component

Figure 11: Profile example (without vectors)

Figure 12: Profile example (with vectors)

Page 22 MYRIAD Model User Reference Guide

Figure 13: Profile construction for vectors

Management of raster geographic data

MYRIAD Model User Reference Guide Page 23

Profile extraction of raster geographic data

R Verticals and horizontals

Figure 14: Extraction of a profile

Page 24 MYRIAD Model User Reference Guide

Deygout's methods of calculating diffraction

a) The first Fresnel zone: It is generally understood that diffraction

b) The Huyghens principle: The fundamental idea behind Deygout’s method

Figure 15: Profile example of obstacles in thin ridges