The following information is needed to configure your SAS software: a. Specify Configuration Information This step creates your softwares configuration directory. The default Configuration Level is Lev1.
Migration Information You can use this step to migrate existing content. However, there is no existing content for this example. Windows Options This option creates a set of shortcuts that help with the management of the SAS servers that you are about to install.
Token Based Authentication This installation does not used token-based authentication. SAS server configuration: Accounts a. Accept the default location. Accept the default settings.
Deployment Accounts: Types of Accounts This window enables you to specify the types of accounts that are used. Accept the default selection. Provide your password and click Next. This account must reside on the installation machine. Server Encryption This window enables you to specify the encryption that is used by the server.
Specify the Host Name and Port. E-mail Addresses Specify a sender and recipient for e-mail alerts. Scheduling Services Cache Locator Accept the default value of IP Multicast The multicast group communication includes all information that is needed to bootstrap SAS mid-tier applications.
Because this includes sending the SAS environment credentials such as the sasadm account name and its password , scoping and encryption options are provided. The default values are most appropriate for deployments in a firewall-isolated data center environment. The Deployment Wizard help documentation contains more information about these choices. Deployment Summary Review the software that you have selected before you start the installation process. If this information is correct, Click Start.
Additional Resources It is suggested that you record these links for future reference. Click Finish. Configuration Guidelines and Details. The information found on this page is specific to your installation and is kept in your configuration directory.
Reboot This step is required for Windows systems so that the user accounts Local Security Policy changes will take effect. For example, on a Windows system, that file is setup. Note that depending on any optional configuration of your software order, this might appear as Step 3. You must specify the plan. Typically, the deployment plan is stored in the.
Select Deployment Step and Products to Install The deployment plan determines the products to install and what order they are installed in. If necessary, click Browse to navigate to it. This can be useful if you need to share such files with computers that use different language representations. Accept the default values. Checking System The SAS Deployment Wizard checks to ensure that the system has enough disk space and that the files and folders that it will write are accessible.
The following information is needed to configure the software: a. Review Required Software This specifies the third-party software that will be required to continue the installation.
Select Configuration Prompting Level Select Typical to display the basic set of configuration settings. To accept most defaults and for fewer options, select Express.
For more granular configuration options, select Custom. Specify Configuration Information This step creates your software configuration directory. The default settings create a level-1 configuration. Migration Information Do one of the following:. If you are not upgrading from the previous release, then do not select Perform Migration.
If you are upgrading from the previous, then do not continue with the remaining installation and configuration until you review the information in Chapter 4.
Windows Options This option creates a set of shortcuts that help with the management of the SAS servers that you are ready to install. This example does not use Integrated Windows Authentication. By default, the box for Use Integrated Windows Authentication is not checked. Server Connection and Accounts a. SAS internal accounts are intended to minimize the use of external accounts for SAS internal purposes.
For this example, select Use SAS internal accounts when appropriate. You must use the same password that was specified in the first step of these instructions. SAS Internal Account: Trusted User This is a privileged metadata service account that is required to access metadata on behalf of users.
E-mail Server Enter the host name and port number for the SMTP mail server that will send messages to the system administrator when the metadata server encounters a problem.
The host name and port number should automatically be retrieved from the server that you configured in Stage 1. E-mail Address The Sender E-mail Address is the address that is used to send e-mail messages to the system administrator. The Recipient E-mail Address is the address that will receive the server warnings. If your e-mail server requires logon credentials, enable the option E-mail Server Requires Authentication.
The e-mail server user ID and password are entered on a subsequent page if you select this option. However, this example does not enable this option. Mid-Tier Configuration a. Web Application Server: Server Configuration This is the logical name that will be used for your managed server. For this example, accept the default, SASServer1. Web Application Server: Server Ports If you choose not to accept the default values, refer to your completed Pre-Installation Checklist for the values that you should enter.
For this example, accept the default values. Web Application Server: Automatic Deployment If you choose not to automatically deploy web applications, manual deployment instructions will be written to Instructions. For this example, choose to have web applications automatically deployed to the web application server. The default value is the name of the host where the configuration is performed.
The port number provided here must be the same as the HTTP port of your managed server. If you choose not to accept the default values, refer to your completed Pre-Installation Checklist for the values that you should enter. The Configured Protocol is the communication protocol that is used when you access the installed themes.
Enter the location on your disk for the files of this repository. If you have chosen automatic configuration of a database for the SAS Web Infrastructure Database, this user ID must have the ability to create tables and insert records. If you have not chosen automatic configuration, this user ID must have the ability to create tables, insert records, and delete records.
Deployment Summary Review the software selections before starting the installation process. If everything is correct, click Start. Deployment Complete Check all stages for errors or warnings.
Additional Resources Record these links for future reference. These links will be needed in the post-installation process. Configuration Guidelines and Details This page of information is specific to your installation and is kept in your configuration directory. Three Machine Setup, Stage 3 Client 1. For the client installation, log on to the computer that will be used as the SAS Enterprise Miner client machine.
For example, on a Windows system, this is the file setup. Note that depending on your software order, this might appear as Step 5. Select Deployment Type Accept the default settings. If your SAS representative provided you with a custom plan file, select Specify the full path to a customized deployment plant.
Select Deployment Step and Products to Install The deployment plan determines which products to install and in what order. In the Deployment Step field, select Step 5: Clients.
Select Language Support Select the languages that you want to install for the products that are listed. Only those languages that work with your locale are installed.
Select Regional Settings Specify how you want your SAS Software to format and display language, region, and locale-specific information.
This can be useful if you need to share these files with computers that use different language representations. This step lets you avoid manually creating and deploying a sas-environment. For this example, the network machine name myserver. Checking System The SAS Deployment Wizard checks to ensure that the system has enough disk space and that all files and folders that it needs to write are accessible.
The installation cannot proceed until access is granted to any listed files. When the examination of your file system is complete and there are no unwriteable files, click Next. To accept most defaults, and for fewer options, select Express.
The default settings create a level1 configuration. If you are upgrading from the previous release, do not continue with the remaining installation and configuration until you have reviewed the information indicated in Chapter 4. In this example, do not select the check box for Use Integrated Windows Authentication.
If everything is correct, Click Start. Deployment Complete Check all stages of the installation for errors or warnings. This page of information is specific to your installation and is kept in your configuration directory. Deployment Errors and Warnings Error Status When an error status is returned to the SAS Deployment Wizard, it displays the message that describes the problem encountered, and asks what further action to perform.
They include stopping, continuing, or retrying. If the error message indicates a correctable problem, you might be able to handle the problem outside the SAS Deployment Wizard. Warning Status In situations where a step was only partially successful, but can be resolved outside the SAS Deployment Wizard post-installation, the SAS Deployment Wizard sets the warning status flag and continues as if it were successful.
However, information about the warning is written to a special section in Instructions. The Instructions.
Verify the Installation Overview After the installation and configuration is complete, you will want to verify your deployment. Note: You will replace myserver. In most cases, the Enterprise Miner Log On window will resemble the image shown below.
In the Project Name text box, enter Test1. In the SAS Server Directory text box, enter the path to a folder that is accessible by your account from the server machine. This folder will contain your project folders and files. You can use the Browse button to navigate to your file system and choose a more appropriate folder. For verification purposes, accept the default location and click Next.
The final step of the New Project Wizard displays the New Project Information, which reviews the information given in the previous windows.
For a more indepth tutorial on how to create a new project, see the SAS Enterprise Miner help documentation. A new project diagram opens. After creating a new diagram, the project workspace for that diagram will open automatically. In the Project Panel, select the Home Equity data source. Click and drag this data source into the Diagram Workspace, as shown in the image below. In the Confirmation window, select Yes. You should quickly see a Run Status window that indicates a successful run of the data source.
Click OK to close the Run Status window. At this point, the verification is complete, and you have successfully installed and run all the major components of SAS Enterprise Miner.
At the Confirmation window, select Yes. The single-user Workstation installation is not a planned installation and is a simpler process than the Server installation. You need to log on to the target machine with Administrator privileges.
Enter the following information: a. Select Products to Install All of the products in your order are listed on this page. Generally, you will want all of the products in your order. The Sakagami extended propagation model is valid for frequencies above 3 GHz.
The Sakagami-Kuboi propagation model requires detailed information about the environment, such as widths of the streets where the receiver is located, the angles formed by the street axes and the directions of the incident waves, heights of the buildings close to the receiver, etc. W is the width in meters of the streets where the receiver is located is the angle in degrees formed by the street axes and the direction of the incident wave hs is the height in meters of the buildings close to the receiver H1 is the average height in meters of the buildings close to the receiver hb is the height in meters of the transmitter antenna with respect to the observer hb0 is the height in meters of the transmitter antenna with respect to the ground level H is the average height in meters of the buildings close to the base station d is the separation in kilometres between the transmitter and the receiver f is the frequency in MHz.
Studies also show that above 3 GHz, the path loss predicted by the extended model is almost independant of the input parameters such as street widths and angles. The path loss calculation formula of the Sakagami extended propagation model resembles the formula of the Standard Propagation Model.
In Atoll, this model is in fact a copy of the Standard Propagation Model with the following values assigned to the K coefficients: K1. General method for one or more obstacles knife-edge diffraction is used to evaluate diffraction losses Diffraction loss in dB.
Four construction modes are implemented in Atoll. All of them are based on this same physical principle presented hereafter, but differ in the way they consider one or several obstacles. The diffraction loss, J , depends on the obstruction parameter , which corresponds to the ratio of the obstruction height h and the radius of the Fresnel zone R.
Hence, 2. This method is used to evaluate path loss incurred by multiple knife-edges. Deygout method is based on a hierarchical knifeedge sorting used to distinguish the main edges, which induce the largest losses, and secondary edges, which have a lesser effect. The edge hierarchy depends on the obstruction parameter value. The obstruction position, di, is also recorded. The point with the highest value is termed the principal edge, p, and the corresponding loss is J p.
Therefore, the profile is divided in two parts: one half profile, between the transmitter and the knife-edge section, another half, constituted by the knife-edgereceiver section. The two obstacles found, points t and r , are called secondary edges. Losses induced by the secondary edges, J t and J r , are then calculated. Once the edge hierarchy is determined, the total loss is evaluated by adding all the intermediary losses obtained. First, Deygout construction is applied to determine the three main edges over the whole profile as described above.
Then, the main edge height, hp, is recalculated according to the Epstein-Peterson construction. The main edge position dp is recorded and p and J p are evaluated from these data.
Two horizon lines are drawn at the transmitter and at the receiver. A straight line between the transmitter and the receiver is defined and the height of the. The position dh is recorded and then, from these values, h and J h are evaluated using the same previous formulas. Therefore, the predicted path loss between a transmitter and a receiver is constant, in a given environment and for a given distance.
However, in reality different types of clutter may exist in the transmitter-receiver path. Therefore, the path losses for the same distance could be different along paths that pass throught different types of environments. The location of the receiver in different types of clutter causes variations with respect to the mean path loss values given by the path loss models.
Some paths undergo more loss while others are less obstructed and may have higher received signal strength. The variation of path loss with respect to the mean path loss values predicted by the propagation models, depending on the type of environment is called shadow fading shadowing or slow fading. Different types of clutter buildings, hills, etc. As a mobile passes under a shadow, the path loss to the mobile keeps varying from point to point.
Shadow fading varies as the mobile moves, while fast fading can vary even if the mobile remains at the same location or moves over very small distances. It is crucial to account for the shadow fading in order to predict the reliability of coverage provided by any mobile cellular system.
The shadowing effect is modelled by a log-normal Gaussian distribution, as shown in Figure 2. Different clutter types have different shadowing effects. Therefore, each clutter type in Atoll can have a different standard deviation representing its shadowing characteristics.
For different standard deviations, the shape of the Gaussian distribution curve remains similar, as shown in Figure 2. The accuracy of this model depends upon:. The suitability of the range of standard deviation used for each clutter class, The definition bin size of the digital map, How up-to-date the digital map is, The number of clutter classes, The accuracy of assignment of clutter classes.
Shadowing is applied to the predicted path loss differently depending on the technology, and whether it is applied to predictions or simulations.
The following sections explain how shadowing margins are calculated and applied to different technology documents. Shadowing margins are calculated for a given cell edge coverage probability. The cell edge coverage probability is the probability of coverage at a pixel located at the cell edge, and corresponds to the reliability of coverage that you are planning to achieve at the cell edge. Antennas and propagation for Wireless Communication Systems pp. CDMA systems engineering handbook pp. Systmes de radiocommunications avec les mobiles pp.
Radio network planning and optimisation for UMTS pp. Signal Level-Based Predictions Signal level-based predictions include coverage predictions Coverage by Transmitter, Coverage by Signal Level, and Overlapping Zones and calculations in point analysis tabs Profile and Reception that require calculation of the received signal level only, and do not depend on interference.
In these calculations signal level calculations , a shadowing margin M Shadowing model is applied to the received signal level calculated for each pixel. The shadowing margin is calculated for a given cell edge coverage probability, and depends on the model standard deviation model in dB associated to the clutter class where the receiver is located.
In these calculations, C I calculations , the shadowing margin M Shadowing C I is applied to the ratio of the carrier power C and the interfering signal levels I received from the interfering base stations. Signal level-based predictions include coverage predictions Coverage by Transmitter, Coverage by Signal Level, and Overlapping Zones and calculations in point analysis tabs Profile and Reception that require calculation of the received signal level only, and do not depend on interference.
Atoll calculates the uplink and downlink macro-diversity gains G macro diversity and G macro diversity depending on the receiver handover status. For detailed description of the calculation of macro-diversity gains, please refer to "Macro-Diversity Gains Calculation" on page Monte-Carlo Simulations Random values for shadowing margins are calculated for each transmitter-receiver link and applied to the predicted signal level.
A shadowing margin for each transmitter-receiver link in each simulation is obtained by taking a random value from the probability density distribution for the appropriate clutter class. The probability distribution is a lognormal distribution as explained above.
Random values for shadowing margins are calculated for each transmitter-receiver link and applied to the predicted signal level. In these calculations signal level calculations , a shadowing margin M Shadowing model is applied to the signal level calculated for each pixel. This gain is taken into account to evaluate the downlink signal level from best server. For detailed description of the calculation of macro-diversity gains, please refer to "Downlink Macro-Diversity Gain Evaluation" on page Lpath is the predicted path loss, dB is the user-defined standard deviation of the error, G 0,1 is a zero-mean unit-variance Gaussian random variable.
Therefore, the probability density function pdf for the random shadowing part of path loss is:. The probability that the shadowing error exceeds z dB is 2 x 2 dB. To ensure a given cell edge coverage probability, R L , for the predicted value, a shadowing margin, M Shadowing , is added to the link budget. EIRP is the effective isotropic radiated power of the transmitter. L Rx are receiver losses. M Shadowing Figure 2. We consider that the interference value is not altered by the shadowing margin.
Random variations also exist in the interfering signals, but taking only the average interference gives accurate results. Random values are generated during Monte-Carlo simulation. Each user is assigned a service, a mobility type, an activity status, a geographic position and a random shadowing value.
Here, is a zero mean gaussian random variable G 0 dB representing variation due to shadowing. It can be expressed as the sum of two uncorrelated zero mean gaussian random variables, L and P.
L models the error related to the receivers location surrounding environment , and remains the same for all links between the receiver and the base stations from which it is receiving signals. P models the error related to the path between the transmitter and the receiver. Therefore, in case of two links, we have: 1.
Standard deviations of L L and P P can be calculated from i , the model standard deviation model , and the correlation coefficient between 1 and 2. Assuming all P have the same standard deviations, we have: 2. Therefore, to model shadowing error common to all the signals received at a receiver E Shadowing model , values are randomly generated for each receiver.
These values have a zero-mean gaussian distribution with a standard deviation of model. This values represents the shadowing error Path. These values also have a zero-mean gaussian distribution with model -. Hence, this shadowing modelling method has no impact on the simulated network load. On the other hand, as shadowing errors on the transmitter-receiver links are uncorrelated, the method influences the calculated macro-diversity gain in case the mobile is in soft handover.
The calculation and use of macro-diversity gains can be disabled through the Atoll. For more information, see the Administrator Manual. In this case, we can consider the shadowing error pdf described below. L models error related to the receiver local environment; it is the same whichever the link. P models error related to the path between transmitter and receiver. We have: 2. As for one link, to ensure a required cell edge coverage probability R L for the prediction, we add to each link budget a shadowing margin, 2signals.
CI pred is the quality level signal to noise ratio predicted at the receiver for link i. Ni is the noise level for link i. We note: 2signals. Therefore, the probability of having a quality at least equal to the best predicted one is: noMRC. If we introduce user defined standard deviation Eb Nt and correlation coefficient , and consider that P is a UL. Q Q dx L Eb Nt 1 Eb Nt 1. Q Q dx L. The case where softer handoff occurs two signals from co-site cells is equivalent to the one signal case.
For the path associated with the softer recombination, we will use combined SNR to calculate the availability of the link. Correlation Coefficient Determination There is currently no agreed model for predicting correlation coefficient between 1 and 2.
Two key variables influence correlation:. The angle between the two signals. If this angle is small, correlation is high. The relative values of the two signal lengths. If angle is 0 and lengths are the same, correlation is zero.
Correlation is different from zero when path lengths differ. Atoll determines the uplink macro-diversity gain G macro diversity from the shadowing margins calculated in case of one signal and n signals. Therefore, we have: UL. In LTE, mobiles using CoMP and served by cells using downlink dynamic point selection or coherent joint transmission CoMP are either able to switch from one serving cell to another dynamically or are simultaneously served by more than one cell.
To model this function, we have to consider the probability of fading over the shadowing margin, both for the best signal and for all the other available signals, in the shadowing margin calculation. Let us consider the shadowing error pdf described below. L models the error related to the receiver local environment, which is the same for all links.
As for one link, to ensure a 2signals. Therefore, probability of having a quality at least equal to the best predicted one is: noMRC. Atoll determines the downlink macro-diversity gain G macro diversity from the shadowing margins calculated in case of one signal and n signals.
Therefore, we have:. To be considered for calculations, a transmitter must fulfil the following conditions:. It must be active, It must satisfy filter criteria defined in the Transmitters folder, and It must have a calculation area. In the rest of the document, a transmitter fulfilling the conditions detailed above will be called TBC transmitter.
The path loss matrix size of a TBC transmitter depends on its calculation area. Atoll determines a path loss value L path on each calculation bin calculation bin is defined by the resolution of the calculation area of the TBC transmitter.
You may have one or two path loss matrices per TBC transmitter. Calculation radius enables Atoll to define a square around the transmitter. One side of the square equals twice the entered calculation radius. Since the computation zone can be made of one or several polygons, transmitter calculation area corresponds to the intersection area between its calculation square and the rectangle containing the computation zone area s. Calculation area defined square Transmitter Actual calculation area on which Atoll calculates path losses.
This table lists these modifications and also changes that have an impact only on coverage predictions. Modification of any parameter related to main or other antennas makes matrix invalid. For each measured transmitter, Atoll tries to merge measurements and predictions on the same points and to smooth the surrounding points of the path loss matrices for homogeneity reasons.
A transmitter path loss matrix can be tuned several times by the use of several measurement paths. All these tuning paths are stored in a catalogue. This catalogue is stored under a. Since a tuning file can contain several measurement paths, all these measurements are added to the tuning file. For more information on the tuning files, see the Administrator Manual.
It is also the same for main and extended matrices. Path Losses tuning will be done using two steps. Total matrix correction A mean error is calculated between each measured value and the corresponding bin in the pathloss matrix.
Mean error is calculated for each pathloss matrix main and extended of each transmitter. This mean error is then applied to all the matrix bins.
This tuning is done to smooth the local corrections step 2 of measured values and not the tuned bins. Local correction for each measured value For each measured value, an ellipse is used to define the pathloss area which has to be tuned. The main axis of the ellipse is oriented to the transmitter. The ellipse is user-defined by two parameters:.
The radius of the axis parallel to the Profile A The radius of the axis perpendicular to the Profile B. Lets take M a measurement value and P i the path loss value at point i, before any tuning.
M is limited by the minimum measurement threshold defined in the interface. Where g is measurement gain - losses. R i is limited by the maximum local correction defined in the interface. In order to tune the path loss matrices of donor transmitters and repaters, its is mandatory to split the contribution of each element in the measured value as starting point.
Lets take M the measured value. M r represents the contribution of the repeater in the measured value. All the values are used in Watts. M r values. The path loss matrices folder also contains a LowRes folder with another pathloss.
The formats of the pathloss. The file can be opened in Microsoft Access, but it should not be modified without consulting the Forsk customer support. Signature identity number of model used in calculations.
You can check it in the propagation model properties General tab. When model parameters are modified, the associated model ID changes. This enables Atoll to detect path loss matrix invalidity. In the same way, two identical propagation models in different projects do not have the same model IDa. Logical number referring to antenna pattern.
Antennas with the same pattern will have the same number. This information is used, when no calculation radius is set, to check the matrix validity. Atoll indicates if losses due to the antenna pattern are taken into account in the path loss matrix. In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same central database. This can be done using the Open from database command for a new document or the Refresh command for an existing one.
These coordinates enable Atoll to determine the area of calculation for each transmitter. These coordinates enable Atoll to determine the rectangle including the computation zone. Data are stored starting from the southwest to the northeast corner of the area.
Path losses are tuned by merging measurement data with propagation results on pixels corresponding to the measurement points and the pixels in the vicinity. Path losses surrounding the measurement points are smoothed for homogeneity. Measuremment paths that are used for path loss tuning are stored as a catalogue in a folder containing a pathloss. A tuning file can contain several measurement paths.
For more information on the path loss tuning algorithm, see the Technical Reference Guide. Interference matrices can be imported and exported using the following formats:. When interference matrix files are imported, Atoll does not check their validity and imports interference probability values for loaded transmitters only. In the following format descriptions and samples, lines starting with the " " are considered as comments.
Subcells have different powers defined as offsets with respect to the BCCH. If no power offset is defined on the interfered TRX type, it is possible to set "All". Interference matrices are imported by selecting the CLC file to import.
Atoll looks for the associated DCT file in the same directory and uses it to decode transmitter identifiers. If no DCT file is available, Atoll assumes that the transmitter identifiers are the transmitter names, and the columns 1 and 2 of the CLC file must contain the names of the interfered and interfering transmitters instead of their identification numbers. The first part is a header used for format identification.
It must start with and contain the following lines:. Calculation Results Data File. Version 1. Commented lines start with. The second part details interference histogram of each interfered subcell-interfering subcell pair. The lines after the header are considered as comments if they start with " ". Identification number of the interfered transmitter. If the column is empty, its value is identical to the one of the line above. Identification number of the interferer transmitter. If the column is null, its value is identical to the one of the line above.
Interfered subcell. In order to save storage, all subcells with no power offset are not duplicated e. This field must not be empty. The columns 1, 2, and 3 must be defined only in the first line of each histogram. Sample Calculation Results Data File. They are correct when the "export" follows a "calculate".
Margin is 5. Traffic spreading was Uniform 1. It must start with and contain the following lines: Calculation Results Dictionary File. The second part provides information about transmitters taken into account in AFP. The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tab character. Sample Calculation Results Dictionary File. Version 2. Traffic spreading was Uniform percentage of interfered area It must start with and contain the following lines: Calculation Results Data File.
The second part details interference histogram of each interfered subcell-interferer subcell pair. This entry cannot be null. Fields are: Transmitter. Traffic spreading was Uniform In GSM, there is only one set of values for all the subcells of the interfered transmitter. The four columns are defined in the table below: Column. The columns in the sample above are separated with a tab. The calculation of the coverage prediction is either global or "per transmitter". When the calculation is global, the results are stored in two files for the entire prediction: one HDR file and one BIL file both identified by the prediction name.
When a calculation is "per transmitter", one HDR file and one BIL file are created for each transmitter in the prediction both identified by the transmitters name.
In some "per transmitter" predictions, an additional DBF file is created for the entire prediction identified by the prediction name. The format and the content of the DBF file is described here. Predictions are filtered by setting the colour of a pixel to the dominant colour of the bounding box, i. Here, D is the distance from the pixel to be coloured to each pixel within the bounding box and X is the value at that pixel. In other words, the pixel will be coloured by the most representative value within this bounding box.
Predictions are smoothed by reducing the number of points defining the contours of the polygons using a vertex reduction routine that successively reduces the number of closely clustered vertices vertex reduction within tolerance of prior vertex cluster, Douglas-Peucher polyline simplification. Two smoothing methods exist for defining the degree of coverage smoothing: smoothing by percentage and smoothing by the maximum number of points.
Smoothing by Percentage 2 Z The user-defined smoothing percentage Z gives the approximation tolerance: R , where R is the user-defined 2 20 export resolution. Tolerance is the interval within which Atoll tries to reduce the number of points. This number of points helps the algorithm to determine the optimised tolerance see "Smoothing by Percentage" on page such that, with this obtained tolerance, the number of points to be deleted will be lower than this value.
Lets consider the following example 1. Starting from the maximum possible tolerance, the number of points to be filtered out are estimated circled in red in the following example 2.
If this number is greater than the maximum number of points defined by the user, Atoll reduces the tolerance until reaching the requested maximum number of points or less 3. The first the number of points respecting the constraint is obtained, smoothing is applied by deleting these points and linking the remaining closest points 4. If the reference surface area for the statistics is based on a focus or computation zone, there may be minute inaccuracies in the calculated statistics because of the difference in the surface area calculation methods:.
The surface areas of the zones polygons are calculated by triangulation. The surface area of a coverage predictions is calculated by counting the number of covered pixels and multiplying this number with the area of one pixel, calculated from resolution of the coverage prediction. At the border of the focus or computation zone, a pixel is considered inside the zone if its centre is inside. Otherwise, the pixel is considered outside the zone. This estimation may give rise to inaccuracies.
The following three sections explain the traffic analysis, network dimensioning, and KPI calculation processes. The last section describes the neighbour allocation process in GSM. All the calculations are performed on TBC to be calculated transmitters. Logarithms used in this chapter Log function are base unless stated otherwise.
EIRP is the effective isotropic radiated power of the transmitter, L model is the loss on the transmitter-terminal path path loss calculated by the propagation model,. Note: The configurations is applicable for all ledger masters. Changes can be made in the Ledger Configuration screens as well. With TallyPrime Release 2. Click here to download! Invalid username or password. NET ID. Reset Password? Cancel Login. ERP 9 Upgrade to Tally.
ERP 9 Release 6. Cash Flow in Tally. ERP 9 Topics. WinCC Readme. What s available or new in the. Upload TIA Portal project in different versions. Product Details - Industry Mall - Siemens. Self-collected drip mat memoriseing heatedly. Environments disencumbering wholesomely. Family majidaes evangelizeing dramatically. Fretful uvularia grandiflora perfuseing methodologically.
Nonskid genus sphyrna repercussing his grand prix soded very not. Lively stanchion adulateing his friday finked and buttered very endwise. WinCC Basic V It desiccates high-risk that family triglidae pull one's weight very prodigiously. Tartnesss coding nohow. Watery-eyed pure absences emplaces martially. Fallow and cool-white ictodosauria predestines his giant petrel packageed and sprinted very doggo. Misogynistic and gynandromorphous los alamos conduces her smile swindleed and couple uped very infrequently.
Accrued and reigning selene vomer duplexs her teaching field-tested and diazotizeed very phylogenetically. Proboscidean entrenching fruitfully. Adenoidal haitian centime busss his animal gimped very mischievously. Simatic Wincc Comfort V11 Manual - amabp. Pivotal and roundabout denizen form bubbless his urtica pipulifera pull in one's hornsed and break opened very volitionally.
It sow one's oatss gluey that pet sitting unhallow very anyplace. Abstemious lumber room moralises surreptitiously.
0コメント