Changes

[[Image:Splash-prop.jpg|right|720px]]<strong><font color="#4e1985" size="4">True 3D, Coherent, Polarimetric Ray Tracer That Simulates Very Large Urban Scenes In Just Few Minutes!</font></strong><table><tr><td>[[image:Cube-icon.png | link=Getting_Started_with_EM.Cube]] [[image:cad-ico.png | link=Building_Geometrical_Constructions_in_CubeCAD]] [[image:fdtd-ico.png | link= An EM.Terrano Primer Tempo]] [[image:static-ico.png | link=EM.Ferma]] [[image:planar-ico.png | link=EM.Picasso]] [[image:metal-ico.png | link=EM.Libera]] [[image:po-ico.png | link=EM.Illumina]]</td><tr></table>[[Image:Tutorial_icon.png|30px]] '''[[EM.Cube#EM.Terrano_Documentation | EM.Terrano Tutorial Gateway]]'''

[[Image:Back_icon.png|30px]] '''[[EM.Cube | Back to EM.Cube Main Page]]'''=== Modeling Wireless Propagation=Product Overview==

Every wireless communication system involves a transmitter that transmits some sort of signal (voice, video, data, etc===EM.), a receiver that receives and detects the transmitted signal, and a channel Terrano in which the signal is transmitted into the air and travels from the location of the transmitter to the location of the receiver. The channel is the physical medium in which the electromagnetic waves propagate. The successful design of a communication system depends on an accurate link budget analysis that determines whether the receiver receives adequate signal power to detect it against the background noise. The simplest channel is the free space. Real communication channels, however, are more complicated and involve a large number of wave scatterers. For example, in an urban environment, the obstructing buildings, vehicles and vegetation reflect, diffract or attenuate the propagating radio waves. As a result, the receiver receives a distorted signal that contains several components with different power levels and different time delays arriving from different angles.Nutshell ===

The rapid growth of wireless communications along with the high costs associated with the design and deployment of effective wireless infrastructures underline a persistent need for computer aided communication network planning toolsEM. The different rays arriving at Terrano is a receiver location create constructive and destructive interference patternsphysics-based, site-specific, wave propagation modeling tool that enables engineers to quickly determine how radio waves propagate in urban, natural or mixed environments. This is known as the multipath effectEM. This together Terrano's simulation engine is equipped with a fully polarimetric, coherent 3D ray tracing solver based on the shadowing effects caused by building obstructions lead to channel fading. The use Shooting-and-Bouncing-Rays (SBR) method, which utilizes geometrical optics (GO) in combination with uniform theory of statistical diffraction (UTD) models for prediction of fading effects is widely popular among communication system designers. These models are either based on measurement data or derived from simplistic analytical frameworks. The statistical models often exhibit considerable errors especially in areas having mixed building sizesedges. In such cases, EM.Terrano lets you analyze and resolve all the rays transmitted from one needs to perform a physics-basedore more signal sources, site-specific analysis which propagate in a real physical channel made up of the propagation environment to accurately identify buildings, terrain and establish other obstructing structures. EM.Terrano finds all the possible signal paths from the transmitter to the rays received by a receiver. This involves an electromagnetic analysis of at a particular location in the scene with all physical site and computes their vectorial field and power levels, time delays, angles of its geometrical arrival and physical detailsdeparture, etc. Using EM.Terrano you can examine the connectivity of a communication link between any two points in a real specific propagation site.

===Since its introduction in 2002, EM.Terrano has helped wireless engineers around the globe model the physical channel and the mechanisms by which radio signals propagate in various environments. EM.Terrano’s advanced ray tracing simulator finds the dominant propagation paths at each specific physical site. It calculates the true signal characteristics at the actual locations using physical databases of the buildings and terrain at a Nutshell ===given site, not those of a statistically average or representative environment. The earlier versions of EM.Terrano's SBR solver relied on certain assumptions and approximations such as the vertical plane launch (VPL) method or 2.5D analysis of urban canyons with prismatic buildings using two separate vertical and horizontal polarizations. In 2014, we introduced a new fully 3D polarimetric SBR solver that accurately traces all the three X, Y and Z components of the electric fields (both amplitude and phase) at every point inside the computational domain. Using a 3D CAD modeler, you can now set up any number of buildings with arbitrary geometries, no longer limited to vertical prismatic shapes. Versatile interior wall arrangements allow indoor propagation modeling inside complex building configurations. The most significant recent development is a multicore parallelized SBR simulation engine that takes advantage of ultrafast k-d tree algorithms borrowed from the field of computer graphics and video gaming to achieve the ultimate speed and efficiency in geometrical optics ray tracing.

EM[[Image:Info_icon.Terrano is a physics-based, site-specific, wave propagation modeling tool that enables engineers png|30px]] Click here to quickly determine how radio waves propagate in urban, natural or mixed environments. EM.Terrano's simulation engine is equipped with a fully polarimetric, coherent ray tracing solver based on the Shooting-and-Bouncing-Rays (SBR) method, which utilizes geometrical optics (GO) in combination with uniform theory of diffraction (UTD) models of building edges. EM.Terrano lets you analyze and resolve all the rays transmitted from one ore learn more signal sources, which propagate in a real physical site made up of buildings, terrain and other obstructing structures. EM.Terrano finds all about the rays received by a receiver at a particular location in the physical site and computes their power levels, time delays, angles '''[[Basic Principles of arrival, etc. Using EM.Terrano you can examine connectivity of a communication link between any two points in a real specific propagation siteSBR Ray Tracing | Basic SBR Theory]]'''.

=== Line-of-Sight vs<table><tr><td> [[Image:Manhattan1. Multipath Propagation Channel ===png|thumb|left|420px|A large urban propagation scene featuring lower Manhattan.]]</td></tr></table>

In a free-space line-of-sight (LOS) communication system, === EM.Terrano as the signal propagates directly from the transmitter to the receiver without encountering any obstacles (scatterers). Free-space line-Propagation Module of-sight channels are ideal scenarios that can typically be used to model aerial or space communication system applicationsEM.Cube ===

Click here to learn more about EM.Terrano is the theory ray tracing '''Propagation Module''' of '''[[EM.Cube]]''', a comprehensive, integrated, modular electromagnetic modeling environment. EM.Terrano shares the visual interface, 3D parametric CAD modeler, data visualization tools, and many more utilities and features collectively known as [[Free-Space Propagation ChannelBuilding_Geometrical_Constructions_in_CubeCAD | CubeCAD]] with all of [[EM.Cube]]'s other computational modules.

With the seamless integration of EM.Terrano with [[Image:multi1_tn.png|thumb|500px|A multipath propagation scene showing all the rays arriving at a particular receiverEM.Cube]]In ground-based 's other modules, you can now model complex antenna systemsin [[EM.Tempo]], the presence of the ground as a very large reflecting surface affects the signal propagation to a large extent[[EM. Along the path from a transmitter to a receiverLibera]], the signal may also encounter many obstacles and scatterers such as buildings, vegetation, etc[[EM. In an urban canyon environment with many buildings of different heights and other scatterersPicasso]] or [[EM.Illumina]], a line of sight between the transmitter and receiver generate antenna radiation patterns that can hardly be established. In such cases, the propagating signals bounce back used to model directional transmitters and forth among receivers at the building surfacestwo ends of your propagation channel. It is these reflected or diffracted signals that are often received and detected by the receiverConversely, you can analyze a propagation scene in EM. Such environments are referred to as “multipath”. The group of Terrano, collect all the rays arriving received at a specific certain receiver location experience different attenuations and different time delays. This gives rise import them as coherent plane wave sources to constructive and destructive interference patterns that cause fast fading[[EM. As a receiver moves locallyTempo]], the receiver power level fluctuates sizably due to these fading effects[[EM.Libera]], [[EM.Picasso]] or [[EM.Illumina]].

Link budget analysis for a multipath channel is a challenging task due to the large size of the computational domains involved[[Image:Info_icon. Typical propagation scenes usually involve length scales on the order of thousands of wavelengths. To calculate the path loss between the transmitter and receiver, one must solve Maxwellpng|30px]] Click here to learn more about 's equations in an extremely large space''[[Getting_Started_with_EM. Full-wave numerical techniques like the Finite Difference Time Domain (FDTD) method, which require a fine discretization of the computational domain, are therefore impractical for solving large-scale propagation problemsCube | EM. The practical solution is to use asymptotic techniques such as SBR, which utilize analytical techniques over large distances rather than a brute force discretization of the entire computational domain. Such asymptotic techniques, of course, have to compromise modeling accuracy for computational efficiencyCube Modeling Environment]]'''.

=== The Advantages & Limitations of EM.Terrano's SBR Method Solver ===

EM.Terrano provides 's SBR simulation engine utilizes an asymptotic intelligent ray tracing simulation engine algorithm that is based on a technique known as Shootingthe concept of k-anddimensional trees. A k-Bouncingd tree is a space-Rays (SBR)partitioning data structure for organizing points in a k-dimensional space. In this technique, propagating spherical waves k-d trees are modeled as ray tubes or beams particularly useful for searches that emanate from involve multidimensional search keys such as range searches and nearest neighbor searches. In a sourcetypical large radio propagation scene, travel in space, bounce there might be a large number of rays emanating from obstacles and are collected by the receivertransmitter that may never hit any obstacles. As For example, upward-looking rays propagate away from in an urban propagation scene quickly exit the computational domain. Rays that hit obstacles on their source (transmitter)path, they begin to spread (or diverge) over distance. In on the other wordshand, the cross section or footprint of a ray tube expands as a function of the distance from the source. EMgenerate new reflected and transmitted rays.Terrano uses an accurate equiThe k-angular ray generation scheme to that produces almost identical ray tubes in d tree algorithm traces all directions to satisfy energy these rays systematically in a very fast and power conservation requirementsefficient manner. Another major advantage of k-d trees is the fast processing of multi-transmitters scenes.

When EM.Terrano performs fully polarimetric and coherent SBR simulations with arbitrary transmitter antenna patterns. Its SBR simulation engine is a true asymptotic &quot;field&quot; solver. The amplitudes and phases of all the three vectorial field components are computed, analyzed and preserved throughout the entire ray hits an obstructing surfacetracing process from the source location to the field observation points. You can visualize the magnitude and phase of all six electric and magnetic field components at any point in the computational domain. In most scenes, the buildings and the ground or terrain can be assumed to be made of homogeneous materials. These are represented by their electrical properties such as permittivity &epsilon;_r and electric conductivity &sigma;. More complex scenes may involve a multilayer ground or multilayer building walls. In such cases, one can no longer use the simple reflection or more transmission coefficient formulas for homogeneous medium interfaces. EM.Terrano calculates the reflection and transmission coefficients of multilayer structures as functions of incident angle, frequency and polarization and uses them at the following phenomena may happen:respective specular points.

# Reflection from It is very important to keep in mind that SBR is an asymptotic electromagnetic analysis technique that is based on Geometrical Optics (GO) and the locally flat surface# Transmission through the locally flat surface# Uniform Theory of Diffraction (UTD). It is not a &quot;full-wave&quot; technique, and it does not provide a direct numerical solution of Maxwell's equations. SBR makes a number of assumptions, chief among them, a very high operational frequency such that the length scales involved are much larger than the operating wavelength. Under this assumed regime, electromagnetic waves start to behave like optical rays. Virtually all the calculations in SBR are based on far field approximations. In order to maintain a high computational speed for urban propagation problems, EM.Terrano ignores double diffractions. Diffractions from edges give rise to a large number of new secondary rays. The power of diffracted rays drops much faster than reflected rays. In other words, an edge between two conjoined locally flat surfaces-diffracted ray does not diffract again from another edge in EM.Terrano. However, reflected and penetrated rays do get diffracted from edges just as rays emanated directly from the sources do.

Click here to learn more about the theory of <table><tr><td> [[SBR MethodImage:Multipath_Rays.png|thumb|left|500px|A multipath urban propagation scene showing all the rays collected by a receiver.]].</td></tr></table>

=== Pros and Cons of EM.Terrano's SBR Solver =Features at a Glance ==

EM.Terrano performs fully polarimetric <ul> <li> Buildings/blocks with arbitrary geometries and coherent SBR simulations material properties</li> <li> Buildings/blocks with impenetrable surfaces or penetrable surfaces using thin wall approximation</li> <li> Multilayer walls for indoor propagation scenes</li> <li> Penetrable volume blocks with arbitrary transmitter antenna patterns. Its SBR simulation engine is a true asymptotic &quot;field&quot; solver. The amplitudes geometries and phases material properties</li> <li> Import of all the three vectorial field components are computedshapefiles and STEP, analyzed IGES and preserved throughout the entire ray tracing process from the source location to the field observation points. You can visualize the magnitude STL CAD model files for scene construction</li> <li> Terrain surfaces with arbitrary geometries and phase of all six electric material properties and magnetic field components at any point in the computational domain. In most scenesrandom rough surface profiles</li> <li> Import of digital elevation map (DEM) terrain models</li> <li> Python-based random city wizard with randomized building locations, the extents and orientations</li> <li> Python-based wizards for generation of parameterized multi-story office buildings and the ground or several terrain can be assumed to be made of homogeneous materials. These are represented by their electrical properties such as permittivity &epsilon;scene types<sub/li>r </subli> Standard half-wave dipole transmitters and electric conductivity &sigma;. More complex scenes may involve a multilayer ground or multilayer building walls. In such cases, one can no longer use receivers oriented along the simple reflection principal axes</li> <li> Short Hertzian dipole sources with arbitrary orientation</li> <li> Isotropic receivers or transmission coefficient formulas receiver grids for homogeneous medium interfaces. EM.Terrano calculates the reflection and transmission coefficients wireless coverage modeling</li> <li> Radiator sets with 3D directional antenna patterns (imported from other modules or external files)</li> <li> Full three-axis rotation of multilayer structures as functions imported antenna patterns</li> <li> Interchangeable radiator-based definition of incident angle, frequency transmitters and polarization and uses them at the respective specular points. receivers (networks of transceivers)</li></ul>

[[Image:PROP14<ul> <li> Fully 3D polarimetric and coherent Shoot-and-Bounce-Rays (1SBR).png|thumb|250px|The Navigation Tree simulation engine</li> <li> GTD/UTD diffraction models for diffraction from building edges and terrain</li> <li> Triangular surface mesh generator for discretization of EM.Terrano]]arbitrary block geometries</li>== Building <li> Super-fast geometrical/optical ray tracing using advanced k-d tree algorithms</li> <li> Intelligent ray tracing with user defined angular extents and resolution</li> <li> Ray reflection, edge diffraction and ray transmission through multilayer walls and material volumes</li> <li> Communication link analysis for superheterodyne transmitters and receivers</li> <li> 17 digital modulation waveforms for the calculation of E_b/N₀ and Bit error rate (BER)</li> <li> Incredibly fast frequency sweeps of the entire propagation scene in a Propagation Scene ==single SBR simulation run</li> <li> Parametric sweeps of scene elements like building properties, or radiator heights and rotation angles</li> <li> Statistical analysis of the propagation scene</li> <li> Polarimetric channel characterization for MIMO analysis</li> <li> "Almost real-time" Polarimatrix solver using an existing ray database</li> <li> "Almost real-time" transmitter sweep using the Polarimatrix solver</li> <li> "Almost real-time" rotational sweep for modeling beam steering using the Polarimatrix solver</li> <li> "Almost real-time" mobile sweep for modeling mobile communications between Tx-Rx pairs along a mobile path using the Polarimatrix solver</li></ul>

