Professional Documents
Culture Documents
Administrator Manual
AT332_AM_E0
AT332_AM_E0
Table of Contents
3
Atoll 3.3.2 Administrator Manual
Table of Contents © Forsk 2016
6 Multi-user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.1 Setting Up Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
4
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Table of Contents
5
Atoll 3.3.2 Administrator Manual
Table of Contents © Forsk 2016
6
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Table of Contents
7
Atoll 3.3.2 Administrator Manual
Table of Contents © Forsk 2016
8
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Table of Contents
9
Atoll 3.3.2 Administrator Manual
Table of Contents © Forsk 2016
10
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Table of Contents
11
Atoll 3.3.2 Administrator Manual
Table of Contents © Forsk 2016
12
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter : Atoll 3.3.2 Administrator Manual
About Atoll
Atoll is a 64-bit multi-technology wireless network design and optimisation platform. Atoll is open, scalable, flexible, and
supports wireless operators throughout the network life cycle, from initial design to densification and optimisation.
Atoll includes integrated single RAN – multiple RAT network design capabilities for both 3GPP (GSM/UMTS/LTE) and 3GPP2
(CDMA/LTE) technology streams. It provides operators and vendors with a powerful native 64-bit framework for designing
and optimising current and future integrated multi-technology networks. Atoll supports multi-technology HetNets, small cell
planning, and Wi-Fi offloading.
Atoll Microwave is a complete backhaul and microwave link planning solution based on the leading Atoll platform, which
includes a high performance GIS and advanced data and user management features. Atoll Microwave can share its site data-
base with Atoll radio planning and optimisation modules, thus allowing easy data consistency management across the oper-
ator organisation.
Atoll’s integration and automation features help operators smoothly automate planning and optimisation processes through
flexible scripting and SOA-based mechanisms. Atoll supports a wide range of implementation scenarios, from standalone to
enterprise-wide server-based configurations.
If you are interested in learning more about Atoll, please contact your Forsk representative to inquire about our training solu-
tions.
About Forsk
Forsk is an independent company providing radio planning and optimisation software solutions to the wireless industry since
1987.
In 1997, Forsk released the first version of Atoll, its flagship radio planning software. Since then, Atoll has evolved to become
a comprehensive radio planning and optimisation platform and, with more than 7000 installed licenses worldwide, has
reached the leading position on the global market. Atoll combines engineering and automation functions that enable opera-
tors to smoothly and gradually implement SON processes within their organisation.
Today, Forsk is a global supplier with over 450 customers in 120 countries and strategic partnerships with major players in the
industry. Forsk distributes and supports Atoll directly from offices and technical support centres in France, USA, and China as
well as through a worldwide network of distributors and partners.
Since the first release of Atoll, Forsk has been known for its capability to deliver tailored and turn-key radio planning and opti-
misation environments based on Atoll.
To help operators streamline their radio planning and optimisation processes, Forsk provides a complete range of implemen-
tation services, including integration with existing IT infrastructure, automation, as well as data migration, installation, and
training services.
Getting Help
The online help system that is installed with Atoll is designed to give you quick access to the information you need to use the
product effectively. It contains the same material as the Atoll 3.3.2 User Manual.
You can browse the online help from the Contents view, the Index view, or you can use the built-in Search feature.
You can also download manuals from the Forsk web site at:
http://www.forsk.com/MyForskAccount/
13
Atoll 3.3.2 Administrator Manual
Chapter : Atoll 3.3.2 Administrator Manual © Forsk 2016 Forsk
4. In the Print Topics dialog box, select what you want to print:
• If you want to print a single topic, select Print the selected topic.
• If you want to print an entire section, including all topics and sections in that section, select Print the selected
heading and all subtopics.
5. Click OK.
14
Chapter 1
Getting Started
16
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 1: Getting Started
1 Getting Started
Atoll is an open, scalable, and flexible multi-technology network design and optimisation platform that supports wireless
operators throughout the network life cycle, from initial design to densification and optimisation. Atoll supports a wide range
of implementation scenarios, from single-user standalone to enterprise-wide server-based configurations using distributed
and multi-threaded computing.
This manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage users in
a multi-user environment. In this chapter, the following are explained:
• "Supported Technologies" on page 17
• "Supported Operating Systems" on page 17
• "Supported Database Management Systems" on page 18
• "Supported Installation Configurations" on page 18
• "Recommended Hardware and Software" on page 18
Among other Microsoft Windows components, Atoll 64-bit uses Microsoft Access
Database Engine 64-bit. Microsoft Access Database Engine 64-bit is included in Microsoft
Office 64-bit, and is also available as a free redistributable Microsoft Windows
component from the Forsk support website.
• If the computer on which you wish to install and run Atoll 64-bit already has
Microsoft Office installed, you must upgrade it to Microsoft Office 64-bit (version
2010 SP1 or newer).
• If you do not have Microsoft Office installed, you can download and install the
Microsoft Access Database Engine 64-bit redistributable (version 2010 SP1)
needed by Atoll 64-bit from the Forsk support website.
Note: Installing Microsoft Office 64-bit or the Microsoft Access Database Engine 64-bit
requires uninstalling any 32-bit Microsoft Office components that may be installed on
the computer.
17
Atoll 3.3.2 Administrator Manual
Chapter 1: Getting Started © Forsk 2016
18
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 1: Getting Started
The following table lists the required/recommended hardware and software in a single-user standalone Atoll configuration:
Atoll Workstation
Processor Core i7 at 2.5+ GHz
RAM 8 GB or more
Storage 512 GBa (SSD recommended)
Windows 7
Operating System
Windows 8/8.1 Professional or Enterprise
a. Depends on size of locally stored data.
The following tables list the required/recommended hardware and software in a multi-user thick client configuration:
19
Atoll 3.3.2 Administrator Manual
Chapter 1: Getting Started © Forsk 2016
The following tables list the required/recommended hardware and software in a multi-user thin client Atoll configuration:
20
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 1: Getting Started
21
Atoll 3.3.2 Administrator Manual
Chapter 1: Getting Started © Forsk 2016
22
Chapter 2
Atoll and Component
Installation
This chapter covers the following topics:
• "Installing Atoll Using the Setup Wizard" on page 25
• "Installing Atoll C++ Development Kit" on page 28
• "Setup Command Line Parameters" on page 29
• "Installing and Uninstalling Add-ins" on page 30
• "Installing and Uninstalling Macros" on page 30
• "Atoll Command Line Parameters" on page 31
• "Troubleshooting and Other Information" on page 32
Atoll 3.3.2 Administrator Manual
© Forsk 2016
24
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 2: Atoll and Component Installation
Installing Microsoft Office 64-bit requires uninstalling any 32-bit Microsoft Office
components that may be installed on the computer.
25
Atoll 3.3.2 Administrator Manual
Chapter 2: Atoll and Component Installation © Forsk 2016
4. Select the Create a system restore point check box if you wish to the Atoll setup to create a system restore point.
5. Click Next. The Select Components dialog box appears.
6. Select the components to install.
• Full installation: Atoll and all its components will be installed.
• Compact installation: Only Atoll will be installed.
• Custom installation: Atoll and the selected components will be installed.
7. Click Next.
If you selected the Distributed Calculation Server component for installation, the Logon Information dialog box
appears.
If you did not select this component, the Select Start Menu Folder dialog box appears. In which case, proceed to
step 8.
26
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 2: Atoll and Component Installation
11. Click Install. Atoll and its selected components are installed on the computer.
• If you work with fixed licenses and you installed the Driver for Fixed Licence Keys, restart the computer. Restarting
the computer is necessary for the driver to work.
• If you work with fixed licenses, plug in the fixed license key.
• On the versions of Microsoft Windows that support UAC (disabled before the installation), run Atoll once using an
administrator account and with UAC disabled when the installation is complete.
• If the following files do not already exist in the installation folder, empty ones are
created by the setup:
• [Atoll installation folder]\Atoll.ini
• [Atoll installation folder]\AntennaImport.ini
• [Atoll installation folder]\CWMeasurementsImport.ini
• [Atoll installation folder]\DriveTestDataImport.ini
• [Atoll installation folder]\coordsystems\Favourites.cs
These files are not removed when Atoll is uninstalled.
• If you have installed Atoll on a Citrix server, you must publish it to make it accessible
to users.
To restrict access to the Atoll installation folder, you can assign read/write access rights
to this folder to administrators and read-only rights to end users.
27
Atoll 3.3.2 Administrator Manual
Chapter 2: Atoll and Component Installation © Forsk 2016
28
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 2: Atoll and Component Installation
29
Atoll 3.3.2 Administrator Manual
Chapter 2: Atoll and Component Installation © Forsk 2016
Available Add-ins
The following Atoll add-ins can be downloaded in their most recent version from the Forsk web site at:
http://www.forsk.com/support. For more information, contact to your Forsk representative.
• General add-ins:
• Export to Google Earth (installed with Atoll)
• Multistorey Prediction
• Easy Location Converter
• ArcView Grid ASCII Import
• Multi-RAT Converter
• Difference Plot
• Update Sites With Geo Data
• FCC Boundaries
• Incidence Angle Footprint
• Database add-ins:
• History Module
• Scenario Manager
• Geo Selector
30
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 2: Atoll and Component Installation
The following Atoll macros and scripts can be downloaded from the Forsk web site at http://www.forsk.com/support.
For more information, contact to your Forsk representative.
• Macros:
• Predictions Slideshow
• Display Site Picture and Antenna Documentation
• Show Hide Repeaters and Remote Antennas
• Save Part of Document
• GSM to UMTS
• GSM to LTE
• UMTS to LTE
• CDMA2000 to LTE
• Show in Google Maps Street View
• Scripts:
• Update Pathloss Matrices
• Radio Data Import-Export
• Propagation Models Import-Export
• CW Measurements Import-Export
• Test Mobile Data Import-Export
31
Atoll 3.3.2 Administrator Manual
Chapter 2: Atoll and Component Installation © Forsk 2016
• -log "logfilename"
Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful for
troubleshooting. "logfilename" is the full path and file name of the log file inside quotes.
• -Ini "inifilename"
Instructs Atoll to load the specified initialisation file when run. This can be used to override the default loading of the
Atoll.ini file located in the Atoll installation folder. "inifilename" is the full path and file name of the initialisation file
inside quotes.
• -Cfg "cfgfilename"
Instructs Atoll to load the specified user configuration file when run. This can be used to override the default loading
of the Atoll.cfg file located in the Atoll installation folder. "cfgfilename" is the full path and file name of the user
configuration file inside quotes.
• -Stu "studiesfilename"
Instructs Atoll to load the specified studies XML file when run. This can be used to override the default loading of the
studies XML file located in "C:\Temp\studies.xml". "studiesfilename" is the full path and file name of the studies XML
file inside quotes.
• -Provider providername
Instructs Atoll to use the mentioned providername to access the database server:
• -DataSource server
Instructs Atoll to access the mentioned database server using the given provider.
• -UserId username
Instructs Atoll to access the mentioned Oracle database server using the mentioned username.
• -Password password
Instructs Atoll to access the mentioned Oracle database server using the mentioned password.
• -Project projectaccount
Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount.
• The keywords Provider, Password, UserId, DataSource, and Project are case sensitive.
• It is recommended to install new Windows updates. However, it is also recommended to go through the description
of each update patch to see whether it might have a negative effect on your system or network. Pay special attention
to updates and patches related to networking.
• It is also recommended to keep the Windows updates uninstall folders, named "$NtUninstall...", under the Windows
folder, in case you have to uninstall a certain patch. Some of the update patches might require uninstall folders of
older patches to be available for their own installation.
32
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 2: Atoll and Component Installation
• Fixed license keys cannot be used with "Server"-type operating systems. Therefore, you should not install the driver
for fixed license keys on:
• Microsoft Windows Server 2003
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 R2
• Microsoft Windows Server 2012
• The current version of the driver for fixed license keys (Sentinel SuperPro driver) installed with Atoll is the 7.6.3.
• If Atoll is unable to access the fixed license key, even after a clean installation, try reinstalling the Sentinel SuperPro
driver manually. The driver’s setup program (SPI763.exe) is copied by the setup to the Sentinel subfolder in the Atoll
installation folder if you selected the Driver for Fixed Licence Keys component during the installation. You can also
download the driver from http://www.safenet-inc.com.
• Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed license
keys to work.
• If you get a protection key error message, verify that the fixed license key is correctly plugged in and that the license
has not expired.
• In case the fixed or the floating license key becomes unavailable, Atoll will ask the users currently accessing the key
to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue
working.
• Do not change the computer’s date.
Citrix
• If you have installed Atoll on a Citrix XenApp server, you must publish it to make it available to the users.
• You can get information about Atoll (version, build, type of license and remaining time before expiration, etc.) by
selecting Help > About Atoll in the main menu in Atoll.
ATL file properties store the Atoll version and build number in which the file was last saved, and the technologies contained
in the file. To access the ATL file properties:
1. Right-click the ATL file in the Windows Explorer. The context menu appears.
2. Select Properties from the context menu. The file properties dialog box appears.
3. In Windows XP, click the Summary tab and then the Advanced button.
In Windows Vista, 7 and 8, click the Details tab.
The Atoll version and build number in which the ATL file was last saved are stored in the Revision number property.
The technologies of the document are listed in the Category property.
Support website
• You can download the latest versions of Atoll from the Forsk’s support website by logging in with the user name and
password provided to you by Forsk.
• The Atoll User Manual and other documents are available on the installation CD. More documents are available for
download on the Forsk’s support website.
• The support website also offers you:
• Sample add-ins, macros, and scripts
• Sample geographic data,
• List of fixed issues in the versions available for download,
• List of known issues, and possible workarounds,
• Schedule for upcoming versions,
• List of holidays.
For full contact details for customer support, see back cover.
Acknowledgement
• Atoll uses Inno Setup for installation. For more information, see http://www.jrsoftware.org/isinfo.php.
It is recommended to uninstall Atoll and its components through the Control Panel.
To uninstall Atoll:
33
Atoll 3.3.2 Administrator Manual
Chapter 2: Atoll and Component Installation © Forsk 2016
34
Chapter 3
Distributed Calculation
Servers
This chapter covers the following topics:
• "Setting Up Calculation Servers" on page 37
• "Setting Up Atoll to Access the Calculation Servers" on
page 39
• "Distributed Calculation Process" on page 39
Atoll 3.3.2 Administrator Manual
© Forsk 2016
36
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 3: Distributed Calculation Servers
5. On the Log On tab, enter the user name and password for the user account through which you wish to run this service.
6. Click OK.
37
Atoll 3.3.2 Administrator Manual
Chapter 3: Distributed Calculation Servers © Forsk 2016
Where binPath should correspond to the location of the AtollSvr.exe file, DisplayName is the name of the service as it
will appear in the Windows list of services.
3. To start the service created in step 2, type and run the following command:
net start AtollCalcSvr1
4. Repeat steps 2 and 3 for each new instance of the service that you want to run by replacing "AtollCalcSvr1" and "Atoll
DCS1" by "AtollCalcSvr2" and "Atoll DCS2", respectively, and so on.
You can verify that the new service instances appear in the list of services through Control Panel > Administrative Tools >
Services.
You can also run additional instances of the distributed calculation service by double-click the AtollSvr.exe file located in the
Atoll installation folder. For each new instance of the service, a command prompt window opens. To stop an additional,
manually run service, close the corresponding command prompt window.
38
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 3: Distributed Calculation Servers
39
Atoll 3.3.2 Administrator Manual
Chapter 3: Distributed Calculation Servers © Forsk 2016
40
Chapter 4
License Management
42
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 4: License Management
4 License Management
Atoll can be used on:
• Computers with fixed license keys plugged in to USB ports on the computers themselves.
• Computers connected to a license server with a floating license key plugged in to a physical USB port on the server or
a network-attached USB hub.
The driver for fixed license keys can be installed at the same time as Atoll. For more information, see "Atoll and Component
Installation" on page 25.
The software for managing floating license keys must be installed on a server accessible to the computers on which Atoll is
going to be used. For more information, see "Working with Floating Licenses" on page 43.
For information on the Atoll license management utility, see "Using the Atoll License Manager" on page 46.
HASP hardware keys are supported by Windows 2000 Server and Windows Server 2003
with HASP License Manager 8.20 or above.
43
Atoll 3.3.2 Administrator Manual
Chapter 4: License Management © Forsk 2016
Do not plug the floating license key into the server before installing the device driver.
Wait for the HASP license manager setup to indicate when to plug in the key.
• If the floating license server is protected by a firewall, port 475 must be open for the
UDP protocol.
• In case the fixed or the floating license key becomes unavailable, Atoll will ask the
users currently accessing the key to save their open documents before Atoll closes. If
the key becomes available again, Atoll will let the users continue working.
• The floating license key can become unavailable and a key protection error message
appears in Atoll if the license management server is heavily loaded. Check if there is
any application running on the server that might be causing the problem. If this is the
case, remove any such application from memory. If this is not possible, try changing
the latency associated to the HASP License Manager in accessing the key.
• You can optionally install the HASP Monitor on the floating license server, or on one
or several other computers, to monitor the token allocation and retrieval activity. The
HASP Monitor displays the list of computers using tokens available on the floating
license key.
The installer is not compatible with Windows 8 or later. To install the HASP Device Driver
on Windows 8 or later, right-click the installer, select Properties > Compatibility and run
the program in Windows Vista (Service Pack 2) compatibility mode.
44
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 4: License Management
Once the HASP license manager has been installed, the floating license key must always
remain plugged in.
System administrators might want to restrict access to the HASP license manager
installation folder. To do this, you can assign read/write access rights to this folder to
administrators and read-only rights to end-users.
File Location
If used, the nhsrv.ini file must be located in the installation directory (recommended) or a directory listed in the system path
variable.
File Contents
The following is a sample nhsrv.ini file that shows how to set a list of computers allowed access to the floating license server.
Complete syntax can be found on the HASP installation CD or on the Safenet website.
[NHS_IP]
NHS_USE_UDP = enabled ; enabled or disabled (default: enabled)
NHS_USE_TCP = enabled ; enabled or disabled (default: enabled)
NHS_IP_portnum = 475 ; IP port number (default: 475 (IANA registered))
; CAUTION: clients must use the same port !
File Location
The nethasp.ini file must be located in the installation directory (recommended) or a directory listed in the system path
variable.
A nethasp.ini file located in the Atoll installation folder has priority over any nethasp.ini file located elsewhere.
Storing the nethasp.ini file in the Windows folder instead of the Atoll installation folder can be useful if you have more than
one version of Atoll installed, and you wish to access the same floating license server. This avoids making a copy of the file in
each Atoll installation folder, but might not work on the latest versions of Windows.
File Contents
The following is a sample of the nethasp.ini file with the minimum required information. Complete syntax can be found on
the HASP installation CD or on the Aladdin website.
[NH_COMMON]
NH_IPX = Disabled ;Use the IPX protocol - Enabled or Disabled
45
Atoll 3.3.2 Administrator Manual
Chapter 4: License Management © Forsk 2016
• Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if these
exist.
• These fields define the timeout delays depending to the network. They can be useful
in slow networks and should be set only if required.
46
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 4: License Management
4. Under Available licenses, select a license key in order to display the information related to it.
Under Selected key the following information is available for the selected key:
• Number: Unique key number given by the key provider. This number must be communicated to Forsk, when
requested, for reprogramming the license key.
• Type: The type of key, Fixed license or Floating license.
• Reference: Unique floating license key reference provided by Forsk. This number must be communicated to Forsk,
when requested, for reprogramming the license key. This reference is also printed on the sticker on the key.
• Location (server): Name of the floating license management server on which the floating license key is plugged.
• Under Modules and licenses, all the Atoll modules available on the selected key are listed along with the numbers
of license tokens of each.
• Under Number of licenses, the Modify buttons are reserved for Forsk use only.
• Under Dates and durations, the following dates and durations are available:
• License start
• License end
• Duration of validity
• Time bomb
A purchased Atoll license corresponds to a particular Atollversion. There is no time limit on using this version.
However, yearly maintenance must be purchased in order to access newer versions with updates and bug fixes.
When you purchase maintenance, Forsk reprograms your license keys to allow access to new versions.
The time bomb date is the end date for maintenance. When the time bomb date passes, the license key stops
working. You can then choose to either purchase maintenance for the next year, and benefit from the new
features and bug fixes, or have the license key reprogrammed without maintenance for the next year, in which
case users can continue working with the existing version.
47
Atoll 3.3.2 Administrator Manual
Chapter 4: License Management © Forsk 2016
Atoll can inform you about the approaching time bomb date 30 days in advance. This alert can be configured
through the Atoll.ini file.
Do not attempt to modify the time bomb settings on the fixed license key. Contact Forsk
support.
Do not change the computer’s date.
• Under Profile signature, the PID (profile signature or ID) is the encrypted description of the user rights available
on the key. Each key has a unique PID.
• Under Current profile summary, all of the above information is summarised.
Do not attempt to reprogram a license key without full information and support from
Forsk support.
48
Chapter 5
Managing Databases
50
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
5 Managing Databases
In Atoll, you can work with standalone documents, i.e., documents without any back-end database, or with documents
connected to databases. Standalone documents are more portable, however a back-end database is required when working
in a multi-user environment. In multi-user environments, several users work on the same project and a central data storage
is necessary for keeping the data modifications made by a team of radio planning and optimisation engineers.
Atoll enables you to create databases, upgrade them to newer versions, archive and refresh data with databases, manage and
resolve data conflicts, and create and work with multi-level databases.
A database server can store one or more databases. For example, a GSM, a UMTS, and a microwave links database can be
stored on the same database server using the same RDBMS (Oracle, for example).
In this chapter, the following are explained:
• "Atoll Database Templates" on page 51
• "Customising Atoll Database Structures" on page 52
• "Atoll Management Console" on page 53
• "Creating New Databases" on page 55
• "Upgrading Existing Databases" on page 58
• "Working With Multi-level Databases Using Oracle" on page 61
• "Setting Database Access Privileges" on page 66
• "Managing Data Modifications History" on page 67
Database template files must not be modified without consulting Forsk customer support.
The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field types and
sizes in different RDBMS:
Atoll Oracle Equivalent Microsoft SQL Server Equivalent Microsoft
Access
Field Type Length Field Type Length Field Type Length Equivalent
Float 4 FLOAT 32 real 4 Single
Double 8 FLOAT 64 float 8 Double
Integer 4 NUMBER 11 int 4 Long Integer
Short 2 NUMBER 6 tinyint 1 Integer
Boolean 2 NUMBER 1 bit 1 Yes/No
Text a VARCHAR2 Variable1 varchar Variable1 Text1
Variable
Memo Variable VARCHAR2 2000 varchar 4000 Memo
b > 2000
CLOB
Binary Variable image 16 OLE Object
BLOBc Variable
a. Lengths for these fields are specified in parentheses in the database structure tables.
b. Character large object
c. Binary large object
51
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console" on
page 53 and "Upgrading Existing Databases" on page 58, respectively.
Do not add custom fields to data tables in the default document templates. It is
recommended to add them in copies of the default templates so that the original database
structure remains intact.
If you add custom fields to a default template of your current Atoll version (N-1), and forget
to add the same in the template of the next version (N), the Atoll Management Console of
the next version (N) will consider that these fields were intentionally removed by the
administrator. It will delete such custom fields from the database during upgrade.
Custom fields can be added to data tables at different stages keeping in mind that:
• Custom fields added directly to the Atoll database templates (MDB files), using Microsoft Access 2003, will be
available in all new Atoll documents created from that template. A new database created by exporting such a
document will also contain these custom fields.
• Custom fields added to an Atoll document through the Atoll user interface will not be automatically added to the
corresponding Atoll database template. However, a new database created by exporting such a document will contain
these custom fields. For more information on adding custom fields to Atoll documents through the user interface, see
the User Manual.
• Custom fields added to an Atoll database will be available in all new Atoll documents created from that database.
To add a custom field to a data table:
1. Add the custom field to the definition of the data table by defining its name, type, and size.
2. Add a corresponding record in the CustomFields table and enter values for each of the following fields:
User Interface
Field Description
Caption
TABLE_NAME Database name of the data table that contains the field
COLUMN_NAME Name Database name of the field
DEFAULT_VALUE Default value User-defined default value (optional)
CHOICE_LIST Choice list User-defined choice list for text fields (optional)
Caption of the field as it will appear in the user interface (optional but
CAPTION Legend
recommended)
Semicolon-separated list of the names of groups to which the field belongs
GROUP_NAME Group
(optional)
1: Custom field only accepts values listed in the choice list
CHOICE_TYPE Restricted
0: Custom field accepts values other that those listed in the choice list
1: Custom field is read-only in the user interface
DISPLAY_TYPE Read-only
0: Custom field is modifiable in the user interface
52
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
Custom fields are for information only and are not taken into account in calculations. You
can find these fields on the Other Properties tab of an object’s Properties dialog box.
You can set your own default values for standard as well as custom fields using the CustomFields table. User-defined default
values entered in the CustomFields table have precedence over the predefined default values.
To enter a user-defined default value for any field, add a new record in the CustomFields table and enter values for each of
the following fields:
User Interface
Field Description
Caption
TABLE_NAME Database name of the data table that contains the field
COLUMN_NAME Name Database name of the field
DEFAULT_VALUE Default value User-defined default value
For floating point default values, make sure that all the users use the same decimal
symbol.
You can set your own choice lists for standard as well as custom text fields using the CustomFields table. User-defined choice
lists entered in the CustomFields table have precedence over the predefined choice lists.
To enter a user-defined choice list for any text field, add a new record in the CustomFields table and enter values for each of
the following fields:
User Interface
Field Description
Caption
TABLE_NAME Database name of the data table that contains the text field
COLUMN_NAME Name Database name of the text field
CHOICE_LIST Choice list Choice list items, one per line
For example, you can replace the default choice list available for the SUPPORT_INFO field in the Sites table with a different
list of options corresponding to the different types of towers and pylons that may exist in your network.
• You can enter one of the choice list items in the DEFAULT_VALUE in order to set a
default value for the text field.
• For custom text fields, you can set the CHOICE_TYPE to 1 if you want the custom text
field to only accept values listed in the choice list. By default, CHOICE_TYPE is
considered to be 0 meaning that users are allowed to enter values other than those
defined in the choice list.
53
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking the AMC.msc
file in the management subfolder of the Atoll installation folder. The Atoll Management Console runs using the Microsoft
Management Console environment.
When the Atoll Management Console is run for the first time, you must register your database server in order to have the
databases installed on the server to be available in the Atoll Management Console.
To register a database server:
1. Open the the Atoll Management Console.
2. In the left pane, right-click Database under Administration Atoll. The context menu appears.
3. Select Register a New Server from the context menu. The Data Link Properties dialog box appears.
4. On the Provider tab, select the provider for your database server and click Next.
5. On the Connection tab, enter the server name, user name, and password required to access the database server.
6. Click Test Connection to verify that the information you entered is correct. An information message should appear to
indicate that the "Test connection succeeded" .
7. Click OK. The selected database server is registered and available in the Atoll Management Console. You now have
access to the features offered by the Atoll Management Console.
54
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
The tree in the left pane lists the registered database servers. Registered database servers can be connected ( ) or
disconnected ( ).
The right pane lists the databases available on the connected database server currently selected in the left pane. The current
user can be the owner of one of the listed databases; his name appears between parentheses in the title bar after the name
of the database owner. One Oracle user can create and own one database. Therefore, for each new database, you must create
a new Oracle user who will own the new database.
The following details are available for databases created or upgraded using the Atoll Management Console:
• Name: name of the database preceded by an icon which indicates whether the database corresponds:
• to the current version of Atoll ( ), or
• to a previous version of Atoll not yet upgraded to the current version of Atoll ( )
• Owner: name of the database owner.
• Version: most recent Atoll version to which the corresponding database was upgraded.
Only the databases corresponding to the current and previous major releases of Atoll are
listed. The version is indicated if the database has been upgraded via the AMC.
• The databases corresponding to other major releases of Atoll are not listed.
• If the database server does not contain any database corresponding to the current/
previous major release of Atoll, no database is listed.
55
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
You must have administrator rights to the database and to the server for creating new
databases.
If your password must contain special characters, for example, !, ?, etc., type the
password inside double quotation marks: "mypassword!" instead of mypassword!
5. Click Next. The Name the database and specify a network type page appears.
6. Enter a Name for the new database and select the Network type. The Network type can be one of the database
templates installed with Atoll.
56
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
Atoll and the Atoll Management Console must have the same version. This means that
the Atoll Management Console can create databases based on the database templates
installed with Atoll of the same version.
7. Click Next. The Specify units and coordinate systems page appears.
8. Select a Transmission power unit and a Reception threshold unit.
9. Under Coordinate systems, select a Cartographic projection system and the System to be used in the database.
10. Click Next. The Ready to create database page appears. This page provides a summary of the selected parameters.
11. Click Execute. The Atoll Management Console creates the new database with the defined parameters on the selected
database server.
A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure:
Among other uses, the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. This table stores
the data required by the Atoll Management Console for database upgrade.
Databases created with Atoll, instead of the Atoll Management Console, and databases that have never been upgraded using
the Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME, ATOLL_VERSION, and
ATOLL_BUILD fields. Upgrading such databases using the Atoll Management Console can take a long time because the Atoll
Management Console must search for the data required for the upgrade in the whole database.
For more information on upgrading databases, see "Upgrading Existing Databases" on page 58.
All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain a
non-modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table. It is not added to
Microsoft Access databases.
By setting an option in the Atoll.ini file, you can instruct Atoll to always use a defined
database type (MS Access, SQL Server, or Oracle). In this case, the Export to a Database
dialog box will be skipped and the database-specific authentication dialog box will appear
immediately. For more information, see "Setting the Type of Database Being Used" on
page 195.
5. Depending on the selected database type, enter the user name and password of the database owner.
6. Click Save. Atoll asks whether you want to connect the document to the new database.
7. Click Yes or No. Atoll creates a new database based on the document.
A database created using Atoll contains an ATOLL_ADMIN table with the following structure:
57
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
• Before creating the database, make sure that you have defined the coordinate
systems and units in the source document.
• Before creating the database, make sure that you have added any required custom
fields. Custom fields of the source document are created in the new database.
• If you want to add a custom field to the data structure after you have created the
database, you will have to add it directly in the database and not through Atoll.
Custom fields added to a database are available to users connected to the database
when they create a new Atoll document from the database or refresh an existing one.
• Do not skip a major version of Atoll. For example, if you are currently using Atoll 2.8.x,
you should first upgrade the database to Atoll 3.1.x before upgrading to Atoll 3.2.x.
Upgrading your database will be simpler if you do not skip a major version. If you skip
or have skipped an intermediate major version, you must upgrade your database
twice in order to make it compatible with the new version.
• If you are upgrading a database which was neither created nor already upgraded (at
least once) using the Atoll Management Console, see "Upgrading Databases for the
First Time" on page 59 first.
The Microwave Radio Links template now supports Radio Series. Similar microwave
radios belong to the same radio series. In order to organise the microwave radios
(microwave equipment) in radio series before the database upgrade:
1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to the
MWEquipments table.
2. Enter the radio series names in this field for each radio, i.e., group the radios of
the same series under the same radio series name in the FAMILY field.
Without this manual organisation of the microwave radios into radio series, the database
upgrade will create one radio series for each microwave radio.
58
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
• If some of the tables in a database have been replaced by views, the Database
Upgrade Wizard asks to select the views to upgrade. Select the views that you want
the Atoll Management Console to upgrade and click Execute.
If, for example, the definition of a view is given by the condition:
Select Field1, Field2 from Table1 where (Condition1);
The wizard first upgrades the schema of Table1 and then upgrades the definition of
the view. The upgraded definition will take the newly added fields into account.
• When you upgrade a 3GPP Multi-RAT database, the Atoll Management Console adds
any missing tables to the database. For example, a database created by exporting a
3GPP Multi-RAT document containing only GSM contains only GSM tables. When
upgraded, the Atoll Management Console will add the UMTS and LTE tables to the
database as well.
Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console during
the upgrade.
If you use the Atoll Management Console’s history management tool, you must repair
the upgraded database in order to continue using this tool. For more information, see
"Managing Data Modifications History" on page 67.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as
required by the new version. For information on manually upgrading a database, see "Upgrading Databases Manually" on
page 60.
59
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
For the Atoll Management Console to be able to recognise obsolete or deleted fields from
database tables, it is imperative that the ATOLL_ADMIN table exist in the database. This
means that when upgrading a database for the first time using the Atoll Management
Console, the database administrator will have to remove the obsolete fields manually.
Once the Atoll Management Console has been used to upgrade a database, it will be able
to recognise obsolete or deleted fields in the following upgrades.
If you are upgrading your database using a script based on the data structure
modifications listed in the Data Structure Reference Guide, you must:
• Add the ATOLL_ADMIN table to the database. For more information on this table,
see "Creating a New Database Using the Atoll Management Console" on page 55.
• For LTE databases, rename the smart antenna models and equipment as follows:
• Delete existing smart antenna equipment ("Optimum Beamforming Smart
Antenna") from the SmartAntennas table.
• Delete existing smart antenna model ("Optimum Beamformer") from the
SmartAntennasModels table.
• Create a new smart antenna equipment ("Conventional Beamforming Smart
Antenna") in the SmartAntennas table. Set the smart antenna model for this
equipment to "Conventional Beamformer."
60
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
A new record is added to the networks table for each technology added to the database.
61
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
Project databases are intermediate databases created from a common master database. A project database contains the
original master database, that remains hidden from the end-users, and an copy of the master database accessible to the end-
users. When a user modifies a record, only its accessible copy is modified in the project database. The original value in the
master database remains unchanged until the database administrator archives all the modifications from the project
databases to the master database.
Project databases can be used to improve performance and ensure data security and reliability. Instead allowing all the end-
users to work directly with the master database, one or many project databases can be created with copies of the entire
master database or a part of the master database corresponding to a given physical location or region.
Creating and working with project databases restricts the number of users who have access to the master database. This
reduces the risk of conflicts in the database as only the database administrator can archive modifications from project
databases to the master database.
For example, if a country-wide network database is accessible to all end-users:
• The probability of human error increases with the number of users who can modify data.
• The probability of conflicts increases with the number of users accessing the database.
• The performance is reduced because the entire network is loaded every time a user accesses the database.
• For routine city-wide planning, an end-user does not require the entire country’s database to be loaded.
Project databases can be created using filters on sites, thus allowing users to work with regional databases. A possible scenario
is depicted in the figure below:
62
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
Multi-level databases can be set up using the Atoll Management Console. In this section, the following are explained:
• "Creating Project Databases" on page 63
• "Archiving Project Databases to Master Databases" on page 65
• "Refreshing Project Databases from Master Databases" on page 66
For creating a project database, you must have enough rights to be able to create new
tables in the master database schema.
Some versions of Oracle let you create a new user through this dialog box but the new
user is not assigned DBA rights, which makes the new user unable to create the project
database. Therefore, it is recommended to create the new user with DBA rights directly
in the database before create the project database using the Atoll Management Console
using the new user account.
63
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
A project database created using the Atoll Management Console contains an ATOLL_ADMIN_PRJ table, in addition to the
ATOLL_ADMIN table, with the following structure:
Field Type Description
NAME Text (50) The name of the project database
Text
MASTER_CONNECTION Connection parameters to the master database
(255)
MASTER_DBSCHEMA Text (50) The name of the original schema of the master database
Data extraction method used to select the sites to include in the project
SEL_METHOD Short
database
Text
SEL_PARAM Site selection method parameters (the SQL condition, if any)
(255)
SEL_PGON Memo Site selection polygon (if used)
64
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above details
of a project database:
1. In the right pane, right-click the project database in the list. The context menu appears.
2. Select Properties. The database Properties dialog box appears.
3. The Properties dialog box contains three tabs:
• General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.
• Project Database tab: Under Source master database, the Project Database tab displays the Connection settings
to and the Owner of the master database. Under Site selection, this tab displays the site filtering Method and
Settings used for creating the project database.
• Statistics tab: The Statistics tab displays the number of records in each table of the project database.
The project database contains a copy of all the original tables of the master database. The names of the original tables are
prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under the
name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot be
different from those of the master database.
All the tables in a project database contain a non-modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED field.
The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in master database
using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set to
TRUE for records modified in the project database.
65
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
Under Errors, Atoll Management Console displays errors that occurred during archive.
4. Once archive is complete, click Close.
66
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
All of these permissions can be set as regular SELECT, INSERT, UPDATE, and DELETE privileges on database objects. Triggers
can also be used to prevent users making certain actions on the database.
Different permissions for different users can be granted directly or through database roles. Database roles enable you to
define permission templates, which can then be assigned to existing or new users of the database.
You can use the Atoll Management Console for defining user access rights to database tables and elements in the Atoll GUI.
For more information on managing user access rights, see "Managing User Accounts and Access Rights in Oracle" on page 81.
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data Modifications
History Management" on page 68 for more information). If you want, you can also purge old data modifications history (see
"Purging Old Data Modification Records" on page 69 for more information).
The history management tool is available for Oracle databases. The following section describes how to set up the history
management tool using the Atoll Management Console.
The above fields are also added to all the tracked tables in order to store information about the latest modification. Therefore,
opening any tracked table, you can see when a record was last modified, by whom, and the type of modification.
67
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
68
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
3. In the Data Modifications History Management dialog box, right-click the table for which you want to purge old data
modifications history. The context menu appears.
4. In the context menu, select Purge. The table record purge dialog box appears (see Figure 5.12 on page 70).
69
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
5. Under Purge data modifications recorded before, move the slider to select from which date onwards you want to
keep the data modification history records.
All the data modification history records before this date will be deleted. The fields under Record Information indicate
the number of Records that will be left after the purge and the corresponding Size.
6. Under Options, select the Keep creation and deletion records check box if you want to keep the records related to
creation and deletion.
7. Click Purge. All the history records before the selected date are deleted from the history management table.
If you selected the Keep creation and deletion records check box, creation and deletion records before the selected
date are not deleted.
70
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
Here:
Parameter Description
job_name AHMS_<schema_name>
job_type PLSQL_BLOCK
job_action Actual PL-SQL code for the purge
start_date SYSTIMESTAMP
Frequency of the scheduled purge
repeat_interval
For example, once a month, on the 15th, at 1:30am: "freq=month;monthday=15;byhour=1;byminute=30"
end_date NULL
enabled TRUE or FALSE, based on the user input
comments Custom character string with codes for easy identification of the scheduler type
71
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
5.9 Appendices
The first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how to set up
databases for co-planning taking the example of GSM and UMTS MS Access databases.
Assumptions:
• Connection string = AtollDB
• GSM Project account = AtollADMINGSM, password = ADMINGSM
• UMTS Project account = AtollADMINUMTS, password = ADMINUMTS
• Common Project account = AtollADMIN, password = ADMIN
To share the Sites table:
1. Create the AtollADMIN.SITES table and copy all sites from AtollADMINGSM.SITES to AtollADMIN.SITES.
4. Commit.
72
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
3. Create a POSTCODETABLE table to link users and postcodes (one user can be linked to several postcodes).
4. Create a view owned by this user hiding the actual SITES table through these commands.
"with check option" is very important as it specifies that insert and update operations performed through the view
must result in rows that the view query can select.
5. Hide the TRANSMITTERS table, so that Atoll can only select transmitters whose associated sites are present in the
SITES view.
SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS;
SQL > create view TRANSMITTERS as
select * from PRIVATE_TRANSMITTERS
where SITE_NAME in (select NAME from SITES);
6. Commit.
SQL > commit;
The error message "ORA-01402: view WITH CHECK OPTION - clause violation" appears if
you try to archive a record that does not match the project.
73
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
4. Export the GSM document to the database by entering the user name and password for GSMUser.
5. Log in as GSMUser to the database.
6. Delete the Sites table.
7. Open the UMTS document in Atoll.
8. Export the UMTS document to the database by entering the user name and password for UMTSUser.
9. Log in as UMTSUser to the database.
10. Right-click the Sites table and select Create a View from the context menu. The Create View dialog box appears.
a. Enter Sites as the view name.
b. Enter GSMUser as the name of the schema which will contain the view.
c. Select Table as object type.
d. Enter UMTSUser as the name of the schema you want to use.
e. Select Sites as the object used to model the view.
11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now the
same as UMTSUser Sites table.
12. Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select.
To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
4. Export the GSM document to a Microsoft Access database (GSM.mdb).
5. Open GSM.mdb in Microsoft Access.
6. Delete the Sites table.
7. Open the UMTS document in Atoll
8. Export the UMTS document to a Microsoft Access database (UMTS.mdb).
9. Open GSM.mdb in Microsoft Access.
10. In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007 and later,
select External Data > Access Database.
11. In Microsoft Access 2003 and earlier, the Link dialog box appears. Select UMTS.mdb. In Microsoft Access 2007 and
later, the Get External Data - Access Database dialog box appears, specify UMTS.mdb as data source and select Link
to data source by creating a linked table.
12. Click OK. The Link Tables dialog box appears.
13. Select the Sites table.
14. Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb. The tables
contain the same data.
Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with the other
tables in the database. See the Data Structure Reference Guide for detailed information on database tables.
• The UMTS Sites table has more fields than the GSM Sites table. Therefore, you should
replace the GSM Sites table with the UMTS one.
• When you upgrade one by one the databases that share the Sites table, any triggers
that you might have set on the Sites table of the database that is upgraded first might
be overwritten by the triggers set on the Sites table of the database upgraded last. In
order to avoid the triggers being overwritten, you can rename the triggers on the Sites
table of the database upgraded first (by adding, for example, the database technology
as prefix to the trigger names) before upgrading the other database(s).
When users work with two Atoll documents and databases at the same time, it is important to have a protection mechanism
against database inconsistencies. If a user archives the changes made in one document but forgets to archive the changes
made in the other, this can create inconsistencies between the two networks.
74
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 5: Managing Databases
To ensure database consistency, you can save or archive the linked documents at the same time, i.e., when a user saves or
archives one document, Atoll automatically saves or archives the other. This can be done using a macro triggered by the save
or archive operation.
75
Atoll 3.3.2 Administrator Manual
Chapter 5: Managing Databases © Forsk 2016
76
Chapter 6
Multi-user
Environments
This chapter covers the following topics:
• "Setting Up Multi-user Environments" on page 79
• "Components of Multi-user Environments" on page 79
• "Managing User Accounts and Access Rights in Oracle"
on page 81
• "Appendices" on page 87
Atoll 3.3.2 Administrator Manual
© Forsk 2016
78
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 6: Multi-user Environments
6 Multi-user Environments
A multi-user environment is where more than one user work simultaneously on an Atoll project, sharing data over a network.
In large, structured multi-user environments, groups of users can work on specific parts of a common, large-scale project. For
example, different user groups can work on different regions of a country-wide network. In this chapter, the following are
explained:
• "Setting Up Multi-user Environments" on page 79
• "Components of Multi-user Environments" on page 79
• "Managing User Accounts and Access Rights in Oracle" on page 81
• The Atoll administrator should regularly update the shared path loss matrices.
• As the users work on the network and archive changes in the database, the Atoll
administrator should regularly run data integrity checks on the master Atoll
document after loading modified data from the master database. For more
information, see "Appendix 1: Checking Data Integrity" on page 87.
79
Atoll 3.3.2 Administrator Manual
Chapter 6: Multi-user Environments © Forsk 2016
If you wish to add custom fields in the Atoll document, you should first add the field in
the database, and then update your Atoll document from the database. Custom fields
added in an Atoll document connected to a Microsoft Access database are automatically
added to the database. However, this is not the case with other RDBMS, such as Oracle.
The same database server can be used to store one or more master databases
corresponding to different technologies. For example, a GSM database and a UMTS
database can be stored on the same database server using the same RDBMS (Oracle, for
example).
80
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 6: Multi-user Environments
If users modify geographic data locally, for example edit clutter or traffic in their
respective projects, they should store these modified geographic data locally so that the
modifications do not impact other users.
The shared path loss matrices must be unlocked in order for users to be able to work with
them. You can check whether path loss matrices are unlocked in the Propagation tab of
the Transmitters folder’s properties dialog box.
If you wish to add custom fields in the Atoll document, you should first add the field in
the database, and then update your Atoll document from the database. Custom fields
added in an Atoll document connected to a Microsoft Access database are automatically
added to the database. However, this is not the case with other RDBMS, such as Oracle.
81
Atoll 3.3.2 Administrator Manual
Chapter 6: Multi-user Environments © Forsk 2016
on a database for the first time. The database has to be of the same version as the Atoll Management Console being used to
manage user accounts and access rights.
To make your database compatible with the user management tool:
1. In the Atoll Management Console window, right-click the database whose user accounts you wish to manage.
2. Select Manage Users. The User Management dialog box appears.
3. Click Yes when asked whether you want to make your database compatible with the user management tool.
The Atoll Management Console adds a GUIUserRights table in the database with the following structure:
Each user’s interface access rights are stored in a unique record in the GUIUserRights table. The contents of the RIGHTS field
have the following syntax:
RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD
The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 82.
If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have
unrestricted access to the Atoll interface.
If interface access rights are defined for a database, and a user creates a document from the database or opens a document
connected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and password
to access the database.
If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct, the user’s
interface access rights are set to read-only by default (for more information, see "Defining Database and Interface Access
Rights" on page 82). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atoll
interface (table grids and properties dialog boxes). A message is displayed in the Event Viewer window to inform the user of
his interface access rights. It is possible to remove interface access restrictions by disconnecting the document from the
database. However, a disconnected document cannot be reconnected to the database.
The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence, users can
work on their documents without actually being connected to the database, and still have their usual interface access rights
applied in the document.
Atoll does not ask for the user name and password when a document is opened using the
API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his user name
and password in the connection properties, Atoll reads and applies the interface access rights defined for the new user.
82
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 6: Multi-user Environments
3. Under Atoll projects, select the project for which you want to manage user accounts.
4. Under List of users, select the user account whose database and interface access rights you want to set.
Users who have database access rights in the selected database are marked with the green icon ( ). Users who do
not have any database access rights in the selected database (Category = No Access) are marked with the red icon
( ). Locked (deactivated) user accounts are marked with a yellow lock icon ( ). For more information on locked
user accounts, see "Creating and Managing User Accounts" on page 85.
5. You can set the Filter list to:
• All users: Users with access ( ), without access ( ), or locked ( )
• Users with access ( )
• Administrators: Users with administrator rights among the users with access
• Standard users: Users with standard rights among the user with access
• Read-only users: Users with read-only access rights among the users with access
6. Under Database rights, you can select a database access Rights category:
• No access: User without read and write access to the database. The database is not visible to these users and they
are not allowed to create Atoll documents based on this database.
• Read only: Users allowed to create Atoll documents from the database but without write permissions to any table
of the database, i.e., users cannot archive changes made in the Atoll document to the database.
• Standard: Users with read and write access to some tables of the database containing radio network data (see
table below).
• Super-User: Users with read and write access to all the tables of the database.
Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS other
than Oracle, you will not be able to set database access rights. You can, however, still set interface access rights as
explained below.
83
Atoll 3.3.2 Administrator Manual
Chapter 6: Multi-user Environments © Forsk 2016
7. Under Interface rights, you can select interface access rights for:
• Access to radio data:
• Full: (RADIOPARAMS = ALL) Users with read and write access to all the tables and properties dialog boxes.
• Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and
properties dialog boxes including sites, transmitters, cells, carrier aggregation groups, carrier aggregation
group definitions, CoMP sets, CoMP set definitions, MBSFN areas, MBSFN area definitions, subcells, repeaters,
remote antennas, secondary antennas, intra- and inter-technology neighbours and exceptional pairs, site and
transmitter lists, microwave point-to-point, point-to-multipoint, and multi-hop links, microwave repeaters,
microwave hubs.
• Read only: (RADIOPARAMS = NONE) Users with read-only access to tables and properties dialog boxes, i.e.,
users are not allowed to modify radio network data and parameters.
• Database access rights and access rights to radio data in Atoll can be set
independently. For example, a user can have full access rights in the interface but not
be allowed to archive changes to the database.
• However, access rights in the interface should only be granted if the user has at least
read-only access to the database.
84
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 6: Multi-user Environments
4. Under Identification:
• Enter a User name, a Password, and Confirm your password.
• Select a Tablespace, a Temporary tablespace, and a Profile.
5. Under Advanced:
• Select Use operating system authentication if you want to use OS authentication prefix with the user name.
• Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a Quota
in megabytes.
6. Click OK. The new user account is created.
To edit a user account:
1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears.
2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83).
3. Under List of users, select the user account whose information you want to edit.
4. Under Users, click Edit. The Create/Edit User dialog box appears (Figure 6.3 on page 85).
5. Under Identification, modify the user’s Password and the assigned Tablespace, Temporary tablespace, and Profile.
6. Under Advanced:
• Select Use operating system authentication if you want to use OS authentication prefix with the user name.
• Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a Quota
in megabytes.
7. Click OK. The new account information is saved.
To deactivate (lock) a user account:
1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears.
2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83).
3. Under List of users, select the user account you want to deactivate.
4. Under Users, click Edit. The Create/Edit User dialog box appears (Figure 6.3 on page 85).
85
Atoll 3.3.2 Administrator Manual
Chapter 6: Multi-user Environments © Forsk 2016
The duration of the database rebuilding process depends on the number of users and on
the database processing speed.
86
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 6: Multi-user Environments
6.4 Appendices
The following appendices provide additional information on:
• "Appendix 1: Checking Data Integrity" on page 87
• "Appendix 2: Database Regionalisation" on page 87
• "Appendix 3: Calculating Path Loss Matrices" on page 88
• "Appendix 4: Path Loss Matrices From Different Sources" on page 88
If you fix any problems in the Atoll document, you must archive the changes in the
database in order to fix the problems for all the users working with that database.
87
Atoll 3.3.2 Administrator Manual
Chapter 6: Multi-user Environments © Forsk 2016
You should only calculate the shared path loss matrices when they are not being accessed
by users.
You should also make regular backups of the master Atoll document. The above macro
could also create a backup ATL file of the master Atoll document on a regular basis. This
file can be overwritten daily, whenever path losses are calculated.
88
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 6: Multi-user Environments
Path loss matrices calculated by other tools should include antenna pattern attenuation
(i.e., should be masked) in order to be consistent with the path loss matrices calculated
by Atoll.
The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf file
provides the means to manage several sources of path loss matrices. This file stores, among other information, the validity
status and the location (path) of the path loss matrix files for each transmitter.
Let us assume that users of group A wish to work with the path loss matrices generated by Atoll only, and users of group B
wish to work with path loss matrices generated by a different tool for a part of the network and with path loss matrices
generated by Atoll where the matrices from the other tool are not available.
Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files is
C:\Path_Loss_Internal, and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External.
The Pathloss.dbf file in the Path_Loss_Internal folder will store the path to the LOS files for each transmitter in the network.
This folder can be set as the shared path loss matrices folder in the ATL files of group A users.
To set up the shared path loss matrices folder for group B users, you must create a new folder with a Pathloss.dbf file in it.
This folder can be called C:\Path_Loss_Mixed. The Pathloss.dbf file in this folder can be a copy of the Pathloss.dbf file in the
Path_Loss_Internal folder with the paths to the LOS files modified. For example, if the path loss matrices generated by the
other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries as
Pathloss.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. Figure 6.4
on page 89 explains this concept.
Figure 6.4: Path Loss Architecture for Multiple Source Path Loss Matrices
Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the different
transmitters, the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files of group B users.
If a group B user changes some parameters which make some path loss matrices invalid, Atoll will recalculate the private path
loss matrices with the propagation models assigned to the transmitters. The external path loss matrix will no longer be used.
89
Atoll 3.3.2 Administrator Manual
Chapter 6: Multi-user Environments © Forsk 2016
90
Chapter 7
Coordinate Systems
and Units
This chapter covers the following topics:
• "Coordinate Systems" on page 93
• "Units" on page 99
• "BSIC Format" on page 100
Atoll 3.3.2 Administrator Manual
© Forsk 2016
92
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 7: Coordinate Systems and Units
References:
1. Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd Edition,
United States Government Printing Office, Washington, D.C., 313 pages, 1982.
2. http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html
3. http://www.epsg.org/Geodetic.html
4. http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/
transfo.pdf (French)
The geographic coordinate system is a datum and a meridian. Atoll enables you to choose the most suitable geographic
coordinate system for your geographic data.
Datum
The datum consists of the ellipsoid and its position relative to the WGS84 ellipsoid. In addition to the ellipsoid, translation,
rotation, and distortion parameters define the datum.
Meridian
The standard meridian is Greenwich, but some geographic coordinate systems are based on other meridians. These meridians
are defined by the longitude with respect to Greenwich.
93
Atoll 3.3.2 Administrator Manual
Chapter 7: Coordinate Systems and Units © Forsk 2016
Ellipsoid
The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters.
Projection
The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different projection
methods that use specific sets of parameters.
The projection coordinate system is the result of the application of a projection to a geographic coordinate system. It
associates a geographic coordinate system and a projection. Atoll enables you to choose the projection coordinate system
matching your geographic data.
The projection coordinate system is the coordinate system of the available raster geographic data files. You should set the
projection coordinate system of your Atoll document so that it corresponds to the coordinate system of the available raster
geographic data. You can set the projection coordinate system of your document in the Options dialog.
All the raster geographic data files that you want to import and use in an Atoll document must have the same coordinate
system. You cannot work with raster geographic data files with different coordinate systems in the same document.
If you import vector geographic data (e.g., traffic, measurements, etc.) with different
coordinate systems, it is possible to convert the coordinate systems of these data into
the projection coordinate system of your Atoll document.
The projection coordinate system is used to keep the coordinates of sites (radio network data) consistent with the geographic
data.
When you import a raster geographic data file, Atoll reads the geo-referencing information from the file (or from its header
file, depending on the geographic data file format), i.e., its Northwest pixel, to determine the coordinates of each pixel. Atoll
does not use any coordinate system during the import process. However, the geo-referencing information of geographic data
files are considered to be provided in the projection coordinate system of the document.
The display coordinate system is the coordinate system used for the display, e.g., in dialogs, in the Map window rulers, in the
status bar, etc. The coordinates of each pixel of geographic data are converted to the display coordinate system from the
projection coordinate system for display. The display coordinate system is also used for sites (radio network data). You can
set the display coordinate system of your document in the Options dialog.
If you import sites data, the coordinate system of the sites must correspond to the display coordinate system of your Atoll
document.
If you change the display coordinate system in a document which is not connected to a database, the coordinates of all the
sites are converted to the new display system.
If the coordinate systems of all your geographic data files and sites (radio network data)
are the same, you do not have to define the projection and display coordinate systems
separately. By default, the two coordinate systems are the same.
94
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 7: Coordinate Systems and Units
The internal coordinate systems are the projection and the display coordinate systems stored in a database. The projection
and display coordinate systems set by the administrator in the central Atoll project are stored in the database when the
database is created, and cannot be modified by users. Only the administrator can modify the internal coordinate systems
manually by editing the entries in the CoordSys and the Units tables. All Atoll documents opened from a database will have
the internal coordinate systems of the database as their default projection and display coordinate systems.
When exporting an Atoll project to a database, the currently chosen display coordinate system becomes the internal display
coordinate system for the database, and the currently chosen projection coordinate system becomes the internal projection
coordinate system for the database.
Although Atoll stores both the coordinate systems in the database, i.e., the projection and the display coordinate systems,
the only relevant coordinate system for the database is the internal display coordinate system because this coordinate system
is the one used for the coordinates of sites (radio network data).
Users working on documents connected to a database can modify the coordinate systems in their documents locally, and save
these changes in their documents, but they cannot modify the coordinate systems stored in the database.
If you change the display coordinate system in a document which is not connected to a database, the coordinates of all the
sites are converted to the new display system.
If you change the display coordinate system in a document which is connected to a database, the coordinates of all the sites
are converted to the new coordinate system in the Atoll document locally but not in the database because the internal
coordinate systems cannot be changed.
Atoll uses the internal coordinates systems in order to keep the site coordinates consistent in the database which is usually
accessed by a large number of users in a multi-user environment.
Examples:
4230 = "ED50"; 101; 230; 1; "Europe - west"
You should keep the following points in mind when editing or creating .cs files:
• The identification code enables Atoll to differentiate coordinates systems. In case you create a new coordinate
system, its code must be an integer value higher than 32767.
• When describing a new datum, you must enter the ellipsoid code and parameters instead of the datum code in
brackets. There can be 3 to 7 parameters defined in the following order: Dx, Dy, Dz, Rx, Ry, Rz, S. The syntax of the line
in the .cs file will be:
Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz, S};
Projection Method Code, Projection Parameters; "Comments"
• There can be up to seven projection parameters. These parameters must be ordered according to the parameter index
(see "Projection Parameter Indices" on page 98). Parameter with index 0 is the first one. Projection parameters are
delimited by commas.
• For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative numbers for
south UTM zones.
• You can add all other information as comments (such as usage or region).
Codes of units, data, projection methods, and ellipsoids, and projection parameter indices are listed in the tables below.
95
Atoll 3.3.2 Administrator Manual
Chapter 7: Coordinate Systems and Units © Forsk 2016
Unit Codes
Datum Codes
96
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 7: Coordinate Systems and Units
Ellipsoid Codes
97
Atoll 3.3.2 Administrator Manual
Chapter 7: Coordinate Systems and Units © Forsk 2016
98
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 7: Coordinate Systems and Units
3. Click the Browse button ( ) to the right of Projection. The Coordinate Systems dialogue appears.
4. Click New. The Coordinate System dialogue appears.
5. In the Coordinate System dialogue:
a. Select the coordinate systems catalogue to which you want to add the new coordinate system.
b. Under General, enter a Name for the new coordinate system and select a Unit. In Use, you can enter comments
about its usage. Atoll assigns the code automatically.
c. Under Category, select the Type of coordinate system. Enter the longitude and latitude for a geographic
coordinate system, or the type of projection and its set of associated parameters for a cartographic coordinate
system (false easting and northing, and the first and second parallels).
d. Under Geo, specify the meridian and choose a Datum for the coordinate system. The associated ellipsoid is
automatically selected. You can also describe a geodetic datum by selecting "<Customised>" in the Datum list. In
this case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S) needed for the
transformation of the datum into WGS84.
6. Click OK. The new coordinate system is added to the selected coordinate system catalogue.
To create a new coordinate system based on an existing system, select a coordinate system in the Coordinate Systems
dialogue before clicking New in step 4. The new coordinate system is initialised with the values of the selected coordinate
system.
7.2 Units
In the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance, height and
offset, and temperature. You can accept the default measurement units, or you can change them using the document
properties dialogue.
Depending on the working environment, Atoll can use either one or two measurement units for the transmission/reception
power.
If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement
unit used in Atoll for display. It corresponds to the transmission/reception power unit defined in the Atoll document.
If you are working in a multi-user environment, Atoll uses two measurement units:
• A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power unit
defined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g., reception
thresholds (coverage prediction properties, microwave link properties, etc.), and received signal levels
(measurements, point analysis, coverage predictions, microwave link properties, etc.).
• An internal measurement unit for the database. The internal unit is the transmission/reception power unit stored in
the database. It corresponds to the transmission/reception power unit used in the master Atoll document when the
database is created. Users working in documents connected to a database can modify the transmission/reception
power unit and save this change in their documents locally, but they cannot modify the internal power unit stored in
the database. Only the administrator can modify it manually by editing the entry in the Units tables.
Depending on the working environment, Atoll can use either one or two measurement units for the antenna gain.
If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement
unit used in Atoll for display. It corresponds to the antenna gain unit defined in the Atoll document.
If you are working in a multi-user environment, Atoll uses two measurement units:
• A measurement unit for display in the Atoll document. It corresponds to the antenna gain unit defined in the current
Atoll document and it is used for the display in the dialogues and in the tables.
• An internal measurement unit for the database. The internal unit is the antenna gain unit stored in the database. It
corresponds to the antenna gain unit used in the master Atoll document when the database is created. Users working
in documents connected to a database can modify the antenna gain unit and save this change in their documents
locally, but they cannot modify the antenna gain unit stored in the database. Only the administrator can modify it
manually by editing the entry in the Units tables.
Distance Units
Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues, in the
tables, and in the status bar.
99
Atoll 3.3.2 Administrator Manual
Chapter 7: Coordinate Systems and Units © Forsk 2016
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to
databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Atoll uses the height and offset unit defined in the current Atoll document as display unit of the heights and the offsets in the
dialogues, in the tables, and in the status bar.
Metre is used as the internal measurement unit for the heights and offsets in all Atoll documents whether they are connected
to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Temperature Units
Atoll uses the temperature unit defined in the current Atoll document as display unit of the temperatures in the dialogues
and in the tables.
Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they are
connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Atoll expects the BSIC format in the database to be the octal format. If that is not the case,
do the following:
• In the Atoll database, update the setting of UNITS.BSIC_FORMAT to 1.
• In your ATL project (and in any ATL project created from the previous database
configuration), go to the Parameters tab, select GSM Network Settings > BSICs >
Format > Octal and save the ATL file.
100
Chapter 8
Atoll File Formats
102
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
"Vector" Formats
103
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
"Raster" Formats
• World files (e.g. TFW, BPW) are header files used for the georeferencing of raster
files. See next sections for more information on World file types generated by Atoll.
• The smallest supported resolution for raster files is 1 m. There is no restriction on the
resolution of images.
• DTM, clutter classes, and clutter height maps must have an integer resolution.
• All the raster maps you want to import in an ATL document must be represented in
the same projection system.
Specific header files are used to describe how data is organised within any of these geographic data file formats. This section
describes the following header file formats:
• "HDR Header File for BIL Files" on page 104
• "TFW Header File for TIFF Files" on page 106
• "BPW/BMW Header Files for BMP Files" on page 107
• "PGW Header File for PNG Files" on page 107
• "JGW Header File for JPG Files" on page 107
keyword value
where ‘keyword’ corresponds to an attribute type, and ‘value’ defines the attribute value.
Keywords required by Atoll are described below. Other keywords are ignored.
ulxmap x coordinate of the centre of the upper-left pixel.
ulymap y coordinate of the centre of the upper-left pixel.
xdim x size in metre of a pixel.
ydim y size in metre of a pixel.
ncols Number of columns in the image.
nrows Number of rows in the image.
104
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
If no pixeltype parameter is available, then the default value is UNSIGNEDINT (8, 16, or
32 bits).
DTM Sample
nrows 1500
ncols 1500
nbands 1
nbits 8 or 16
byteorder M
layout bil
105
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
skipbytes 0
ulxmap 975000
ulymap 1891000
xdim 20.00
ydim 20.00
nrows 1500
ncols 1500
nbands 1
nbits 8
byteorder M
layout bil
skipbytes 0
ulxmap 975000
ulymap 1891000
xdim 20.00
ydim 20.00
[RasterExport]
ExportBILAsESRI = 1 #default=0
984_UTM_Zone_31N",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137,298.257223563]],
PRIMEM["Greenwich",0],
UNIT["Degree",0.017453292519943295]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",3],
PARAMETER["scale_factor",0.9996],
PARAMETER["false_easting",500000],
PARAMETER["false_northing",0],
UNIT["Meter",1]]
Line Description
1 x dimension of a pixel in map units
2a amount of translation
3 amount of rotation
4 negative of the y dimension of a pixel in map units
5 x-axis map coordinate of the centre of the upper-left pixel
6 y-axis map coordinate of the centre of the upper-left pixel
a. Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file.
106
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
100.00
0.00
0.00
-100.00
60000.00
2679900.00
Atoll supports BPW and BMW header file extensions for Import, but exports headers with BPW file extensions.
100.00
0.00
0.00
-100.00
60000.00
2679900.00
Line Description
1 x dimension of a pixel in map units
2 amount of translation
3 amount of rotation
4 negative of the y dimension of a pixel in map units
5 x-axis map coordinate of the centre of the upper-left pixel
6 y-axis map coordinate of the centre of the upper-left pixel
Line Description
1 x dimension of a pixel in map units
2 amount of translation
3 amount of rotation
107
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
Line Description
4 negative of the y dimension of a pixel in map units
5 x-axis map coordinate of the centre of the upper-left pixel
6 y-axis map coordinate of the centre of the upper-left pixel
DBF Structure
1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) …; last
n+1 If .dbf is not empty
record
DBF Header
The DBF header size is variable and depends on the field count.
108
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
Field descriptor array in the DBF header (32 bytes for each field):
Field type and size in the DBF header, field descriptor (1 byte):
Size Type Description/Storage Applies to
ASCII (OEM code page chars)
C 1...n Char all
rest= space, not \0 term.
n = 1...64kb (using deci count) FS
n = 1...32kb (using deci count) Fp, CL
n = 1...254 all
D8 Date 8 ASCII digits (0...9) in the YYYYMMDD format all
ASCII digits (-.0123456789)
F 1...n Numeric variable pos. of float.point FS, D4, D5, Fp
n = 1...20
ASCII digits (-.0123456789)
N 1...n Numeric all
fix posit/no float.point
109
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
110
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
111
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
112
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
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 "#". If not, they must have the following format:
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
The columns 1, 2, and 3 must be defined only in the first line of each histogram.
Sample
113
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
10 0.904
11 0.892
14 0.844
15 0.832
16 0.812
17 0.752
22 0.316
25 0.292
1 2 BCCH,TCHa 8 1
9 0.944
10 .904
13 0.872
14 0.84
17 0.772
a. If the TCH and BCCH histograms are the same, they are not repeated. A single record indicates that the histograms
belong to TCH and BCCH both.
The second part provides information about transmitters taken into account in AFP. The lines after the header are considered
as comments if they start with "#". If not, they must have the following format:
<Column1><tab><Column2><newline>
The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tab
character.
Sample
114
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
#
# Service Zone Type is "Best signal level per HCS layer".
# Margin is 5.
# Cell edge coverage probability is 75%.
# Traffic spreading was Uniform (percentage of interfered area)
##---------------------------#
Site0_0 1 -1 -1 100 100
Site0_1 2 -1 -1 100 100
Site0_2 3 -1 -1 100 100
Site1_0 4 -1 -1 100 100
Site1_1 5 -1 -1 100 100
Site1_2 6 -1 -1 100 100
Site2_0 7 -1 -1 100 100
Site2_1 8 -1 -1 100 100
The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the header
are considered as comments if they start with "#". If not, they must have the following format:
<Column1><tab><Column2><tab><Column3><tab><Column4><newline>
Sample
115
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
#
Site0_2 Site0_1 BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.964 -1 0.936
0 0.932 1 0.924 4 0.896 7 0.864 8 0.848
9 0.832 10 0.824 11 0.804 14 0.712 17 0.66
Site0_2 Site0_3 BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.972 -1 0.948
0 0.94 1 0.928 4 0.896 7 0.856 8 0.84
11 0.772 13 0.688 14 0.636 15 0.608 18 0.556
Site0_3 Site0_1 BCCH,TCH-10 1 -9 0.996 -6 0.98 -3 0.948 0 0.932
1 0.924 4 0.892 7 0.852 8 0.832 9 0.816
10 0.784 11 0.764 14 0.644 15 0.616 18 0.564
Site0_3 Site0_2 BCCH,TCH-9 1 -6 0.972 -3 0.964 -2 0.96 0 0.94
1 0.932 4 0.904 7 0.876 8 0.86 9 0.844
11 0.804 13 0.744 14 0.716 15 0.692 18 0.644
The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the header
are considered as comments if they start with "#". If not, they must have the following format:
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
Sample
116
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
Site0_2 Site0_1 BCCH,TCH -10 1
Site0_2 Site0_1 BCCH,TCH -9 0.996
Site0_2 Site0_1 BCCH,TCH -6 0.976
Site0_2 Site0_1 BCCH,TCH -4 0.964
Site0_2 Site0_1 BCCH,TCH -1 0.936
Site0_2 Site0_1 BCCH,TCH 0 0.932
Site0_2 Site0_1 BCCH,TCH 1 0.924
Site0_2 Site0_1 BCCH,TCH 4 0.896
Site0_2 Site0_1 BCCH,TCH 7 0.864
Site0_2 Site0_1 BCCH,TCH 8 0.848
Site0_2 Site0_1 BCCH,TCH 9 0.832
Site0_2 Site0_1 BCCH,TCH 10 0.824
...
Sample
117
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon:
Site0_2;Site0_1;0.226667;0.024
Site0_2;Site0_3;0.27;0.024
Site0_3;Site0_1;0.276;0.02
Site0_3;Site0_2;0.226;0.028
0 none
1 open
2 sea
3 inland_water
4 residential
5 meanurban
118
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 8: Atoll File Formats
In LTE, when a Cell Identifier Collision Zones (DL) prediction is calculated by value intervals with the display type set
"No. of interferers per cell", the HDR file and the BIL file are created for each cell in the prediction (both identified by
the cell’s name).
The format and the content of the DBF file is described here.
In both cases, an XML file describing the prediction is also created in the corresponding
’<doc_name>\{<GUID>}’ folder.
119
Atoll 3.3.2 Administrator Manual
Chapter 8: Atoll File Formats © Forsk 2016
120
Chapter 9
Administration and
Usage
Recommendations This chapter covers the following topics:
• "Geographic Data" on page 123
• "Path Loss Matrices" on page 124
• "Atoll Documents" on page 125
• "Databases" on page 125
• "Calculation Server" on page 126
• "Atoll Administration Files" on page 126
• "Process Memory" on page 127
• "Printing" on page 127
• "Coverage Prediction Calculations" on page 128
• "CW Measurements and Drive Test Data" on page 128
• "Antenna Patterns and Import" on page 128
• "Traffic Maps" on page 128
• "Atoll API" on page 129
• "Performance and Memory" on page 129
Atoll 3.3.2 Administrator Manual
© Forsk 2016
122
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 9: Administration and Usage Recommendations
• In multi-user environments, it is recommended to place all the geographic data on a file server accessible to all the
users. This approach avoids the need to replicate the geographic data on all the workstations.
• Geographic data should either be located on each server or accessible through a fast network connection, e.g., 1 Gbps.
• You can restrict access to the geographic data locations by assigning read/write access rights to administrators and
read-only rights to end-users.
Link or Embed
• Only embed geographic data in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link geographic data files to the Atoll documents.
• It is recommended to set the paths to linked geographic data files using the Universal Naming Convention (UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\Geo Data\...", is represented as
"\\Computer\C\Program Files\Forsk\Geo Data\...", where "Computer" is the computer name, and "C" is the share
name of disk C.
Example:
If you define paths to geographic data files using the UNC, Atoll will be able to keep track of the linked files even if the
Atoll document is moved to another computer.
Size of Tiles
• Some network planning tools require geographic data to be available in small tiles in order to work more efficiently.
For a country-wide project, this can lead to hundreds of files describing the geographic data. Atoll is designed to
optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). In
Atoll, Merging small tiles to build a regional tile can improve performance greatly.
• To note as well:
• Recommended file size: 100 to 200 MB
• Erdas Imagine Pyramids files can be bigger.
• ECW files can be of any size (no limitations).
Recommended Formats
• In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example, BIL
files. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause performance
reduction due to decompression of these files in real time. If you are using compressed geographic data files, it is
strongly recommended to:
• Either, hide the status bar that displays geographic data information in real time. You can hide the status bar from
the View menu.
• Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class, and
clutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar" on page 186.
• The following table shows the recommended file formats for different geographic data:
123
Atoll 3.3.2 Administrator Manual
Chapter 9: Administration and Usage Recommendations © Forsk 2016
• Shared path loss matrices should be accessible through a fast network connection, e.g., 1 Gbps. These results are
accessed by Atoll during calculations, and should be available to the users through a fast network connection, i.e.,
30 Mbps at least per user.
• You can restrict access to the shared path loss matrices folder by assigning read/write access rights to administrators
and read-only rights to end-users.
• Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are
invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices
and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information, see "Synchronising Private and Shared Path Loss Matrices" on page 178.
Link or Embed
• Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link path loss matrices to the Atoll documents.
Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable, which will
result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and
calculations in Atoll.
• It is recommended to set the paths to the private and shared path loss matrices folders using the Universal Naming
Convention (UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\PathLosses\...", is represented as
"\\Computer\C\Program Files\Forsk\PathLosses\...", where "Computer" is the computer name, and "C" is the share
name of disk C.
Example:
If you define paths to the private and shared path loss matrices folders using the UNC, Atoll will be able to keep track
of the linked files even if the Atoll document is moved to another computer.
• When the path loss matrices in multi-RAT documents using the RunPathloss API function, the path loss matrices of
each technology are calculated simultaneously using the same number of threads. For example, if 4 threads are used
to calculate path loss matrices, and there are 3 technologies (GSM, UMTS, and LTE), a total of 12 threads will be used
to calculate the path loss matrices at the same time. This can lead to the following problems:
• Insufficient CPU resources
• Insufficient memory
• Insufficient licenses if external propagation models are used.
• To avoid these problems when using the RunPathloss API function to calculate path loss matrices in multi-RAT
documents, use the following work-arounds:
• Use the Distributed Calculation Server, even locally.
• In your script or macro, deactivate the transmitters of the technologies for which you do not want to calculate the
path loss matrices and reactivate them afterwards. Repeat it for all technologies.
• Lower the number of threads using the NumberOfThreadsPathloss option in RemoteCalculation section in
Atoll.ini. For example, you can set the option to 2 to use a maximum of 6 threads (3*2) during path loss calculation
using the RunPathloss function.
• Resource saturation during the calculation of path loss matrices for multi-RAT
documents only occurs when using the RunPathloss API function in a macro or script.
When calculating path loss matrices for a multi-RAT document using Atoll, this does
not occur.
124
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 9: Administration and Usage Recommendations
• Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are
invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices
and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information, see "Synchronising Private and Shared Path Loss Matrices" on page 178.
• It is recommended to define a rule for making backups of your Atoll documents at regular intervals.
• Do not skip a major Atoll version. For example, if you are currently using Atoll 2.8.x, you should first upgrade the
document to Atoll 3.1.x before upgrading to Atoll 3.2.x.
Upgrading your document will be simpler if you do not skip a major version. If you skip or have skipped an
intermediate major version, you should upgrade your document twice in order to make it compatible with the new
version.
9.4 Databases
General
• In order to use Atoll with Oracle, you must create Oracle users and schema with names in uppercase.
• Create backups of the database before upgrading.
• It is recommended to define a rule for making backups of the database at regular intervals.
• Do not skip a major Atoll version. For example, if you are currently using Atoll 2.7.x, you should first upgrade the
database to Atoll 2.8.x before upgrading to Atoll 3.1.x.
Upgrading your database will be simpler if you do not skip a major version. If you skip or have skipped an intermediate
major version, you must upgrade your database twice in order to make it compatible with the new version.
125
Atoll 3.3.2 Administrator Manual
Chapter 9: Administration and Usage Recommendations © Forsk 2016
In certain conditions, as described below, Atoll users might experience a decrease in server performance and stability in a
multi-user Citrix environment. The principal difference observed might be the inability to run multiple Atoll sessions on the
server without getting error messages, general application failures, or server crashes. Such problems can occur when the
number of Atoll sessions on the server, carrying out calculations, increases to more than four.
This general instability and low performance of the servers is due to:
• Insufficient memory resources: globally and per process (Atoll session)
• Insufficient CPU resources
• Network congestion
Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource consumption,
and as path loss calculations share the amount of memory allocated to the Atoll session, the total memory requirement can
exceed the Microsoft Windows’ (32-bit editions) limit of 2 GB per process. This is especially the case with large Atoll
documents and propagation models that require considerable memory.
As the cause of this problem is resource saturation on the server, resource consumption should be controlled in order to avoid
memory and CPU overloading as follows:
• To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation Server should
be set up. Using the Distributed Calculation Server, path loss calculations can be performed outside Atoll. Using the
Distribution Calculation Server has the following advantages:
• Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions running on
the server. This notably improves the memory and CPU consumption.
• A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from
different Atoll sessions.
• A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in case a
problem occurs.
• Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory allocation apart
from Atoll, i.e., the amount of memory needed for calculations does not impacts the Atoll memory allocation.
This set up can introduce considerable improvements in both the number of Atoll sessions per server and the calculations. A
server with four processors (eight threads with hyper-threading) can accommodate four simultaneous path loss calculations
and use the other four threads for Atoll sessions. Atoll’s interface will also be more efficient and the overall processing time
for various tasks will be improved.
In order to prevent users from deactivating the use of the Distributed Calculation Server,
and hence bypassing the resource control procedure established above, the Atoll.ini file
should be set made read-only for end-users.
Apart from the above setup, you can also make some other system improvements:
• To avoid error messages caused by requesting a large number of files over the network, the following Microsoft
Windows registry parameter can be modified in order to dedicate more resources to network read/write operations:
IRQSTACKSIZE should be set to 30 instead of 11, for example.
• To avoid ‘out of memory’ problems, the Pagefile size should be increased so that the server does not run out of global
memory when supporting more than 10 Atoll sessions simultaneously. This is different from the 2 GB per process
limit. Virtual memory can be increased from 8 GB to 16 GB, for example.
• For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB
to 3 GB as explained in "Process Memory" on page 127.
126
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 9: Administration and Usage Recommendations
files, or create them, you will not have the same configuration of the new server, but apart from that you will be able to work
with Atoll normally. These files are optional, not obligatory.
• It is highly recommended that the Atoll initialisation file be created and modified only by the administrator.
• If you are using Windows 2000 Server, state the actual number of processors in the INI file.
• Use Atoll to create these files and avoid modifying these files manually as human errors can create problems.
• Uncheck image visibility to avoid loading unnecessary data in the memory.
• You can set up your configuration files in the following manner:
• A common configuration file that points to the geographic data, macros, and other common parameters in your
Atoll documents.
• Separate configuration files created for your 2G and 3G projects, which would store their respective coverage
prediction studies parameters, traffic information, neighbour allocation parameters, and other technology-
specific parameters.
• Separate configuration files based on, and for, different groups of users. These groups of users can be, for
example, groups of users working on different regions, groups of users working on different technologies, groups
of users focusing on certain operations (i.e., performing certain types of coverage predictions, performing the AFP,
etc.).
• Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the XML
studies file, make sure that this study template is aimed at serving a number of users. This means, avoid creating study
templates unless these will be needed for a long time by a number of users. You can use the configuration files to store
your created coverage prediction studies locally. And, you can also use the study duplicate feature to create copies of
existing coverage prediction studies.
Atoll can support 3 GB address space on a properly configured 32-bit system. For more information, please refer to the
following URL: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx (/3GB section in “Memory
Support and Windows Operating Systems”).
The following link provides information on how you can setup your Windows Server 2003 systems to activate the 3 GB switch
at startup: http://technet.microsoft.com/en-us/library/bb124810.aspx.
9.8 Printing
You should place different layers of geographic and radio data in a definite order when printing a project or a section of the
project. The following order should be followed:
1. Visible objects of the Data tab
All the visible objects of the Data tab are displayed above those in the Geo tab. However, it is strongly recommended
to place vector layers on the top of coverage prediction plots. You can do this by transferring these vector layers to
the Data tab using the context menu. For performance reasons, it is advised to place vector layers on top of raster
layers before printing a project. Sites and Transmitters must be on the very top, above all other layers. You should
place sites and sectors on the top, then vector layers, and then raster layers.
2. Unidimensional vectors (points)
3. Open polygonal vectors (lines, i.e., roads and other linear items, etc.)
4. Closed polygonal vectors (surfaces, i.e., zones and areas, etc.)
5. Multi-format maps (vector or raster maps, i.e., population, rain, generic maps, traffic, etc.)
6. Transparent raster maps (clutter class maps, etc.)
7. Non-transparent maps (images, DTM, clutter height maps, etc.)
127
Atoll 3.3.2 Administrator Manual
Chapter 9: Administration and Usage Recommendations © Forsk 2016
128
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 9: Administration and Usage Recommendations
• You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time to
time, closing and restarting Atoll, and reopening the document.
This advice is applicable to any application running under Microsoft Windows because many common DLL files are
accessed by applications, and unloading and reloading these DLL files refreshes the memory allocation.
• If you are working in a Citrix XenApp environment, you should restart your Citrix server every week or fortnight. The
exact time should be determined by the administrator depending on the state of the network (LAN).
• In certain cases, it might be more appropriate to start working on a completely fresh ATL file. If you have been working
on your existing ATL file for a long time, it might become unnecessarily large and might contain some useless remains
from your earlier operations, e.g., traces of records that no longer exist in the database, etc. You can completely
refresh your project by following these steps:
a. Open the existing ATL file in Atoll that you want to replace.
b. Create a CFG file from your existing ATL file with all the required information, e.g., geographic data set, coverage
prediction parameters, neighbour allocation parameters, etc. For more information, refer to "Configuration Files"
on page 135.
c. Close the old ATL file.
d. Create a new ATL from the database to create a fresh ATL file.
e. Import the CFG file in the new ATL file.
You now have a clean ATL file to work with, which has all the same information as the old ATL file, and takes up less
space on the hard disk, has less fragmented data, and improved performance.
Memory Allocation
• If you have to open several large ATL files simultaneously on the same computer, it is better to open each in a separate
Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its
own memory space allocated by the operating system. Each computer consumes a single license token independent
of the number of Atoll sessions opened simultaneously.
• For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB
to 3 GB as explained in "Process Memory" on page 127.
File Size
• Coverage predictions calculated over large areas require more memory. If you are working on an Atoll document
covering a large area, with coverage predictions calculated over the entire network, this document will require more
memory for loading all the coverage predictions. You can reduce memory consumption by making copies of your Atoll
document, and keeping a few coverage predictions in each copy. These ATL files will be faster to load and work with
compared to a single ATL file with all the coverage predictions.
Large coverage predictions can take up a considerable amount of memory even if they are not displayed on the map.
• Externalise DTM, clutter, path loss matrices, and any other data that can be externalised, so that the ATL file size does
not become unnecessarily large.
• Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different types of
transmitters are consistent. For example, calculating path loss matrices of picocells over large calculation radii would
only waste memory and disk space.
129
Atoll 3.3.2 Administrator Manual
Chapter 9: Administration and Usage Recommendations © Forsk 2016
• For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define short
calculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low resolutions
for extended path loss matrices. This approach decreases the calculation time significantly compared to calculating
just one matrix per transmitter using a fine resolution. The main path loss matrices should be calculated using the
same resolution as the resolution of the geographic data available. The extended path loss matrices can be calculated
using a lower resolution, e.g., twice the resolution of the geographic data.
Regionalisation
• Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll loads only the
data necessary for your working area. If you load a large network, Atoll will load a lot of data that might not be
necessary all the time, such as the neighbour relation data.
Memory problems might be experienced in the C/I coverage prediction studies, interference matrices calculations, and the
AFP while working on large GSM networks. Large network projects are more susceptible to these problems. If the network is
large but homogeneous, these problems might only appear if the number of transmitters is over 15,000 or so. But, if there are
large city centres involved, with each pixel having many overlapping path loss matrices, then this size limit might decrease to
around 5,000 transmitters or so.
Also, if the Atoll session has been open for a long time, memory problems can even appear while working on smaller
networks. This is because the process memory space (memory space allocated to Atoll by the operating system) becomes
fragmented.
Following is a list of advice which you can follow in order to avoid such problems:
• Use regionalisation or site lists: If you load a large network, Atoll will be required to load a lot of data that might not
be necessary all of the time. For example, in a typical large GSM network, you might have around 10,000 transmitter
records, 20,000 subcell records, 50,000 TRX records, and up to 150,000 neighbour records.
• Externalise embedded interference matrices: You can store interference matrices listed in the Interference Matrices
folder in external files. Atoll loads interference matrices from the external files to the memory only when needed. You
will also reduce the ATL file size by externalising the interference matrices.
• Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices, take care to correctly
associate calculation radii and resolutions to different types of cells. If you calculate path loss matrices for all types of
cells over a large calculation radius, it will unnecessarily burden the C/I and interference matrices computations.
• Properly configure the interference thresholds: These thresholds indicate the level after which an interferer can be
ignored. The default value for this threshold (-130 dBm), defined in the Predictions tab of the Predictions folder’s
Properties dialogue, means that the computations will take into account all the interferers. However, if you set it too
high, you might lose important interference information. The proper value for this threshold depends on the
Reception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be
Min AllSubcells RT i – CIT i – M . Which means the minimum value of the factor RT i – CIT i – M computed for all
subcells, i. Where, RTi is the reception threshold of the subcell i, CITi the C/I threshold of this subcell, and M is a safety
margin.
Since this interference threshold is used both in interference matrices calculation and in interference predictions, it is
important to have at least a 3-dB margin for the interference energy aggregation in C/I studies. We recommend a
safety margin of 5 dB, which can be reduced if any problem is encountered.
• Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you want a certain
TRX type to carry GPRS/EDGE traffic, you can add 1 or 2 dB to this value for that TRX type, and use the option of safety
margin in the AFP module’s Cost tab. The 12 dB and 9 dB default values already include safety margins. If you
increment these values too much, it will unnecessarily load the interference matrix generation and the AFP.
• Do not start an AFP session if the interference matrices report indicates problems: All the transmitters should have
interferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many or
too few entries in your interference matrices, the AFP plan will not be optimal.
• If the memory-critical task is interference matrices generation: You can generate interference matrices in a piecewise
manner.
This means that you can generate nation-wide interference matrices with low resolutions based on the percentage of
interfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no access
to clutter for reading standard deviation values), and an interference threshold of -112 dBm. This will provide rough
global interference matrices which can be locally improved. These interference matrices will be less memory-
consuming.
Then, use polygon or site list filters to focus on each important location, and calculate local interference matrices with
higher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses the
filtering zones that you define.
• If the memory-critical task is the AFP session: Try to make the document lighter, e.g., remove coverage prediction
studies, exit and restart Atoll, and try to generate interference matrices with fewer entries.
130
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 9: Administration and Usage Recommendations
• If the memory-critical task is the traffic capture: You can use traffic load field of the Subcells table to provide traffic
loads directly to the AFP, and possibly skip this step.
• In order to optimise memory usage during simulations, you can set the "Information to retain" option to "Only the
Average Simulation and Statistics". With this option Atoll uses much less memory because it only keeps limited
information in memory during the simulation process. Simulation results are detailed enough to be used in generating
coverage prediction studies.
Co-planning with Atoll requires that both technology documents be open in the same Atoll window at the same time.
However, loading, for example, a GSM and a UMTS document can cause memory saturation especially if the documents
contain large, country-wide networks. To decrease the amount of memory used by Atoll in such cases, you can:
• Load vector layers in main document only. Loading vectors in the linked document is not necessary and only consumes
more memory.
• Avoid loading neighbours and custom fields which are not required. This can be performed by creating views in the
database. For more information, see "Appendix 2: Setting Up Databases for Co-planning" on page 73.
131
Atoll 3.3.2 Administrator Manual
Chapter 9: Administration and Usage Recommendations © Forsk 2016
132
Chapter 10
Configuration Files
134
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
10 Configuration Files
Configuration files can be used to store parameter and display settings. These files are optional, not required for working with
Atoll, but are useful means for making work easier.
This chapter describes the formats of these files in detail:
• User configuration files (UTF-8 encoded XML-format GEO or CFG files)
A user configuration file containing only the geographic data settings can be saved with a GEO extension. A user
configuration file containing the geographic data settings and other parameter settings can be saved with a CFG
extension.
User configuration files must be created using Atoll to ensure correct syntax and structure. It is possible to edit the
contents of these files in an XML editor and make changes if required (for example, to update the paths to geographic
data files). For more information on how to create and load user configuration files in Atoll, see the User Manual.
These files can store:
• Geographic data settings
• Filtering, focus, computation, printing, and geographic export zones
• Map centre and zoom level
• Folder configurations
• List of coverage predictions in the Predictions folder and their settings
• Automatic neighbour allocation parameters
• Automatic frequency planning parameters (GSM GPRS EDGE documents)
• Automatic scrambling code allocation parameters (UMTS HSPA and TD-SCDMA documents)
• Automatic PN offset allocation parameters (CDMA2000 documents)
• Automatic OFDM resource allocation parameters (LTE, WiMAX, Wi-Fi)
• Microwave link parameters
• Full paths to macro files
• Projection and display coordinate systems are stored in the database, not in user
configuration files.
• Simulation settings are not stored in user configuration files.
For more information on the contents of user configuration files, see "Contents of User Configuration Files" on
page 136.
A user configuration file can be automatically loaded when Atoll is run if:
a. The file is identified in the command line parameter -Cfg "cfgfilename" (see "Atoll Command Line Parameters" on
page 31 for more information), or
b. The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a user
configuration file is loaded through the command line parameter.
• Additional configuration files (UTF-8 encoded XML-format CFG files or plain text INI files)
The following parameter settings can be stored in additional configuration files with a CFG extension:
• Print setup configuration
• Table import/export configuration
• Coverage prediction report configuration
The following parameter settings can be stored in specific INI files:
• CW measurement import configuration
• Drive test data import configuration
For more information on the contents of additional configuration files, see "Contents of Additional Configuration
Files" on page 159.
• Custom predictions file (UTF-8 encoded XML files)
This file (one for all customised predictions) contains the list and parameter settings of customised coverage
predictions. By default, t
135
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
136
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
• Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
as <FieldSelector>) and <FieldTitle>, transparency level <Opacity>, visibility flag <visible>, and visibility range
between <minZoom> and <maxZoom>
• <Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
• <AddToLegend>: Add to legend option checked or not
• <Attributes>, such as: <records> and <fields>, which are,
• Common: CODE, COLOR, NAME, HEIGHT, INDOOR
• Under <GSM>: STDDEV, COVERI_STDDEV, TX_DIV_GAIN, ANT_HOP_GAIN
• Under <UMTS>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO,
SM_GAIN_FACTOR, STTD_GAIN_OFFSET
• Under <LTE>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, DIV_GAIN_OFFSET_DL,
DIV_GAIN_OFFSET_UL
• Under <1XRTT>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO
• Under <TD-SCDMA>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, FORTHO_UL,
FORTHO_DL, ANGULAR_SPREAD
• Under <IEEE_802.16e>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL,
STTD_OFFSET_UL
• Under <Wi-Fi>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL, STTD_OFFSET_UL
• <DefaultValues>, for the fields stated above.
• Clutter Heights and Digital Terrain Models:
• <Name>: Name of the folder
• <Display>: (Different combinations of the following parameters exist in different display settings.)
• Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
as <FieldSelector>) and <FieldTitle>, transparency level <opacity>, visibility flag <visible>, and visibility range
between <minZoom> and <maxZoom>
• <Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
• <AddToLegend>: Add to legend option checked or not
• <File>: <Format> and <Path> to linked files, if any
Sample
137
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Population(Density) <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 0 0</SecondaryColor>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>
<Type>
<Name>Population</Name>
<Formats>15</Formats>
<Type>800</Type>
<Integrable>1</Integrable>
</Type>
<Files/>
</Population> // or </GeoClimaticParams> or </Vectors>
<ClassifiedClutter UseOnlyDefault="0">
<Display>
<Type>ByIntervals</Type>
<FieldSelector>3</FieldSelector>
<FieldDesc>
<FieldId>3</FieldId>
<FieldTitle>Height (m)</FieldTitle>
</FieldDesc>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>54.</Min>
<Max>56.</Max>
<Legend>54 <=Height (m) <56</Legend>
<MainColor>255 38 0</MainColor>
<SecondaryColor>255 38 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
138
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<visible>Yes</visible>
</Display>
<Attributes>
<fields>
<field length="1" type="uint" name="CODE"/>
<field length="4" type="int" name="COLOR"/>
<field length="50" type="text" name="NAME"/>
<field length="4" type="real" name="HEIGHT"/>
<field length="2147483647" type="text" name="INDOOR"/>
</fields>
<records/>
</Attributes>
<Name>Clutter Classes</Name>
<AddToLegend>0</AddToLegend>
<DefaultValues>
</DefaultValues>
</ClassifiedClutter>
<Altitudes> // or <BuildingHeights>
<Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>0</FieldSelector>
<FieldDesc>
<FieldId>0</FieldId>
<FieldTitle>Altitude</FieldTitle>
</FieldDesc>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Altitude <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 96 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>
</Altitudes> // or </BuildingHeights>
</Geodataset>
</Atoll>
139
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
10.1.2 Zones
The user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and geographic
export zone polygons, i.e., the points forming these polygons. The first and the last points have the same coordinates.
Sample
The following sample has rectangular computation and focus zones of the same size.
Sample
140
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
• <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
• Antennas folder:
• <Name>: Name of the folder
• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
• <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
• Transmitters, Multi-Hops, and Point to Multipoint folders:
• <Name>: Name of the folder
• <Display>:
• Displate type <Type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
as <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range between
<MinZoom> and <MaxZoom>
• <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, label
font background colour <BackColor>, and label font style <Style>
• <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,
and <SymbolSize>
• <DataTips>: List of <items> displayed in tip texts
• <Labels>: List of <items> displayed in labels
• <AddToLegend>: Add to legend option checked or not
• <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
• <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
• <OFDM_AFP>: LTE, WiMAX, and Wi-Fi frequency allocation constraint weights:
• <Techno>: Name of the technology
• <NeighbourWeight>: Weight of the first order neighbour relation
• <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell
• <IMWeight>:Weight of the interference matrices relation
• <DistanceWeight>: Weight of the distance-based relation
• <PCI_Alloc>: LTE physical cell ID allocation constraint weights:
• <NeighbourWeight>: Weight of the first order neighbour relation
• <SecondNeighbourWeight>: Weight of the second order neighbour relation
• <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell
• <IMWeight>:Weight of the interference matrices relation
• <DistanceWeight>: Weight of the distance-based relation
• <IDWeight>: Weight of the physical cell ID constraint
• <PSSWeight>: Weight of the PSS ID constraint
• <SSSWeight>: Weight of the same SSS ID per site constraint
• <ULDMRSSGWeight>: Weight of the UL DMRS (PCI Mod 30) collision constraint
• <DLRSSCaWeight>: Weight of the single antenna port DL CRS (PCI Mod 6) collision constraint
• <PCFICHREGWeight>: Weight of the PCFICH REG (PCI Mod (N_RB/2)) collision constraint
• <PI_Alloc>: WiMAX preamble index allocation constraint weights:
• <NeighbourWeight>: Weight of the first order neighbour relation
• <SecondNeighbourWeight>: Weight of the second order neighbour relation
• <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell
• <IMWeight>:Weight of the interference matrices relation
• <DistanceWeight>: Weight of the distance-based relation
• <IndexWeight>: Weight of the preamble index constraint
• <SegmentWeight>: Weight of the segment constraint
• <PermBaseWeight>: Weight of the same cell permbase per site constraint
• Links folder:
• <Name>: Name of the folder
• <Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom>
• <AddToLegend>: Add to legend option checked or not
• <DefaultConfiguration>: The default configuration for the folder
• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label
font background colour <BackColor>, and label font style <Style>
• <SiteDisplay> properties, such as:
• <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
• <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
141
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
Sample
142
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<visible>Yes</visible>
<Type>ByValues</Type>
<FieldSelector>8</FieldSelector>
<FieldDesc>
<FieldId>8</FieldId>
<FieldTitle>Vendor</FieldTitle>
</FieldDesc>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>32</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>33</Style>
</LabelFont>
<Items>
<Item>
<Value>Vendor</Value>
<Legend>Vendor</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>255 255 255</SecondaryColor>
<Symbol>164</Symbol>
<SymbolSize>120</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
<Labels>
<Item>0</Item>
</Labels>
</Display>
<AddToLegend>1</AddToLegend>
<DefaultConfiguration>
<Groups>Type</Groups>
</DefaultConfiguration>
</Sites>
<Antennas>
<Name>Antennas</Name>
<DefaultConfiguration>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</DefaultConfiguration>
<Configuration>
143
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
<Name>Conf</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</Configuration>
</Antennas>
<Transmitters> // or <MWMultiHops> // or <MWHubs>
<Name>Transmitters</Name> // or <Name>Multi-Hops</Name> //
or <Name>Point to Multipoint</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByValues</Type>
<FieldSelector>0</FieldSelector>
<FieldDesc>
<FieldId>0</FieldId>
<FieldTitle>Automatic</FieldTitle>
</FieldDesc>
<Items>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
</Display>
<AddToLegend>1</AddToLegend>
<DefaultConfiguration/>
</Transmitters> // or </MWMultiHops> // or </MWHubs>
<MWLinks>
<Name>Links</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
</Display>
<AddToLegend>0</AddToLegend>
<DefaultConfiguration/>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<SiteDisplay>
<SymbolFont>
<Name>Wingdings</Name>
<Size>80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
144
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
</SiteDisplay>
<Symbol>65444</Symbol>
<ShowText>0</ShowText>
<RepeaterDisplay>
<SymbolFont>
<Name>Wingdings</Name>
<Size>80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
</RepeaterDisplay>
</MWLinks>
<CWMeasurements>
<DefaultConfiguration>
<Distance>
<Min>0.</Min>
<Max>1000.</Max>
</Distance>
<DistanceUnit>0</DistanceUnit>
<Measure>
<Min>-105.</Min>
<Max>-90.</Max>
</Measure>
<MeasureUnit>0</MeasureUnit>
<Angle>
<Min>-180.</Min>
<Max>180.</Max>
</Angle>
<Relative>Yes</Relative>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced>([DIST]> 500)</Advanced>
</DefaultConfiguration>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
145
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<Type>ByIntervals</Type>
<FieldSelector>Error (P-M) (dB)</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-20.</Min>
<Legend>Error (P-M) (dB) >=-20</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<Symbol>167</Symbol>
<SymbolSize>100</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>M (dBm)</Item>
</DataTips>
<Labels>
<Item>M (dBm)</Item>
</Labels>
</Display>
</CWMeasurements>
<TestMobileData>
<Techno>GSM</Techno>
<DefaultConfiguration>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced></Advanced>
146
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
</DefaultConfiguration>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<Type>ByIntervals</Type>
<FieldSelector>Ec_I0</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-60.</Min>
<Legend>Ec_I0 >=-60</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<Symbol>167</Symbol>
<SymbolSize>100</SymbolSize>
</Item>
</Items>
</Display>
</TestMobileData>
<PropagationModels> // or <SmartAntennasModels>
<Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name>
<DefaultConfiguration/>
</PropagationModels> // or </SmartAntennasModels>
</FoldersConfigurations>
</Atoll>
147
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
Sample
148
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<Min>-95.</Min>
<Legend>Best Signal Level (dBm) >=-95</Legend>
<MainColor>0 255 217</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
<Min>-105.</Min>
<Legend>Best Signal Level (dBm) >=-105</Legend>
<MainColor>0 0 255</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
<DataTips>
<Item>c0000000</Item>
<Item>c0000001</Item>
</DataTips>
</Display>
<AddToLegend>1</AddToLegend>
<Resolution>50</Resolution>
<GUID>{52D66F26-5710-4F4B-A327-6DAFF337AB21}</GUID>
<LockedStudy>0</LockedStudy>
<ComputeHisto>1</ComputeHisto>
<HistoPerTx>0</HistoPerTx>
<HistoLabel></HistoLabel>
<Conditions>
<FieldDbm>
<Min>-105.</Min>
</FieldDbm>
<Reliability>0.75</Reliability>
<TRXType>BCCH</TRXType>
<DefTrgThreshold>1</DefTrgThreshold>
<Indoor>0</Indoor>
<WithShadowing>0</WithShadowing>
</Conditions>
</CoverageTRXStudy>
</Studies>
</Atoll>
149
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
• <ANP_IL_options>: Intra-technology inter-carrier neighbour allocation parameters (UMTS HSPA and CDMA2000
documents)
• <ANP_IT_options>: Inter-technology neighbour allocation parameters
A <Techno></Techno> tag is also present if the user configuration is exported from a 3GPP Multi-RAT document. This
tag contains the name of the technology to which the parameters belong.
The following parameters are saved:
• Parameters common to all technologies:
• <numMax>: Maximum number of neighbours to allocate
• <useCoSite>: Force co-site transmitters/cells as neighbours or not
• <useAdjacent>: Force adjacent transmitters/cells as neighbours or not
• <symetric>: Force symmetry between neighbours or not
• <keepNeighbs>: Reset existing neighbours or keep them
• <MaxDist>: Maximum distance between sites
• <PercentCoverage>: Coverage conditions: Minimum percentage of covered area
• <UseShadowing>: Coverage conditions: Take shadowing into account or not
• <reliability>: Coverage conditions: Cell edge coverage probability
• <applyConstraints>: Force exceptional pairs as neighbours or not
• <covBased>: Not implemented yet
• <minCov>: Neighbour importance: minimum factor for coverage
• <maxCov>: Neighbour importance: maximum factor for coverage
• <minAdj>: Neighbour importance: minimum factor for adjacency
• <maxAdj>: Neighbour importance: maximum factor for adjacency
• <minCos>: Neighbour importance: minimum factor for co-site
• <maxCos>: Neighbour importance: maximum factor for co-site
• <minDistImportance>: Neighbour importance: minimum factor for distance
• <maxDistImportance>: Neighbour importance: maximum factor for distance
• <resolution>: Resolution used for coverage calculation for overlapping (-1 means the default resolution defined in
the properties of the Predictions folder is used)
• <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not
• <UseGlobalThreshold>: Coverage conditions for WiMAX and LTE: Whether to use a global minimum preamble C/
N or RSRP, or per-cell values
• Parameters specific to GSM GPRS EDGE:
• <minField>: Coverage conditions: Minimum BCCH signal level
• <margin>: Coverage conditions: Margin for the minimum signal level (Handover start)
• <traffic>: Coverage conditions: Take traffic into account or not
• <deltaMax>: Coverage conditions: Handover end
• Parameters specific to UMTS HSPA, TD-SCDMA, and CDMA2000 1xRTT 1xEV-DO:
• <minField>: Coverage conditions: Minimum pilot signal level
• <margin>: Coverage conditions: Margin for the minimum signal level (Ec/I0 margin)
• <traffic>: Coverage conditions: Take traffic into account or not
• <deltaMax>: Coverage conditions: Handover end
• <EcIoMin>: Coverage conditions: Minimum Ec/I0
• <usePmax>: Coverage conditions: Use maximum power or not
• <PerCentMaxPower>: Coverage conditions: Percentage of maximum power to consider in calculations
• <EcIoMax>: Coverage conditions: Maximum Ec/I0
• <useEcIoMax>: Coverage conditions: Use maximum Ec/I0 or not
• <TDrop>: TDrop value (TD-SCDMA documents, intra-technology neighbour allocation only)
• Parameters specific to WiMAX 802.16e and LTE:
• <HOStart>: The handover start margin (intra-technology neighbour allocation only)
• <HOEnd>: The handover end margin (intra-technology neighbour allocation only)
• <BSmargin>: RSRP margin from the best server (inter-technology neighbour allocation only)
Sample
150
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<minField>-10500</minField>
<margin>500</margin>
<useCoSite>1</useCoSite>
<useAdjacent>1</useAdjacent>
<traffic>0</traffic>
<symetric>0</symetric>
<keepNeighbs>0</keepNeighbs>
<MaxDist>10000</MaxDist>
<PercentCoverage>1000</PercentCoverage>
<UseShadowing>0</UseShadowing>
<reliability>7500</reliability>
<UseIndoor>0</UseIndoor>
<deltaMax>1200</deltaMax>
<applyConstraints>0</applyConstraints>
<covBased>1</covBased>
<minDistImportance>100</minDistImportance>
<maxDistImportance>1000</maxDistImportance>
<minCov>1000</minCov>
<maxCov>3000</maxCov>
<minAdj>3000</minAdj>
<maxAdj>6000</maxAdj>
<minCos>6000</minCos>
<maxCos>10000</maxCos>
<UseGlobalThreshold>0</UseGlobalThreshold>
<EcIoMin>-1400</EcIoMin>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<EcIoMax>-700</EcIoMax>
<useEcIoMax>0</useEcIoMax>
</ANP_options>
</Atoll>
151
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
• <IM_calculate__ServiceZoneType>: All or Best signal level per HCS layer (for interference matrices calculation)
• <IM_calculate__reliability_X_10000>: Cell edge coverage probability (for interference matrices calculation)
• <TakeTfFromCapt>: Whether traffic loads are read from the default traffic capture or from the Subcells table
• <preferedSenario>: Scenario type, i.e., modification of existing TRXs allowed or not
Sample
152
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
Sample
153
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseIndoor>0</UseIndoor>
<UseCloseNghbs>1</UseCloseNghbs>
<CloseDistance>80000.</CloseDistance>
<CloseImportance>3000.</CloseImportance>
<MaxCloseCost>100</MaxCloseCost>
</SCP_options>
</Atoll>
Sample
154
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<SameCodeForCarriers>0</SameCodeForCarriers>
<PilotIncr>4</PilotIncr>
<PNClusterSize>3</PNClusterSize>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<UseMaxCodes>1</UseMaxCodes>
<MinEcI0>-1600.</MinEcI0>
<TDrop>-1800.</TDrop>
<reliability>6000.</reliability>
<UseShadowing>0</UseShadowing>
<minField>-10500</minField>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseIndoor>0</UseIndoor>
</PNO_options>
</Atoll>
Sample
155
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
<MinDistance>100.</MinDistance>
<SiteStrategy>1</SiteStrategy>
<UniformIDDistribution>1</UniformIDDistribution>
<RangeType>2</RangeType>
<ExcludedPis></ExcludedPis>
</OFDM_AFP_options>
</Atoll>
Sample
156
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<QualityModel>6</QualityModel>
<QualityObjective0>3</QualityObjective0>
<QualityObjective1>4</QualityObjective1>
<QualityObjective2>2</QualityObjective2>
<QualityObjective3>1</QualityObjective3>
<AvailabilityObjective0>3</AvailabilityObjective0>
<AvailabilityObjective1>2</AvailabilityObjective1>
<AvailabilityObjective2>1</AvailabilityObjective2>
<RainModel>5</RainModel>
<RBER>1.e-012</RBER>
<ALFA1>10</ALFA1>
<ALFA2>1</ALFA2>
<RefDelayM>6.30000019</RefDelayM>
<refDelayNM>6.30000019</refDelayNM>
<EquipPercent>33.</EquipPercent>
<RainPercent>33.</RainPercent>
<kMoy>1.33</kMoy>
<kMin>0.88</kMin>
<UseAtpc>0</UseAtpc>
<P0Method>1</P0Method>
<IgnoreXPD>1</IgnoreXPD>
<IgnorePR>0</IgnorePR>
<WhichBER>5</WhichBER>
<BER1>1.e-003</BER1>
<BER2>1.e-006</BER2>
<Rec838>1</Rec838>
<UseK1Global>1</UseK1Global>
<UseK2Global>1</UseK2Global>
<CALC_LINK_PORTS>selected</CALC_LINK_PORTS>
<MultilineShared>0</MultilineShared>
<NoAcm>1</NoAcm>
<InterferenceDistanceMax>50000.</InterferenceDistanceMax>
<InterferenceDropMin>1.</InterferenceDropMin>
<InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal>
<InterferenceCalcGo>1</InterferenceCalcGo>
<InterferenceCalcReturn>1</InterferenceCalcReturn>
<InterferenceCalcUplink>0</InterferenceCalcUplink>
<InterferenceCalcDownlink>0</InterferenceCalcDownlink>
<InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation>
<InterferenceAutoWeight>0</InterferenceAutoWeight>
<InterferenceUseAtpc>0</InterferenceUseAtpc>
<InterferenceWidth>250</InterferenceWidth>
<InterferenceOverShoot>0</InterferenceOverShoot>
<CochannelOnly>0</CochannelOnly>
<IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>
<Resolution>50</Resolution>
<INTERF_DETAIL>both</INTERF_DETAIL>
<ClutterCategory0>0</ClutterCategory0>
<ClutterDryCategory0>B</ClutterDryCategory0>
157
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
<ClutterCategory1>1</ClutterCategory1>
<ClutterDryCategory1>B</ClutterDryCategory1>
<ClutterCategory2>1</ClutterCategory2>
<ClutterDryCategory2>B</ClutterDryCategory2>
<ClutterCategory3>1</ClutterCategory3>
<ClutterDryCategory3>B</ClutterDryCategory3>
<ClutterCategory4>0</ClutterCategory4>
<ClutterDryCategory4>B</ClutterDryCategory4>
<ClutterCategory5>1</ClutterCategory5>
<ClutterDryCategory5>B</ClutterDryCategory5>
<ClutterCategory6>2</ClutterCategory6>
<ClutterDryCategory6>B</ClutterDryCategory6>
<ClutterCategory7>2</ClutterCategory7>
<ClutterDryCategory7>B</ClutterDryCategory7>
<ClutterCategory8>2</ClutterCategory8>
<ClutterDryCategory8>B</ClutterDryCategory8>
<ClutterCategory9>4</ClutterCategory9>
<ClutterDryCategory9>B</ClutterDryCategory9>
<ClutterCategory10>2</ClutterCategory10>
<ClutterDryCategory10>B</ClutterDryCategory10>
<ClutterCategory11>2</ClutterCategory11>
<ClutterDryCategory11>B</ClutterDryCategory11>
<ClutterCategory12>2</ClutterCategory12>
<ClutterDryCategory12>B</ClutterDryCategory12>
<ClutterCategory13>2</ClutterCategory13>
<ClutterDryCategory13>B</ClutterDryCategory13>
<ClutterCategory14>2</ClutterCategory14>
<ClutterDryCategory14>B</ClutterDryCategory14>
<ClutterCategory15>1</ClutterCategory15>
<ClutterDryCategory15>E</ClutterDryCategory15>
<ClutterCategory16>1</ClutterCategory16>
<ClutterDryCategory16>E</ClutterDryCategory16>
<ClutterCategory17>0</ClutterCategory17>
<ClutterDryCategory17>E</ClutterDryCategory17>
<ClutterCategory18>1</ClutterCategory18>
<ClutterDryCategory18>E</ClutterDryCategory18>
<ClutterCategory19>1</ClutterCategory19>
<ClutterDryCategory19>E</ClutterDryCategory19>
<ClutterCategory20>1</ClutterCategory20>
<ClutterDryCategory20>E</ClutterDryCategory20>
<ClutterCategory21>1</ClutterCategory21>
<ClutterDryCategory21>E</ClutterDryCategory21>
<ClutterCategory22>1</ClutterCategory22>
<ClutterDryCategory22>E</ClutterDryCategory22>
<ClutterCategory23>1</ClutterCategory23>
<ClutterDryCategory23>E</ClutterDryCategory23>
<ClutterCategory24>1</ClutterCategory24>
<ClutterDryCategory24>E</ClutterDryCategory24>
<ClutterCategory25>1</ClutterCategory25>
158
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
<ClutterDryCategory25>E</ClutterDryCategory25>
<ClutterCategory26>1</ClutterCategory26>
<ClutterDryCategory26>A</ClutterDryCategory26>
<ClutterCategory27>1</ClutterCategory27>
<ClutterDryCategory27>A</ClutterDryCategory27>
<ClutterCategory28>1</ClutterCategory28>
<ClutterDryCategory28>A</ClutterDryCategory28>
<ClutterCategory29>1</ClutterCategory29>
<ClutterDryCategory29>A</ClutterDryCategory29>
<ClutterCategory30>1</ClutterCategory30>
<ClutterDryCategory30>A</ClutterDryCategory30>
<ClutterCategory31>1</ClutterCategory31>
<ClutterDryCategory31>E</ClutterDryCategory31>
<ClutterCategory32>1</ClutterCategory32>
<ClutterDryCategory32>E</ClutterDryCategory32>
<ClutterCategory33>1</ClutterCategory33>
<ClutterDryCategory33>E</ClutterDryCategory33>
<ClutterCategory34>1</ClutterCategory34>
<ClutterDryCategory34>E</ClutterDryCategory34>
<ClutterCategory35>1</ClutterCategory35>
<ClutterDryCategory35>E</ClutterDryCategory35>
<ClutterCategory36>1</ClutterCategory36>
<ClutterDryCategory36>E</ClutterDryCategory36>
</Microwave>
</Atoll>
10.1.12 Macros
The following parameters are saved for macros:
• <Path>: Full path to the macro file
• <Language>: Language in which the macro is written
• <Timeout>: The target time allocated to macro execution
Sample
159
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
Sample
160
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
Sample
Sample
161
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
...
</SelectedFields>
</ReportConfiguration>
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.txt
Xindex=1
Yindex=2
MeasIndex=4
Unit=0
Frequency=2110
Height=1.5
Gain=0
Losses=0
NbCol=23
Col0=1
Col3=4
Col5=0
...
162
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 10: Configuration Files
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.*
Xindex=1
Yindex=2
Unit=0
Height=1.5
Gain=0
Losses=0
GenericNameIdOne=
GenericNameIdTwo=BSID
IdFormat=Decimal
Techno=IEEE 802.16e
NbCol=21
Col0=1
Col3=1
Col4=4
...
163
Atoll 3.3.2 Administrator Manual
Chapter 10: Configuration Files © Forsk 2016
164
Chapter 11
Initialisation Files
166
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
11 Initialisation Files
Initialisation files can be used to store operational and working environment settings. These files are optional, not required
for working with Atoll, but are useful means for selecting required calculation methods and other settings.
This chapter describes the formats of these files in detail:
• Atoll initialisation file (Atoll.ini)
This file contains conventions, calculation settings, and other options for Atoll. For more information on these options,
see "Atoll Initialisation File" on page 167.
Atoll.ini can be automatically loaded when Atoll is run when it is:
a. Identified in the command line parameter -Ini "inifilename" (see "Atoll Command Line Parameters" on page 31 for
more information), or
b. Located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through the
command line parameter.
• You can open the Atoll.ini file in the Atoll installation folder for editing by pressing
CTRL+SHIFT+i. If no Atoll.ini file exists, a blank Atoll.ini file is created.
• You must restart Atoll in order to take into account modifications made in Atoll.ini.
• A given Atoll.ini section, e.g. [GUIUserRights] or [LTE], must occur only once in the file,
with all options pertaining to that section listed under it. If you enter the same section
twice, only the first occurrence of the section will be read and loaded by Atoll.
The Atoll initialisation file is a powerful tool. You should not modify any option until and
unless you are absolutely sure of what you are doing.
167
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
The maximum amount of usable memory for Atoll 64-bit is determined by the size of available physical memory and the
paging file. In Windows operating systems, the memory allocated to any process is either part of the physical memory or of
the paging file. In order to track the memory consumption of a process, two memory usage indicators are available:
• Committed Memory: The amount of memory allocated either from the physical memory or from the paging file. This
information is available in the Windows Performance Monitor (Perfmon) under the "Process->Virtual Bytes" counter.
• Working Set Memory: The amount of committed memory allocated from the physical memory. The working set
memory is less than or equal to the committed memory. This information is available in the Windows Performance
Monitor (Perfmon) under the "Process->Working Set" counter.
You can set a maximum working set memory per Atoll session by adding the following lines to the Atoll.ini file:
[Memory]
MaximumWorkingSetSize = N
If required, multiple Atoll shortcuts can also be created, each using a dedicated Atoll.ini file. This enables you to define
different values for the maximum working set memory option in different Atoll.ini files and assign different memory limits to
different users. Once you have created different Atoll.ini files with different values for this option, you can point to these
Atoll.ini files in the path defined in the Atoll shortcut. For more information, see "Atoll Command Line Parameters" on
page 31.
You can also monitor the amount of memory used by an Atoll session using:
• The Event Viewer: You can have the maximum working set size defined for the Atoll session displayed in the Atoll
Event Viewer. To do so, add the following lines to the Atoll.ini file:
[Memory]
DisplayMaximumWorkingSetSize = 1
[Units]
MeterToFeetFactor = value
168
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[Units]
MilesToMeterFactor = value
[Site]
Prefix = <prefix>
When the Prefix parameter is specified, new sites are named <prefix><number> instead of Site<number>.
By default, when a transmitter is created, it is named <sitename>_<number>, where <sitename> is the name of the site where
the transmitter is located and <number> is the sequential transmitter sector identifier on that site. You can specify a prefix
and a suffix for the default transmitter name by adding the following lines to the Atoll.ini file:
[Transmitter]
Prefix = <prefix>
Suffix = <suffix>
• When the Prefix parameter is specified, new transmitters are named <prefix>_<number> instead of
<sitename>_<number>.
• When the Suffix parameter is specified, new transmitters are named <sitename>_<suffix><number> instead of
<sitename>_<number>.
• When both the Prefix and Suffix are specified, new transmitters are named <prefix>_<suffix><number> instead of
<sitename>_<number>.
• If you omit the Prefix or Suffix parameters (or if you use Prefix = <AUTO>) the default naming method is used.
It is also possible to remove the underscore character ("_") from the transmitter name. For example, new transmitters can be
named <sitename><number> instead of <sitename>_<number>. To remove the underscore, add the following lines to the
Atoll.ini file:
[Transmitter]
Underscore = 0
By default, Underscore is set to 1. When Underscore is set to 0, the underscore character is omitted in new transmitter names.
You can also specify whether the sequential <number> identifier that is appended to transmitter name should be a numeric
(0-9) or an alphabetic (a-z or A-Z) character. You can also specify whether the numbering sequence starts with 0, 1 or any other
value, or whether the alphabetical sequence starts with a, A (to specify upper or lower case), or any other character. The
following lines define these options in the Atoll.ini file:
[Transmitter]
SuffixIsNum = 0|1
First = <numeric_value>
FirstCharSuffix = <character>
• When SuffixIsNum = 1 , new transmitter names are appended with a numeric suffix. The parameter First specifies the
number of the first transmitter in the numbering sequence. For example, if SuffixIsNum = 1 and First = 0, then the
transmitter names will be appended with 0, 1, and 2.
• When SuffixIsNum = 0, new transmitter names are appended with a letter. The parameter FirstCharSuffix specifies the
letter of the first transmitter in the alphabetic sequence. For example, if SuffixIsNum = 0 and FirstCharSuffix = a, then
the transmitter names will be appended with a, b, and c.
By default, SuffixIsNum is set to 1, First is set to 1, and FirstCharSuffix is set to A.
169
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
Transmitters = 0
3GCells = 0
Repeaters = 0
[TiffExport]
PaletteConvention = Gis
The path should be the full path to the log file, which can be, for example, "\\Server\Drive\Root\Folder\Atoll\" or "C:\Program
Files\Forsk\Atoll\" (without quotation marks). "LogFile.log" will be created by Atoll as an ASCII text file, and can have any file
name and extension. Atoll will overwrite any already existing log file with the same name. If Atoll is unable to overwrite the
existing log file, it will not create any log.
You can also start Atoll, specifying a log file, by starting it with "Atoll.exe -log LogFile.log", either from the command line, or
by modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the -log option in
the command line, the command line log file will have priority over the one mentioned in the Atoll.ini file.
The option available in Atoll.ini is more suitable for running Atoll using macros. Apart from these options, you also have the
possibility to save the messages in the Event Viewer to a log file during an Atoll session (via context menu of Event Viewer).
[Print]
MaxDPI = 300
170
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
• Make copies of the externalised calculation results with the new document
• Do not retrieve externalised calculation results for the new document
To set the default option and suppress this dialog box, add the following lines to the Atoll.ini file:
[Settings]
CopyExternalResultsDialog = 0
CopyExternalResults = value
CopyExternalResultsDialog is set to 1 by default. This means that the dialog box appears by default. Setting
CopyExternalResultsDialog to 0 hides the dialog box and the externalised calculation results are managed according to the
value of the CopyExternalResults option:
• 0: Link the new Atoll document with the externalised calculation results of the original document
• 1: Make copies of the externalised calculation results with the new document
• 2: Do not retrieve externalised calculation results for the new document
CopyExternalResultsDialog is ignored when Atoll is run in non-interactive mode, for example using the API, and the
externalised calculation results are managed according to the value of the CopyExternalResults option.
When NumericalResults is set to 0, the Store prediction numerical results check box is cleared by default. When
NumericalResults is set to 1, the Store prediction numerical results check box is checked by default.
[Studies]
CoordSystemForTextExportIsProjection = 1
11.1.1.13 Restricting the List of Predictions for Creating Sector Traffic Maps
When you create a sector traffic map, i.e., traffic map based on cell coverage areas, Atoll uses an existing best server coverage
prediction in order to be able to distribute the live traffic data geographically. Atoll lets you select the best server coverage
prediction on which the traffic map will be based. In the list of available best server coverage predictions, Atoll lists all the best
server coverage prediction available in the Predictions folder, whether they were created using a margin or without.
If you want Atoll to list only the best server coverage predictions that were created without a margin, i.e., with 0 dB margin,
you can add the following lines to the Atoll.ini file:
[Studies]
SelectNullMarginOnly = 1
SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions available.
[Pathlosses]
DisplayInvalidityCause = 1
DisplayIndividualSuccessOrFailure = 1
171
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
DisplayOverallSuccessOrFailure = 1
Setting the DisplayInvalidityCause option to 1 will display the cause for which path losses were calculated for each transmitter,
setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded or failed for each
transmitter, and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path loss matrices calculated, the
number of path loss matrices calculated successfully, and the number of calculations that failed.
These details are listed in the Events tab of the Event Viewer.
In this way, Atoll is able to exactly detect the coordinate system used by the vector file being imported. In MIF files, the
CoordSys clause defines the coordinate systems, datum, unit, and other information. The coordinate system definition is
different in the PRJ files. The syntax used in Atoll.ini follows the syntax of the CoordSys clause in MIF files. Using the same
syntax for MIF and PRJ files, Atoll is able to read the detect the coordinate systems for both MapInfo and ESRI vector files.
The coordinate system codes in Atoll are stored in the CS files in the coordsystems folder. To access the coordinate system
codes through Atoll:
1. Select Tools > Options. The Options dialog box opens.
2. On the Coordinates tab, click the browse button (...) to the left of the Projection field. The Coordinate Systems dialog
box opens.
3. Select a coordinate system in the pane.
4. Click the Properties button. The Coordinate System properties dialog box opens.
The coordinate system code is available in the properties dialog box.
A few examples of such mapping are given below.
[MITAB]
; NTF
Earth Projection 1, 107 = 4275
; Tokyo
Earth Projection 1, 97 = 4301
; WGS 84 / UTM zone 31N
Earth Projection 8, 104, "m", 3, 0, 1, 500000, 0 = 32631
; WGS 84 / UTM zone 53N
Earth Projection 8, 104, "m", 135, 0, 0.9996, 500000, 0 = 32653
; WGS 84 / UTM zone 54N
Earth Projection 8, 104, "m", 141, 0, 0.9996, 500000, 0 = 32654
; NTF (Paris) / France II étendue
Earth Projection 3, 1002, "m", 0, 46.8, 45.8989188889, 47.69601444, 600000, 2200000
= 27595
Enabling this option influences the export feature for all exportable vector fomats (MIF,
TAB, AGD, SHP, TXT). When this option is enabled, only the largest polygon is exported
for coverage layers having more than one polygon.
You can enable this feature by adding the following lines to the Atoll.ini file:
[Studies]
EnableLBS = 1
172
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The polygons are
exported in a comma separated values format.
You can define any number of servers by incrementing the index N. These servers will be available in the WMS data import
dialog box in Atoll.
PtAnalysisNbServersMax allows you to define the maximum number of servers (i.e. transmitters or cells) to consider when
calculating the received signal levels. X is the maximum number of servers and it is set to 0 by default, i.e. no limit.
PtAnalysisMargin allows you to define a margin with respect to the best server signal level. Atoll calculates the signal levels
from all servers within a Y dB margin from the best server signal level. The default value is 30 dB.
In addition to the above, you can also set the maximum number of servers displayed in the Point Analysis window and,
consequently, the maximum number of arrows displayed in the Map window (from the pointer location). To set this number,
add the following lines to the Atoll.ini file:
[Perfos]
PtAnalysisNbServersDisplayed = Z
PtAnalysisNbServersDisplayed is set to 100 by default. It affects all tabs and reports of the Point Analysis tool in GSM, LTE,
WiMAX, and WiFi. Only the Reception tab is impacted in UMTS, CDMA2000, and TD-SCDMA.
LoadKMLVectors is set to 1 by default, which means that vectors are imported along with placemarks.
ShowOptionMergeZone is set to 0 by default. When the option is set to 1, a Combine with existing zones option is available
in the User Configuration dialog box.
173
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
11.1.1.21 Setting the Precision for the Antenna Pattern Verification at Import
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are
correctly aligned when:
• the horizontal pattern attenuation at 0° is the same as the vertical pattern attenuation at the pattern electrical tilt
angle, and
• the horizontal pattern attenuation at 180° is the same as the vertical pattern attenuation at the 180° less the pattern
electrical tilt angle.
By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB. If you
want to change this default precision, add the following lines to the Atoll.ini file:
[Antenna]
PrecisionTimes10 = X
Where X is the required precision in dB multiplied by 10. For example, if you want to set the precision to 0.5 dB, X will be
0,5 10 = 5 .
[Export]
AdvancedXML = 1
11.1.1.23 Keeping the Original List Separator when Exporting in CSV Format
Before exporting in CSV format, Atoll verifies if the list separator symbol is identical to the decimal or digit grouping symbols
defined in your regional settings.
By default, Atoll will change the list separator if it is found to be identical to the decimal symbol or the digit grouping symbols.
You can force Atoll to keep the original list separator symbol by adding the following option in the Atoll.ini file:
[Export]
AlwaysUseListSeparatorInCSV = 1
[GUIUserRights]
EnableNewDocFromTemplate = 0
[GUIUserRights]
EnableMacrosAddins = 0
174
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[GUIUserRights]
EnableZip = 0
[GUIUserRights]
HidePropagationModelsFolder = 1
[GUIUserRights]
AllowSharedParameterModification = 0
[Transmitter]
CheckImpactOnRepeaters = 1
[Grids]
NbDecimals = 2
This option applies to most non-formatted floating point parameters in Atoll, i.e., excluding geographic coordinates,
formatted floating point values, and certain values where decimal precision is important.
NbDecimals is set to -1 by default. This corresponds to maximum precision, i.e., all the digits after the decimal point available
in the database are displayed.
175
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[Geo]
FindGeoButtonAlwaysActive = 1
FindGeoButtonAlwaysActive can be useful when you have changed the location of a geographic data file, and you wish to
change the path to the new location. It is set to 0 by default.
When changing the path to a linked geographic data file, you must provide the new path
to the same file. This option does not allow linking to another file instead. In order to link
to another file, you must follow the normal file import procedure.
VectorDisplayConfigurationCompanionFile is set to 1 by default. The exported display configuration file will have the same file
name and will be saved in the same directory as the exported vector-format file.
When you import vector data in anAtoll document, the same option enables you to simultaneously import the corresponding
display configuration file (CFG). The display configuration file will only be imported if it has the same file name and if it is
located in the same directory as the imported vector-format file.
11.1.1.35 Exporting BMP, TIF, and PNG Files with a TAB Reference File
When exporting BMP, TIF, and PNG files, Atoll can export the georeference information in a TAB file instead of the default
respective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the georeference
information in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines to the Atoll.ini file:
[RasterExport]
GeorefWithTAB = 1
[RasterExport]
ExportBILAsESRI = 1
[CoPlanning]
LinkSites = 1
176
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
11.1.1.40 Adding the Duplicate Site to the Original Site’s Site List
When you duplicate a site, you can choose to add the duplicate site to the site list (if any) of the original site by adding the
following lines to the Atoll.ini file:
[Site]
AddToSiteListOnDuplicate = 1
[GUI]
MoveSiteMethod = 1
MoveSiteMethod is set to 0 by default. The following behaviour occurs when you move a site according to the value of
MoveSiteMethod:
MoveSiteMethod Behaviour
0 The relative coordinates of the antennas follow the coordinates of the site.
1 The absolute coordinates of the antennas do not change.
2 A dialog box appears asking you whether to move the antennas with the site or not.
177
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
ResetAltitude is set to 0 by default. The following occurs to the duplicate/moved site according to the setting of ResetAltitude:
If a site’s coordinate(s) and its real altitude are modified at the same time (from the site’s
Properties dialog box or from the Sites table), the new value in the Real field will be kept
even if ResetAltitude is set to 1 or 2.
OnlyVisibleClassesInInterferenceReport is set to 0 by default. The visibility of clutter classes on the map can be managed
through the Display tab of the Properties dialog box of the Clutter Classes folder. Using this option, you can exclude clutter
classes which are not relevant in interference prediction reports, for example, water.
178
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[Pathlosses]
FullResyncPrivShared = 0|1|2
• When FullResyncPrivShared is set to 0: invalid private path loss matrices are deleted if shared path loss matrices are
valid when running calculations or checking the validity of path loss matrices (Propagation tab of the transmitter
Properties dialog box). Valid private path loss matrices are preserved.
• When FullResyncPrivShared is set to 1: in addition to the 0 setting, valid private path loss matrices are deleted if shared
path loss matrices are valid when checking the validity of path loss matrices.
• When FullResyncPrivShared is set to 2: in addition to the 1 setting, valid private path loss matrices are deleted if shared
path loss matrices are valid when running calculations. This setting is not compatible with the use of tuned path loss
matrices.
FullResyncPrivShared is set to 1 by default.
• If you have private path loss matrices tuned using measurement data, setting
FullResyncPrivShared to 2 will force Atoll to delete them automatically when
calculations are run.
• You should set FullResyncPrivShared to 1 when working with tuned private path
loss matrices.
[Print]
LogoFooterChecked = 1
11.1.1.48 Filtering Predictions by Technology When Reading the XML Studies File
In the XML studies file, some common CDMA coverage predictions can be available for CDMA2000 and UMTS, or some
common OFDMA coverage predictions can be available for WiMAX and LTE. If you want to filter the customised predictions
stored in the XML studies file by technology, e.g. separate the WiMAX and LTE coverage predictions, and load only the
predictions specific to the technology of the current Atoll document, add the following lines to the Atoll.ini file:
[Studies]
CustomStudiesFilteredByTechno = 1
CustomStudiesFilteredByTechno is set to 0 by default. This option is only relevant for reading the XML studies file. Atoll always
writes the technology type in the XML studies file when customised coverage predictions are saved in it.
[MITAB]
EnableMessages = 1
EnableMessages is set to 0 by default. Atoll does not display any message related to MapInfo file import and export.
[Population]
ReportResolution = X
Where X is the resolution for the conversion of population map vectors into raster.
179
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
If you set ReportResolution to a very precise (low) value, the performance (calculation
speed) can be considerably decreased depending on the size of the population maps in
the document. It is recommended to set this parameter to an optimum value, i.e., just
precise enough to get the required accuracy.
[Studies]
ReportDecimalPlacesAbsolute = X
ExportOnlyVisibleLevels is set to 0 by default, which means that when a coverage prediction is exported, Atoll will export all
of its levels whether they are visible or not.
Atoll exports only visible coverage predictions. If a coverage prediction consists of only
one level, the visibility check box of that level also controls the visibility check box of the
prediction itself. This means that if the visibility check box of the only level of such a
prediction is cleared, the prediction will itself be hidden and will not be exported.
180
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[Studies]
NoOverlapOnBestServer = 1
NoOverlapOnBestServer is set to 0 by default. When NoOverlapOnBestServer is set to 1, Atoll arbitrarily selects one of the
best servers on such pixels. This option can be useful, for example, when calculating population statistics based on a best
server coverage prediction. When a pixel is covered by more than one best server, the population belonging to that pixel is
counted as many times as the number of best servers, which can give erroneous percentages of covered population.
[Studies]
ReportMethod = 0
[Compression]
StartSizeInMB = X
Where X is the file size in MB. Atoll will compress the ATL file if it is larger than X. By default, StartSizeInMB is set to 200.
•If you want an add-in to be loaded, activated, and accessible in the Add-ins and Macros dialog box for activation/
deactivation, add the following lines to the Atoll file:
[Add-ins]
Add-in Name = 1
•If you want an add-in to be loaded and activated, but only shown in the Add-ins and Macros dialog box for information
(impossible to deactivate), add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 2
• If you want to set an add-in to be mandatory for Atoll, add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 3
Any add-in set to option 3 will be loaded and activated, but only shown in the Add-ins and Macros dialog box for
information (impossible to deactivate). Atoll will not run if it is unable to load this add-in.
Add-in Name is the name of the add-in as it appears in the Add-ins and Macros dialog box. Atoll fails to start if for some reason
it is unable to load an add-in whose status is set to 3. The default status for add-ins is 1.
181
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
You can define any number of online map URLs by incrementing the index N. These URLs will be available in the online map
import dialog box in Atoll.
11.1.1.60 Changing the Default Cache Location for the Loaded Map Tiles
The map tiles that you load into Atoll are stored in a specific cache directory named after the corresponding tile server. By
default, the location of this cache is "%TEMP%\OnlineMaps". You can change this location by adding the following lines to the
Atoll.ini file:
[OnlineMaps]
TilesCachePath = new_path
11.1.1.61 Defining the Microsoft Bing Tile Server for Online Maps
If you want to define the Microsoft Bing Maps Server for online maps, you must request a Bing Maps key from Microsoft and
use it with the following option in the Atoll.ini file:
[OnlineMaps]
BingKey = key
You must request your key from Microsoft. When BingKey is specified with a valid key, "Bing" becomes available under
Provider in the Add a Tile Server dialog box. A Type and a Language must also be defined before you can validate.
• Type: available choices are "Aerial", "Road", and "Hybrid"
• Language: default languages are "English", "French", and "Japanese".
More languages can be selected if they are defined with the following options in the same section of the Atoll.ini file:
BingCultureX = culture
BingLanguageX = language
• X = 0 is equivalent to 4th position in the Language list (after the 3 default languages)
• culture and language settings can be found in the Culture and Language columns at
the following URL: http://msdn.microsoft.com/en-us/library/hh441729.aspx
11.1.1.62 Defining the Microsoft Bing Tile Server for Online Searches
By default, when you search for a point on the map by its full or partial postal address, Atoll returns specific search results. If
you want to force Atoll to return a list of results based on the Microsoft Bing Maps server, you must request a Bing Maps key
from Microsoft and use it with the following option in the Atoll.ini file:
[OnlineSearch]
BingKey = key
182
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[OnlineSearch]
MapQuestKey = key
[Settings]
KeepFilterZoneOnRemoveFilter = 0
[Settings]
EnableDataExchangeCommands = 0
[System]
RestartOnImproperExit = 1
RestartOnImproperExit is set to 0 by default. If set to 1, Atoll restarts following an improper exit without using any command
line options that may be defined for its shortcut.
183
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
You can use RootFolder as a global shortcut, which can be used in the other folder paths. For example:
RootFolder = \\Server\Path
ATLFilesFolder = {RootFolder}\ATL
You can use the shortcut {UserLogin} to replace the Windows user name. For example:
RootFolder = \\Server\Path
ATLFilesFolder = {RootFolder}\ATL\{UserLogin}
In this case, if the user name is JSmith, then the default directory for ATL files is:
\\Server\Path\ATL\JSmith
[FavouriteViews]
DefaultStorage = 0|1
• When DefaultStorage is set to 0, favourite views are created and stored in the user profile.
• When DefaultStorage is set to 1, favourite views are created and stored in the document.
DefaultStorage is set to 0 by default, which means that favourite views are created and stored in the user profile.
[FavouriteViews]
UpdateFocusAndComputationZone = 1
UpdateFocusAndComputationZone is set to 0 by default, which means that the computation zone and focus zone are not
saved in the favourite views.
11.1.1.71 Fixing Antenna Electrical Azimuth and Tilt Values on Document Update
Antenna electrical azimuths and tilts are used in calculations to determine the attenuation due to antenna patterns in
different directions. Therefore, it is important that these values be correct. When you update Atoll documents from version
3.2V7.2 to 3.3V7.3, you can have Atoll check and fix any erroneous values in the Antennas table.
• If you want Atoll to ignore any errors in the electrical azimuths and tilts, add the following lines to the Atoll.ini file:
[Antenna]
CheckOrFixElecAzAndTilt = 0
• If you want Atoll to notify you about any errors in the electrical azimuths and tilts, add the following lines to the
Atoll.ini file:
[Antenna]
CheckOrFixElecAzAndTilt = 1
• If you want Atoll to notify you about any errors in the electrical azimuths and tilts and fix these errors, add the
following lines to the Atoll.ini file:
184
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[Antenna]
CheckOrFixElecAzAndTilt = 2
•If you want Atoll to notify you about any errors in the electrical azimuths and tilts and set the electrical azimuths to 0,
add the following lines to the Atoll.ini file:
[Antenna]
CheckOrFixElecAzAndTilt = 3
[SitesSymbol]
FontName = Name of the font
Symbol = Character used for the site symbol from the character set of the font
Size = Character size in number of pts
Color = Colour of the symbol
The default sites symbol is used when a new document is created in Atoll. To know the name of the font to use, and to set the
symbol, you can use the Windows’ Character Map tool. You can use the copy/paste features to set the symbol in the Atoll.ini
file.
Example:
[SitesSymbol]
FontName = Wingdings
Symbol = ¤
Size = 12
Color = 0
[RemoteAntennas]
FrozenSymbol = 1
185
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and clutter
height.
[EventsObserver]
milliseconds = 1
date = 1
186
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
11.1.2.9 Setting the Maximum Number of Lines to Coverage Prediction Tool Tips
If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the coverage
predictions available at a pixel up to 30 lines by default. You can change this default number of tool tip text lines through the
following option in the Atoll.ini file:
[Studies]
MultiplePlotsTipTextLines = X
X is the number of lines to display in the tool tips. By default, MultiplePlotsTipTextLines is set to 30. If you set it to a very large
value, however, the tool tip might not display correctly.
H
DrawSingleElementPattern is set to 1 by default, and the displayed diagram is g n S R Avg S . When you set
H
DrawSingleElementPattern to 0, the diagram displayed will represent S R Avg S .
The comments are displayed between the name of the coverage prediction and the thresholds. CommentsInLegend is set to
0 by default.
Where X is the number of digits that the CELL_IDENTITY field should contain. For example, CellIDNbDigits = 5 means that Atoll
will display at least five digits in the CELL_IDENTITY field by adding leading zeros where required. This means that Atoll will
display "00678" in the above example. However, if the CELL_IDENTITY field contains a number that has more than X digits, all
the digits will still be displayed. For example, all seven digits in "9376562" will still be displayed even if CellIDNbDigits is set to
5.
[Antenna]
REDTDisplay = 1
187
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
11.1.2.14 Increasing the Width of the Clutter Description Pane in the Status Bar
You can increase the width of the clutter description pane in the Status bar (bottom right), to display the descriptions of
clutter classes with long names, by adding the following lines to the Atoll.ini file:
[StatusBar]
ClutterPaneWidth = X
ClutterPaneWidth is set to 100 by default, which means 100% of its default width. To increase the width to, for example, twice
the original width, set ClutterPaneWidth to 200.
[DocTitle]
UseTechnoName = 0
You can also override user-defined colours, if any, and force shading (from red to blue) by setting the following option in the
Atoll.ini file.
[Display]
DiscreteValueColoring=Shading
[GeoProfileDisplay]
Beamwidth = 1
BeamwidthColor = 128 128 128
Upper3dbColor = 255 0 0
Lower3dbColor = 196 0 196
188
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
The geographic profile displays clutter classes and the Fresnel ellipsoid by default. When the Beamwidth option is set to 1, the
option is enabled and three additional lines are added to the diagram:
• Thick upper and lower lines: These lines todicate the upper and lower -3 dB beamwidth limit in the vertical plane.
• Thick central line: This line indicates the axis of minimal loss, which coincides with the actual tilt axis of the antenna
(combining the physical and electrical tilt).
You can specify the colors of the lines with the BeamWidthColor, Upper3dbColor, and Lower3dbColor options.
The vertical beamwidth is widest in the azimut axis of the antenna. If you move the position of the Point Analysis tool off of
the antenna azimut axis, the vertical beamwidth diminishes and disappears when the vertical beamwidth loss exceeds -3 dB.
[RemoteCalculation]
NumberedServers = Server1NameN; Server2NameN; ...
189
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
Here Server1Name and Server2Name refer to the names of the computers being used as calculation servers, and N is a number
from 0 to 9. This means, for example, that Server1 can run up to 10 instances of the distributed calculation application, and
all these instances can be listed in the NumberedServers option (Server1Name0; Server1Name1; Server1Name2; ...). Using
this option, you can assign distributed calculation servers to different groups of users working with two different Atoll.ini files.
For example, user group 1 can use Server1Name0 to Server1Name4, and group 2 can use Server1Name5 to Server1Name9.
If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local computer.
However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the path loss matrices one
by one. It does not attempt creating more than one thread.
[RemoteCalculation]
AtollSvrPriority = -1, 0, 1 or 2
X is the number of days prior to the temporary License end date you want Atoll to warn you. When no information is given in
the Atoll.ini file, Atoll warns the user 30 days before the License end.
190
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi-RAT documents using these options.
In order to carry out a Wi-Fi frequency planning using the AFP module, you must have access to the WiMAX AFP module
license, i.e. WiMAX_AFP must not be set to 0.
In order to carry out a combined GSM and UMTS optimisation using the ACP module, you must have access to both ACP
module Licenses, i.e. ACP_GSM and ACP_UMTS must both not be set to 0.
In order to carry out a Wi-Fi optimisation using the ACP module, you must have access to the WiMAX ACP module license, i.e.
ACP_WiMAX must not be set to 0.
Where X is the time in minutes. The idle time can be set to infinity by defining IdleTime = 0.
191
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[Refresh]
RefreshUnmodifiedDataOnlyByDefault = 1
[Database]
IntegrityChecker = 1
If this option is set to 1, Atoll performs SELECT filters in the database to guarantee data integrity. This feature enables selection
directly in the database in order to avoid integrity problems in the future.
192
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[Database]
SubCellAuditConsistency = 1
To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables and fix any problems
found, add the following lines to the Atoll.ini file:
[Database]
SubCellAuditConsistency = 2
To automatically audit the compatibility of the main subcell values without fixing any problems found, add the following lines
to the Atoll.ini file:
[Database]
SubCellAuditMainValues = 1
To automatically audit the compatibility of the main subcell values and fixi any problems found, add the following lines to the
Atoll.ini file:
[Database]
SubCellAuditMainValues = 2
Where X is the timeout value in an integer number of seconds. After X seconds, the command is considered too long to
execute. If you set CommandTimeout = 0, there will be no time limit for the execution of the command.
[Database]
ExportTransactionMethod = 1
[PlanetImport]
SensitiveCase = 1
Case sensitive means that "Site0" will be considered different from "site0" during import.
193
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
11.1.5.10 Setting the Sign for KClutter When Importing Data From Planet EV
Planet EV uses the opposite sign for the Kclutter parameter with respect to Planet DMS. If you are importing data from Planet
EV, you might have to change the sign of this parameter. You can instruct Atoll to change the sign for Kclutter when importing
data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ChangeKclutterSign = 1
11.1.5.11 Setting the Clutter No Data Value for When Importing Data From Planet
EV
Atoll automatically detects undefined clutter class data as No Data when importing data from Planet EV. No Data clutter is
considered transparent on the map and in calculations. You can instruct Atoll to use a specific value as the No Data value when
importing data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ClutterNoData = X
Where X is the No Data value for clutter. ClutterNoData is set to -9999 by default.
PromptOnArchive = 1 is the default setting used if this option is not provided in the Atoll.ini file. The user will be prompted for
password when he tries to archive data in the database for the first time during anAtoll session.
If you want Atoll to ask the user to enter the username and password for every refresh and archive, set:
PromptOnArchive = 2
• Username and password are stored in the ATL file in an encrypted form.
• This option is only appropriate if the database connection string contains a password.
Before modifying this option, make sure that the database server is correctly configured
for transactions.
194
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
OverwriteSharedFolderPath is set to 1 by default, meaning that the path loss directory is overwritten.
[Database]
ExclusiveProvider = providername
Where providername can be "Access", "SQLServer", or "Oracle". When this option is set, Atoll uses the defined database type
and does not display the database selection dialog box that appears when creating a new document from an existing database
or when exporting a document to create a new database.
11.1.5.17 Displaying Only the First Export to Database Error in a Dialog Box
When a document containing several inconsistencies is exported to a database, you can force Atoll to display only the first
error in a dialog box and log all other inconsistencies in the Events viewer by adding the following lines to the Atoll.ini file:
[Database]
LogExportToDbErrors = 1
[Antenna]
Catalog Vertical Diagram Orientation = 90 or angle value
InterpolatePatternEvenIfOnlyOneDiagram = 0 or 1
InterpolatePatternIndB = 0 or 1
Catalog Vertical Diagram Orientation is a display option. It enables rotating the antenna’s vertical diagram to a user-defined
angle. By default, Catalog Vertical Diagram Orientation is set to 90 meaning that the vertical diagram is displayed pointing to
the right. Setting it to 0, for example, will show the vertical diagram pointing to the top.
InterpolatePatternEvenIfOnlyOneDiagram can be used to change the way Atoll interpolates antenna pattern attenuation
diagrammes for antennas with only one diagramme available, vertical or horizontal. With
InterpolatePatternEvenIfOnlyOneDiagram = 0 (default, new method), Atoll uses the only diagramme available for both
vertical and horizontal planes. With InterpolatePatternEvenIfOnlyOneDiagram = 1 (previous method), Atoll uses the
195
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
diagramme available for the plane to which it corresponds, vertical or horizontal, and an isotropic diagramme (a 0 dB circular
attenuation pattern) for the plane for which no diagramme is available.
InterpolatePatternIndB sets the unit used by Atoll when it performs linear interpolations on antenna pattern attenuation.
When InterpolatePatternIndB = 0 (default), interpolations are calculated in Watts. When InterpolatePatternIndB = 1 (or any
value other than 0), interpolations are calculated in dB leading to stronger antenna pattern attenuation.
AutoLock is to 1 by default.
This option does not affect the shadowing margin calculation during Monte Carlo
simulations. Monte Carlo simulations do not use an average value of the shadowing
margin depending on the cell edge coverage probability. During Monte Carlo simulations,
random shadowing margin values are calculated based only on the standard deviations
defined per clutter class.
In UMTS HSPA and CDMA2000 documents, you can also deactivate the calculation and use of macro-diversity gains. For more
information, see "Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt" on page 209.
11.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability
The default value of the cell edge coverage probability can be configured in the Atoll.ini file. If you enter the following lines to
the Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file as the default
value, and will take it into account when performing point analysis, in the shadowing margins calculator, and will propose it
as the default value for coverage prediction studies.
[Shadowing]
Reliability = 60
The value of cell edge coverage probability used for automatic neighbour allocation and
interference matrices calculation is stored in user configuration files (CFG).
196
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ClutterParams]
IndoorActivity = 1
11.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site
The calculation of line of sight area around a given site uses the resolution of the geographic data as the default calculation
resolution. These calculations can be time-consuming if the geographic data is available with a very high resolution. You can
set the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines to the Atoll.ini
file:
[LOSArea]
ResolutionMultFactor = X
Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease the
time required for the calculation by half.
[Pathlosses]
EmbeddedByDefault = 1
ContinueOnError = 1 by default. This means that by default Atoll does not stop the calculations on error.
11.1.6.9 Warning About Prediction Validity When Display Options are Modified
Coverage predictions have to be recalculated if you modify their display options. Atoll displays a warning message when you
modify the display options for coverage predictions. To deactivate this warning message, add the following lines to the
Atoll.ini file:
[Studies]
RecomputationWarning = 0
UseSiteAltitude is set to 1 by default, which means that the altitude used in calculations will be the one which is either read
from the Sites table or from the DTM at the site’s coordinates, if the user-defined altitude is not available in the Sites table.
197
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact
coordinates of each transmitter considering the values entered for the DX and DY parameters.
The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during calculations,
Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering the values entered for
the DX_A, DY_A, DX_B, and DY_B parameters.
With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave links
located at the site coordinates, Atoll will still use the altitudes defined per site, if any, or
the altitudes from the DTM otherwise
Once SpecifyResolutionAfterComputation is set to 0, Atoll no longer resets the resolution to the default value for coverage
predictions that do not have a resolution defined. Atoll allows you to leave the field empty in the coverage prediction
properties, and directly reads the default resolution defined in the Predictions folder’s Properties dialog box. In this way,
when you create coverage predictions without defining resolutions for them, you can modify the default resolution in the
Predictions Properties dialog box and, therefore, change the display resolution for all the coverage predictions, new or
existing.
To return to the normal working, remove the lines from the Atoll.ini file or set SpecifyResolutionAfterComputation to 1.
[RemoteCalculation]
Priority = 0, 1, or 2
Priority enables you to set the priority between calculations and user interface.
• 0: User interface has the highest priority.
• 1 (default): User interface has a higher priority than calculations.
• 2: User interface and calculations have the same priority.
[RemoteCalculation]
NumberOfProcessors = X
NumberOfThreadsPathloss = 1, 2, ..., or 8
NumberOfThreadsSimulation = 1, 2, ..., or 8
NumberOfThreadsStudy = 1, 2, ..., or 8
NumberOfThreadsStudyTile = 0, 1, 2, ..., or 8
NumberOfThreadsNeighbour = 1, 2, ..., or 8
NumberOfThreadsMicrowave = 1, 2, ..., or 8
198
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
• NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4 by
default, 8 maximum)
• NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation
calculations (4 by default, 8 maximum)
• NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage
predictions (4 by default, 8 maximum)
• NumberOfThreadsStudyTile is the maximum number of threads that can be used per coverage prediction calculation
(0 by default, 8 maximum). If you set this option to 0 or 1 (recommended), Atoll will use one thread for the calculation.
• NumberOfThreadsNeighbour is the maximum number of threads that can be used for automatic neighbour allocation
(4 by default, 8 maximum)
• NumberOfThreadsMicrowave is the maximum number of threads that can be used for microwave link calculations (4
by default, 8 maximum)
All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.
[GSM]
ParallelSimulations = 1
11.1.6.14.2 Parallel Calculation of Monte Carlo Simulations in UMTS HSPA and CDMA2000
In UMTS HSPA and CDMA2000 (1xRTT and 1xEV-DO) documents, Atoll perform multi-threaded calculations of Monte Carlo
simulations by default. To disable parallel calculations in these two technologies, add the following lines to the Atoll.ini file:
[CDMA]
ParallelSimulations = 0
ParallelSimulations in UMTS HSPA and CDMA2000 (1xRTT and 1xEV-DO) documents is set to 1 by default.
By default, when you open a read-only Atoll document, it is not possible to run calculations in it. If you want to run calculations
in read-only documents, add the following lines to the Atoll.ini file:
[Studies]
ComputeEvenIfReadOnly = 1
If you open a document that is already open in another Atoll session, Atoll lets you open the document as read-only.
199
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[Studies]
AerialStudy = 1
11.1.6.19 Estimating Required and Used Memory Size for UMTS Simulations
Atoll can estimate the required and used memory sizes for UMTS simulations and display the estimates in the Source Traffic
tab of the new simulation group dialog box. Estimated memory size within the green region means low consumption, within
the yellow region means medium consumption, within the orange region means high consumption, and within the red region
means very high consumption, in which case the simulations might generate an out of memory error and not complete.
To activate the memory estimation feature, add the following lines to the Atoll.ini file:
[CDMA]
PredictSimuMemorySize = 1
11.1.6.20 Disabling Calculations Over NoData Values for DTM and Clutter Classes
If you don’t want Atoll to calculate path losses on the pixels located over nodata values defined in the DTM and clutter classes
files, add the following lines to the Atoll.ini file:
[FskPropagModels]
OptimOnNoData = 1
By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by default.
200
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
LinkedPredictionsComputationMode is set to "Serialized" by default, which means the path loss matrices and unlocked
coverage predictions in the current and linked documents are calculated in a serial way. If you set the option to any other
value, the calculations are performed in parallel but without being managed by a task list. Calculations are carried out starting
with the current document in the order of the coverage predictions in the Predictions folder.
[Simulation]
RandomTotalUsers = 0
EIRPfromMaxPower is set to 0 by default. This option applies to "Coverage by Transmitter", "Coverage by Signal Level", and
"Overlapping Zones" predictions in UMTS, CDMA2000, and LTE.
[Neighbours]
ExcludeFilteredCellsFromNeighbourLists = 1
201
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[Neighbours]
DistanceAzimutWeightingPercent = 30 (default)
If the value you set is too high (e.g. 70), the resulting inter-transmitter distance can be
negative. In such a case, nothing will be displayed in the corresponding table cell.
[Neighbours]
CandidatesMaxDistanceInImportanceCalculation = 1
11.1.6.31 Keeping Assigned Neighbours that are not Symmetric with the Reference
Transmitter
By default, when the Force Symmetry option is selected and the neighbour list of a transmitter is full, the reference
transmitter is not added as a neighbour and that transmitter is removed from the reference transmitter’s neighbours list.
To force Atoll to keep that transmitter in the reference transmitter’s neighbours list, add the following lines to the Atoll.ini file:
[Neighbours]
DoNotDeleteSymmetrics = 1
202
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[Neighbours]
DeleteOnAuditIfSourceEqualsTarget = false
[Transmitter]
MaximumCalculationRadius = value
Where value is the maximum calculation radius in metres. By default, there is no limit for the path loss calculation radii. The
limit you set here is applied to values entered by the user in the Transmitters table or properties dialog box.
[Transmitter]
UpdateLossIfNoEquipment = 0
The above applies if no equipment is defined and if the Miscellaneous losses are set to 0
dB (in transmission and reception) in the Equipment Specifications dialog box. If no
equipment is defined and one of these values is different from 0 dB, then the total losses
will be updated even if UpdateLossIfNoEquipment is set to 0.
203
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[DisplayProfileRealTime]
Propagation Model Type = False
Here Propagation Model Type is the text string stored under Type in the Propagation Models table. For example, the
Propagation Model Type of the "Standard Propagation Model" is "Atoll.StdPropagModel". This option does not apply to Aster
and CrossWave propagation models. These two models always redraw the profile when the left mouse button is released.
ExternalIncluded is set to 1 by default, i.e. inter-technology interference is taken into account by default in GSM "Coverage by
C/I Level (DL)" predictions (the Inter-technology check box does not appear in the list of Interference Sources) and in point
analyses’ "Interference" and "Details" views.
[BsicFormat]
DefaultValue = 1 for Octal or 0 for Decimal format
DefaultValue enables you to change the default BSIC format (Octal by default) when you create a new Atoll document.
[Refresh]
TRXIntegrity = 1
204
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
If you set this option to anything other than "No", Atoll will use the maximum range parameter and set it to the default value
of 35 km.
[Studies]
MultiBandManagement = 1
MultiBandManagement is set to 0 by default. Enabling multi-band management allows the users to access the multi-band
management features through the Frequency Band Propagation button under the Subcells section of the TRXs tab of a
transmitter’s Properties dialog box, and through the Subcells > Multi-Band Propagation Parameters command in the context
menu of the Transmitters folder.
In the Multi-Band Propagation Parameters table and in the database, Atoll uses the "@" character to identify the multi-band
transmitters. Therefore, if you are working on a document with multi-band transmitters, and you have the "@" character in
the names of repeaters, remote antennas, or subcells without a donor/main transmitter, Atoll deletes these records when
opening the document from a database. If you do not want Atoll to automatically delete such records when opening the
document from a database, you have to sett the following option in the Atoll.ini file:
[Studies]
RemoveBadMultiCells = 0
11.1.7.7 Setting the Best Server Calculation Method in Same Priority HCS Layers
Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level received from
HCS
the serving transmitter must be higher than the minimum reception threshold ( T Rec ) for its HSC layer.
• 1st strategy: The serving transmitter is the one for which the difference between the received signal level and T HCS
Rec
[Studies]
UseThresholdForSameLayerPriorities = 0
205
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[AFP]
SimpleUserGUI = 1
SimpleUserGUI is set to 0 by default. When set to 1, the Interference Matrices, Finalisation, and Advanced tabs are hidden.
[AFP]
HideHopping = 1
HideHopping is set to 0 by default. When set to 1, the HSN tab, the MAL tab, and the MAIO frame on the Reuse tab are hidden.
11.1.7.10 Hiding Violations from Low Importance GSM Neighbours in AFP Results
By default, each neighbour pair has an importance value which defines the quality (and the rank) of the neighbour link. This
importance can be evaluated during the automatic neighbour allocation, a specific calculation process or manually populated
in the neighbour tables. In the Allocation tab of the AFP results dialog box, no difference is made between high and low
importance neighbours in term of violation display. In other words, whatever the importance value is, any neighbour link in a
separation violation is systematically displayed in a specific colour. You can avoid displaying separation violations between
low importance neighbours in a specific colour by adding the following lines to the Atoll.ini file:
[GSM]
MinNeighbourImportanceInAFPResults = XX
Where XX is the minimum importance for a neighbour pair to be considered as potentially violated.
The value in the Atoll.ini file has to be between 0 and 100 whereas the importance value
in the neighbours tables is between 0 and 1.
CoRedColorThreshPercent (for co-channels) and AdjRedColorThreshPercent (for adjacent channels) are set to 12 and 15 by
default. You can modify these thresholds to any value from 0 to 999.
206
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
Setting CoRedColorThreshPercent and/or AdjRedColorThreshPercent to 0 will force the behaviour of previous versions of
Atoll where important and less important violations were both highlighted.
WorstCaseIM_FskAfp is set to 1 by default (corresponding to the Worst Case Method) and is only valid for Forsk’s AFP.
When set to 0, the First Value Method is used.
• Worst Case Method: For each interference matrix relationship, the worst case value in all the active interference
matrices is taken into consideration.
• First Value Method: For each interference matrix relationship, the first value found in any active interference matrix
is taken into consideration. The order in which the interference matrices are scanned to find the first value is the order
of the interference matrices in the Interference Matrices folder in the Network tab, i.e. the first IM is the one on top.
• The First Value Method was the default method in previous versions of Atoll.
That allowed multiple interference matrix imports.
[AFP]
GlobalDistanceMatrixDegreeUB = 70
[AFP]
MaxNumberofSeparations = 21
The redundant fields in the Transmitters table are the BCCH and the Number of TRXs fields.
CanEditTRXInfoAtTXLevel is set to 1 by default, which means that the fields are editable.
207
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
FirstTRXIndex is set to 0 by default. Setting it to any other value has the same effect as FirstTRXIndex = 1.
[GSM]
TRXIndexHidden = 1
[GSM]
SortSubcellsAlphabetically = 1
208
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
If you wish to modify this default behaviour, add the following lines to the Atoll.ini file:
[GSM]
SubcellValueFixMethod = 1
SubcellValueFixMethod is set to 0 by default, which corresponds to the default behaviour described above.
If you set this parameter to 1, the values currently out-of-range are shifted to the closest boundary of the authorised range.
For example if the reception threshold is less than -116 dBm, it will be replaced by -116 dBm instead of -102 dBm as in the
default behaviour. Likewise, if it is greater than -50 dBm, it will be replaced by -50 dBm instead of -102 dBm.
[3GCells]
NoSuffixIfUniqueCarrier = 0 or 1
This is set to 0 by default, which means that cell names will follow the normal convention of Atoll, SiteN_X(C). If there is only
one carrier, meaning that C is unique, then this option can be set to 1. This will result in cell names which will be same as the
transmitter names, SiteN_X.
11.1.8.2 Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt
In UMTS HSPA and CDMA2000 documents, macro-diversity gains are calculated by default for pilot Ec/Io, DL and UL Eb/Nt
based on their respective standard deviations.
You can deactivate the calculation and use of macro-diversity gains for all of the above by adding this option in the Atoll.ini file:
[Shadowing]
WithSHOGain = 0
[CDMA]
AddPilotSHOGain = 0
[CDMA]
HSDPAThroughputPeak = 0 or 1
209
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
• Display the average HSDPA throughput per user in the Cells tab of the simulation results.
HSDPA resource scheduling will not be carried out. The HSDPA throughput for each user will be calculated by taking into
account the MUG corresponding to the current number of connected HSDPA users.
In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations where no
HSDPA users were served. To do this, add the following lines to the Atoll.ini file:
[CDMA]
HSDPAAvgSimuResults = 1
HSDPAAvgSimuResults = 0 by default.
[CDMA]
UseStudyCnxProba = 1
MinUsersPerBin = X
This coverage prediction study is available in the list of prediction studies if UseStudyCnxProba is set to 1. Otherwise, it will
not be available. MinUsersPerBin is the minimum number of users per pixel required for that pixel to be taken into account
in the coverage prediction.
[CDMA]
CQIDeltaWithPower = 0 or 1
CQIDeltaWithPower is set to 1 by default. In this case, the HS-PDSCH CQI is calculated using the formula:
CQI HS – PDSCH = CQI pilot – P pilot + P HS – PDSCH
If you set CQIDeltaWithPower to 0, the HS-PDSCH CQI will be calculated using the formula:
EC EC
CQI HS – PDSCH = CQI pilot – ------- + -------
N T pilot N T HS – PDSCH
Note that the default configuration (CQIDeltaWithPower set to 1) is relevant only when N T is calculated using the "Total
Noise" option.
The above equations are in dB. Refer to the Technical Reference Guide for more details.
210
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[CDMA]
OrthoInCPICH = 1
[CDMA]
MaxRejections = X
If a mobile is rejected X number of times, it will no longer be considered in the next iterations.
Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the
simulation.
[CDMA]
CutOffSimu = X
Where, X is the offset value in dBs. During Monte Carlo simulations, calculations performed on each mobile only take into
account the cells whose received power, at the mobile location, is greater than the thermal noise minus this offset. You should
set CutOffSimu to 20 dB for optimum performance without losing a lot of interference.
The primitive libraries, which perform the conversion from vector to raster, deal in terms of float values for the x and y
coordinates of the vector polygons. Since these are float values, you will have to create vector polygons with the exact
(accurate to all the decimal places) size of a pixel (or multiples of a pixel) in order to get raster pixels with the exact same
surface area as the vector polygons. If the coordinates of the vector polygons are not accurate, it is possible that the raster
pixel found from the vector polygon will be shifted 1 bin to the right or to the left.
211
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
Such a rasterisation means that the number of users in the vector remains correct, but the density might be different since
the surface area has changed (Number of users = User Density x Area).
If you want Atoll to increase the precision of the rasterisation process for hotspots in your network. You can add the following
lines to the Atoll.ini file:
[Rasterization]
Improve = 0 or 1
Precision = 1
SurfRatio = 20
MaximumSurf = 2500
• SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is smaller than
20 times the size of the normal raster bin. The normal raster bin size in anAtoll document is the finest resolution
among the geographic data available in the document.
If your Atoll document contains two geographic data files, one with a 20 m resolution and
the other with a 5 m resolution, and you remove the 5 m one from your document, Atoll
will still keep 5 m as the normal raster bin size.
• MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less than or
equal to 2500 sq. m.
So, a polygon will be considered small, and will be rasterised using the accurate algorithm, if either the ratio of its surface area
to the surface area of the normal raster bin is equal to or less than SurfRatio, or if its surface area is less than MaximumSurf.
If you want to use just the MaximumSurf option, you can set the SurfRatio to 0.
[CDMA]
PFSchedulerCQIFactor = X
Where X is a number between 0 and 100, which represents the proportional fair scheduler weight. PFSchedulerCQIFactor =
50 by default. If you set PFSchedulerCQIFactor = 0, the proportional fair scheduler functions like the Round Robin scheduler.
If you set PFSchedulerCQIFactor = 100, the proportional fair scheduler functions like the Max C/I scheduler.
212
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[CDMA]
DisplayEcIoOfRejected = 1
11.1.8.16 Switching Back to the Old Radio Bearer Allocation Algorithm for Multi-
carrier EVDO Rev.B
Before Atoll 3.2.1, radio bearer allocation for multi-carrier EVDO Rev.B used to be performed by equally sharing the available
terminal power between the carriers.
To switch back to this radio bearer allocation method, add the following lines to the Atoll.ini file:
[CDMA]
SharingEquallyPower = 1
UsingPreviousIterationPowerWeight = 1
[PSC]
DisplayCostValues = 1
213
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[PSC]
ConstantStep = 1
[Neighbours]
CompressModeEval = 1
[Studies]
SCActivesetMaxSize = X
Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get the same
results in the coverage prediction as the SC Interference tab in the point analysis.
214
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
11.1.8.23 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise
Estimation
In UMTS HSPA simulations, Atoll assumes a constant uplink reuse factor for estimating the maximum available noise rise per
HSUPA user. This can cause unnecessary rejection of some HSUPA users in very low traffic cases. You can set an upper limit
for the uplink reuse factor by adding the following lines to the Atoll.ini file:
[UMTSSimus]
MaxReuseFactor = value
Atoll can calculate HSUPA-results for a single user by adding the following lines to the Atoll.ini file:
[UMTS]
HSUPA_users_sharing_resource = 0
In this case, the entire remaining load of the cell is allocated to a single HSUPA bearer user.
HSUPA_users_sharing_resource is set to 1 by default.
By default, ModifiableIEEEParams is set to 1, which means that all the parameters are modifiable. When you set
ModifiableIEEEParams to 0, it means that the following parameters will be unmodifiable in the GUI:
• In the Permutation Zones table: Number of Used Subcarriers, Number of Data Subcarriers, and Number of
Subchannels per Channel.
• In the Permutation Zones table: Subchannel Groups (Segment 0), Subchannel Groups (Segment 1), and Subchannel
Groups (Segment 2) for FFT sizes < 1000.
In the Permutation Zones table, the first DL PUSC permutation zone cannot be
deactivated.
• In the Frame Configurations table and in the General tab of the frame configurations Properties dialog box:
Number of Preamble Subcarriers.
In the Frames Configurations table, the cells under Total Number of Subcarriers change
into combo boxes with the following five values: 128, 256, 512, 1024, 2048.
11.1.9.2 Using Only Bearers Common Between the Terminal’s and Cell’s
Equipment
If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal equipment,
add the following lines to the Atoll.ini file:
[OFDM]
UseCommonBearersOnly = 1
215
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for
which selection thresholds are defined in both the terminal’s and the cell’s equipment for both downlink and uplink bearer
selection.
[LTE]
DisplaySignalsPerSCInPtA = 1
DisplaySignalsPerSCInPtA is set to 0 by default. When the DisplaySignalsPerSCInPtA option is set to "0" or is absent, SS & PBCH
per subcarrier and PDCCH & PDSCH per subcarrier are not available options in a point analysis.
[LTE]
ExcludeCPFromUsefulPower = 0
11.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi-Fi Signal Level Calculation
The useful signal level calculation can exclude the energy corresponding to the cyclic prefix part of the total symbol duration,
hence taking into account only the energy belonging to the useful symbol duration. In order to do so, you must add the
following lines to the Atoll.ini file:
[WiMAX]
ExcludeCPFromUsefulPower = 1
216
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
InterNeighbourIDCollisions = 0
[WiMAX]
ReplaceOPUSCwithPUSCUL = 1
11.1.9.11 Excluding the Adjacent Channel Overlap from the AFP Cost Functions
The LTE, WiMAX, and Wi-Fi AFPs take the adjacent channel overlap into account for allocation frequencies, physical cell IDs,
preamble indexes, and other resources. If you wish to take only the co-channel overlap into account and exclude the effect of
adjacent channel overlap in resource allocation, add the following lines to the Atoll.ini file:
[OFDM_AFP]
AdjacentProtection = 0
Synchronised transmission and reception means that OFDM symbols of the interfered and interfering frames overlap
and match each other in time.
217
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
This method is also used to calculate interference received from LTE cells of an external network in co-planning and
multi-RAT modes, i.e. inter-technology interference received from LTE cells calculated using inter-technology IRFs.
ApplyDLLoadOnPDCCHInterf is set to 1 by default. Using SameItf_PDSCH_RS_PDCCH = 1, Atoll calculates a single total noise
(I+N) value for the RS, PDCCH, and PDSCH containing interference from the RS, PDCCH, and PDSCH. Within this combined total
noise (I+N) value, the ApplyDLLoadOnPDCCHInterf option only impacts the interference component from the PDCCH. The RS
and PDSCH interference components are calculated as usual.
For more information on SameItf_PDSCH_RS_PDCCH, see "Synchronised/Unsynchronised LTE Downlink Interference
Calculation" on page 217 and the Technical Reference Guide.
EIRPfromRSEPRE is set to 0 by default. This option applies to Coverage by Transmitter, Coverage by Signal Level, and
Overlapping Zones predictions in LTE.
[OFDM_SIMU]
MeanNRInDB = 1
[LTE]
ServiceMBRDowngrading = 0
ServiceMBRDowngrading is set to 1 by default. The above does not apply to LTE-A mobiles performing carrier aggregation or
downlink non-coherent joint transmission CoMP.
218
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[OFDM]
DisplayThroughputZero = 1
Positive values of NR_CONTROL_MARGIN_MIN are considered as negative margins. For example, X is interpreted by Atoll as
-X dB. NR_CONTROL_MARGIN_MIN is set to 1 by default, interpreted as -1 dB.
If you wish to include the uplink noise rise control in the simulation convergence criteria, you can change the uplink noise rise
control method from best effort to strict by setting the following option in the Atoll.ini file:
[LTE]
ULNRControlMethod = 1
[LTE]
ULNRControlPrecision = X
Integer values of ULNRControlPrecision are considered as tenths of dB. For example, X is interpreted by Atoll as 0.X dB.
ULNRControlPrecision is set to 5 by default, interpreted as 0.5 dB.
By default, UseABSonCellEdgeOnly is set to 0. Applying the ABS patterns only on the cell-edge means that all subframes are
considered non-ABS subframes in the cell centre. This method enables you to include the cell-edge traffic ratio in the
calculation of interference.
219
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[LTE]
CAWithinENB = 0
If you wish to manage groups of cells that can perform carrier aggregation with each other, you can do so by adding the follow-
ing lines to the Atoll.ini file:
[LTE]
CAWithinENB = 2
CAWithinENB is set to 1 by default. For more information on managing carrier aggregation groups, see the User Manual.
[GOB_MODEL]
DisplayLinearDiagram = 0
220
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
CellEdgeMethod is set to 0 by default. For calculating the cell-edge regions for CoMP, if CellEdgeMethod is set to 1, Atoll
compares the difference between the RSRP from the best server and the second best server belonging to the same CoMP set
with the cell edge margin defined for the best server.
[LTE]
FilterUsedGroups = 1
CandidatePrachRsiListsWithOverlap is set to 1 by default. This option is also taken into account by the audit.
Note that setting this option to 0 reduces the number of available resources for allocation, reduces the AFP search space, and
may result in an allocation plan with many full collisions between PRACH RSI lists. CandidatePrachRsiListsWithOverlap set to
0 may provide better allocation results when the number of cells to allocate is less than the number of available resources.
[LTE]
ApplyDMRSOverhead = 1
221
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
For example, if AutoNameForbiddenChars is set to "_ ", any new link will be named "SiteName123-SiteName345" instead of
"Site_Name 123-Site_Name 345".
AutoNameForbiddenChars is set to "" by default, meaning that no characters are forbidden.
222
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
ShieldingFactorOnWantedSignal is set to 1 by default, which means that the shielding factor is taken into account at the
receiver when calculating interference. On the transmitter side, the shielding factor is always taken into account when
calculating interference.
CCDP_XPIF is set to 0 by default, which means that XPIF is considered in the decoupling calculation only. When the option is
set to 1, the XPIF value is considered in the decoupling and it is deducted from the interference level.
HIDE_REC-5 is set to 1 by default. If the method was selected in a document saved in a previous Atoll version, it will be
available even if HIDE_REC-5 is set to 1 in the Atoll.ini file.
[Compatibility]
MWEquipment_CIMIN = 1
Where each of the above options corresponds to a specific Report Configuration dialog box:
• DesignSummaryCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button ( ) from the Design Summary view (MW Analysis window).
223
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
• LinkAnalysisCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Analysis Report view (MW Analysis window).
• LinkInterferenceCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Interference Report view (MW Analysis window).
• RequiredMarginCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Required Margin view (MW Analysis window).
• LinksBudgetCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio Links
> Links > Link Budgets > Configuration Report from the Network explorer.
• LinksInterferenceCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio
Links > Links > Interference > Configuration Report from the Network explorer.
• MultihopAnalysisCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio
Links > Multi-Hops > [Multi-Hop X] > Analysis from the Network explorer.
• ReflectionAnalysisCfg: corresponds to the Report Configuration dialog box displayed after:
• right-clicking in the Profile Analysis view (MW Analysis window) and selecting Reflection and Diversity Analysis,
• then clicking the Configure Report button from the Analysis Report view (MW Reflection/Diversity window).
Where the above option corresponds to the Channel Arrangement dialog box displayed after selecting Microwave Radio
Links > Interference > Channel Arrangement > Display on Map from the Network explorer.
224
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[MWCalculations]
NewDecouplingCoSite = 0
11.1.12.2 Setting the Number of Transmitters per Drive Test Data Path
By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six neighbour
transmitters (or cells in CDMA documents) for drive test data paths. You can change the number of transmitters per drive test
data path by adding the following lines to the Atoll.ini file:
[TestMobileData]
NumberOfTestMobileTransmitters = X
Where X is the number of transmitters per drive test data path. The default value of NumberOfTestMobileTransmitters is 7.
[TestMobileData]
RecalcDist = 1 or 0
The default value of RecalcDist is 1, which means that Atoll will calculate the distance for each measurement point. The
nearest serving cell is the one closest to the measurement point which has the same (Scrambling Code, SC Group), (BSIC,
BCCH), or (PN Offset, PN Offset Group) pair as the point.
11.1.12.4 Defining the BCCH and BSIC Columns for FMT Import
The .fmt files generated by the TEMS Investigation GSM tool contain a number of columns. To define which of these columns
should be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the following lines to the
Atoll.ini file:
[TestMobileDataImportFmt]
BCCHColumn = Column1
BSICColumn = Column2
Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the BSIC
columns respectively.
225
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
FloatingPointScramblingCodeSupport is set to 0 by default, and the scrambling codes are imported according to the numeric
data type selected for the scrambling code column in the import dialog box.
11.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only
When you import drive test data in Atoll, it assigns servers and neighbours to each measurement point based on the cell
identification method defined for the import. By default, Atoll takes all the transmitters and cells of the document into
account, whether they are active or inactive and filtered or not. If you want Atoll to take only active and filtered transmitters
and cells into account for drive test data import, add the following option in the Atoll.ini file:
[TestMobileData]
ImportForFilteredTransmittersOnly = 1
The ACP initialisation file is a powerful tool. You should not modify any option in the
ACP.ini file until and unless you are absolutely sure of what you are doing.
In order for the ACP initialisation file to be used by Atoll, you should place the ACP.ini file in the Atoll installation directory.
You can define a different location for the ACP.ini file as shown in "Specifying the Location of the ACP.ini File" on page 226.
• The local settings, defined using the ACP - Automatic Cell Planning Properties
dialog box, take precedence over the same settings defined in the global ACP.ini
file. The settings in the ACP.ini file are read when you start a new project to
initialise the settings of the ACP.
• When using the ACP.ini file to define options, instead of using the ACP -
Automatic Cell Planning Properties dialog box, you can also define any other
settings even if they can not be set using the ACP - Automatic Cell Planning
Properties dialog box. These settings redefined locally have precedence over the
global settings.
226
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ACPTplGeneralPage]
nbIteration = 100
resolution = 50
[ACPTplGeneralPage]
cost.type = 0|1|2
# 0=off, 1=limt to max, 2=apply cost to change plan
cost.unit = unit
# unit = $, yen, etc. (less than 4 characters recommended)
cost.tradeoffLevel = 0|1|2
# 0=low, 1 = normal, 2=strong
cost.maxCost = 50
cost.azimuth.cost = 1
cost.azimuth.isSiteVisit=true
cost.tilt.cost = 1
cost.tilt.isSiteVisit=true
cost.antenna.cost = 1
cost.antenna.isSiteVisit=true
cost.etilt.cost = 0.1
cost.etilt.isSiteVisit=false
cost.height.cost = 1
cost.height.isSiteVisit=true
cost.power.cost = 0.1
cost.power.isSiteVisit=false
cost.siteVisitCost = 2
cost.upgradeSiteCost = 5
cost.newSiteCost = 10
cost.removeSiteCost = -5
11.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab
The following options can be used to define the default settings for advanced cost control. Advanced cost control options
allow you to define the maximum number of changes to be made (either as a value or a ratio) and to change the ranking of
the order of cost in the final implementation plan.
The option below allows you to display the Advanced label under Cost Control in the left-hand pane of the Optimisation tab.
It is set to 0 by default.
[ACPGeneralPage]
enableAdvancedCost = 1
The following option enables you to define the importance of cost in the implementation plan. It is set to 1 by default.
[ACPTplGeneralPage]
227
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
cost.planCostWeighting = 0|1|2
#0=low, 1=medium (default), 2=high
The following option enables you to specify the number of changes in the implementation plan. It is set to 0 by default.
[ACPTplGeneralPage]
cost.planLimitType = 0|1|2
#0=unlimited, 1=max as absolute value, 2=max as ratio
• 2: use cost.planChangePercent to define the max. number of changes in the implementation plan as a ratio of the
number of antennas currently available in the computation zone:
cost.planChangePercent = 20
When cost.planLimitType is set to 2, you can also set cost.planChangeRefZone to 1 in the [ACPGeneralPage] section
to define the focus zone as the reference zone instead of the computation zone:
cost.planChangeRefZone = 0|1
#0=computation zone (default), 1=focus zone
The following options can be used to automatically create ACP custom zones from one or more clutter classes or from a SHP
file:
[ACPGeneralPage]
zone.count = 2
# Number of zones to be created.
zone.0.name = MyClutterZone1
# Name of the zone (in this case from clutter)
zone.0.clutters = 10,11,12
# Clutter classes that will constitute this zone
zone.1.name = MyVectorZone2
# Name of the zone (in this case from SHP)
zone.1.file=c:\path\to\file.shp
# Absolute path to the SHP file.
[ACPTplObjectivePage]
traffic.global.file = "C:\tmp\traffic.bil"
The following option can be used to define the default extraction resolution of the traffic map (in metres). It is set to 50 by
default.
[ACPTplObjectivePage]
traffic.global.resolution = value
228
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
The following options can be used to define the default values for the technology quality indicators (UMTS Ec/Io, UMTS RSCP,
UMTS overlap, GSM signal level, GSM overlap, WiMAX CINR, WiMAX C/N, LTE C/N, etc.):
[ACPTplObjectivePage]
param.gsm.overlap.autoPrediction = yes
param.gsm.overlap.margin = 5
param.gsm.overlap.minRxLevel = 0
# 0=use defined TRG threshold, other=defined value
param.gsm.bcch.autoPrediction = yes
param.gsm.bcch.isShadowing = no
param.gsm.bcch.cellEdgeCov = 0.75
param.umts.overlap.autoPrediction = yes
param.umts.overlap.margin = 10
param.umts.overlap.minRxLevel = -120
param.umts.rscp.autoPrediction = yes
param.umts.rscp.isShadowing = no
param.umts.rscp.cellEdgeCov = 0.75
param.umts.ecio.autoPrediction = yes
param.umts.ecio.isShadowing = no
param.umts.ecio.cellEdgeCov = 0.75
param.cdma.overlap.autoPrediction = yes
param.cdma.overlap.margin = 10
param.cdma.overlap.minRxLevel = -120
param.cdma.coverage.autoPrediction = yes
param.cdma.coverage.isShadowing = no
param.cdma.coverage.cellEdgeCov = 0.75
param.cdma.ecio.autoPrediction = yes
param.cdma.ecio.isShadowing = no
param.cdma.ecio.cellEdgeCov = 0.75
param.lte.overlap.autoPrediction = yes
param.lte.overlap.margin = 5
param.lte.overlap.minRxLevel = -105
param.lte.coverage.autoPrediction = yes
param.lte.coverage.isShadowing = no
param.lte.coverage.cellEdgeCov = 0.75
param.lte.cinr.autoPrediction = yes
param.lte.cinr.isShadowing = no
param.lte.cinr.cellEdgeCov = 0.75
param.lte.cinr.useFreqBand = 1
param.lte.cinr.useICIC = 1
param.wimax.overlap.autoPrediction = yes
param.wimax.overlap.margin = 5
param.wimax.overlap.minRxLevel = -105
param.wimax.coverage.autoPrediction = yes
param.wimax.coverage.isShadowing = no
param.wimax.coverage.cellEdgeCov = 0.75
param.wimax.cinr.autoPrediction = yes
param.wimax.cinr.isShadowing = no
param.wimax.cinr.cellEdgeCov = 0.75
param.wimax.cinr.useFreqBand = 1
param.wimax.cinr.useSegmentation = 1
param.wifi.overlap.autoPrediction = yes
param.wifi.overlap.margin = 5
param.wifi.overlap.minRxLevel = -105
param.wifi.coverage.autoPrediction = yes
param.wifi.coverage.isShadowing = no
param.wifi.coverage.cellEdgeCov = 0.75
param.wifi.cinr.autoPrediction = yes
param.wifi.cinr.isShadowing = no
param.wifi.cinr.cellEdgeCov = 0.75
The following options can be used to define the default threshold for each objective rule:
[ACPTplObjectivePage]
229
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
quality.gsm.bcch.threshold = -85
quality.gsm.overlap.threshold = 4
quality.gsm.distance.threshold = 5000
quality.umts.rscp.threshold = -85
quality.umts.ecio.threshold = -13
quality.umts.overlap.threshold = 4
quality.umts.distance.threshold = 5000
quality.cdma.rscp.threshold = -85
quality.cdma.ecio.threshold = -13
quality.cdma.overlap.threshold = 4
quality.cdma.distance.threshold = 5000
quality.lte.coverage.threshold = -85
quality.lte.c.threshold = -85
quality.lte.cn.threshold = 20
quality.lte.rsrp.threshold = -105
quality.lte.cinr.threshold = 10
quality.lte.rsrq.threshold = -12
quality.lte.rssi.threshold = -80
quality.lte.overlap.threshold = 5
quality.lte.distance.threshold = 5000
quality.wimax.coverage.threshold = -85
quality.wimax.c.threshold = -85
quality.wimax.cn.threshold = 20
quality.wimax.cinr.threshold = 10
quality.wimax.overlap.threshold = 5
quality.wimax.distance.threshold = 5000
quality.wifi.coverage.threshold = -85
quality.wifi.c.threshold = -85
quality.wifi.cn.threshold = 20
quality.wifi.cinr.threshold = 10
quality.wifi.overlap.threshold = 5
quality.wifi.distance.threshold = 5000
quality.lpwa.coverage.threshold = -130
quality.lpwa.redserver.threshold = 3
The following option can be used to define a default number of servers for the 1st-Nth objective. It is set to 4 by default.
[ACPTplObjectivePage]
NbServers1stNth = value
The following option can be used to remove the Capacity and Load Balancing features from the Objectives tab.
[ACPCapacityPage]
enable = 0
The following option can be used to clear the Scale Traffic according to Zone Weighting check box on the Capacity page:
[ACPCapacityPage]
useZoneWeight = 0
The following options can be used to define a capacity traffic map, either by a BIL file or by a comma-separated list of traffic
map names:
[ACPTplCapacityPage]
traffic.file = c:\tmp\traffic.bil
traffic.maps = user_density_traffic_map; environment_map
traffic.resolution = 50
The following option can be used to avoid recalculating capacity traffic maps after each new run:
[ACPTplCapacityPage]
calculationcapacitytrafficmap = 1
230
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
The following option can be used to force ACP to show load balancing and traffic capture results when either feature is
enabled:
[ACPTplCapacityPage]
show.loadbalancingandthroughput = 1
The following options can be used to define the default threshold for each quality (Objectives tab > Capacity page > Services
Definition frame):
[ACPTplCapacityPage]
quality.gsm.bcch.threshold = -85
quality.umts.rscp.threshold = -85
quality.umts.ecio.threshold = -13
quality.cdma.rscp.threshold = -85
quality.cdma.ecio.threshold = -13
quality.wimax.coverage.threshold = -85
quality.wimax.c.threshold = -85
quality.wimax.cn.threshold = 20
quality.wimax.cinr.threshold=10
quality.lte.coverage.threshold = -85
quality.lte.c.threshold = -85
quality.lte.cn.threshold = 20
quality.lte.rsrp.threshold = -105
quality.lte.cinr.threshold=10
quality.lte.rsrq.threshold = -12
quality.lte.rssi.threshold = -80
The following options can be used to define the default quality used by each technology for traffic capture condition:
[ACPTplCapacityPage]
service.gsm.condition.quality=bcch
service.umts.condition.quality=rscp
service.cdma.condition.quality=coverage
service.wimax.condition.quality=coverage
service.lte.condition.quality=coverage
service.factor=1.0
service.density = 30
The following option can be used to enable the load balancing feature by default:
[ACPTplCapacityPage]
loadBalancing.enable = 1
The following options can be used to specify the load balancing default target coverage (%) and the load balancing weight:
[ACPTplCapacityPage]
loadBalancing.target = 80
loadBalancing.weight = 1
The options in this section do not select the default reconfiguration options when set to
"1", instead they disable those reconfiguration options.
By default, all the zones listed under Zone Parameters on the Optimisation > Zones tab appear in the drop-down list next to
Display on on the Reconfiguration tab (except the KPI zones and lines). You can force ACP to list only the main zones
("Computation", "Focus", "All") in both drop-down lists by adding the following lines to the ACP.ini file:
231
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[ACPReconfPage]
filter.onlyMainZones = 1
[ACPTplReconfPage]
umts.disablePilotPowerOptimisation = 1
umts.disableMaxPowerOptimisation = 1
umts.SyncMultiCellPower = 1
umts.SyncSiteMultiCellPower = 1
# lock UMTS cell power optimisation for co-site cells
umts.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
cdma.1xrtt.SyncMultiCellPower = 1
cdma.1xrtt.SyncSiteMultiCellPower = 0
cdma.1xrtt.disablePilotPowerOptimisation = 1
cdma.1xrtt.disableMaxPowerOptimisation = 1
cdma.1xevdo.SyncMultiCellPower = 1
cdma.1xevdo.SyncSiteMultiCellPower = 0
cdma.1xevdo.disableMaxPowerOptimisation = 1
cdma.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
gsm.disablePowerOptimisation = 1
gsm.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
wimax.disablePreamblePowerOptimisation=1
wimax.SyncMultiCellPower = 1
wimax.SyncSiteMultiCellPower = 1
# lock WiMAX cell power optimisation for co-site cells
wimax.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
lte.disablePowerOptimisation = 1
lte.SyncMultiCellPower = 1
lte.SyncSiteMultiCellPower = 1
# lock LTE cell power optimisation for co-site cells
lte.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
The following options can be used to define the default settings for the reconfiguration of transmitters and sites:
[ACPTplReconfPage]
disableAntennaOptimisation = 1
disableAzimuthOptimisation = 1
disableHeightOptimisation = 1
disableETiltOptimisation = 1
disableMechTiltOptimisation = 1
disableSiteSelection = 1
disableRepGainOptimisation = 1
disableCandidateSelection = 1
The following options can be used to define default settings for reconfiguration ranges:
[ACPTplReconfPage]
defaultTxAzimuthVariation = 20
defaultTxAzimuthStep = 5
232
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
defaultTxAzimuthMinInterSector = 0
defaultTxTiltMin = 0
defaultTxTiltMax = 5
defaultTxTiltStep = 1
defaultTxETiltMin = 0
defaultTxETiltMax = 10
defaultTxHeightMin = 0
defaultTxHeightMax = 10
defaultTxHeightStep = 5
defaultTxHeightMin.feet = 0
defaultTxHeightMax.feet = 30
defaultTxHeightStep.feet = 15
umts.disablePilotPowerOptimisation = 0
umts.disableMaxPowerOptimisation = 0
The following options can be used to define a default range for the optimisation of repeater gains:
[ACPTplReconfPage]
defaultRepGainMin = -1
# if -1, the default equipment min value is used
defaultRepGainMax = -1
# if -1, the default equipment max value is used
defaultRepGainStep = 3
# default = 3
The following option can be used to hide the No. Remotes column on the Reconfiguration > Transmitters vertical tab:
[ACPReconfPage]
showNbRemotes = 0
#default = 1 to display the No. Remotes column
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional constraint
applied to electrical tilt changes.
[ACPReconfPage]
tx.etilt.deltaLimitConstraint.show = 1
#default = 0
When tx.etilt.deltaLimitConstraint.show = 1, the Variation + column appears under Electrical Tilt (deg). You can enter
a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.deltaLimitConstraint = 1,2,...
#default = 0
• If etilt.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
• If etilt.deltaLimitConstraint = 1,2,..., the constraint is enabled and the following appears under Variation +:
• A check box which must be selected in order for the constraint to be considered.
• A range determined by the value under Current and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final electrical tilt will fall within the intersection of the two ranges.
You can use the following option to disable proposals for electrical tilt changes below a defined relative variation.
E.g. to disable electrical tilt change proposals for relative variations of 1 degree, you should set this option to 2.
[ACPTplReconfPage]
etilt.relative.min.variation = 2
#default = 1
233
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional constraint
applied to mechanical tilt changes.
[ACPReconfPage]
tx.tilt.deltaLimitConstraint.show = 1
#default = 0
When tx.tilt.deltaLimitConstraint.show = 1, the Variation + column appears under Mechanical Tilt (deg).
You can enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
tilt.deltaLimitConstraint = 1,2,...
#default = 0
• If tilt.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
• If tilt.deltaLimitConstraint = 1,2,..., the constraint is enabled and the following appears under Variation +:
• A check box which must be selected in order for the constraint to be considered.
• A range determined by the value under Current and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final mechanical tilt will fall within the intersection of the two ranges.
You can use the following option to disable proposals for mechanical tilt changes below a defined relative variation.
E.g. to disable mechanical tilt change proposals for relative variations of 1 degree, you should set this option to 2.
[ACPTplReconfPage]
tilt.relative.min.variation = 2
#default = 1
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional constraint
applied to global tilt changes (electrical + mechanical).
[ACPReconfPage]
tx.etilt.tilt.sum.deltaLimitConstraint.show = 1
#(Default = 0)
When tx.etilt.tilt.sum.deltaLimitConstraint.show=1, ETilt + MTilt (deg) appears with Current and Variation + columns.
You can enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.tilt.sum.deltaLimitConstraint = 1|2|...
#(Default = 0)
• If etilt.tilt.sum.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
• If etilt.tilt.sum.deltaLimitConstraint = 1,2,etc., the constraint is enabled and this appears under Variation +:
• A check box which must be selected in order for the constraint to be considered.
• A range determined by the value under Current (sum of the values under Current for electrical and mechanical
tilts) and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final gloabl tilt will fall within the intersection of the two ranges.
The final mechanical tilt will fall within the intersection of the two ranges.
The following option allows you to reconfigure inter-sector electrical tilts as asymetrics, i.e. it allows you to obtain different
tilts for sectors belonging to the same site. The value you specify (in degree) is a "minimum difference" constraint if tilts are
reconfigured. If they are not reconfigured, the constraint will not apply.
[ACPTplReconfPage]
etilt.asymetric = 1
#(No default)
The following option can be used to automatically disable reconfiguration of all donors (possibly in cascade) of a repeater:
[ACPTplReconfPage]
autoLockDonor = 0
#(Default = 0)
234
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
Possible settings:
Value Description
0 No auto lock (default).
The Use check boxes for transmitter reconfiguration parameters are cleared (antenna, tilt,
1 azimuth, and height). Only the last repeater in a series of cascading repeaters is optimised; the rest
are cleared by default (but can be selected manually).
The Use check boxes for all reconfiguration parameters are cleared (antenna, tilt, azimuth, height,
2 and power). Only the last repeater in a series of cascading repeaters is optimised; the rest are
cleared by default (but can be selected manually).
5 Same as 1, except that the Use check boxes can not be selected in the user interface.
6 Same as 2, except that the Use check boxes can not be selected in the user interface.
[ACPTplReconfPage]
defaultSiteCellsRemoveable = 1
defaultSiteRemoveable = 1
defaultSiteAzimuthLocked = 1
#Lock Sector/Azimuth
defaultSiteHeightLocked = 1
#Lock Sector/Height
defaultSiteReconfigurationLocked = 1
[ACPTplReconfPage]
site.min.distance.colocated = 2
#default setting in metres
[ACPTplReconfPage]
tx.min.distance.colocated = 1
#default setting in metres
[ACPReconfPage]
site.custom.count=x
site.custom.0.type=tabularDataColumn
235
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
site.custom.0.column=FOO
Where ’tabularDataColumn’ displays data issued from Atoll’s SITES table and identified by site.custom.0.column (column
name). Atoll column names are case sensitive.
The option below defines an optional label for a given column. If unset, the Atoll column name is used (e.g. FOO):
[ACPReconfPage]
site.custom.0.label=The Foo Label
The following option can be used to display the minimum and maximum electrical tilts only once for each group of linked
transmitters, when the Advanced mode is selected for display.
[ACPReconfPage]
tx.etilt.groupMinMax = 1 (default = 1)
When tx.etilt.groupMinMax is set to 0, the min/max electrical tilts are displayed for each transmitter.
[ACPReconfPage]
tx.custom.count = 2
You can then set the following options to specify the data you want to show under each custom column.
tx.custom.0.type=tabularDataColumn
tx.custom.0.column=FOO
tx.custom.0.label=The FOO label
tx.custom.1.type=elevation
#site altitude + transmitter height
tx.custom.1.type=bandwidth
#cell bandwidth (only for LTE, WiMAX, and Wi-Fi)
[ACPTplEMFPage]
enable = 1
The following option enables you to define the level of importance accorded to the optimisation of EMF exposure.
236
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ACPTplEMFPage]
weightLevel = 1
#(normal, default)
Possible values:
Value Description
0 Low: EMF exposure is optimised only if does not worsen coverage quality.
1 Normal: There is a trade-off between EMF exposure and coverage quality (default).
2 Critical: EMF exposure is optimised independently from the effect it may have on coverage quality.
The following options enable you to define the default resolution in metres in the X, Y, and Z planes:
[ACPTplEMFPage]
resolutionXY = 5
resolutionZ = 3
The following options define how EMF exposure will be measured in buildings: only on the facade or inside the building as
well:
[ACPTplEMFPage]
onlyFacade=1
#only on facade in building propagation classes. Default = 1 (yes)
buildingDeeping=10
#if onlyFacade is set to 0, the depth in the building measured.
The following option defines whether clutter classes and clutter heights are used to create a 3D representation of the terrain
or whether just vectors are to be used. The default is 1 (yes), but, given that vectors are always given priority where they exist,
this option can be disabled if vectors are available for the entire area of interest.
[ACPTplEMFPage]
useDhmFromClutter=1
# Default is 1 (yes)
The following option defines whether the 3D propagation model is using diffraction. When it is not, only positions with a direct
LOS to transmitters will register EMF exposure.
[ACPTplEMFPage]
useDiffraction = 0
The following option defines whether the EMF module should use transparent mode. When transparent mode is used, no
obstacle or indoor loss is accounted for.
[ACPTplEMFPage]
isWorstCase = 0
# Default is 0 (no)
The following option defines the calculation radius (in metres) around transmitters when calculating EMF exposure:
[ACPTplEMFPage]
calculationRadius = 300
The following options define the default threshold and weight for the EMF exposure objective:
[ACPTplEMFPage]
defaultObjThreshold = 0.6
defaultObjWeight = 1
The following options enable you to define up to 16 propagation classes for EMF exposure. Each class is defined by a name,
an indoor loss, and whether it can be edited by the user.
[ACPTplEMFPage]
237
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
eclass.count = 2
# Total number of propagation classes defined.
eclass.0.name=Open
eclass.0.position = 0
# Distribution of measurement points:
# 0 = 3D, i.e., distribution at all heights over area, 1 = 2D on top, 2 = 2D on bottom
eclass.0.buildingLos = 0
eclass.0.linearBuildingLos = 0
eclass.0.linearBuildingStart = 0
eclass.0.editionFlag = 0
# 0 can not be edited by user
The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two lines: the first
line defines the clutter class (by its code from the Description tab of the Clutter Classes Properties dialog box); the second
line defines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialog box). The
default propagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and "Building" (ID "2"). Any additional
propagation classes will have an ID assigned when they are created.
[ACPTplEMFPage]
clutterMapping.count = 3
clutterMapping.0.clutterCode = 10
clutterMapping.0.classCode = 0
clutterMapping.1.clutterCode = 4
clutterMapping.1.classCode = 1
clutterMapping.2.clutterCode = 6
clutterMapping.2.classCode = 2
clutterMapping.3.clutterCode = 7
clutterMapping.3.classCode = 2
In the [ACPEMFPage] section, you can specify whether or not users can define new propagation classes:
[ACPEMFPage]
isPropClassesExtendable = 1
# 1 enables user to create propagation classes.
[ACPTplMultistoreyPage]
enable = 1
#default = 0
The following option can be used to define the minimum number of storeys for a building to be considered by the Multi-Storey
module. This is the value displayed next to Ignore buldings smaller than (storeys) on the Optimisation > Multi-Storey tab.
[ACPTplMultistoreyPage]
minHeight = value
#default = 3
The following option can be used to define the vertical calculation step in the number of storeys. This is the value displayed
next to Calculation step (storeys) on the Optimisation > Multi-Storey tab.
[ACPTplMultistoreyPage]
resStorey = value
#default = 3
The following options can be used to define the default storey height in metres (or in feet when Atoll is configured to use feet)
displayed next to Storey height on the Optimisation > Multi-Storey tab.
238
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ACPTplMultistoreyPage]
storeyHeight = value
#default = 3
storeyHeight.feet = value
#default=10
The following option can be used to define the traffic weighting method for pixels in storeys, i.e. weight inside buildings Vs.
weight outside buildings (when value = 1, the total weight for all indoor pixels is equal to the weight of an outdoor pixel). The
defined weighting method will only be considered when the Vertical weight sharing check box is selected.
[ACPTplMultistoreyPage]
weightShareMode = value
#default=1
where X is a value between 0 and 500 specified by AntennaLossesThreshold in Crosswave.ini to increase the specific threshold
applied by Crosswave.
[ACPAntennaPage]
autoGroupPattern=(.*)
#for example (.*18deg) or (.+18deg)
autoGroupPattern_ant=(.*)
autoGroupPattern_group=(.*)
When the following option is set to 1 (default), ACP applies the default antenna configuration automatically (i.e. the last
configuration backed up as default) each time a new setup is created:
[ACPTplAntennaPage]
autoRestoreDefaultConfig = 1
You can add the following lines to the ACP.ini file to enable the management of electrical tilt constraints on antenna patterns;
additional columns appear under Electrical Tilt Constraint (°). When the Use check box is selected, a electrical constraint will
be applied to the corresponding antenna pattern.
[ACPAntennaPage]
enableETilt = 1
# (default = 0)
You can also use the option below to enable management of AEDT (additional electrical downtilt); an additional Use AEDT
column appears. When a check box is selected under this column, an AEDT constraint will be applied to the corresponding
antenna pattern.
[ACPAntennaPage]
enableAedt = 1
When enableETilt and/or enableAEDT is set to 1, you can modify the Min and Max values that appear under Electrical Tilt
Constraint (°).
239
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[ACPTplAntennaPage]
defaultETiltMin = 0
#default = 0
defaultETiltMax = 10
#default = 10
You can use the following option if you want to use a regular expression to define a set of antenna patterns on which electrical
tilt constraints will be used automatically. As a result, the Use check box will be selected under Electrical Tilt Constraint (°)
and the defined electrical tilt constraints will appear under Min and Max.
[ACPTplAntennaPage]
autoUseEtiltFromRegex=(.*)
Conversely, you can use the autoDisableEtiltFromRegex option if you want to use a regular expression to define a set of
antenna patterns on which electrical tilt constraints will be disabled automatically. As a result, the Use check box is cleared
under Electrical Tilt Constraint (°) and a dash appears under Min and Max..
[ACPTplAntennaPage]
autoDisableEtiltFromRegex=(.*)
You can add the following lines to the ACP.ini file to enable the management of mechanical tilt constraints on antenna
patterns; additional columns appear under Mechanical Tilt Constraint (°). When the Use check box is selected, a mechanical
constraint will be applied to the corresponding antenna pattern.
[ACPAntennaPage]
enableMTilt = 1
#default = 0
When enableMTilt is set to 1, you can modify the Min and Max values that appear under Mechanical Tilt Constraint (°).
[ACPTplAntennaPage]
defaultTiltMin = 0
#default = 0
defaultTiltMax = 5
#default = 5
You can use the following option if you want to use a regular expression to define a set of antenna patterns on which
mechanical tilt constraints will be used automatically. As a result, the Use check box will be selected under Mechanical Tilt
Constraint (°) and the defined mechanical tilt constraints appear under Min and Max.
[ACPTplAntennaPage]
autoUseTiltFromRegex=(.*)
Conversely, you can use the autoDisableTiltFromRegex option if you want to use a regular expression to define a set of
antenna patterns on which mechanical tilt constraints will be disabled automatically. As a result, the Use check box is cleared
under Mechanical Tilt Constraint (°) and a dash appears under Min and Max.
[ACPTplAntennaPage]
autoDisableTiltFromRegex=(.*)
For physical antennas containing several antenna patterns with different electrical tilts, if you set the following option the Use
check box will be selected under Mechanical Tilt Constraint (deg) and a dash appears under Min and Max.
[ACPTplAntennaPage]
autoDisableTiltOnMultiPattern = 1
#default = 0
240
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
You can also add the following lines to the ACP.ini file if you want to activate electrical tilt sharing between merged physical
antennas when the frequency difference lies within a defined limit.
[ACPAntennaPage]
etiltShareFrequencyRange = 100
#default = 100 (MHz)
The following option can be used to allow "Optimised" propagation models (i.e., propagation models that use the "Optimised"
mode) to use "Full Path Loss" mode:
[ACPAntMaskModelPage]
nativeAllowFullPathLoss = 1
#default = 0 (disabled)
For external propagation models other than Aster that correctly implement the relevant API, the following option can be used
to force the default setting of "Antenna Masking Method" to "Antenna Correction":
[ACPAntMaskModelPage]
DefaultAntennaCorrection = 0
#default = 0
The relevant API interface must be implemented in order for the above option to work.
241
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
11.2.2.18.1 Defining Reconfiguration Values for Transmitters, Repeaters, and Secondary Antennas
Using Custom Fields
In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields in the
Transmitters, Repeaters, and Secondary Antennas tables of the Atoll database. This data will be used to initialise the
reconfiguration parameters of transmitters, repeaters, remote antennas, and secondary antennas in the corresponding
technology.
The custom columns in the Transmitters, Repeaters, Remotes, and Secondary Antennas tables of the Atoll platform must
match the column names defined in the ACP.ini file.
Some reconfiguration parameters such as height and azimuth can be defined either as
relative values (i.e., by defining the reconfiguration range starting from the current
value) or as absolute values. You therefore only need to define the settings relevant to
the value type (i.e., relative or absolute).
[ACPCustomFieldExtraction]
tx.antenna.optimize=acp_ant_use
#Best to define this column as a Boolean
tx.antenna.group=acp_ant_group
tx.etilt.optimize=acp_etilt_use
tx.etilt.min=acp_etilt_min
tx.etilt.max=acp_etilt_max
tx.etilt.deltamin=acp_etilt_deltamin
tx.etilt.deltamax=acp_etilt_deltamax
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.deltamin=acp_tilt_deltamin
tx.tilt.deltamax=acp_tilt_deltamax
tx.tilt.step=acp_tilt_step
tx.tilt.sum.optimize=acp_tilt_sum_use
tx.tilt.sum.delta=acp_tilt_sum_delta
tx.azimuth.optimize=acp_azim_use
#Relative values from current azimuth
tx.azimuth.deltamin=acp_azim_deltamin
tx.azimuth.deltamax=acp_azim_deltamax
tx.azimuth.min=acp_azim_min
#Absolute value for azimuth angle
tx.azimuth.max=acp_azim_max
tx.azimuth.step=acp_azim_step
tx.azimuth.minInterSector=acp_azim_inter
The following options are NOT valid for the SecondaryAntennas table.
[ACPCustomFieldExtraction]
tx.height.optimize=acp_height_use
tx.height.deltamin=acp_height_deltamin
#Relative values from current height
tx.height.deltamax=acp_height_deltamax
tx.height.min=acp_height_min
#Absolute value for height values
tx.height.max=acp_height_max
tx.height.step=acp_height_step
242
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
The following options are ONLY valid for the GSM Transmitters table.
In GSM, ACP extracts data from custom fields in the GSM Transmitters tables of the Atoll
database and displays it in ACP on the Reconfiguration > GSM Cells vertical tab.
[ACPCustomFieldExtraction]
tx.gsm.power.optimize=acp_gsmpower_use
tx.gsm.power.min=acp_gsmpower_min
tx.gsm.power.max=acp_gsmpower_max
tx.gsm.power.step=acp_gsmpower_step
The following options are ONLY valid for the Repeaters table.
[ACPCustomFieldExtraction]
repeater.gain.optimize=acp_gain_use
repeater.gain.min=acp_gain_min
repeater.gain.max=acp_gain_max
repeater.gain.step=acp_gain_step
In GSM, ACP extracts data from custom fields of the Transmitters table (not Cells table)
in the Atoll database and displays it in ACP on the Reconfiguration > GSM Cells vertical
tab. The relevant options are described in "Defining Reconfiguration Values for
Transmitters, Repeaters, and Secondary Antennas Using Custom Fields" on page 242.
The following options can be used to extract data from custom fields in the "CDMA2000 cells" table of the database. The
custom columns in the CDMA2000 Cells table of the Atoll platform must match the column names defined in the ACP.ini file.
[ACPCustomFieldExtraction]
ccell.pilotPower.optimize=acp_pilotpower_use
ccell.pilotPower.min=acp_pilotpower_min
ccell.pilotPower.max=acp_pilotpower_max
ccell.pilotPower.step=acp_pilotpower_step
ccell.maxPower.optimize=acp_maxpower_use
ccell.maxPower.min=acp_maxpower_min
ccell.maxPower.max=acp_maxpower_max
ccell.maxPower.step=acp_maxpower_step
The following options can be used to extract data from custom fields in the "UMTS cells" table of the database. The custom
columns in the UMTS Cells table of the Atoll platform must match the column names defined in the ACP.ini file.
[ACPCustomFieldExtraction]
wcell.power.optimize=acp_power_use
wcell.power.min=acp_power_min
wcell.power.max=acp_power_max
wcell.power.step=acp_power_step
The following options can be used to extract data from custom fields in the "LTE cells" table of the database. The custom
columns in the LTE Cells table of the Atoll platform must match the column names defined in the ACP.ini file.
[ACPCustomFieldExtraction]
lcell.power.optimize=acp_power_use
243
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
lcell.power.min=acp_power_min
lcell.power.max=acp_power_max
lcell.power.step=acp_power_step
[ACPCustomFieldExtraction]
site.status=acp_site_status
# Name of the custom column in Sites table.
# Default value is 'ACP_STATUS'.
site.gsm.status=acp_site_gsm_status
site.umts.status=acp_site_umts_status
site.lte.status=acp_site_lte_status
site.status.candidate=candidate
# Name used to define a candidate site.
The following options can be used to define custom columns in the Sites table of the Atoll platform. These will be used for
default reconfiguration options for each site.
[ACPCustomFieldExtraction]
site.disableSelection=acp_site_disableSelection
site.gsm.disableSelection=acp_site_gsm_disableSelection
site.umts.disableSelection=acp_site_umts_disableSelection
site.lte.disableSelection=acp_site_lte_disableSelection
site.removeable=acp_site_removeable
site.gsm.removeable=acp_site_gsm_removeable
site.umts.removeable=acp_site_umts_removeable
site.lte.removeable=acp_site_lte_removeable
site.sectorsRemoveable=acp_site_sectorsRemoveable
site.gsm.sectorsRemoveable=acp_gsm_site_sectorsRemoveable
site.umts.sectorsRemoveable=acp_umts_site_sectorsRemoveable
site.lte.sectorsRemoveable=acp_lte_site_sectorsRemoveable
The following option can be used to manage the Inter Sector Lock check boxes (Height and Azimuth) in the Reconfiguration
column of the Reconfiguration > Sites vertical tab.
The following option can be used to manage the Disable check box in the Reconfiguration column of the Reconfiguration >
Sites vertical tab.
244
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
multi-band antenna. The antenna model is by default set to the PHYSICAL_ANTENNA column of the Antennas table. Hence by
default the auto antenna grouping is always enabled if antenna patterns are correctly assigned to physical antennas.
[ACPCustomFieldExtraction]
antenna.model=PHYSICAL_ANTENNA
If the physical antenna has been defined using the antenna.model option, the following option can be used to name the
custom column in the Antennas table that is used to define antenna groups. In the custom column in the Antennas table, all
antenna patterns corresponding to physical antenna belonging to the same group are identified with a unique string. The ACP
automatically groups all physical antenna into a new group with the name given by the string used in the column.
[ACPCustomFieldExtraction]
antenna.group.model=acp_group_model
The following options can be used to name the custom columns in the Antennas table to automatically define the mechanical
tilt options.
• The name of the custom column in ANTENNA table of type 'bool', defining which antenna pattern is associated with
a mechanical tilt constraint:
[ACPCustomFieldExtraction]
antenna.tilt.use=ACP_TILT_USE
• The name of the custom columns in ANTENNA table of type 'string' or numeric, defining the mechanical tilt allowed
range. Non-valid values are treated as "forbidden":
[ACPCustomFieldExtraction]
antenna.tilt.min=ACP_TILT_MIN
antenna.tilt.max=ACP_TILT_MAX
The following options can be used to name the custom columns in the Antennas table to automatically define the electrical
tilt options.
In order to optimise the electrical tilt, you must first activate the following option:
[ACPReconfPage]
enableETilt = 1
Optionally, if you want to activate AEDT support, you must also set the following option:
[ACPAntennaPage]
enableAedt = 1
• The name of the custom column in the ANTENNA table of type 'bool', defining which antenna pattern is associated
with an 'electrical tilt constraint':
[ACPCustomFieldExtraction]
antenna.etilt.use=ACP_ETILT_USE
ACP supports additional electrical downtilt (AEDT) processing. AEDT is used when antenna patterns are not available
for changes in electrical tilts. The patterns are derived by ACP using geometric downtilts of the original antenna
pattern. When you have activated AEDT support, new columns appear in the Antenna Pattern table on the Antenna
> Patterns vertical tab allowing you to configure which antenna uses AEDT and the range of allowed electrical tilt.
[ACPCustomFieldExtraction]
antenna.aedt.use=ACP_AEDT_USE
• The name of the custom columns in the ANTENNA table of type 'string' or numeric, defining the allowed range for
AEDT and electrical tilt. Non-valid values are treated as "forbidden":
[ACPCustomFieldExtraction]
antenna.etilt.min=ACP_ETILT_MIN
antenna.etilt.max=ACP_ETILT_MAX
The following option can be used to name the custom column in the Antennas table to automatically link antenna elements
of a multi-band physical antenna which have the same electrical tilt. In the ACP Setup dialog box, this is accomplished by
selecting the check box in the Same Elec. Tilt column. The antenna.etilt.share option should contain a list of the space-
separated frequencies for which the corresponding physical antenna must be linked (i.e., physical antenna that always uses
same electrical tilt):
245
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[ACPCustomFieldExtraction]
antenna.etilt.share=ACP_ETILT_SHARE
[ACPGeneralPage]
cost.classes.showUI = 1
# Default = 1 (site class feature is enabled).
The following option can be used to define the default settings when the site class option is available. These settings are local.
[ACPTplGeneralPage]
cost.classes.count = 1
# Number of defined classes
You can then define the site classes that will appear each time a new ACP optimisation is created along with pre-defined costs.
The name of each class as it appears in the ACP is defined by an option called cost.classes.X.name where X is a sequential
number. The corresponding settings for the class defined in cost.classes.X.name are defined using the following options:
• cost.classes.X.azimuth.cost: This key is used to define the cost of changing the antenna azimuth.
• cost.classes.X.azimuth.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
• cost.classes.X.tilt.cost: This key is used to define the cost of changing the mechanical tilt of the antenna.
• cost.classes.X.tilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
• cost.classes.X.antenna.cost: This key is used to define the cost of changing the type of the antenna.
• cost.classes.X.antenna.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
• cost.classes.X.etilt.cost: This key is used to define the cost of changing the electrical tilt of the antenna.
• cost.classes.X.etilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
• cost.classes.X.height.cost: This key is used to define the cost of changing the antenna height.
• cost.classes.X.height.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
• cost.classes.X.power.cost: This key is used to define the cost of changing the power.
• cost.classes.X.power.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
• cost.classes.X.siteVisitCost: This key is used to define the cost of a site visit.
• cost.classes.X.upgradeSiteCost: This key is used to define the cost of upgrading an existing site.
• cost.classes.X.newSiteCost: This key is used to define the cost of creating a new site.
• cost.classes.X.removeSiteCost: This key is used to define the cost of removing an existing site.
The following is an example of the keys for the first site class (numbered 0) called "Planned" in this example.
[ACPTplGeneralPage]
cost.classes.0.name=Planned
cost.classes.0.azimuth.cost = 1
cost.classes.0.azimuth.isSiteVisit=true
cost.classes.0.tilt.cost = 1
cost.classes.0.tilt.isSiteVisit=true
cost.classes.0.antenna.cost = 1
cost.classes.0.antenna.isSiteVisit=true
cost.classes.0.etilt.cost = 0.1
cost.classes.0.etilt.isSiteVisit=false
cost.classes.0.height.cost = 1
cost.classes.0.height.isSiteVisit=true
cost.classes.0.power.cost = 0.1
cost.classes.0.power.isSiteVisit=false
cost.classes.0.siteVisitCost = 2
cost.classes.0.upgradeSiteCost = 5
246
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
cost.classes.0.newSiteCost = 10
cost.classes.0.removeSiteCost = -5
You must first create the corresponding custom column in the Sites table of the Atoll
database and assign a site class to each site in this column for this option to have effect.
[ACPCustomFieldExtraction]
site.costClass=[name of custom field in Site table]
The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For new candidate
sites which are located on an existing site, the site class is the same as the site on which the new candidate is located. For new
candidate sites which are not co-located on an existing site, the site class is set to "Default" and can be changed manually.
By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 246, the cost structure is
automatically defined as well.
11.2.2.20.1 Defining the Colours in the Analysis Maps on the Quality Tab
The following settings can be used to define the colours in the analysis maps on the Quality tab.
None of the options described in this section are available by default in the ACP.ini file. If
you want to use any of them, you must specify it manually in the ACP.ini file.
There are two possible formats for defining the range of colours on maps:
1. Detailed format: The detailed format enables you to set a non-uniform range. The number of ranges is defined and,
for each range, the minimum and maximum value of the range followed by its RGB color representation.
[ACPMapDefault]
colormap.techno.quality.nbRange = 8
# Number of ranges to be defined
colormap.techno.quality.range.0=[-99999.000000 -15.000000] RGB(0 0 255)
colormap.techno.quality.range.1=[-15.000000 -13.000000] RGB(0 128 255)
colormap.techno.quality.range.2=[-13.000000 -11.000000] RGB(0 196 196)
colormap.techno.quality.range.3=[-11.000000 -9.000000] RGB(0 224 0)
colormap.techno.quality.range.4=[-9.000000 -7.000000] RGB(128 255 0)
colormap.techno.quality.range.5=[-7.000000 -5.000000] RGB(255 224 0)
colormap.techno.quality.range.6=[-5.000000 -3.000000] RGB(255 128 0)
colormap.techno.quality.range.7=[-3.000000 99999.000000] RGB(255 0 0)
•
Uniform format description: A uniform format description using a range and step, in one of the following
intervals: [firstBreak startcolor] [lastBreak endColor]
• -INF [firstBreak startcolor] [lastBreak endColor]
where interval starts from minus infinite to englobe all lower values and avoid transparent pixels for lower values.
[ACPMapDefault]
colormap.techno.quality.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
colormap.techno.quality.rangeDefinition = -INF[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
247
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
These descriptions are used for default colormap and can easily be changed by the user. The settings are the same for the
various quality indicator in various technologies, where you replace:
• techno by "umts", "gsm", "lte", "wimax", "cdma"
• quality by "sl", "slgain" (in GSM), "ecio", "ec", "ecgain", "eciogain", "ecnt", "ecntgain" (in UMTS), "sl", "slC", "slCN",
"rsrp", "cinr", "rsrq", "slgain", "cinrgain", "rssi" (in LTE), "sl", "slC", "slCN", "cinr", "slgain", "cinrgain" (in WiMAX)
[ACPMapDefault]
colormap.gsm.sl
colormap.gsm.slgain
colormap.umts.ec
colormap.umts.ecgain
colormap.umts.ecio
colormap.umts.eciogain
colormap.umts.ecnt
colormap.umts.ecntgain
colormap.lte.cinr
colormap.lte.cinrgain
colormap.lte.rsrp
colormap.lte.rsrq
colormap.lte.rssi
colormap.lte.sl
colormap.lte.slC
colormap.lte.slCN
colormap.lte.slgain
colormap.wimax.cinr
colormap.wimax.cinrgain
colormap.wimax.sl
colormap.wimax.slC
colormap.wimax.slCN
colormap.wimax.slgain
In addition, a number of other colormaps can be defined for other types of maps, e.g: overlap maps, objective status maps,
electrical tilt maps, mechanical tilt maps, combined electrical/mechanical tilt maps, change maps, emf maps, etc.
248
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ACPMapDefault]
colormap.bestcell.etilt
colormap.bestcell.objective
colormap.bestcell.sector
colormap.bestcell.tilt
colormap.bestcell.ttilt
colormap.bestcellHeight
colormap.capacity
colormap.capacitygain
colormap.change.azimuth
colormap.change.cost
colormap.change.etilt
colormap.change.impr
colormap.change.power.cdma
colormap.change.power.gsm
colormap.change.power.lte
colormap.change.power.umts
colormap.change.power.wimax
colormap.change.power2.cdma
colormap.change.power2.umts
colormap.change.selectionType
colormap.change.tilt
colormap.change.ttilt
colormap.change.type
colormap.changeHeight
colormap.diff
colormap.emf
colormap.emf.badSector
colormap.emf.gain
colormap.gain
colormap.imprCoverage
colormap.objective
colormap.objective.gain
colormap.objective.weighting
colormap.overlap
colormap.overlapgain
[ACPMapPage]
config.foreground = 0
#default foreground colour setting (black)
config.background = 16777215
#default background colour code (white)
The RGB code for white is calculated as follows: 255 + 255 2 8 + 255 2 16 = 16777215 .
The following options define the size of the map title on the Quality tab:
[ACPMapPage]
config.titleHeight = 16
# Title height in pixels
config.titleFontSize = 16
# Size of title font in points
The following option defines the width of the margin on the Quality tab:
[ACPMapPage]
config.margin = 2
# Margin width in pixels
The following options define the appearance of the map legend on the Quality tab:
249
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[ACPMapPage]
config.showLegend = 1
# Defines whether the legend is displayed.
config.legendWidth = 40
# Defines the width of the legend in pixels.
config.legendFontSize = 11
# Defines the font used in points.
config.legendForeground = 0
# RGB code as integer: here black
The following option defines whether or not the axis will be displayed on the Quality tab:
[ACPMapPage]
config.showAxis = 1
The following options define the appearance of the histogram on the Quality tab:
[ACPMapPage]
config.showHistogram = 1
# Defines whether the histogram is displayed.
config.histogramHeight = 60
# Defines the width of the histogram in pixels.
The following options define the appearance of the selected zone on the Quality tab:
[ACPMapPage]
config.showZoneSelection = 1
# Defines whether the selected zone is displayed.
config.zoneLighterPercent = 70
# Defines how much lighter selected zone is displayed.
[ACPMapDefault]
transparency = 50
The following option automatically selects the Add to legend check box in the properties of new ACP predictions:
[ACPMapDefault]
isAddToLegend = 1
The following option forces any new ACP prediction to not reuse the shading settings (if any) of the Atoll prediction defined
next to Base prediction settings in the Objectives page of the corresponding quality parameter.
[ACPMapDefault]
isUsePredictionColormap = 1
#default = 1 (shading settings of ACP prediction prevail)
[ACPNewPredictionDlg]
showBestServerAerialPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the coverage by layer.
250
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ACPNewPredictionDlg]
showBestServerLayerPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the weight used for the traffic and for each zone.
[ACPNewPredictionDlg]
showObjectiveWeightPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the improvement in coverage.
[ACPNewPredictionDlg]
showchangeImprovementPrediction = 1
#default = 0
You can use the addCandidateComment option to create a comment in any site, transmitter, and cells automatically created
by ACP in Atoll as part of the candidate site selection. No comment is added if this option is left blank.
In the [ACPOverlayDialog] section is the option for defining the opacity of the overlay window when it loses focus. A value of
100 disables it.
[ACPOverlayDialog]
opacity = 100
[ACPGraphPage]
showTimeMarkers = 1
# To add time markers on the X axis. Default is 0
[ACPUI]
DefaultFont = MS UI Gothic
#Font used by grid, graph component, and map component
DefaultGridFontSize = 0
#Font size for grid only. 0 mean default size
251
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
[ACPXmlReport]
enableXmlExport = 1
# Enable the XML report from the ResultStatPage
generateXmlSection = -1
# Bit combination of the following: 1=metadata, 2=setup, 4=resultSummary,
# 8=resultSectors, 16=resultIterations, 32=resulstChangeset, 64=resultMaps, -1=all
encoding=UTF-8
saveDefaultStylesheet = 1
#save a default stylesheet if none exist
defaultStylesheetName=.acpReport.xslt
# Name of default stylesheet file.
# Set it empty to disable stylesheet processing instruction
[ACPCore]
generateLogFile = 0
# default = 0; no log file.
Possible settings:
Value Description
The default value means that the propagation model will use the same number of threads as the
-2
number of threads defined by computationThreadPoolSize.
-1 Auto configuration; the propagation model will use one thread for each CPU core.
Other The defined numerical value indicates the number of threads that the propagation model can use.
252
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
• memLimitNumPos: Memory use is determined to be excessive when the maximum number of pixels (as defined by
memLimitNumPos) is reached during a calculation. Setting memLimitNumPos to -1 deactivates this option.
• memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb (as defined by
memLimitMemory) is reached during a calculation. Setting memLimitMemory to -1 deactivates this option.
• memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds the
percentage of the total memory available for Atoll, as defined in memLimitUseableMemory. Setting
memLimitUseableMemory to -1 deactivates this option.
If all three options are deactivated, ACP does not check excessive memory usage.
The abortIfMemLimitReach option defines how ACP reacts if the defined maximum memory use is reached. By default (with
abortIfMemLimitReach set to 0), ACP will attempt to allocate memory. If unable to successfully allocate memory, ACP displays
a message and the calculation is stopped. When using the option abortIfMemLimitReach, then ACP will not start if the
message indicating excessive memory use is displayed.
By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is not
prevented running even when 80% is exceeded.
When ACP estimates actual memory use (i.e., using either memLimitMemory or
memLimitUseableMemory), the memory estimate is only a rough estimate. Depending
on the project, actual memory usage can be quite different.
[ACPCore]
memLimitNumPos = -1
# -1 deactivates this option.
memLimitMemory = -1
# -1 deactivates this option.
memLimitUseableMemory = 80
# -1 deactivates this option.
abortIfMemLimitReach = 0
253
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
The following options define the values used by ACP to control the curve shapes. Although you can modify these settings, they
are the recommended factory values:
[ACPCore]
gsm.signallevel.th.min = -120
gsm.signallevel.th.max = -50
gsmcnircocanal.th.min = 0
gsm.cinrcocanal.th.max = 20
umts.rscp.th.min = -120
umts.rscp.th.max = -60
umts.ecio.th.min = -20
umts.ecio.th.max = -6
lte.rsrp.th.min = -130
lte.rsrp.th.max = -70
lte.rscinr.th.min = -10
lte.rscinr.th.max = 30
lte.rsrq.th.min = -20
lte.rsrq.th.max = -8
lte.pdschcinr.th.min = -10
lte.pdschcinr.th.max = 40
wimax.signallevel.th.min = -120
wimax.signallevel.th.max = -50
wifi.signallevel.th.min = -120
wifi.signallevel.th.max = -50
lpwa.signallevel.th.min = -140
lpwa.signallevel.th.max = -50
[ACPCore]
addPilotSHOGain = 1
#Default = 1
For details on disabling macro-diversity gains calculation, see "Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and
Eb/Nt" on page 209.
Possible settings:
Value Description
ACP does not take macro diversity gains into account.
0 For consistency with the Atoll platform, the following option must be set in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0
1 Default. ACP takes macro diversity gains into account.
ACP uses the same value as the one defined for the AddPilotSHOGain option in the Atoll.ini file:
2 [CDMA]
AddPilotSHOGain = value
[ACPCore]
useSiteAltitude = 1
#Default = 1
For details on reading altitudes from the DTM in Atoll, see "Reading Exact Altitudes From the DTM" on page 197.Possible
settings:
254
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
Value Description
During calculations, ACP will read the altitudes from the DTM at the exact coordinates of each
0
transmitter considering the values entered for the DX and DY parameters.
Default. This is the value used by the Atoll platform (which uses either the user-defined site
1 altitudes from the Sites table or, if they are not defined, the site altitudes read from the DTM for
the site coordinates defined in the Sites table).
ACP uses the same value as the one defined for the useSiteAltitude option in the Atoll.ini file:
2 [Calculations]
useSiteAltitude = value
[ACPAutoCandPosDlg]
interSiteDist = 500
#default = 500
For areas (polygon zones only, not polylines), you can set the following option to modify the default minimum ratio of inter-
site distance below which candidate sites will not be proposed:
[ACPAutoCandPosDlg]
minInterSiteDistRatio = 25
#default = 25
ACP normally places candidate sites in a strict hexagonal pattern. However, the ACP can search for a more appropriate site
within a search radius ratio according to the defined rules. The following option defines the default search radius ratio as a
percentage of the defined inter-candidate site distance.
[ACPAutoCandPosDlg]
searchRadiusRatio = 30
The following option defines the default minimum increase in altitude (in metres) that the ACP must find when placing a new
automatic candidate site.
[ACPAutoCandPosDlg]
hpHeightThres = 10
255
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
• maxMonitorCell: defines the maximum number of cells monitored. This option affects memory use and accuracy. The
analogous options for the high speed mode and the high precision mode are maxMonitorCellSpeed and
maxMonitorCellPrec, respectively.
• threshLevelMonitorCell: defines the best server signal threshold (dB) in order to be monitored. This option affects
memory and accuracy.
• The analogous options for the high speed mode and the high precision mode are threshLevelMonitorCellSpeed and
threshLevelMonitorCellPrec, respectively.
The following options define the values ACP uses for default mode:
[ACPCore]
maxMonitorCell = 32
threshLevelMonitorCell = 35
The following options define the values ACP uses for high speed mode:
[ACPCore]
maxMonitorCellSpeed = 30
threshLevelMonitorCellSpeed = 30
The following options define the values ACP uses for high precision mode:
[ACPCore]
maxMonitorCellPrec = 35
threshLevelMonitorCellPrec = 40
Other options in the ACP.ini file can be used to define additional offsets that will be used by the specific technology that ACP
is optimising:
[ACPCore]
threshLevelOffGsm = 0
maxMonitorOffGsm = 0
threshLevelOffUmts = 0
maxMonitorOffUmts = 0
threshLevelOffCdma = 0
maxMonitorOffCdma = 0
threshLevelOffLte = 10
maxMonitorOffLte = 10
threshLevelOffWimax = 5
maxMonitorOffWimax = 5
threshLevelOffWifi = 5
maxMonitorOffWifi = 5
threshLevelOffLpwa = 20
maxMonitorOffLpwa = 20
ACP loads raster data with block-based processing to reduce memory usage. The maximum memory (in Mb) allowed for this
block processing in Mb is controlled with the following setting (you can reduce the value if you experience issues with ACP
failure due to memory allocation):
[ACPCore]
gisDataCacheMemMax = 256
For lower memory usage, you can use the following option to specify an optimized block-based raster data loading strategy:
256
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
[ACPCore]
gisDataCacheStrategy = 1
# default = 1
When you set the following option, ACP will consider a mix or raster data and polygons for the DLU file (should be set to 1
when clutter classes are edited with the clutter editor):
[ACPCore]
gisDataClutterUsePoly = 0
# default = 0
When you set the following option, ACP creates multistorey points for areas where the DLU file is present (with default
heights) without the presence of DHM raster (clutter height). The default setting (TRUE) makes the ACP distribute vertical
points only where DHM is available:
[ACPCore]
multistorey.onlyDHM = TRUE|FALSE
# default = TRUE
If you set the gisDataClutterOnlyRes option to filter out all clutter classes but those with the defined option, you should also
list the clutter classes that are not to be used in the zone.clutter.hiddenCodes in the [ACPGeneralPage] section to ensure that
the user will not create zones based on clutter classes that are not used. When you define the clutter classes that are not used,
they will not be displayed in the Zone Definition dialog box.
[ACPGeneralPage]
zone.clutter.hiddenCodes = 0,1,2,12,13
# These clutter classes are not displayed
11.2.3.14 Fixed Ratio Between Pilot Power and Max Power (UMTS)
When optimising the maximum cell power in UMTS, the ACP forces the ratio between pilot power and maximum power to
stay constant. You can remove this constraint using the following option:
[ACPCore]
umtsPilotPowerRatioFixed = 0
[ACPResultSectorPage]
257
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
custom.count = 2
#default = 2
You can then set the following options to specify the data you want to show under each custom column.
custom.0.type=tabularDataColumn
custom.0.column=FOO
custom.0.label=FOO label of custom.0.column
custom.1.type=tabularDataColumn
custom.1.column=BAR
The ACP can automatically adjust the height of transmitters that are below roof so that they are on top of the clutter height
using the defined offset (in metres).
[ACPEMFCore]
resetTxHeightWhenIndoor = 0
#default = 0; height is not reset.
The following option defines the internal resolution in metres (2 by default) for terrain 3D representations when the ACP
rasterises input vectors:
[ACPEMFCore]
vectorRasterizationResolution = 2
The following option allows you decrease the displayed EMF exposure level when penetration loss is increased for buildings.
[ACPEMFCore]
258
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Chapter 11: Initialisation Files
flagPixelFacadeDist = distance
flagPixelFacadeDist defines (in metres) the indoor distance from facade for a pixel to be considered as "indoor". When the
distance is 0, the outdoor pixels will be applied the indoor penetration loss specified in the Propagation Class Definition table
(Propagation page on the Optimisation tab).
Likewise, you can add the following lines to show the Optimisation > Multi-Storey tab in ACP setups (equivalent to manually
selecting the Multi-Storey check box under Extensions on the Preferences tab):
[ACPExtension]
multistorey = 1
[ACPMisc]
autoCheckPathlossValidity = 0|1
autoCheckPathlossValidity is set to 1 by default, which means that the validity of path loss matrices is automatically checked
before running an optimisation setup.
In addition, the following options can be used:
• To enable ("1") or disable ("0") the automatic check of the path loss matrix files (file location and file size) before a run:
autoCheckPathlossFileValidity = 0|1
259
Atoll 3.3.2 Administrator Manual
Chapter 11: Initialisation Files © Forsk 2016
260
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Index of Initialisation Options
261
Atoll 3.3.2 Administrator Manual
Index of Initialisation Options © Forsk 2016
262
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Index of Initialisation Options
263
Atoll 3.3.2 Administrator Manual
Index of Initialisation Options © Forsk 2016
264
Atoll 3.3.2 Administrator Manual
AT332_AM_E0 Index of Initialisation Options
265
• Head Office • US Office • China Office
7 rue des Briquetiers 200 South Wacker Drive – Suite 3100 Suite 302, 3/F, West Tower, Jiadu Commercial Building,
31700 Blagnac, France Chicago, IL 60606, USA No. 66 Jianzhong Road, Tianhe Hi-Tech Industrial Zone,
Tel: +33 562 747 210 Tel: +1 312 674 4800 Guangzhou, 510665, P. R. of China
Fax: +33 562 747 211 Fax: +1 312 674 4847 Tel: +86 20 8553 8938 Fax: +86 20 8553 8285