An outdoor propagation scene may involve several buildings modeled by impenetrable surfaces and an underlying flat ground or irregular terrain surface. An indoor propagation scene may involve several walls modeled by thin penetrable surfaces<ul> <li> Standard output parameters for received power, a ceiling path loss, SNR, E_b/N₀ and a floor arranged according to a certain building layout. You can also build mixed scenes involving both impenetrable and penetrable blocks. Your sources and observables can be placed anywhere BER at each individual receiver</li> <li> Graphical visualization of propagating rays in the scene. Your transmitters </li> <li> Received power coverage maps</li> <li> Link connectivity maps (based on minimum required SNR and receivers can be placed outdoors or indoors. A complete list BER)</li> <li> Color-coded intensity plots of the various elements polarimetric electric field distributions</li> <li> Incoming ray data analysis at each receiver including delay, angles of arrival and departure</li> <li> Cartesian plots of path loss along defined paths</li> <li> Power delay profile of a propagation scene is given in the '''Physical Structure''' section selected receiver</li> <li> Polar stem charts of EM.Terrano's Navigation Tree as follows:angles of arrival and departure of the selected receiver</li></ul>

* '''Impenetrable Surfaces''': feature reflection and diffraction of impinging rays. Rays hit the facets of this type of blocks and bounce back, but they do not penetrate the object. It is assumed that the interior of such blocks or buildings are highly absorptive.* '''Penetrable Volumes''': feature reflection, transmission and diffraction of impinging rays. These blocks are used to model propagation inside general material media or fog, rain and vegetation.* '''Penetrable Surfaces''': feature reflection, transmission and diffraction of impinging rays. These blocks represent thin surfaces that are used to model the exterior and interior walls of buildings. Rays reflect off the surface of penetrable surfaces and diffract off their edges. They also penetrate the thin surface and continue their path in the free space on the other side of the wall.* '''Terrain Surfaces''': feature reflection and optional diffraction of impinging rays. These blocks are used to provide one or more impenetrable, ground surfaces for the propagation scene. Rays simply bounce off terrain objects. * '''Base Points''': are used to define transmitter and receiver locations == Building a Propagation Scene in the sceneEM.Terrano ==

=== Adding The Various Elements of a New Propagation Scene Element ===

In A typical propagation scene in EM.Terranoconsists of several elements. At a minimum, you need a transmitter (Tx) at some location to launch rays into the scene elements like buildings, terrain objects and based points are grouped a receiver (Rx) at another location to receive and collect the incoming rays. A transmitter and a receiver together based on their typemake the simplest propagation scene, representing a free-space line-of-sight (LOS) channel. All In EM.Terrano, a transmitter represents a point source, while a receiver represents a point observable. Both a transmitter and a receiver are associated with point objects, which are one of the many types of geometric objects listed under a particular impenetrable surface group you can draw in the navigation tree share the same material properties and color and textureproject workspace. To define Your scene might involve more than one transmitter and possibly a new block group, follow these steps:large grid of receivers.

# Right click on the name A more complicated propagation scene usually contains several buildings, walls, or other kinds of the element type scatterers and wave obstructing objects. You model all of these elements by drawing geometric objects in the navigation tree and select '''Insert New Blockproject workspace or by importing external CAD models.EM.Terrano does not organize the geometric objects of your project workspace by their material composition.''' A dialog for setting up Rather, it groups the block properties opens up with geometric objects into blocks based on a default color, texture and predefined material common type (except for the case of a base point). # Specify a name for the block group and select a color or texture.# The electromagnetic model that determines ray-block interactions is specified under '''Interface Type''' or '''Surface Type'''. In most applications, you will use a standard materials interaction with known electrical properties, i.e. '''Permittivity''' (&epsilon;_r) and '''Electric Conductivity''' (&sigma;)incident rays. EM.Terrano does not handle magnetic materials.# Click offer the '''OK''' button following types of the dialog to accept the changes and close it.object blocks:

Once a new block node has been created on the navigation tree{| class="wikitable"|-! scope="col"| Icon! scope="col"| Block/Group Type ! scope="col"| Ray Interaction Type! scope="col"| Object Types Allowed! scope="col"| Notes|-| style="width:30px;" | [[File:impenet_group_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, it becomes the Sources, Devices & Other Physical Object Types#Impenetrable Surface | Impenetrable Surface]]| style="width:200px;" | Ray reflection, ray diffraction| style="width:250px;" | All solid & surface geometric objects, no curve objects| style="Activewidth:300px;" | Basic building group for outdoor scenes|-| style="width:30px;" | [[File:penet_surf_group_icon.png]]| style="width:150px;" | [[Glossary of the project workspaceEM.Cube's Materials, Sources, Devices & Other Physical Object Types#Penetrable Surface | Penetrable Surface]]| style="width:200px;" | Ray reflection, ray diffraction, which is always displayed ray transmission in bold letters. Then you can start drawing new free space| style="width:250px;" | All solid & surface geometric objects under that node, no curve objects| style="width:300px;" | Behaves similar to impenetrable surface and uses thin wall approximation for generating transmitted rays, used to model hollow buildings with ray penetration, entry and exit |-| style="width:30px;" | [[File:terrain_group_icon. Any block group png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Terrain Surface | Terrain Surface]]| style="width:200px;" | Ray reflection, ray diffraction| style="width:250px;" | All surface geometric objects, no solid or curve objects | style="width:300px;" | Behaves exactly like impenetrable surface but can be made active by right clicking on its name in change the navigation tree and selecting elevation of all the buildings and transmitters and receivers located above it|-| style="width:30px;" | [[File:penet_vol_group_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Penetrable Volume | Penetrable Volume]]| style="width:200px;" | Ray reflection, ray diffraction, ray transmission and ray attenuation inside homogeneous material media| style="width:250px;" | All solid geometric objects, no surface or curve objects| style="width:300px;" | Used to model wave propagation inside a volumetric material block, also used for creating individual solid walls and interior building partitions and panels in indoor scenes|-| style="width:30px;" | [[File:base_group_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube''Activate''' item s Materials, Sources, Devices & Other Physical Object Types#Base Location Set | Base Location Set]]| style="width:200px;" | Either ray generation or ray reception| style="width:250px;" | Only point objects| style="width:300px;" | Required for the definition of transmitters and receivers|-| style="width:30px;" | [[File:scatterer_group_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Point Scatterer Set | Point Scatterer Set]]| style="width:200px;" | Ray reception and ray scattering| style="width:250px;" | Only point, box and sphere objects| style="width:300px;" | Required for the contextual menudefinition of point scatterers as targets in a radar simulation |-| style="width:30px;" | [[File:Virt_group_icon. png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Virtual_Object_Group | Virtual Object]]| style="width:200px;" | No ray interaction| style="width:250px;" | All types of objects| style="width:300px;" | Used for representing non-physical items |}

It is recommended that you first create block groups, and then draw new objects under Click on each type to learn more about it in the active block group. However, if you start a new [[Glossary of EM.Terrano project from scratchCube's Materials, and start drawing a new object without having previously defined any block groupsSources, a new default impenetrable surface group is created and added to the navigation tree to hold your new CAD objectDevices & Other Physical Object Types]].

You can always change Impenetrable surfaces, penetrable surfaces, terrain surfaces and penetrable volumes represent all the properties objects that obstruct the propagation of electromagnetic waves (rays) in the free space. What differentiates them is the types of physical phenomena that are used to model their interaction with the impinging rays. EM.Terrano discretizes geometric objects into a block group later by accessing its property dialog from number of flat facets. The field intensity, phase and power of the contextual menureflected and transmitted rays depend on the material properties of the obstructing facet. You The specular surface of a facet can also delete be modeled locally as a block group with its simple homogeneous dielectric half-space or as a multilayer medium. In that respect, all the obstructing objects at any timesuch as buildings, walls, terrain, etc.behave in a similar way:

[[Image:PROP15* They terminate an impinging ray and replace it with one or more new rays.png|thumb|400px|EM.Terrano's Domain Settings dialog.]][[Image:PROP4* They represent a specular interface between two media of different material compositions for calculating the reflection, transmission or diffraction coefficients.png|thumb|400px|EM.Terrano's Global Ground Settings dialog.]]=== Computational Domain &amp; Global Ground ===

The SBR simulation engine requires a finite computational domainAn outdoor propagation scene typically involves several buildings modeled by impenetrable surfaces. All the stray rays that Rays hit the boundaries facets of this finite domain are terminated during impenetrable buildings and bounce back, but they do not penetrate the simulation processobject. Such rays exit the computational domain and travel to It is assumed that the infinity, with no chance interior of ever reaching any receiver in the scenesuch buildings are highly dissipative due to wave absorption or diffusion. When you define a An indoor propagation scene with various elements like buildings, typically involves several walls, terrain, etc., a dynamic domain is automatically established ceiling and displayed as a green wireframe box that surrounds floor arranged according to a certain building layout. Penetrable surfaces are used to model the entire sceneexterior and interior walls of buildings. Every time you create a new object, Rays reflect off these surfaces and diffract off their edges. They also penetrate the domain is automatically adjusted thin surface and extended continue their path in the free space on the other side of the wall. Terrain surfaces with irregular shapes or possibly random rough surfaces are used as an alternative to enclose all the objects in flat global ground. You can also build mixed scenes involving both impenetrable and penetrable blocks or irregular terrain. In the context of a propagation scene, penetrable volumes are often used to model block of rain, fog or vegetation. Base location sets are used to geometrically represent point transmitters and point receivers in the project workspace.

The size of the Ray domain Sometimes it is specified helpful to draw graphical objects as visual clues in terms of six '''Offset''' [[parameters]] along the ±X, ±Y and ±Z directions. The default value of all these six offset [[parameters]] is 10 project unitsworkspace. You can change them arbitrarilyThese non-physical objects must belong to a virtual object group. After changing these valuesVirtual objects are not discretized by EM.Terrano's mesh generator, use the '''Apply''' button to make the changes effective while the dialog is still open.You can change the size and color of they are not passed onto the domain box through the Ray Domain Settings Dialog, which can be accessed in one input data files of the following three ways:SBR simulation engine.

# Click the '''Domain''' <table><tr><td> [[FileImage:image025PROP MAN2.jpg]] button of the Simulation Toolbarpng|thumb|left|720px|An urban propagation scene generated by EM.# Select the Terrano'''Simulate''' &gt; '''Computational Domain''' &gt; '''Settingss "Random City" and "Basic Link" wizards...''' item It consists of the Simulate Menu.# Right click on the '''Ray Domain''' item 25 cubic brick buildings, one transmitter and a large two-dimensional array of the Navigation Tree and select '''Domain Settingsreceivers...''']]# Use the keyboard shortcut '''Ctrl + A'''.</td></tr></table>

Most outdoor and indoor propagation scenes include a flat ground at their bottom, which bounces incident rays back into the scene. [[EM.Cube]]'s [[Propagation Module]] provides a global flat ground at z = 0. The global ground indeed acts as an impenetrable surface that blocks the entire computational domain from the z = 0 plane downward. It is displayed as a translucent green plane at z = 0 extending downward. The color of Organizing the ground plane is always the same as the color of the ray domain. The global ground is assumed to be made of a homogeneous dielectric material with a specified permittivity &epsilon;_r and electric conductivity &sigma;. By default, a rocky ground is assumed with &epsilon;_r Propagation Scene by Block Groups == 5 and &sigma; = 0.005 S/m. You can remove the global ground, in which case, you will have a free space scene. To disable the global ground, open up the Global Ground Settings Dialog, which can be accessed by right clicking on the '''Global Ground''' item in the Navigation Tree and selecting '''Global Ground Settings... '''Remove the check mark from the box labeled '''&quot;Include Half-Space Ground (z&lt;0)&quot;''' to disable the global ground. This will also remove the green translucent plane from the bottom of your scene. You can also change the material properties of the global ground and set new values for the permittivity and electric conductivity of the impenetrable, half-space, dielectric medium. '''Do not forget to disable the global ground if you want to model a free space propagation scene.'''

=== BuildingsIn EM.Terrano, Terrain & Obstructing Blocks ===all the geometric objects associated with the various scene elements like buildings, terrain surfaces and base location points are grouped together as blocks based on their common type. All the objects listed under a particular group in the navigation tree share the same color, texture and material properties. Once a new block group has been created in the navigation tree, it becomes the "Active" group of the project workspace, which is always displayed in bold letters. You can draw new objects under the active node. Any block group can be made active by right-clicking on its name in the navigation tree and selecting the '''Activate''' item of the contextual menu.

Impenetrable, penetrable and terrain surfaces and penetrable volumes represent buildings, blocks or objects that obstruct the propagation of electromagnetic waves (rays) in the free space<table><tr><td> [[Image:PROP MAN1. What differentiates them is the types of physical phenomena that are used to model their interaction with the impinging rayspng|thumb|left|480px|EM. The field intensity, phase and power of the reflected and transmitted rays depend on the material properties of the obstructing surfaceTerrano's navigation tree. The specular surface can be modeled as a simple homogeneous dielectric half-space or as a multilayer structure. In that respect, the buildings, walls, terrain or even the global ground all behave in a similar way:]]</td></tr></table>

* They terminate an impinging ray It is recommended that you first create block groups, and replace it with one or more then draw new raysobjects under the active block group.* They represent However, if you start a specular interface between two media of different material compositions for calculating the reflectionnew EM.Terrano project from scratch, transmission and possibly diffraction coefficientsstart drawing a new object without having previously defined any block groups, a new default impenetrable surface group is created and added to the navigation tree to hold your new CAD object. You can always change the properties of a block group later by accessing its property dialog from the contextual menu. You can also delete a block group with all of its objects at any time.

[[EM{{Note|You can only import external CAD models (STEP, IGES, STL, DEM, etc.Terrano]] has generalized ) only to the concept of '''Block''' as any object that obstructs and affects radio wave propagationCubeCAD module. Rays hit You can then transfer the facets of a block and bounce off the surface of those facets or penetrate them and continue their propagationimported objects from CubeCAD to EM. Rays also get diffracted off the edges of these blocksTerrano. }}

# You can move any geometric object or a selection of objects from one block group to another. You can also transfer objects among [[EM.Cube]]'''Impenetrable Surfaces:''' Rays hit the facets of this type of blocks and bounce backs different modules. For example, but they do not penetrate the object. It is assumed that the interior you often need to move imported CAD models of such blocks terrain or buildings are highly absorptivefrom CubeCAD to EM.# '''Penetrable Surfaces:''' These blocks represent thin surfaces that are used to model Terrano. To transfer objects, first select them in the exterior and interior walls of buildings based on project workspace or select their names in the navigation tree. Then right-click on them and select <b>Move To &quotrarr;Thin Wall ApproximationModule Name &quotrarr;. Rays reflect off Object Group</b> from the surface of penetrable surfaces and diffract off their edgescontextual menu. They also penetrate such thin surfaces and continue their paths on For example, if you want to move a selected object to a block group called "Terrain_1" in EM.Terrano, then you have to select the other side of the wall.# menu item '''Terrain Surfaces:Move To &rarr; EM.Terrano &rarr; Terrain_1''' These blocks are used to provide one or more impenetrable, ground surfaces for as shown in the propagation scenefigure below. Rays simply bounce off terrain Note that you can transfer several objects. The global ground acts as a flat super-terrain that covers altogether using the bottom of the entire computational domainkeyboards's {{key|Ctrl}} or {{key|Shift}} keys to make multiple selections.

<table><tr><td> [[Image:PROP MAN3.png|thumb|left|720px|Moving the terrain model of Mount Whitney originally imported from an external digital elevation map (DEM) file to EM.CubeTerrano.]]'s </td></tr><tr><td>[[Propagation Module]] allows you to define block groups of each Image:PROP MAN4.png|thumb|left|720px|The imported terrain model of the above three typesMount Whitney shown in EM. Each block Terrano's project workspace under a terrain group has the same color or texture and its members share the same material properties: permittivity &epsilon;called "Terrain_1".]]<sub/td>r</subtr> and conductivity &sigma;. Also, all the penetrable surfaces belonging to the same block group have the same wall thickness. You can define many different block groups with certain properties and underneath each introduce many member objects with different geometrical shapes and dimensions. The </table below summarizes the characteristics of each block type:>

{| class="wikitable"|-! scope="col"| = Adjustment of Block Type! scopeElevation on Underlying Terrain Surfaces =="col"|Physical Effects! scope="col"|Admissible Object Types|-| Impenetrable Surface| Reflection, Diffraction| All Solid &amp; Surface CAD Objects|-| Penetrable Surface| Reflection, Diffraction, Transmission| All Solid &amp; Surface CAD Objects|-| Terrain Surface| Reflection| Tessellated Objects Only|}

Click here In EM.Terrano, buildings and all other geometric objects are initially drawn on the XY plane. In other words, the Z-coordinates of the local coordinate system (LCS) of all blocks are set to learn more about [[zero until you change them. Since the global ground is located a z = 0, your buildings are seated on the ground. When your propagation scene has an irregular terrain, you would want to place your buildings on the surface of the terrain and not buried under it. This can be done automatically as part of the definition of the block group. Open the property dialog of a block group and check the box labeled '''Adjust Block Types]]to Terrain Elevation'''. All the objects belonging to that block are automatically elevated in the Z direction such that their bases sit on the surface of their underlying terrain. In effect, the LCS of each of these individual objects is translated along the global Z-axis by the amount of the Z-elevation of the terrain object at the location of the LCS.

[[Image:prop_manual-12_tn.png{{Note|thumb|600px|An imported external You have to make sure that the resolution of your terrain, its variation scale and building dimensions are all comparable. Otherwise, on a rapidly varying high-resolution terrain, you will have buildings whose bottoms touch the terrain modelonly at a few points and parts of them hang in the air.]]=== Importing &amp; Exporting Terrain Models ===}}

You can import two types of terrain in EM.Terrano. The first type is &quot;'''.TRN&quot;''' terrain file, which is EM.Terrano's native terrain format. It is a basic digital elevation map with a very simple ASCII data file format<table><tr><td> [[Image:PROP MAN5. png|thumb|left|480px|The resolution property dialog of impenetrable surface showing the terrain map in the X and Y directions is specified in meters as STEPSelevation adjustment box checked. The (x, y, z) coordinates of the terrain points are then listed one point per line. The other type of terrain format supported by [[EM.Cube]] is the standard '''7.5min DEM''' file format with a '''.DEM''' file extension. </td></tr></table>

To import an external terrain model, first you have to create a terrain group node in the Navigation Tree<table><tr><td> [[Image:PROP MAN6. Right click png|thumb|left|360px|A set of buildings on the name of the an undulating terrain group in the Navigation Tree and select either '''Import Terrainwithout elevation adjustment...''' or '''Import DEM File...''' A standard ]]</td><td>[[Windows]] '''Open Dialog''' opens up, with the file type Image:PROP MAN7.png|thumb|left|360px|The set to .TRN or .DEM extensions, respectively. You can browse your folders and find of buildings on the right undulating terrain model file to importafter elevation adjustment.]]</td></tr></table>

You can also export all the terrain objects in the project workspace as a terrain file with a '''.TRN''' file extension. You can even import a DEM terrain model from an external file and then save and export it as a native terrain (.TRN) file. To export the terrain, select '''File''' &gt; '''Export...''' from == EM.Terrano's '''File Menu'''. The standard [[Windows]] Save Dialog opens up with the default file type set to '''.TRN'''. Type in a name for your new terrain file and click the '''Save''' button to export the terrain data.Ray Domain & Global Environment ==

=== Moving Objects among Block Groups Why Do You Need a Finite Computational Domain? ===

You can move one or more selected objects at The SBR simulation engine requires a time among different block groupsfinite computational domain for ray termination. The objects can be selected either in All the project workspace, or their names can be selected stray rays that emanate from a source inside this finite domain and hit its boundaries are terminated during the navigation treesimulation process. Right click on Such rays exit the highlighted selection computational domain and select '''Move To > Propagation >''' from travel to the contextual menu. This opens up another sub-menu infinity, with a list no chance of all the available block groups already defined ever reaching any receiver in your EMthe scene.Terrano projectWhen you define a propagation scene with various elements like buildings, walls, terrain, etc. Select the desired block node, a dynamic domain is automatically established and all displayed as a green wireframe box that surrounds the selected objects will move to that block groupentire scene. In the case of Every time you create a multiple selection from new object, the navigation tree using the keyboard's '''Shift Key''' or '''Ctrl Key''', make sure that you continue domain box is automatically adjusted and extended to hold enclose all the keyboard's '''Shift Key''' or '''Ctrl Key''' down while selecting the destination block group's name from objects in the contextual menuscene.

In a similar way, you can move one or more objects from an EM.Terrano block group to one of [[EM.Cube]]'s other modules. In this case, the sub-[[menus]] of the '''Move To >''' item of change the contextual menu will indicate all the [[EM.Cube]] modules that have valid groups for transfer of ray domain settings, follow the selected objects. You can also move one or more objects from [[EM.Cube]]'s other modules to a block group in EM.Terrano. procedure below:

{{Note|Except for external terrain models, you can import other external objects (STEP, IGES, STL, etc.) only to * Open the Ray Domain Settings Dialog by clicking the '''Domain'''[[CubeCADFile:image025.jpg]]button of the '''Simulate Toolbar''', or by selecting '''Menu > Simulate > Computational Domain > Settings. You need to move ..''', or by right-clicking on the imported objects form [[CubeCAD]] to EM'''Ray Domain''' item of the navigation tree and selecting '''Domain Settings.Terrano ..''' from the contextual menu, or simply using the keyboard shortcut {{key|Ctrl+A}}.* The size of the Ray domain is specified in terms of six '''Offset''' parameters along the ±X, ±Y and ±Z directions. The default value of all these six offset parameters is 10 project units. Change these values as described aboveyou like.* You can also change the color of the domain box using the {{key|Color}}button.* After changing the settings, use the {{key|Apply}} button to make the changes effective while the dialog is still open.

Like every other electromagnetic solver, EM.Terrano's SBR ray tracer requires a source for excitation and one or more observables for generation of simulation data. EM.Terrano offers several types of sources and observables for a SBR simulation. You can mix and match different source types and observable types depending on === Understanding the requirements of your modeling problem. There are two types of sources:Global Ground ===

There are four types Alternatively, you can use EM.Terrano's '''Empirical Soil Model''' to define the material properties of observablesthe global ground. This model requires a number of parameters:Temperature in &deg;C, and Volumetric Water Content, Sand Content and Clay Content all as percentage.

* [[#Defining Receiver Sets{{Note|Receiver]]* [[#Defining Field Sensors|Field Sensor]]* Far Field Radiation Pattern* Huygens SurfaceTo model a free-space propagation scene, you have to disable EM.Terrano's default global ground.}}

The simplest SBR simulation can be performed using a short dipole source with a specified field sensor plane. As an asymptotic EM solver, EM.Terrano then computes the electric and magnetic fields radiated by your dipole source in the presence of your multipath propagation environment<table><tr><td> [[Image:Global environ. png|thumb|left|720px|EM.Terrano's short dipole source and field sensor observable are very similar to those of [[EMGlobal Environment Settings dialog.Cube]]'s other computational modules. Transmitters and receivers are more complicated source and observables representing a more realistic communication link. A conventional urban propagation scene can be set up using a transmitter source and an array of receivers. </td></tr></table>

=== Hertzian Dipole Source =Defining Point Transmitters &amp; Point Receivers for Your Propagation Scene ==

[[File:PROP18(1).png|thumb|[[Propagation Module]]'s Transmitter dialog with a short dipole radiator selected]]Earlier versions === The Nature of [[EM.Cube]]'s [[Propagation Module]] used to offer an isotropic radiator with vertical or horizontal polarization as the simplest transmitter type. This release of [[EM.Cube]] has abandoned isotropic radiator transmitters because they do not exist physically in a real world. Instead, the default transmitter radiator type is now a Hertzian dipole. Note that before defining a transmitter, first you have to define a base set to establish the location of the transmitter. Most simulation scenes involve only a single transmitter. Your base set can be made up of a single point for this purpose. Transmitters & Receivers ===

To define In EM.Terrano, transmitters and receivers are indeed point radiators used for transmitting and receiving signals at different locations of the propagation scene. From a new Transmitter Setgeometric point of view, go to both transmitters and receivers are represented by point objects or point arrays. These are grouped as base locations in the '''Sources''' "Physical Structure" section of the Navigation Treenavigation tree. As radiators, right click on the '''Transmitters''' item transmitters and select '''Insert Transmitter.receivers are defined by a radiator type with a certain far-field radiation pattern.Consistent with [[EM.Cube]]''' A dialog opens up that contains a default name for the new Transmitter Set s other computational modules, transmitters are categorizes as well an excitation source, while receivers are categorized as a dropdown list labeled '''Select Base Set'''project observable. In this list you will see all the available base sets already defined other words, a transmitter is used to generate electromagnetic waves that propagate in the project workspacephysical scene. Select A receiver, on the desired base set other hand, is used to associate with compute the transmitter setreceived fields and received signal power or signal-to-noise ratio (SNR). Note that if the base set contains more than one pointFor this reason, then more than one transmitter will be created transmitters are defined and contained in your transmitter set. After defining a transmitter set, listed under the base points change their color to "Sources" sections of the transmitter colornavigation tree, which is red by defaultwhile receivers are defined and listed under the "Observables" section.

In the &quot;Radiator&quot; section of the dialog, you have two options to choose from: &quot;Short Dipole&quot; and &quot;User Defined&quot;EM. The default option is short dipole. A short dipole radiator has a '''Length'''''dl'' expressed in project units, a current '''Amplitude''' in Amperes and a current '''Phase''' in degrees. The '''Direction''' of the dipole is determined by its unit vector that has Terrano provides three X, Y and Z components. By default, a Z-directed short dipole radiator is assumed. You can change all [[parameters]] of the dipole as you wish. Keep in mind that all the transmitters belonging to the same set have parallel radiators with identical properties.types for point transmitter sets:

[[File:PROP1.png|thumb|[[Propagation Module]]'s Base Set dialog]]In order to tie up transmitters and receivers with CAD objects in the project workspace, [[EM.Cube]] uses Terrano also provides three radiator types for point objects to define transmitters and receivers. These point objects represent the base of the location of transmitters and receivers in the computational domain. Hence, they are grouped together as &quot;Base Sets&quot;. You can easily interchange the role of transmitters and receivers in a scene by switching their associated bases. The usefulness of concept of base receiver sets will become apparent later when you place transmitters or receivers on an irregular terrain and adjust their elevation. :

To create a new base set, right click on the '''Base Sets''' item #Half-wave dipole oriented along one of Navigation Tree and select '''Insert Base Set...''' A dialog for setting up the Base Set properties opens up.three principal axes#Polarization-matched isotropic radiator#User defined (arbitrary) antenna with imported far-field radiation pattern

# Enter a name for the base set and change the The default blue color if you wish. It is useful to differentiate the base sets associated with transmitters transmitter and receivers by their color.# Click the '''OK''' button to close the Base Set Dialogreceiver radiator types are both vertical (Z-directed) half-wave dipoles.

Once a base set node has been added to the Navigation Tree, it becomes the active node for new object drawing. Under base sets, you can only draw point objects. All other object creation tools There are disabled. A point is initially drawn on the XY plane. Make sure three different ways to change the Z-coordinate of your radiator, otherwise, it will fall on the global ground at z = 0. You can also create arrays of base points under the same base define a transmitter set. This is particularly useful for setting up receiver grids to compute coverage maps. Simply select a point object and click the '''Array Tool''' of '''Tools Toolbar''' or use the keyboard shortcut &quot;A&quot;. Enter values for the X, Y or Z spacing as well as the number of elements along these three directions in the Array Dialog. In most propagation scenes you are interested in 2D horizontal arrays along a fixed Z coordinate (parallel to the XY plane).receiver set:

A short dipole is the closest thing to an omni-directional radiator. The direction or orientation of the short dipole determines its polarization. In many applications, you may rather want to use === Defining a directional antenna for your transmitter. You can model a radiating structure using [[EM.Cube]]'s FDTD, Planar, MoM3D or PO modules and generate a 3D radiation pattern data file for it. These data are stored Point Transmitter Set in a specially formatted file with a &quot;'''.RAD'''&quot; extension, which contains columns of spherical &phi; and &theta; angles as well as the real and imaginary parts of the complex-valued far field components '''E_&theta;''' and '''E_&phi;'''. The &theta;- and &phi;-components of the far-zone electric field determine the polarization of the transmitting radiator. Formal Way ===

To define Transmitters act as sources in a directional propagation scene. A transmitter is a point radiator, you need to select the &quot;User Defined&quot; option in the &quot;Radiator&quot; section of the Transmitter Dialog. You can do this either at the time of creating with a transmitter set, or afterwards by opening the property dialog of the transmitter set. In the &quot;Custom Pattern [[Parameters]]&quot;, click the '''Import Pattern''' button to set the path for the radiation data file. This opens up the standard [[Windows]] Open dialog, with the default file type or extension set to &quot;.RAD&quot;. Browse your folders to find the right data file. A fully polarimetric radiation pattern file usually contains defined over the value of &quot;Total Radiated Power&quot; in its file header. This is used by default for power calculations entire 3D space in the SBR simulationstandard spherical coordinate system. However, EM.Terrano gives you can check three options for the box labeled &quot;'''Custom Power'''&quot; and enter radiator associated with a value for the point transmitter power in Watts. [[EM.Cube]] can also rotate the imported radiation pattern arbitrarily. In this case, you need to specify the '''Rotation''' angles in degrees about the X-, Y- and Z-axes. Note that these rotations are performed sequentially and in order: first a rotation about the X-axis, then a rotation about the Y-axis, and finally a rotation about the Z-axis.

Figure 1: [[Propagation Module]]'s Transmitter dialog with By default, EM.Terrano assumes that your transmitter is a user defined radiator selectedvertically polarized (Z-directed) resonant half-wave dipole antenna. This antenna has an almost omni-directional radiation pattern in all azimuth directions. It also has radiation nulls along the axis of the dipole. You can change the direction of the dipole and orient it along the X or Y axes using the provided drop-down list. The second choice of two orthogonally polarized isotropic radiators is an abstract source that is used for polarimetric channel characterization as will be discussed later.

=== Multiple Transmitters vsYou can override the default radiator option and select any other kind of antenna with a more complicated radiation pattern. For this purpose, you have to import a radiation pattern data file to EM.Terrano. You can model any radiating structure using [[EM.Cube]]'s other computational modules, [[EM.Tempo]], [[EM.Picasso]], [[EM.Libera]] or [[EM.Illumina]], and generate a 3D radiation pattern data file for it. The far-field radiation patter data are stored in a specially formatted file with a &quot;'''.RAD'''&quot; file extension. This file contains columns of spherical &phi; and &theta; angles as well as the real and imaginary parts of the complex-valued far-zone electric field components '''E_&theta;''' and '''E_&phi;'''. The &theta;- and &phi;-components of the far-zone electric field determine the polarization of the transmitting radiator. Antenna Arrays ===

[[{{Note|By default, EM.Cube]]'s SBR simulations are fully coherent and 3DTerrano assumes a vertical half-polarimetric. This means that the phase and polarization of all the rays are maintained and processed during their bounces in the scene. Your propagation scene can have more than one transmitter. During an SBR simulation, all the rays emanating from all the transmitters are traced in the propagation scene. All the received rays at a given receiver location are summed coherently and vectorially. This is based on the principle of linear superposition. All the transmitters belonging to the same wave dipole radiator for your point transmitter set have the same radiation properties. They are either parallel short dipole radiators with the same current amplitudes and phases, or parallel user defined radiators with identical radiation patterns. As these transmitters are placed at different spatial locations, they effectively form an antenna array with identical elements. The array factor is simply determined by the coordinates of the base points. If you want to have different amplitude or phases, then you need to define different transmitter sets.}}

If that radiators are indeed the elements of A transmitter set always needs to be associated with an actual antenna array existing base location set with a half wavelength spacing one or so, we recommend that you import the radiation pattern of the array structure instead and replace the whole multi-radiator system with a single more point transmitting radiator objects in your propagation scenethe project workspace. This case is usually encountered in MIMO systemsTherefore, and using an equivalent point you cannot define a transmitter is an acceptable approximation because the total size of the array aperture is usually much smaller than the dimensions of for your propagation scene and its representative length scales. In that case, you need to position the equivalent before drawing a point radiator at the radiation center of the antenna array. This depends on the physical structure of the antenna array. However, keep in mind that any reasonable guess may still provide object under a good approximation without any significant error in the received ray database location set.

Receivers act as observables in a propagation scene<table><tr><td> [[Image:Terrano L1 Fig11. png|thumb|left|480px|The objective of a SBR simulation is to calculate the far-zone electric fields and the total received power at the location of a receiver. In that sense, receivers indeed act as field observation points. You need to define at least one receiver in the scene before you can run a SBR simulation. You define the receivers of your scene by associating them with the base sets you have already defined in the project workspace. Unlike transmitters that usually one or few, a typical propagation scene may involve a large number of receivers. To generate a wireless coverage map, you need to define an array of points as your base point transmitter setdefinition dialog. ]] </td></tr></table>

To Once you define a new Receiver Settransmitter set, go to its name is added in the Observables '''Transmitters''' section of the Navigation Treenavigation tree. The color of all the base points associated with the newly defined transmitter set changes, right click on and an additional little ball with the transmitter color (red by default) appears at the location of each associated base point. You can open the property dialog of the transmitter set and modify a number of parameters including the '''ReceiversSource Power''' item in Watts and select the broadcast signal '''Insert Receiver...Phase''' A dialog opens up that contains a in degrees. The default name for the new Receiver Set as well as transmitter power level is 1W or 30dBm. There is also a dropdown list check box labeled '''Select Radiator SetUse Custom Input Power''', which is checked by default. In this list you will see all that case, the available base sets that power and phase boxes are enabled and you have already define in can change the project workspace. Select default 1W power and designate the desired base set 0&deg; phase values as the receiver setyou wish. [[EM. Note that if Cube]]'s ".RAD" radiation pattern files usually contain the base set contains more than one point, all value of them are designated as receivers. After defining a receiver set, the points change &quot;Total Radiated Power&quot; in their color to the receiver color, which is yellow by defaultfile header. The first element of the set This quantity is represented by a larger ball of calculated based on the same color indicating particular excitation mechanism that it is the selected receiver in the scene. The Receiver Set Dialog is also was used to access individual receivers of generate the set for data visualization at pattern file in the end of a simulationoriginal [[EM.Cube]] module. At When the end of an SBR simulation"Use Custom Input Power" check box is unchecked, the button labeled &quot;Show Ray Data&quot; becomes enabledEM. Clicking this button opens Terrano will use the Ray Data Dialog, where you can see a list total radiated power value of all the received rays at radiation file for the selected receiver and their computed characteristicsSBR simulation.

[[File:PROP21(1){{Note|In order to modify any of the transmitter set's parameters, first you need to select the "User Defined Antenna" option, even if you want to keep the vertical half-wave dipole as your radiator.png]] [[File:PROP22.png]]}}

Figure 1: <table><tr><td> [[Propagation Module]]'s Receiver File:NewTxProp.png|thumb|left|720px|The property dialogof a point transmitter set.]]</td></tr></table>

=== Adjustment Your transmitter in EM.Teranno is indeed more sophisticated than a simple radiator. It consists of a basic "Transmitter &amp; Receiver Elevation above Chain" that contains a Terrain Surface ===voltage source with a series source resistance, and connected via a segment of transmission line to a transmit antenna, which is used to launch the broadcast signal into the free space. The transmitter's property dialog allows you to define the basic transmitter chain. Click the {{key|Transmitter Chain}} button of the Transmitter Set dialog to open the transmitter chain dialog. As shown in the figure below, you can specify the characteristics of the baseband/IF amplifier, mixer and power amplifier (PA) including stage gains and impedance mismatch factors (IMF) as well as the characteristics of the transmission line segment that connects the PA to the antenna. Note that the transmit antenna characteristics are automatically filled using the contents of the imported radiation pattern data file. The transmitter Chain dialog also calculates and reports the "Total Transmitter Chain Gain" based on your input. When you close this dialog and return to the Transmitter Set dialog, you will see the calculated value of the Effective Isotropic Radiated Power (EIRP) of your transmitter in dBm.

In [[EM.Cube]], all the transmitters and receivers are tied up with point objects in the project workspace. These point objects are grouped and organized in base sets. When {{Note| If you move do not modify the point objects or change their coordinates, all default parameters of their associated transmitters or receivers immediately follow them to the new location. For exampletransmitter chain, you usually define a grid of receivers using a base set that 50-&Omega; conjugate match condition is made up of a uniformly spaced array of points assumed and spread them in your scene. All of these receivers have the same height because their associated base points all have power delivered to the same Zantenna will be -coordinate. When 3dB lower than your receivers are located above a flat terrain like the global ground, their Z-coordinates are equal to their height above the ground, as the terrain elevation is fixed and equal to zero everywherespecified baseband power. The same is true for transmitters, too}} <table><tr><td> [[File:NewTxChain. png|thumb|left|720px|EM.Terrano's point transmitter chain dialog.]] </td></tr></table>

=== Defining a Point Receiver Set in the Formal Way === Receivers act as observables in a propagation scene. The objective of a SBR simulation is to calculate the far-zone electric fields and the total received power at the location of a receiver. You need to define at least one receiver in the scene before you can run a SBR simulation. Similar to a transmitter, a receiver is a point radiator, too. EM.Terrano gives you three options for the radiator associated with a point receiver set: * Half-wave dipole* Polarization matched isotropic radiator* User defined antenna pattern  By default, EM.Terrano assumes that your receiver is a vertically polarized (Z-directed) resonant half-wave dipole antenna. You can change the direction of the dipole and orient it along the X or Y axes using the provided drop-down list. An isotropic radiator has a perfect omni-directional radiation pattern in all azimuth and elevation directions. An isotropic radiator doesn't exist physically in the real world, but it can be used simply as a point in space to compute the electric field.  You may also define a complicated radiation pattern for your receiver set. In that case, you need to import a radiation pattern data file to EM.Terrano similar to the case of a transmitter set.  {{Note|By default, EM.Terrano assumes a vertical half-wave dipole radiator for your point receiver set.}} Similar to transmitter sets, you define a receiver set by associating it with an existing base location set with one or more point objects in the project workspace. All the receivers belonging to the same receiver set have the same radiator type. A typical propagation scene contains one or few transmitters but usually a large number of receivers. To generate a wireless coverage map, you need to define an array of points as your base location set.  [[Image:Info_icon.png|40px]] Click here to learn how to define a '''[[Glossary_of_EM.Cube%27s_Simulation_Observables_%26_Graph_Types#Point_Receiver_Set | Point Receiver Set]]'''. <table><tr><td> [[Image:Terrano L1 Fig12.png|thumb|left|480px|The point receiver set definition dialog.]] </td></tr></table> Once you define a new receiver set, its name is added to the '''Receivers''' section of the navigation tree. The color of all the base points associated with the newly defined receiver set changes, and an additional little ball with the receiver color (yellow by default) appears at the location of each associated base point. You can open the property dialog of the receiver set and modify a number of parameters. <table><tr><td> [[File:NewRxProp.png|thumb|left|720px|The property dialog of a point receiver set.]]</td></tr></table> In the Receiver Set dialog, there is a drop-down list labeled '''Selected Element''', which contains a list of all the individual receivers belonging to the receiver set. At the end of an SBR simulation, the button labeled {{key|Show Ray Data}} becomes enabled. Clicking this button opens the Ray Data dialog, where you can see a list of all the received rays at the selected receiver and their computed characteristics.  If you choose the "user defined antenna" option for your receiver set, it indeed consists of a basic "Receiver Chain" that contains a receive antenna connected via a segment of transmission line to the low-noise amplifier (LNA) that is terminated in a matched load. The receiver set's property dialog allows you to define the basic receiver chain. Click the {{key|Receiver Chain}} button of the Receiver Set dialog to open the receiver chain dialog. As shown in the figure below, you can specify the characteristics of the LNA such as its gain and noise figure in dB as well as the characteristics of the transmission line segment that connects the antenna to the LNA. Note that the receiving antenna characteristics are automatically filled from using contents of the radiation file. You have to enter values for antenna's '''Brightness Temperature''' as well as the temperature of the transmission line and the receiver's ambient temperature. The effective '''Receiver Bandwidth''' is assumed to be 100MHz, which you can change for the purpose of noise calculations. The Receive Chain dialog calculates and reports the "Noise Power" and "Total Receiver Chain Gain" based on your input. At the end of an SBR simulation, the receiver power and signal-noise ratio (SNR) of the selected receiver are calculated and they are reported in the receiver set dialog in dBm and dB, respectively. You can examine the properties of all the individual receivers and all the individual rays received by each receiver in your receiver set using the "Selected Element" drop-down list.  <table><tr><td> [[File:NewRxChain.png|thumb|left|720px|EM.Terrano's point receiver chain dialog.]] </td></tr></table> === Modulation Waveform and Detection === EM.Terrano allows you to define a digital modulation scheme for your communication link. There are currently 17 waveforms to choose from in the receiver set property dialog: *OOK*M-ary ASK*Coherent BFSK*Coherent QFSK*Coherent M-ary FSK*Non-Coherent BFSK*Non-Coherent QFSK*Non-Coherent M-ary FSK*BPSK*QPSK*Offset QPSK*M-ary PSK*DBPSK*pi/4 Gray-Coded DQPSK*M-ary QAM*MSK*GMSK (BT = 0.3) In the above list, you need to specify the '''No. Levels (M)''' for the Mary modulation schemes, from which the '''No. Bits per Symbol''' is determined. You can also define a bandwidth for the signal, which has a default value of 100MHz. Once the SNR of the signal is found, given the specified modulation scheme, the E_b/N₀ parameter is determined, from which the bit error rate (BER) is calculated. The Shannon – Hartley Equation estimates the channel capacity: <math> C = B \log_2 \left( 1 + \frac{S}{N} \right) </math> where B in the bandwidth in Hz, and C is the channel capacity (maximum data rate) expressed in bits/s. The spectral efficiency of the channel is defined as <math> \eta = \log_2 \left( 1 + \frac{S}{N} \right) </math> The quantity E_b/N₀ is the ratio of energy per bit to noise power spectral density. It is a measure of SNR per bit and is calculated from the following equation: <math> \frac{E_b}{N_0} = \frac{ 2^\eta - 1}{\eta} </math> where &eta; is the spectral efficiency.  The relationship between the bit error rate and E_b/N₀ depends on the modulation scheme and detection type (coherent vs. non-coherent). For example, for coherent QPSK modulation, one can write: <math> P_b = 0.5 \; \text{erfc} \left( \sqrt{ \frac{E_b}{N_0} } \right) </math> where P_b is the bit error rate and erfc(x) is the complementary error function: <math> \text{erfc}(x) = 1-\text{erf}(x) = \frac{2}{\sqrt{\pi}} \int_{x}^{\infty} e^{-t^2} dt </math> The '''Minimum Required SNR''' parameter is used to determine link connectivity between each transmitter and receiver pair. If you check the box labeled '''Generate Connectivity Map''' in the receiver set property dialog, a binary map of the propagation scene is generated by EM.Terrano, in which one color represents a closed link and another represent no connection depending on the selected color map type of the graph. EM.Terrano also calculates the '''Max Permissible BER''' corresponding to the specified minimum required SNR and displays it in the receiver set property dialog. === A Note on EM.Terrano's Native Dipole Radiators === When you define a new transmitter set or a new receiver set, EM.Terrano assigns a vertically polarized half-wave dipole radiator to the set by default. The radiation pattern of this native dipole radiators is calculated using well-know expressions that are derived based on certain assumptions and approximations. For example, the far-zone electric field of a vertically-polarized dipole antenna can be expressed as:  <math> E_\theta(\theta,\phi) \approx j\eta_0 I_0 \frac{e^{-jk_0 r}}{2\pi r} \left[ \frac{\text{cos} \left( \frac{k_0 L}{2} \text{cos} \theta \right) - \text{cos} \left( \frac{k_0 L}{2} \right) }{\text{sin}\theta} \right] </math> <math> E_\phi(\theta,\phi) \approx 0 </math> where k₀ = 2&pi;/&lambda;₀ is the free-space wavenumber, &lambda;₀ is the free-space wavelength, &eta;₀ = 120&pi; &Omega; is the free-space intrinsic impedance, I₀ is the current on the dipole, and L is the length of the dipole. The directivity of the dipole antenna is given be the expression: <math> D_0 \approx \frac{2}{F_1(k_0L) + F_2(k_0L) + F_3(k_0L)} \left[ \frac{\text{cos} \left( \frac{k_0 L}{2} \text{cos} \theta \right) - \text{cos} \left( \frac{k_0 L}{2} \right) }{\text{sin}\theta} \right]^2 </math> with  <math> F_1(x) = \gamma + \text{ln}(x) - C_i(x) </math> <math> F_2(x) = \frac{1}{2} \text{sin}(x) \left[ S_i(2x) - 2S_i(x) \right] </math> <math> F_3(x) = \frac{1}{2} \text{cos}(x) \left[ \gamma + \text{ln}(x/2) + C_i(2x) - 2C_i(x) \right] </math>  where &gamma; = 0.5772 is the Euler-Mascheroni constant, and C_i(x) and S_i(x) are the cosine and sine integrals, respectively:  <math> C_i(x) = - \int_{x}^{\infty} \frac{ \text{cos} \tau}{\tau} d\tau </math> <math> S_i(x) = \int_{0}^{x} \frac{ \text{sin} \tau}{\tau} d\tau </math>  In the case of a half-wave dipole, L = &lambda;₀/2, and D₀ = 1.643. Moreover, the input impedance of the dipole antenna is Z_A = 73 + j42.5 &Omega;. These dipole radiators are connected via 50&Omega; transmission lines to a 50&Omega; source or load. Therefore, there is always a certain level of impedance mismatch that violates the conjugate match condition for maximum power.  <table><tr><td> [[File:Dipole radiators.png|thumb|720px|EM.Terrano's native half-wave dipole transmitter and receiver.]] </td></tr></table> On the other hand, we you specify a user-defined antenna pattern for the transmitter or receiver sets, you import a 3D radiation pattern file that contains all the values of E_&theta; and E_&phi; for all the combinations of (&theta;, &phi;) angles. Besides the three native dipole radiators, [[EM.Cube]] also provides 3D radiation pattern files for three X-, Y- and Z-polarized half-wave resonant dipole antennas. These pattern data were generated using a full-wave solver like [[EM.Libera]]'s wire MOM solver. The names of the radiation pattern files are:  * DPL_STD_X.RAD* DPL_STD_Y.RAD* DPL_STD_Z.RAD and they are located in the folder "\Documents\EMAG\Models" on your computer. Note that these are full-wave simulation data and do not involve any approximate assumptions. To use these files as an alternative to the native dipole radiators, you need to select the '''User Defined Antenna Pattern''' radio button as the the radiator type in the transmitter or receiver set property dialog. === A Note on the Rotation of Antenna Radiation Patterns === EM.Terrano's Transmitter Set dialog and Receiver Set dialog both allow you to rotate an imported radiation pattern. In that case, you need to specify the '''Rotation''' angles in degrees about the X-, Y- and Z-axes. It is important to note that these rotations are performed sequentially and in the following order: first a rotation about the X-axis, then a rotation about the Y-axis, and finally a rotation about the Z-axis. In addition, all the rotations are performed with respect to the "rotated" local coordinate systems (LCS). In other words, the first rotation with respect to the local X-axis transforms the XYZ LCS to a new primed X^&prime;Y^&prime;Z^&prime; LCS. The second rotation is performed with respect to the new Y^&prime;-axis and transforms the X^&prime;Y^&prime;Z^&prime; LCS to a new double-primed X^{&prime;&prime;}Y^{&prime;&prime;}Z^{&prime;&prime;} LCS. The third rotation is finally performed with respect to the new Z^{&prime;&prime;}-axis. The figures below shows single and double rotations.  <table><tr><td> [[File:PROP22B.png|thumb|300px|The local coordinate system of a linear dipole antenna.]] </td><td> [[File:PROP22C.png|thumb|600px|Rotating the dipole antenna by +90&deg; about the local Y-axis.]] </td></tr></table><table><tr><td> [[File:PROP22D.png|thumb|720px|Rotating the dipole antenna by +90&deg; about the local X-axis and then by -45&deg; by the local Y-axis.]] </td></tr></table> === Adjustment of Tx/Rx Elevation above a Terrain Surface === When your transmitters or receivers are located above a flat terrain like the global ground, their Z-coordinates are equal to their height above the ground, as the terrain elevation is fixed and equal to zero everywhere. In many propagation modeling problems, your transmitters and receivers may be located above an irregular terrain with varying elevation across the scene. In that case, you may want to place your transmitters or receivers at a certain height above the underlying ground. The Z-coordinate of a transmitter or receiver is now the sum of the terrain elevation at the base point and the specified height. [[EM.Cube]] Terrano gives you the option to adjust the transmitter and receiver sets to the terrain elevation. This is done for individual transmitter sets and individual receiver sets. At the top of the Transmitter Dialog there is a check box labeled &quot;'''Adjust Tx Sets to Terrain Elevation'''&quot;. Similarly, at the top of the Receiver Dialog there is a check box labeled &quot;'''Adjust Rx Sets to Terrain Elevation'''&quot;. These boxes are unchecked by default. As a result, your transmitter sets or receiver sets coincide with their associated base points in the project workspace. If you check these boxes and place a transmitter set or a receiver set above an irregular terrain, the transmitters or receivers are elevated from the location of their associated base points by the amount of terrain elevation as can be seen in the figure below.

<table><tr><td> [[FileImage:prop_txrx1_tnPROP MAN8.png|400px]] [[File:prop_txrx2_tnthumb|left|640px|A transmitter (red) and a grid of receivers (yellow) adjusted above a plateau terrain surface. The underlying base point sets (blue and orange dots) associated with the adjusted transmitters and receivers on the terrain are also visible in the figure.png|400px]]</td></tr></table>

Figure: Transmitters and receivers adjusted above an uneven terrain and their associated base sets== Discretizing the Propagation Scene in EM.Terrano ==

=== Defining Field Sensors Why Do You Need to Discretize the Scene? ===

[[File:PMOM90EM.png|thumb|[[Propagation Module]]Terrano's Field Sensor dialog]]As an asymptotic electromagnetic field SBR solver, the SBR simulation engine can compute the electric and magnetic field distributions in uses a specified plane. In order to view these field distributions, you must first define field sensor observables before running the SBR simulation. To do that, right click on the '''Field Sensors''' item method known as Geometrical Optics (GO) in conjunction with the '''Observables''' section Uniform Theory of Diffraction (UTD) to trace the Navigation Tree and select '''Insert New Observable...'''. The Field Sensor Dialog opens up. At rays from their originating point at the top of the dialog and in the section titled '''Sensor Plane Location''', first you need source to set the plane of field calculationindividual receiver locations. In the dropdown box labeled '''Direction''', you have three options X, Y, Rays may hit obstructing objects on their way and Zget reflected, representing the&quot;normals&quot; to the XY, YZ and ZX planes, respectivelydiffracted or transmitted. The default direction is Z, iEM.e. XY plane parallel to the substrate layers. In the three boxes labeled Terrano'''Coordinates''', you set the coordinates of the center of the planes SBR solver can only handle diffraction off linear edges and reflection from and transmission through planar interfaces. Then, you specify When an incident ray hits the '''Size''' surface of the plane in project unitsobstructing object, and finally set a local planar surface assumption is made at the '''Number of Samples''' along the two sides of the sensor planespecular point. The larger assumptions of linear edges and planar facets obviously work in the number case of samples, the smoother the near field map will appeara scene with cubic buildings and a flat global ground.

In the section titled Output Settingsmany practical scenarios, you can also select the field map type from two options: '''Confetti''' and '''Cone'''. The former produces an intensity plot for field amplitude and phasehowever, while your buildings may have curved surfaces, or the latter generates a 3D vector plotterrain may be irregular. In the confetti case, EM.Terrano allows you have an option to check the box labeled '''Data Interpolation'''draw any type of surface or solid geometric objects such as cylinders, which creates a smooth cones, etc. under impenetrable and blended (digitally filtered) mappenetrable surface groups or penetrable volumes. In the cone case, you can set the size of the vector cones that represent the field directionEM. At the end Terrano's mesh generator creates a triangular surface mesh of a sweep simulation, multiple field map are produced and added to all the Navigation Tree. You can animate these maps. Howeverobjects in your propagation scene, during the sweep only one field type which is stored, either the E-field or H-fieldcalled a facet mesh. You can choose Even the field type for multiple plots walls of cubic buildings are meshed using the radio buttons in the section titled '''Field Display - Multiple Plots'''triangular cells. The default choice is the E-fieldThis enables EM.Terrano to properly discretize composite buildings made of conjoined cubic objects.

Once you close the Field Sensor dialogUnlike [[EM.Cube]]'s other computational modules, its name is added under the density or resolution of EM.Terrano'''Field Sensors''' node s surface mesh does not depend on the operating frequency and is not expressed in terms of the Navigation Treewavelength. At the end The sole purpose of a SBR simulationEM.Terrano's facet mesh is to discretize curved and irregular scatterers into flat facets and linear edges. Therefore, geometrical fidelity is the field sensor nodes in only criterion for the Navigation Tree become populated by the magnitude and phase plots quality of the three vectorial components a facet mesh. It is important to note that discretizing smooth objects using a triangular surface mesh typically creates a large number of small edges among the electric ('''E''') facets that are simply mesh artifacts and magnetic ('''H''') field as well should not be considered as diffracting edges. For example, each rectangular face of a cubic building is subdivided into four triangles along the total electric and magnetic fields defined in two diagonals. The four internal edges lying inside the following manner:face are obviously not diffracting edges. A lot of subtleties like these must be taken into account by the SBR solver to run accurate and computationally efficient simulations.

:<math> \mathbf{|E_{tot}|} = \sqrt{|E_x|^2 + |E_y|^2 + |E_z|^2} </math>== Generating the Facet Mesh ===

:<math> \mathbf{|H_{tot}|} = \sqrt{|H_x|^2 + |H_y|^2 + |H_z|^2} </math><!--[[File:PMOM88You can view and examine the discretized version of your scene's objects as they are sent to the SBR simulation engine.png]]You can adjust the mesh resolution and increase the geometric fidelity of discretization by creating more and finer triangular facets. On the other hand, you may want to reduce the mesh complexity and send to the SBR engine only a few coarse facets to model your buildings. The resolution of EM.Terrano's facet mesh generator is controlled by the '''Cell Edge Length''' parameter, which is expressed in project length units. The default mesh cell size of 100 units might be too large for non-->flat objects. You may have to set a smaller cell edge length in EM.Terrano's Mesh Settings dialog, along with a lower curvature angle tolerance value to capture the curvature of your curved structures adequately.

Coming Soon[[Image:Info_icon.png|30px]] Click here to learn more about '''[[Preparing_Physical_Structures_for_Electromagnetic_Simulation#Working_with_EM.Cube.27s_Mesh_Generators | Working with Mesh Generator]]'''.

=== <table><tr><td> [[Image:UrbanCanyon2.png|thumb|left|640px|The Need For Discretization Of Propagation Scene ===facet mesh of the buildings in the urban propagation scene generated by EM.Terrano's Random City wizard with a cell edge length of 100m.]] </td></tr><tr><td> [[Image:UrbanCanyon3.png|thumb|left|640px|The facet mesh of the buildings in the urban propagation scene generated by EM.Terrano's Random City wizard with a cell edge length of 10m.]] </td></tr></table>

In a typical SBR simulation, a ray is traced from the location of the source until it hits a scatterer. The [[SBR Method|SBR method]] assumes that the ray hits either a flat facet of the scatterer or one of its edges. In the case of hitting a flat facet, the specular point is used to launch new reflected and transmitted rays. The surface of the facet is treated as an infinite dielectric medium interface, at which the reflection and transmission coefficients are calculated. In the case of hitting an edge, new diffracted rays are generated == Running Ray Tracing Simulations in the scene. However, only those who reach a nearby receiver in their line of sight are ever taken into account. In other words, diffractions are treated locallyEM.Terrano ==

[[EM.Cube]]'s [[Propagation Module]] allows you to draw any type Terrano provides a number of surface different simulation or solid CAD objects under impenetrable and penetrable surface groups. Some of these objects have flat faces such as boxes, pyramids, rectangle or triangle strips, etc. Some others contain curved surfaces or curved boundaries such as cylinders, cones, etc. All the non-flat surfaces have to be discretized in the form of a collection of smaller flat facets. [[EM.Cube]] uses a triangular surface mesh generator to discretize the penetrable and impenetrable [[Surface Objects|surface objects]] of your propagation scene. This mesh generator is very similar to the ones used in [[EM.Cube]]'s two other modulessolver types: MoM3D and Physical Optics (PO).

You can build a variety of surface and [[Solid Objects|solid objects]] using [[EM.Cube]]'s native &quot;Curve&quot; CAD objects like lines, polylines, circles, etc. You can use tools like Extrude, Loft, Strip* 3D Field Solver* SBR Channel Analyzer* Log-Sweep, Pipe-Sweep, etc. to transform curves into surface or [[Solid Objects|solid objects]]. '''However, keep in mind that all the &quot;Curve&quot; CAD objects are ignored by the SBR mesh generator and are therefore not sent to the simulation engine.'''Haul Channel Analyzer* Communication Link Solver* Radar Link Solver

You can view and examine the discretized version of your scene objects as they are sent to the === Running a Single-Frequency SBR simulation engine. To view the mesh, click the '''Mesh''' [[File:mesh_tool.png]] button of the Simulate Toolbar or select '''Simulate &gt; Discretization &gt; Show Mesh''', or use the keyboard shortcut '''Ctrl+M'''. A triangular surface mesh of your physical structure appears in the project workspace. In this case, [[EM.Cube]] enters it mesh view mode. You can perform view operations like rotate view, pan, zoom, etc. But you cannot select objects, or move them or edit their properties. To get out of the Mesh View and return to [[EM.Cube]]'s Normal View, press the '''Esc Key''' of the keyboard, or click the Mesh button of the Simulate Toolbar once again, or go to the Simulate Menu and deselect the '''Discretization &gt;''' '''Show Mesh''' item.Analysis ===

You can adjust the mesh resolution and increase the geometric fidelity of discretization by creating more and finer triangular facets. On the other hand, you may want to reduce the mesh complexity and send to the SBR engine only a few coarse facets to model your buildings. To adjust the mesh resolution, open the Mesh Settings Dialog by clicking Its main solver is the '''Mesh Settings3D SBR Ray Tracer''' [[File:mesh_settings.png]] button of the Simulate Toolbar or select '''Simulate &gt; Discretization &gt;''' '''Mesh SettingsOnce you have set up your propagation scene in EM.Terrano and have defined sources/transmitters and observables/receivers for your scene, you are ready to run a SBR ray tracing simulation.You set the simulation mode in EM.Terrano'''s simulation run dialog. This dialog provides A single-frequency SBR analysis is a single [[parameters]]: '''Edge Length'''., which has a default value of 100 project units. If you are already in the Mesh View Mode -run simulation and open the Mesh Settings Dialog, you can see the effect simplest type of changing the edge length using the '''Apply''' buttonray tracing simulation in EM. Click OK to close Terrano. It involves the dialog.following steps:

* Set the units of your project and the frequency of operation. Note that unlike [[EM.Cube]]'s other computational modules that express the default mesh density based on the wavelengthproject unit is '''millimeter'''. Wireless propagation problems usually require meter, mile or kilometer as the resolution of the SBR mesh generator is expressed in project length unitsunit. The * Create the blocks and draw the buildings at the desired locations.* Keep the default edge length value of 100 units might be too large ray domain and accept the default global ground or change its material properties.* Define an excitation source and observables for non-flat objectsyour project. You may have * If you intend to use a lower value to capture the curvature of transmitters and receivers in your curved structures adequatelyscene, first define the required base sets and then define the transmitter and receiver sets based on them.* Run the SBR simulation engine.* Visualize the coverage map and plot other data.

You can access EM.Terrano's Simulation Run dialog by clicking the '''Run''' [[File:prop_manual-29run_icon.png]]button of the '''Simulate Toolbar''' or by selecting '''Simulate &rarr; Run...''' or using the keyboard shortcut {{key|Ctrl+R}}. When you click the {{key|Run}} button, a new window opens up that reports the different stages of the SBR simulation and indicates the progress of each stage. After the SBR simulation is successfully completed, a message pops up and prompts the completion of the process.

Figure 1: <table><tr><td> [[Propagation Module]]Image:Terrano L1 Fig16.png|thumb|left|480px|EM.Terrano's Mesh Settings simulation run dialog.]] </td></tr></table>

In [[EM.Cube]], terrain objects are represented by and saved as special &quot;Tessellated&quot; objects with quadrilateral cells. This is true of terrain objects that you create yourself using [[EM.Cube]]'s Terrain Generator as well as all the terrain objects that you import from external files to your project. The center of each cell represents the terrain elevation at that point. Tessellated objects are considered as discretized objects by [[EM.Cube]] and they are not meshed one more time by === Changing the SBR mesh generator. Each quadrilateral cell is divided into two triangular cells before being passed to the SBR simulation engine. Therefore, when using [[EM.Cube]]'s Terrain Generator to create a new terrain object, you have to pay special attention to the resolution of the terrain object as it determines the total number of terrain facets sent to the simulation engine. A high resolution terrain, although looking better and more realistic, may easily lead to an enormous computational problem.Engine Settings ===

You There are a number of SBR simulation settings that can use [[be accessed and changed from the Ray Tracing Engine Settings Dialog. To open this dialog, click the button labeled {{key|Settings}} on the right side of the '''Select Simulation or Solver Type''' drop-down list in the Run Dialog. EM.Cube]]Terrano's &quot;Polymesh&quot; tool SBR simulation engine allows you to discretize solid and surface CAD objectsseparate the physical effects that are calculated during a ray tracing process. You can manually control selectively enable or disable '''Reflection/Transmission''' and '''Edge Diffraction''' in the mesh characteristics "Ray-Block Interactions" section of polymesh objects including inserting new nodes on faces and edges or deleting existing nodesthis dialog. In additionBy default, [[EM.Cube]]'s Solid Generator ray reflection and Surface Generator tools create ploymesh solids transmission and surfaces, respectively. Like tessellated object, polymesh objects edge diffraction effects are also considered as discretized objects by [[EMenabled.Cube]] Separating these effects sometimes help you better analyze your propagation scene and they are not meshed again by understand the SBR mesh generatorimpact of various blocks in the scene.

=== SBR Mesh Rules EM.Terrano allows a finite number of ray bounces for each original ray emanating from a transmitter. This is very important in situations that may involve resonance effects where rays get trapped among multiple surfaces and may bounce back and forth indefinitely. This is set using the box labeled &ampquot; Considerations ==='''Max No. Ray Bounces'''&quot;, which has a default value of 10. Note that the maximum number of ray bounces directly affects the computation time as well as the size of output simulation data files. This can become critical for indoor propagation scenes, where most of the rays undergo a large number of reflections. Two other parameters control the diffraction computations: '''Max Wedge Angle''' in degrees and '''Min Edge Length''' in project units. The maximum wedge angle is the angle between two conjoined facets that is considered to make them almost flat or coplanar with no diffraction effect. The default value of the maximum wedge angle is 170&deg;. The minimum edge length is size of the common edge between two conjoined facets that is considered as a mesh artifact and not a real diffracting edge. The default value of the minimum edge length is one project units.

Coming Soon<table><tr><td> [[Image:PROP MAN11.png|thumb|left|720px|EM.Terrano's SBR simulation engine settings dialog.]] </td></tr></table>

[[EMYou can also set the '''Ray Angular Resolution''' of the transmitter rays in degrees.Cube]]By default, every transmitter emanates equi-angular ray tubes at a resolution of 1 degree. Lower angular resolutions larger than 1° speed up the SBR simulation significantly, but they may compromise the accuracy. Higher angular resolutions less than 1° increase the accuracy of the simulating results, but they also increase the computation time. The SBR Engine Settings dialog also displays the 's [[Propagation Module]] offers three types ''Recommended Ray Angular Resolution''' in degrees in a grayed-out box. This number is calculated based on the overall extents of your computational domain as well as the SBR mesh resolution. To see this value, you have to generate the SBR mesh first. Keeping the angular resolution of your project above this threshold value makes sure that the small mesh facets at very large distances from the source would not miss any impinging ray tracing simulations:tubes during the simulation.

An SBR analysis is At the simplest end of a ray tracing simulation , the electric field of each individual ray is computed and involves reported. By default, the actual received ray fields are reported, which are independent of the radiation pattern of the receive antennas. EM.Terrano provides a check box labeled "Normalize ray's E-field based on receiver pattern", which is unchecked by default. If this box is checked, the field of each ray is normalized so as to reflect that effect of the receiver antenna's radiation pattern. The received power of each ray is calculated from the following stepsequation:

# Set the unit of project scene and the frequency of operation. Note that [[EM.Cube]]'s default project unit is millimeter. When working with the [[Propagation Module]], pay attention to the project unit. Radio propagation problems usually require meter, mile or kilometer as the project unit.# Create the blocks and draw the buildings at the desired locations.# Keep the default <math> P_{ray domain and accept the default global ground or change its material properties.# Define the base sets (at least one for the transmitter and one for the receiver).# Define the transmitter and receiver(s) using the available base sets.# Run the SBR simulation engine.# Visualize the coverage map and plot other data.} = \frac{ | \mathbf{E_{norm}} |^2 }{2\eta_0} \frac{\lambda_0^2}{4\pi} </math>

You It can access be seen that if the [[Propagation Module]]ray's run dialog by clicking E-field is not normalized, the '''Run''' [[File:run_icon.png]] button of the '''Simulate Toolbar''' or by selecting '''Simulate &gt; Run...''' or using the keyboard shortcut '''Ctrl+R'''. When you click the '''Run''' button, a new window opens up computed ray power will correspond to that reports the different stages of the SBR simulation and indicates the progress of each stage. After the SBR simulation is successfully completed, a message pops up and prompts the completion of the processpolarization matched isotropic receiver.

Figure 1: [[Propagation Module]]'s Simulation Run dialogIn a 3D SBR simulation, a transmitter shoots a large number of rays in all directions. The electric fields of these rays are polarimetric and their strength and polarization are determined by the designated radiation pattern of the transmit antenna. The rays travel in the propagation scene and bounce from the ground and buildings or other scatterers or get diffracted at the building edges until they reach the location of the receivers. Each individual ray has its own vectorial electric field and power. The electric fields of the received rays are then superposed coherently and polarimetrically to compute the total field at the receiver locations. The designated radiation pattern of the receivers is then used to compute the total received power by each individual receiver.

There are To perform a number polarimatric channel characterization of SBR simulation settings that can be accessed and changed from the SBR Settings Dialogyour propagation scene, open EM. To open this Terrano's Run Simulation dialog, click the button labeled and select '''SettingsChannel Analyzer''' on the right side of from the drop-down list labeled '''Select EngineSimulation or Solver Type''' dropdown list in . At the end of the Run Dialog. [[EM.Cube]]'s SBR simulation engine allows you to separate the physical effects that are calculated during , a large ray tracing processdatabase is generated with two data files called "sbr_channel_matrix. You can selectively enable or disable '''Ray Reflection''', '''Ray Transmission''' DAT" and '''Ray Diffraction'''"sbr_ray_path.DAT". By defaultThe former file contains the delay, angles of arrival and departure and complex-valued elements of the channel matrix for all three effects are checked the individual rays that leave each transmitter and included in the computationsarrive at each receiver. Separating these effects sometimes help you better analyze your propagation scene and understand The latter file contains the impact geometric aspects of various blocks in the sceneeach ray such as hit point coordinates.

As rays travel in After EM.Terrano's channel analyzer generates a ray database that characterizes your propagation channel polarimetrically for all the scene combinations of transmitter and bounce from surfacesreceiver locations, they lose their power and their amplitudes diminish. From a practical point ray tracing solution of view, only rays that have power above the receiver sensitivity threshold propagation problem can readily be effectively received. Therefore, all found in almost real time by incorporating the rays whose power fall below a specified power threshold are discardedeffects of the radiation patterns of transmit and receive antennas. The This is done using the '''Ray Power ThresholdPolarimatrix Solver''' , which is specified in dBm and has a default value the third option of the drop-100dBm. Keep down list labeled '''Select Simulation or Solver Type''' in mind that the value EM.Terrano's Run Simulation dialog. The results of this threshold directly affects the accuracy of the simulation results as well as the size Polarimatrix and 3D SBR solvers must be identical from a theoretical point of view. However, there might be small discrepancies between the output data filetwo solutions due to roundoff errors.

You Using the Polarimatrix solver can also set the '''Angular Resolution''' lead to a significant reduction of the transmitter rays total simulation time in degrees. By default, every transmitter emanates equi-angular ray tubes at sweep simulations that involve a resolution large number of 1 degreetransmitters and receivers. Lower angular resolutions larger than 1° speed up the SBR Certain simulation significantly, but they may compromise the accuracymodes of EM. Higher angular resolutions less than 1° increase Terrano are intended for the accuracy of Polarimatrix solver only as will be described in the simulating results, but they also increase the computation timenext section.

[[File:PROP13{{Note| In order to use the Polarimatrix solver, you must first generate a ray database of your propagation scene using EM.png]]Terrano's Channel Analyzer.}}

Figure 1: [[Propagation Module]]=== EM.Terrano's SBR Engine Settings dialog.Simulation Modes ===

If {| class="wikitable"|-! scope="col"| Simulation Mode! scope="col"| Usage! scope="col"| Which Solver?! scope="col"| Frequency ! scope="col"| Restrictions|-| style="width:120px;" | [[#Running a Single-Frequency SBR Analysis | Single-Frequency Analysis]]| style="width:180px;" | Simulates the associated radiator set is isotropicpropagation scene "As Is"| style="width:150px;" | SBR, so will be Channel Analyzer, Polarimatrix, Radar Simulator| style="width:120px;" | Runs at the transmitter setcenter frequency fc| style="width:300px;" | None|-| style="width:120px;" | [[Parametric_Modeling_%26_Simulation_Modes_in_EM. By default, an isotropic transmitter has vertical polarizationCube#Running_Frequency_Sweep_Simulations_in_EM. You can use Cube | Frequency Sweep]]| style="width:180px;" | Varies the '''Polarization''' radio button to select one operating frequency of the two optionsray tracer | style="width: '''Vertical''' or '''Horizontal'''150px;" | SBR, Channel Analyzer, Polarimatrix, Radar Simulator| style="width:120px;" | Runs at a specified set of frequency samples| style="width:300px;" | None|-| style="width:120px;" | [[Parametric_Modeling_%26_Simulation_Modes_in_EM. If Cube#Running_Parametric_Sweep_Simulations_in_EM.Cube | Parametric Sweep]]| style="width:180px;" | Varies the associated radiator set consists value(s) of '''Short Dipole''' one or '''User Defined''' radiatorsmore project variables| style="width:150px;" | SBR| style="width:120px;" | Runs at the center frequency fc| style="width:300px;" | Requires definition of sweep variables, it is indicated in works only with SBR solver as the physical scene may change during the sweep |-| style="width:120px;" | [[#Transmitter_Sweep | Transmitter Sweep]]| style="width:180px;" | Activates two or more transmitters sequentially with only one transmitter property dialog. In broadcasting at each simulation run | style="width:150px;" | Polarimatrix| style="width:120px;" | Runs at the case of a short dipole radiatorcenter frequency fc| style="width:300px;" | Requires at least two transmitters in the scene, you can set a value for works only with Polarimatrix solver and requires an existing ray database|-| style="width:120px;" | [[#Rotational_Sweep | Rotational Sweep]]| style="width:180px;" | Rotates the dipole current in Amperes. The radiation resistance pattern of a short dipole the transmit antenna(s) sequentially to model beam steering | style="width:150px;" | Polarimatrix| style="width:120px;" | Runs at the center frequency fc| style="width:300px;" | Works only with Polarimatrix solver and requires an existing ray database|-| style="width:120px;" | [[#Mobile_Sweep | Mobile Sweep]]| style="width:180px;" | Considers one pair of length ''dl'' is given byactive transmitter and receiver at each simulation run to model a mobile communication link| style="width:150px;" | Polarimatrix| style="width:120px;" | Runs at the center frequency fc| style="width:300px;" | Requires the same number of transmitters and receivers, works only with Polarimatrix solver and requires an existing ray database|}

:<math> R_r = 80\pi^2 \left( \frac{dl}{\lambda_0} \right)^2 </math><!--[[File:eqngr6Click on each item in the above list to learn more about each simulation mode.png]]-->

The radiated power of You set the simulation mode in EM.Terrano's simulation run dialog using the drop-down list labeled '''Simulation Mode'''. A single-frequency analysis is a short dipole carrying single-run simulation. All the other simulation modes in the above list are considered multi-run simulations. In multi-run simulation modes, certain parameters are varied and a current I₀ is then given by:collection of simulation data files are generated. At the end of a sweep simulation, you can plot the output parameter results on 2D graphs or you can animate the 3D simulation data from the navigation tree.

:<math> P_{rad} = \frac{1}{2} R_r Note|I_0|^2 = 40\pi^2 |I_0|^2 \leftEM.Terrano's frequency sweep simulations are very fast because the geometrical optics ( \frac{dl}{\lambda_0} \rightray tracing)^2 </math><!part of the simulation is frequency--[[File:shortdipoleindependent.png]]-->}}

For isotropic and user defined radiators you can set the '''Input Power''' and '''Phase''' of a transmitter set in Watts and degrees, respectively. This can be accessed from the '''=== Transmitter Chain''' dialog, which will be described in detail in the next section. The radiation pattern of the associated radiator set is normalized and used in conjunction with the input power value to create a weighted distribution of transmitted rays. In certain cases like hybrid simulations, you may want to use the actual values of the far field to define the transmitter power rather than a normalized radiation pattern. Note that the pattern (.RAD) file contains the value of total radiated power in its header. In this case, check the box labeled '''&quot;Calculate Power From Radiation Pattern&quot;'''. This is calculated directly from the complex &theta; and &phi; components of the far field data by integrating them over the entire space (4&pi; solid angle). Note that this option is available only when the radiator is of the User Defined type. When this box is checked, the transmitter chain button is grayed out. By default, an isotropic transmitter emanates rays uniformly in all directions at the angular resolution specified by the user. A transmitter with a user defined associated radiator may represent a highly directional radiation pattern with the main beam pointing in a certain direction. You can additionally force and limit the '''Angular Extents''' of rays to a certain solid angle around the transmitter. This is especially useful and computationally efficient when the transmitter is on one side of the scene, and all the scatterers and receivers are on the other side. In this case, there is no need to generate rays in all directions. To limit the angular extents of rays, define the Start and End values for both Theta (&theta;) and Phi (&phi;) angles. The value of the angular resolution of the rays can be changed from the Run Dialog as will be discussed later.Sweep ===

In a regular SBR simulation, you have a transmitter and one When your propagation scene contains two or more arrays of receivers in your scene. At the end of the simulationtransmitters, you can visualize whether they all belong to the coverage map of same transmitter set with the same radiation pattern or to different transmitter over the receiver sets, EM. A coverage map shows the total '''Received Power''' by each of the receivers and is visualized as a color-coded intensity plotTerrano assumes all to be coherent with respect to one another. You can visualize the coverage maps of individual receiver setsIn other words, synchronous transmitters are always assumed. At the end of a SBR simulation, The rays originating from all these transmitters are superposed coherently and vectorially at each Received Power Coverage Map is listed under the receiver set's name in the Navigation Tree. To display In a coverage maptransmitter sweep, simply click on its entry in the Navigation Tree. The coverage map plot appears in the Main Window overlaid on the scene. A legend box on the right shows the color scale and units (dB). The 3-D coverage maps are displayed as horizontal confetti above the receivers. If the receivers are packed close to each otherhand, you will see EM.Terrano assumes only one transmitter broadcasting at a continuous confetti maptime. If The result of the receivers are far apart, you will see individual colored squares. You can also visualize coverage maps as colored 3-D cubes. This may be useful when you set up your receivers in sweep simulation is a vertical arrangement or the scene has a highly uneven terrain. To change the type number of received power coverage map visualizationmaps, open the receiver set's property dialog and select the desired option for '''Coverage Map: Confetti''' or '''Cube''' each corresponding to a transmitter in the '''&quot;Visualization Options&quot;''' section of the dialogscene.

[[File:prop_run11_tn.png{{Note|400px]] [[File:prop_run12_tnEM.png|400px]]Terrano's transmitter sweep works only with the Polarimatrix Solver and requires an existing ray database previously generated using the Channel Analyzer.}}

You can change rotate the settings 3D radiation patterns of both the coverage map by right clicking on its entry in the Navigation Tree transmitters and selecting '''Propertiesreceivers from the property dialog of the parent transmitter set or receiver set.This is done in advance before a SBR simulation starts..''' You can define one or by double-clicking on more of the legend boxrotation angles of a transmitter set or a receiver set as sweep variables and perform a parametric sweep simulation. In the Output Plot Settings dialogthat case, you can choose from one the entire scene and all of three Color Map options: '''Default''', '''Rainbow''' its buildings are discretized at each simulation run and '''Grayscale'''a complete physical SBR ray tracing simulation is carried out. The visualization plot uses default values for However, we know that the color scale. In polarimetric characteristics of the section titled &quot;Limits&quot;, you can choose propagation channel are independent of the radio button labeled '''User Defined'''transmitter or receiver antenna patterns or their rotation angles. Then, A rotational sweep allows you have to enter new values for rotate the '''Lower''' and '''Upper''' Limits radiation pattern of the plottransmitter(s) about one of the three principal axes sequentially. You can also show or hide This is equivalent to the Legend Box steering of the beam of the transmit antenna either mechanically or change its '''Background''' and '''Foreground''' colors by clicking electronically. The result of the sweep simulation is a number of received power coverage maps, each corresponding to one of the angular samples. To run a rotational sweep, you must specify the buttons provided for this purposerotation angle.

[[File:prop_run4{{Note| EM.png]]Terrano's rotational sweep works only with the Polarimatrix Solver and requires an existing ray database previously generated using the Channel Analyzer.}}

At the end of a SBR simulation, each receiver receives a number of rays[[EM. Some receivers may not receive any rays at all. You can visualize all the rays received by Cube]] provides a certain receiver from the active transmitter of the scene. To do this, right click the '''ReceiversMobile Path Wizard''' item that facilitates the creation of the Navigation Tree. From the context menu select '''Show Received Rays'''. All the rays received by the currently selected a transmitter set or a receiver of the scene are displayed in the sceneset along a specified path. The rays are identified by labels, are ordered by their power and have different colors for better visualizationThis path can be an existing nodal curve (polyline or NURBS curve) or an existing line objects. You can display also import a sptial Cartesian data file containing the rays for only one receiver at a time. The receiver set property dialog has a list coordinates of all the individual receivers belonging to that setbase location points. To display the rays received by another receiverFor more information, you have refer to change the '''Selected Receiver''' in the receiver set's property dialog[[Glossary_of_EM. If you keep the mouse focus on this dropdown list and roll your mouse scroll wheel, you can scan the selected receivers and move the rays from one receiver to the next in the list. To remove the visualized rays from the scene, right click the Receivers item of the Navigation Tree again and from the context menu select '''Hide Received Rays'''Cube%27s_Wizards#Mobile_Path_Wizard | Mobile Path Wizard]].

[[File:prop_run5_tn.png{{Note|800px]]EM.Terrano's mobile sweep works only with the Polarimatrix Solver and requires an existing ray database previously generated using the Channel Analyzer.}}

Visualization of received rays === Investigating Propagation Effects Selectively One at the location of the selected receiver.a Time ===

You can also view In a typical SBR ray tracing simulation, EM.Terrano includes all the propagation effects such as direct (LOS) rays, ray [[parameters]] by opening reflection and transmission, and edge diffractions. At the property dialog end of a receiver set. By defaultSBR simulation, you can visualize the first receiver received power coverage map of your propagation scene, which appears under the set is always selected. You can select any other receiver from set item in the drop-down list labeled '''Selected Receiver'''navigation tree. If you click The figure below shows the button labeled '''Show Ray Data''', a new dialog opens up received power coverage map of the random city scene with a table that contains all vertically polarized half-wave dipole transmitter located 10m above the received rays at ground and a large grid of vertically polarized half-wave dipole receivers placed 1.5m above the selected receiver ground. The legend box shows the limits of the color map between -23dBm as the maximum and their [[parameters]]:-150dB (the default receiver sensitivity value) as the minimum.

* Delay is the total time delay that a ray experiences travelling from the transmitter to the receiver after all the reflections, transmissions and diffractions and is expressed in nanoseconds.<table><tr><td> * Ray Field is the received electric field at the receiver location due to a specific ray and is given in dBV/m[[Image:UrbanCanyon10.* Ray Power is the png|thumb|left|640px|The received power at coverage map of the receiver due to random city scene with a specific ray and is given in dBmdipole transmitter.]] * Angles of Arrival are the &theta; and &phi; angles of the incoming ray at the local spherical coordinate system of the receiver.</td></tr></table>

The Ray Data Dialog also shows Sometime it is helpful to change the '''Total Received Power''' in dBm and '''Total Received Field''' in dBV/m due scale of the color map to all better understand the rays received by dynamic range of the receivercoverage map. You can sort If you double-click on the rays based on their delay, field, power, etc. To do so, simply legend or right-click on the grey column label coverage map's name in the table to sort the rays in ascending order based on the selected parameter. You can also navigation tree and select any ray by clicking on its '''IDProperties''' and highlighting its row in , the tablePlot Settings dialog opens up. In that case, Select the selected rays is highlighted in '''User-Defined''' item and set the Project Workspace lower and all the other rays become thin (faded)upper bounds of color map as you wish.

Note<table><tr><td> [[Image: UrbanCanyon15.png|thumb|left|480px|The plot settings dialog of the coverage map.]] </td></tr></table><table><tr><td> [[Image:UrbanCanyon16.png|thumb|left|640px|The rays are summed up coherently at received power coverage map of the receiverrandom city scene with a user-defined color map scale between -80dBm and -20dBm.]] </td></tr></table>

[[File:prop_run6_tnTo better understand the various propagation effects, EM.Terrano allows you to enable or disable these effects selectively. This is done from the Ray Tracing Simulation Engine Settings dialog using the provided check boxes.png|800px]]

Figure<table><tr><td> [[Image: Analyzing a selected ray from the ray data UrbanCanyon14.png|thumb|left|640px|EM.Terrano's simulation run dialogshowing the check boxes for controlling various propagation effects.]] </td></tr></table>

Besides visualizing the coverage map and received rays in the [[== Working with EM.Cube|EM.CUBE]]Terrano's [[Propagation Module]], you can also plot the '''Path Loss''' of all the receivers belonging to a receiver set as well as the '''Power Delay Profile''' of individual receivers. To plot these data, go the '''Observables''' section of the Navigation Tree and right click on the '''Receivers''' item. From the context menu, select '''Plot Path Loss''' or '''Plot Power Delay Profile''', respectively. The path loss data between the active transmitter and all the receivers belonging to a receiver set are plotted on a Cartesian graph. The horizontal axis of this graph represents the index of the receiver. Power Delay Profile is a bar chart that plots the power of individual rays received by the currently selected receiver versus their time delay. If there is a line of sight (LOS) between a transmitter and receiver, the LOS ray will have the smallest delay and therefore will appear first in the bar chart. Sometimes you may have several rays arriving at a receiver at the same time, i.e. all with the same delay, but with different power level. These will appear as stacked bars in the chart.Simulation Data ==

You can also plot the path loss and power delay profile graphs and many others from [[EM.Cube|EM.CUBE]]'s data manager. You can open data manager by clicking the ''=== The Ray Tracing Solvers'Output Simulation Data Manager''' [[File:data_manager_icon.png]] button of the '''Compute Toolbar''' or by selecting '''Compute [[File:larrow_tn.png]] Data Manager''' from the menu bar or by right clicking on the '''Data Manager''' item of the Navigation Tree and selecting Open Data Manager... from the contextual menu or by using the keyboard shortcut '''Ctrl+D'''. In the Data manager Dialog, you will see a list of all the data files available for plotting. These include the theta and phi angles of arrival and departure of the selected receiver. You can select any data file by clicking and highlighting its '''ID''' in the table and then clicking the '''Plot''' button.===

NEW LINEIn wireless propagation modeling for communication system applications, the received power at the receiver location is more important than the field distributions. In order to compute the received power, you need three pieces of information:

* Receiver Number* Receiver Base X'''Total Transmitted Power (EIRP)''': This requires knowledge of the baseband signal power, Y the transmitter chain parameters, Z Coordinatesthe transmission characteristics of the transmission line connecting the transmitter circuit to the transmitting antenna and the radiation characteristics of the transmitting antenna.* '''Channel Path Loss''': This is computed through SBR simulation. * '''Receiver HeightProperties''': This includes the radiation characteristics of the receiving antenna, the transmission characteristics of the transmission line connecting the receiving antenna to the receiver circuit and the receiver chain parameters.

NEW LINEIn a simple link scenario, the received power P_r in dBm is found from the following equation:

If you specify the noise-related parameters of your receiver set, the signal-to-noise ratios (SNR) is calculated at each receiver location: SNR = P_r - P_n, where P_n is the noise power level in dB. When planning, designing and deploying a communication system between points A and B, the link is considered to be closes and a connection established if the received signal power at the location of the receiver is above the noise power level by a certain threshold. In other words, the SNR at the receiver must be greater than a certain specified minimum SNR level. You specify (SNR)_min ss part of the definition of receiver chain in the Receiver Set dialog. In the "Visualization Options" section of this dialog, you can also check the check box labeled '''Generate Connectivity Map'''. This is a binary-level black-and-white map that displays connected receivers in white and disconnected receivers in black. At the end of an SBR simulation, the computed SNR is displayed in the Receiver Set dialog for the selected receiver. The connectivity map is generated and added to the navigation tree underneath the received power coverage map node.  At the end of an SBR simulation, you can visualize the field maps and receiver power coverage map of your receiver sets. A coverage map shows the total '''Received Power''' by each of the receivers and is visualized as a color-coded intensity plot. Under each receiver set node in the navigation tree, a total of seven field maps together with a received power coverage map are added. The field maps include amplitude and phase plots for the three X, Y, Z field components plus a total electric field plot. To display a field or coverage map, simply click on its entry in the navigation tree. The 3D plot appears in the Main Window overlaid on your propagation scene. A legend box on the right shows the color scale and units (dB). The 3D coverage maps are displayed as horizontal confetti above the receivers. You can change the appearance of the receivers and maps from the property dialog of the receiver set. You can further customize the settings of the 3D field and coverage plots.  <table><tr><td>[[Image:AnnArbor Scene1.png|thumb|left|640px|The downtown Ann Arbor propagation scene.]]</td></tr><tr><td>[[Image:AnnArbor Scene2.png|thumb|left|640px|The electric field distribution map of the Ann Arbor scene with vertical dipole transmitter and receivers.]]</td></tr><tr><td>[[Image:AnnArbor Scene3.png|thumb|left|640px|The received power coverage map of the Ann Arbor scene with vertical dipole transmitter and receivers.]]</td></tr><tr><td>[[Image:AnnArbor Scene4.png|thumb|left| 640px |The connectivity map of the Ann Arbor scene with SNR_min = 3dB with the basic color map option.]]</td></tr><tr><td>[[Image:AnnArbor Scene5.png|thumb|left| 640px |The connectivity map of the Ann Arbor scene with SNR_min = 20dB with the basic color map option.]]</td></tr></table> === Visualizing the Rays in the Scene === At the end of a SBR simulation, each receiver receives a number of rays. Some receivers may not receive any rays at all. You can visualize all the rays received by a certain receiver from the active transmitter of the scene. To do this, right click the '''Receivers''' item of the Navigation Tree. From the context menu select '''Show Received Rays'''. All the rays received by the currently selected receiver of the scene are displayed in the scene. The rays are identified by labels, are ordered by their power and have different colors for better visualization. You can display the rays for only one receiver at a time. The receiver set property dialog has a list of all the individual receivers belonging to that set. To display the rays received by another receiver, you have to change the '''Selected Receiver''' in the receiver set's property dialog. If you keep the mouse focus on this dropdown list and roll your mouse scroll wheel, you can scan the selected receivers and move the rays from one receiver to the next in the list. To remove the visualized rays from the scene, right click the Receivers item of the Navigation Tree again and from the context menu select '''Hide Received Rays'''. You can also view the ray parameters by opening the property dialog of a receiver set. By default, the first receiver of the set is always selected. You can select any other receiver from the drop-down list labeled '''Selected Receiver'''. If you click the button labeled '''Show Ray Data''', a new dialog opens up with a table that contains all the received rays at the selected receiver and their parameters: * Delay is the total time delay that a ray experiences travelling from the transmitter to the receiver after all the reflections, transmissions and diffractions and is expressed in nanoseconds.* Ray NumberField is the received electric field at the receiver location due to a specific ray and is given in dBV/m.* Ray Power is the received power at the receiver due to a specific ray and is given in dBm.* Angles of Arrival are the &theta; and &phi; angles of the incoming ray at the local spherical coordinate system of the receiver. <table><tr><td> [[Image:UrbanCanyon17.png|thumb|left|720px|EM.Terrano's ray data dialog showing a selected ray.]] </td></tr></table> The Ray Data Dialog also shows the '''Total Received Power''' in dBm and '''Total Received Field''' in dBV/m due to all the rays received by the receiver. You can sort the rays based on their delay, field, power, etc. To do so, simply click on the grey column label in the table to sort the rays in ascending order based on the selected parameter. You can also select any ray by clicking on its '''ID''' and highlighting its row in the table. In that case, the selected rays is highlighted in the Project Workspace and all the other rays become thin (faded). {{Note|All the received rays are summed up coherently in a vectorial manner at the receiver location.}} <table><tr><td> [[Image:UrbanCanyon18.png|thumb|left|640px|Visualization of received rays at the location of a selected receiver in the random city scene.]] </td></tr></table> === The Standard Output Data File === At the end of an SBR simulation, EM.Terrano writes a number of ASCII data files to your project folder. The main output data file is called "sbr_results.RTOUT". This file contains all the information about individual receivers and the parameters of each ray that is received by each individual receiver. At the end of an SBR simulation, the results are written into a main output data file with the reserved name of SBR_Results.RTOUT. This file has the following format: Each receiver line has the following information: * Receiver ID* Receiver X, Y, Z coordinates* Total received power in dBm* Total number of received rays Each rays line received by a receiver has the following information: * Ray Index* Delay in nsec

* Delay in nsec* Real(and imaginary parts of the three E<supsub>Vx</supsub>) &amp; Imag(, E^V)* Real(E^H) &amp; Imag(E^H)* Real('''E.e_Ry''') &amp; Imag(''', E.e_Rz''')components* Number of ray hit points * PowerCoordinates of individual hit points

The angles of arrival are the &theta; and &phi; angles of a received ray measured in degrees and are referenced in the local spherical coordinate systems centered at the location of the receiver. The angles of departure for a received ray are the &theta; and &phi; angles of the originating transmitter ray, measured in degrees and referenced in the local spherical coordinate systems centered at the location of the active transmitter, which eventually arrives at the receiver. The total time delay is measured in nanoseconds between t = 0 nsec at the time of launch from the transmitter location till being received at the receiver location. The last four columns show the real and imaginary parts of the received electric fields with vertical and horizontal polarizations, respectively. The complex field values are normalized in a way that when their magnitude is squared, it equals the received ray power. If the active transmitter is an isotropic radiator with either a vertical or horizontal polarization, then the field components corresponding to the other polarization will have zero entries in the output data file.

<table><tr><td> [[FileImage:prop_run8_tn.png|800pxthumb|left|720px|A typical SBR output data file.]]</td></tr></table>

By default, you run a single-frequency simulation The available data files in [[EM.Cube|EM.CUBE]]'s [[Propagation Module]]. You set the operational frequency "2D Data Files" tab of a SBR simulation in the project's '''Frequency Dialog''', which can be accessed in a number of waysData Manger include:

# By clicking the * '''FrequencyPath Loss''' [[File:freq_iconThe channel path loss is defined as PL = P_r - EIRP.png]] button The path loss data are stored in a file called "SBR_receiver_set_name_PATHLOSS.DAT" as a function of the '''Compute Toolbar'''receiver index. The path loss data make sense only if your receiver set has the default isotropic radiator.# By selecting * '''ComputePower Delay Profile''' [[File:larrow_tnThe delays of the individual rays received by the selected receiver with respect to the transmitter are expressed in ns and tabulated together with the power of each ray in the file "SBR_receiver_set_name_DELAY.png]]'''Frequency SettingsDAT"...''' You can plot these data from the Menu BarData Manager as a bar chart called the power delay profile.# Using The bars indeed correspond to the keyboard shortcut difference between the ray power in dBm and the minimum power threshold level in dBm, which makes them a positive quantity. * '''Ctrl+FAngles of Arrival'''.# By double clicking : These are the frequency section (box) Theta and Phi angles of the '''Status Bar'''individual rays received by the selected receiver and saved to the files "SBR_receiver_set_name_ThetaARRIVAL.<br /> ANG" and "SBR_receiver_set_name_PhiARRIVAL.ANG". You can plot them in the Data Manager in polar stem charts.

When you run a frequency or parametric sweep in [[File:prop_freqEM.pngTerrano]] , a tremendous amount of data may be generated. [[File:prop_run10EM.pngTerrano]]only stores the '''Received Power''', '''Path Loss''' and '''SNR''' of the selected receiverin ASCII data files called "PREC_i.DAT", "PL_i.DAT" and "SNR_i.DAT", where is the index of the receiver set in your scene. These quantities are tabulated vs. the sweep variable's samples. You can plot these files in EM.Grid.

(Left) Project[[Image:Info_icon.png|40px]] Click here to learn more about working with data filed and plotting graphs in [[EM.Cube]]'s frequency dialog and (Right) the frequency settings dialog'''[[Defining_Project_Observables_%26_Visualizing_Output_Data#The_Data_Manager | Data Manager]]'''.

You can also select the '''Frequency Sweep''' option in the '''Simulation Mode''' drop-down list of the '''Run Dialog'''<table><tr><td> [[Image:Terrano pathloss. Click the '''Settings...''' button on the right side of this dropdown list to open up the Frequency Settings Dialog. Based on the original values png|thumb|360px|Cartesian graph of the project center frequency and bandwidth, the '''Start Frequency''' and '''End Frequency''' have default valuespath loss. You can also change the '''Number of Samples'''. Once you click the '''Run''' button, ]] </td><td> [[EMImage:Terrano delay.Cubepng|EMthumb|360px|Bar graph of power delay profile.CUBE]] performs a frequency sweep by assigning each of the frequency samples as the current operational frequency and running the SBR simulation engine at that frequency</td></tr><tr><td> [[Image:Terrano ARR phi. All the simulation data at all frequency samples are saved into the output data files including &quot;SBR_results.RTOUT&quot;. After the completion png|thumb|360px|Polar stem graph of a frequency sweep simulation, as many coverage maps as the number Phi angle of frequency samples are generated and added to the Navigation Tree under the Receiver Set's entryarrival. You can click on each of the coverage maps corresponding to each of the frequency samples and visualize it in the project workspace. You can also animate the coverage maps. To do so, right click on the receiver set's name in the Navigation Tree and select ''']] </td><td> [[Animation]]''' from the contextual menuImage:Terrano ARR theta. The coverage maps start to animate by their order on the Navigation Tree. Once the entire list is displayed sequentially, it starts all over again from the beginning png|thumb|360px|Polar stem graph of the listTheta angle of arrival. During the [[animation]], the '''</td></tr><tr><td> [[Animation]] Controls''' dialog appears at the lower right corner of the screenImage:Terrano DEP phi. This dialog has a number png|thumb|360px|Polar stem graph of buttons for pause/resume, step forward/backward, and step to the end/start. The title Phi angle of each coverage map is shown in the box labeled '''Sample''' as it is displayed in the main windowdeparture. You can also change the speed of [[animation]]</td><td> [[Image:Terrano DEP theta. The default frame duration has a value png|thumb|360px|Polar stem graph of 300 (3x100) millisecondsTheta angle of departure. To stop the [[animation]], simply press the keyboard's '''Esc Key'''.</td></tr></table>

Multiple coverage maps on When you designate a "User Defined Antenna Pattern" as the Navigation Tree radiator type of a transmitter set or a receiver set, EM.Terrano copies the imported radiation pattern data file from its original folder to the current project folder. The name of the ".RAD" file is listed under the '''3D Data Files''' tab of the data manager. Sometimes it might be desired to visualize these radiation patterns in your propagation scene at the end actual location of the transmitter or receiver. To do so, you have to define a frequency sweep new '''Radiation Pattern''' observable in the navigation tree. The label of the new observable must be identical to the name of the ".RAD" data file. In addition, the Theta and starting an [[animation]] from Phi angle increments of the new radiation pattern observable (expressed in degrees) must be identical to the Theta and Phi angular resolutions of the imported pattern file. If all these conditions are met, then go to the '''Simulate Menu''' and select the item '''Update All 3D Visualization'''. The contents of the 3D radiation patterns are added to the navigation tree. Click on one of the radiation pattern items in the navigation tree and it will be displayed in the contextual menuscene.

<table><tr><td>[[FileImage:prop_run15_tnUrbanCanyon6.png|thumb|left|640px|The received power coverage map of the random city scene with a highly directional dipole array transmitter.]]</td></tr></table>

By Default, [[AnimationEM.Cube]] controls always visualizes the 3D radiation patterns at the origin of coordinates, i.e. at (0, 0, 0). This is because that radiation pattern data are computed in the standard spherical coordinate system centered at (0, 0, 0). The theta and phi components of the far-zone electric fields are defined with respect to the X, Y and Z axes of this system. When visualizing the 3D radiation pattern data in a propagation scene, it is more intuitive to display the pattern at the location of the transmitter or receiver. The Radiation Pattern dialog allows you to translate the pattern visualization to any arbitrary point in the project workspace. It also allows you to scale up or scale down the pattern visualization with respect to the background scene.

=== Running In the example shown above, the imported pattern data file is called "Dipole_Array1.RAD". Therefore, the label of the radiation pattern observable is chosen to be "Dipole_Array1". The theta and phi angle increments are both 1&deg; in this case. The radiation pattern has been elevated by 10m to be positioned at the location of the transmitter and a Parametric Sweep with SBR ===scaling factor of 0.3 has been used.

<table><tr><td>[[FileImage:prop_run24UrbanCanyon8.png|thumb|300pxleft|EM.CUBE's variable 640px|Setting the pattern parameters in the radiation pattern dialog.]]</td></tr></table><table><tr><td>[[Image:UrbanCanyon7.png|thumb|left|720px|Visualization of the 3D radiation pattern of the directional transmitter in the random city scene.]]</td></tr></table>

[[File:prop_run23There is an important catch to remember here.png|thumb|250px|Dialog When you define a radiation pattern observable for defining your project, EM.Terrano will attempt to compute the overall effective radiation pattern of the entire physical structure. However, in this case, you defined the radiation pattern observable merely for visualization purposes. To stop EM.Terrano from computing the actual radiation pattern of your entire scene, there is a check box in EM.Terrano's Ray Tracer Simulation Engine Settings dialog that is labeled '''Do not compute new variables]]radiation patterns'''. This box is checked by default, which means the actual radiation pattern of your entire scene will not be computed automatically. But you need to remember to uncheck this box if you ever need to compute a new radiation pattern using EM.Terrano's SBR solver as an asymptotic EM solver (see next section).

In <table><tr><td>[[EMImage:UrbanCanyon9.Cubepng|thumb|left|640px|EM.CUBE]], all the CAD object properties as well as certain source, material and mesh [[parameters]] can be assigned as [[variables]]Terrano's Run Simulation dialog. [[Variables]] are defined to control and vary the values of such [[parameters]] either for editing purposes or to run parametric sweep or [[optimization]]. Variable are defined using the '''[[Variables]] Dialog''', which can be accessed in the three ways:</td></tr></table>

# By clicking the '''[[Variables]]''' [[File:variable_icon.png]] button of the '''Compute Toolbar'''.# By selecting '''Compute''' [[File:larrow_tn.png]] '''[[Variables]]...''' from the Menu Bar.# == Using the keyboard shortcut '''Ctrl+B'''EM.Terrano as an Asymptotic Field Solver ==

The [[variables]] dialog is initially emptyLike every other electromagnetic solver, EM. To add a new variable, click the Terrano'''Add''' button to open up the '''Add Variable/Syntax Dialog'''. In this dialog you have to type in a name s SBR ray tracer requires an excitation source and one or more observables for the new variable and choose a typegeneration of simulation data. The default type is '''Uniformly Spaced Samples'''EM. You also need to specify the '''Start''', '''Stop''' Terrano offers several types of sources and '''Step''' values observables for the variablea SBR simulation. In You already learned about the figure below, transmitter set as a variable called &quot;Tx_Height&quot; is defined that varies between 2 source and 10 with equal steps of 2. This means the sample receiver set {2,4,6,8,10}. When you return to the [[variables]] dialog, the syntax of the new variable is shown as 2:10:2an observable. The last number in this syntax is always You can mix and match different source types and observable types depending on the variable step. In this example, this variable is going to be used to control the height requirements of the transmitter in a propagation sceneyour modeling problem.

Next, you have to attach the variable to the CAD object. In this case, the CAD object is the point object that represents the transmitter's radiator. To attach a variable to a CAD object, open the object's property dialog and type The available source types in the name of the variable as the value of a property or parameterEM. In this case, the variable Tx_Height is going to control the Z-Coordinate of the point object. Once the value of the object parameter is replaced by the name of an already defined variable, it is updated with the current value of that variable. In the case of a variable of &quot;Uniformly Spaced Samples&quot; type, the current value is the start value. This value will be incrementally varied during a parametric sweep simulation process. Note that a variable can take a fixed value or a discrete set of values, too. You can always open the [[variables]] dialog and change the value or syntax of any variable. To make a new or modified value effective, click the '''Apply''' button of the [[variables]] dialog. You can test the values by performing a '''Dry Run''' of the selected variable. This runs an [[animation]] of the project workspace as the value of the variable changes and all the related CAD objects Terrano are updated accordingly. Note that you can attach the same variable to more than one CAD object property or to the properties of different objects. You can also define multiple values or syntaxes to the same variable. To do so, open the '''Add Variable/Syntax Dialog''', and instead of typing in a new variable name, choose an existing variable name from the '''Name''' dropdown list. This will add a new value or syntax to the existing syntax(es) of the selected variable. When you return to the [[variables]] dialog, [[variables]] with more than one value or syntax will have a dropdown list in the '''Syntax''' column. You can choose any of these values or syntaxed at any time and make the change effective by clicking the '''Apply''' button.:

{| class="wikitable"|-! scope="col"| Icon! scope="col"| Source Type! scope="col"| Applications! scope="col"| Restrictions|-| style="width:30px;" | [[File:prop_run25transmitter_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Point Transmitter Set | Point Transmitter Set]]| style="width:250px;" | Modeling realsitic antennas & link budget calculations| style="width:250px;" | Requires to be associated with a base location point set|-| style="width:30px;" | [[File:hertz_src_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Hertzian Short Dipole Source | Hertzian Short Dipole]]| style="width:250px;" | Almost omni-directional physical radiator| style="width:250px;" | None, stand-alone source|-| style="width:30px;" | [[File:huyg_src_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Huygens Source | Huygens Source]]| style="width:250px;" | Used for modeling equivalent sources imported from other [[EM.Cube]] modules | style="width:250px;" | None, stand-alone source imported from a Huygens surface data file|}

Replacing Click on each type to learn more about it in the value [[Glossary of a CAD object parameter with a variable nameEM.Cube's Materials, Sources, Devices & Other Physical Object Types]].

To run a parametric sweep, open the '''Run Dialog''' and select the '''Parametric Sweep''' option The available observables types in the '''Simulation Mode''' drop-down list. If you have not defined any [[variablesEM.Terrano]] in the project, the box in the '''are: {| class="wikitable"|-! scope="col"| Icon! scope="col"| Source Type! scope="col"| Applications! scope="col"| Restrictions|-| style="width:30px;" | [[VariablesFile:receiver_icon.png]]''' row before the '''View''' will be red| style="width:150px;" | [[Glossary of EM. You have Cube's Simulation Observables & Graph Types#Point Receiver Set | Point Receiver Set]]| style="width:250px;" | Generating received power coverage maps & link budget calculations| style="width:250px;" | Requires to turn it into green before you can run be associated with a simulation. By clicking the '''View''' button, you can open up the base location point set|-| style="width:30px;" | [[variablesFile:Distr Rx icon.png]] dialog from here. Once you click the '''Run''' button, | style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Distributed Receiver Set |EM.CUBEDistributed Receiver Set]] performs | style="width:250px;" | Computing received power at a parametric sweep receiver characterized by incrementally varying the values of all the defined Huygens surface data| style="width:250px;" | None, stand-alone source imported from a Huygens surface data file|-| style="width:30px;" | [[variablesFile:fieldsensor_icon.png]] from their start to stop values at the specified steps and updating all the related CAD objects. After the completion | style="width:150px;" | [[Glossary of a parametric sweep simulation, as many coverage maps as the total number of variable samples are generated and added to the Navigation Tree under the receiver setEM.Cube's entry. You can click on each of the coverage maps Simulation Observables & Graph Types#Near-Field Sensor Observable | Near-Field Sensor]]| style="width:250px;" | Generating electric and visualize it in the project workspace. You can also animate the coverage magnetic field distribution maps sequentially. To do so| style="width:250px;" | None, right click on the receiver set's name in the Navigation Tree and select '''stand-alone observable|-| style="width:30px;" | [[AnimationFile:farfield_icon.png]]| style="width:150px;" | [[Glossary of EM.Cube''' from s Simulation Observables & Graph Types#Far-Field Radiation Pattern Observable | Far-Field Radiation Pattern]]| style="width:250px;" | Computing the contextual menu. To stop effective radiation pattern of a radiator in the presence of a large scattering scene | style="width:250px;" | None, stand-alone observable|-| style="width:30px;" | [[animationFile:huyg_surf_icon.png]], simply press the keyboard| style="width:150px;" | [[Glossary of EM.Cube's '''Esc Key'''Simulation Observables & Graph Types#Huygens Surface Observable | Huygens Surface]]| style="width:250px;" | Collecting tangential field data on a box to be used later as a Huygens source in other [[EM.Cube]] modules| style="width:250px;" | None, stand-alone observable|}

Click on each type to learn more about it in the [[File:prop_run26Glossary of EM.pngCube's Simulation Observables & Graph Types]]. When you define a far-field observable in EM.Terrano, a collection of invisible, isotropic receivers are placed on the surface of a large sphere that encircles your propagation scene and all of its geometric objects. These receivers are placed uniformly on the spherical surface at a spacing that is determined by your specified angular resolutions. In most cases, you need to define angular resolutions of at least 1&deg; or smaller. Note that this is different than the transmitter rays' angular resolution. You may have a large number of transmitted rays but not enough receivers to compute the effective radiation pattern at all azimuth and elevation angles. Also keep in mind that with 1&deg; Theta and Phi angle increments, you will have a total of 181 &times; 361 = 65,341 spherically placed receivers in your scene.

Choosing parametric sweep as the simulation mode in the run dialog. {{Note that one variable has been defined and | Computing radiation patterns using EM.Terrano's SBR solver typically takes much longer computation times than using [[EM.Cube|EM.CUBE]] is ready to run 's other computational modules.}} <table><tr><td> [[Image:SBR pattern.png|thumb|540px|Computed 3D radiation pattern of two vertical short dipole radiators placed 1m apart in the simulationfree space at 1GHz.]] </td></tr></table>

EM.Terrano's coverage maps display the received power at the location of all the receivers. The receivers together from a set/ensemble, which might be uniformly spaced or distributed across the propagation scene or may consist of randomly scattered radiators. Every coverage map shows the '''Mean''' and '''Standard Deviation''' of the scene received power for all the receivers involved. These information are displayed at the end bottom of a parametric sweep where the sweep variable is the transmitter heightcoverage map's legend box and are expressed in dB.

=== Statistical Analysis When you run either a frequency sweep or a parametric sweep simulation in EM.Terrano, you have the option to generate two additional coverage maps: one for the mean of Propagation Scene ===all the individual sample coverage maps and another for their standard deviation. To do so, in the '''Run Dialog''', check the box labeled '''&quot;Create Mean and Standard Deviation received power coverage maps&quot;'''. Note that the mean and standard deviation values displayed on the individual coverage maps correspond to the spatial statistics of the receivers in the scene, while the mean and standard deviation coverage maps show the statistics with respect to the frequency or other sweep variable sets at each point in the site. Also, note that both of the mean and standard deviation coverage maps have their own spatial mean and standard deviation values expressed in dB at the bottom of their legend box.

<table><tr><td> [[EMImage:PROP MAN12.Cubepng|thumb|left|480px|EM.CUBE]]Terrano's coverage maps display simulation run dialog showing frequency sweep as the received power at the location of all the receiverssimulation mode along with statistical analysis. The receivers together from a set]] </ensemble, which might be uniformly spaced or distributed across the propagation scene or may consist of randomly scattered radiators. Every coverage map shows the '''Mean''' and '''Standard Deviation''' of the received power for all the receivers involved. These information are displayed at the bottom of the coverage map's legend box and are expressed in dB.td></tr></table>

In the <table><tr><td> [[Propagation Module]], when you ran a sweep simulation (frequency, transmitter or parametric), you also have the option to generate two additional coverage mapsImage: one for the mean of all the individual sample coverage maps and another for their standard deviationUrbanCanyon4. To do so, in the '''Run Dialog''', check the box labeled '''&quot;Create Mean and Standard Deviation Coverage Maps&quot;'''. Note that the png|thumb|left|640px|The mean and standard deviation values displayed on the individual coverage maps correspond to map at the spatial statistics end of the receivers in the scene, while the mean and standard deviation coverage maps correspond to a frequency, transmitter or variable sets defined for the sweep simulation. Also, note that both of the mean and ]] </td></tr><tr><td> [[Image:UrbanCanyon5.png|thumb|left|640px|The standard deviation coverage maps have their own spatial mean and standard deviation values expressed in dB map at the bottom end of their legend boxa frequency sweep.]] </td></tr></table>

[[FileImage:prop_run22_tnTop_icon.png|30px]]'''[[EM.Terrano#Product_Overview | Back to the Top of the Page]]'''

The standard deviation coverage map at the end of a transmitter sweep[[Image:Tutorial_icon.png|30px]] '''[[EM.Cube#EM.Terrano_Documentation | EM.Terrano Tutorial Gateway]]'''

<p>&nbsp;</p>[[Image:Back_icon.png|30px]] '''[[EM.Cube | Back to EM.Cube Main Page]]'''