Professional Documents
Culture Documents
Release Notes
Version 3.14.15
1 N e w fe a t u r e s
1.1 Whats new in Cellopt AFP 3.14.14 - 3.14.15
No new features have been added.
Icons have been added to the Site and Sector Property pages to allow a user to enable all radios for a site and sector, displayed in the Property page.
To avoid radios becoming inadvertently enabled, a dialog is presented to the user to confirm the action.
1.21.3 Default report destination A new option has been added to set an analysis reports default destination to be a file rather than the screen. The default directory location is stored in Options. 1.21.4 Layer sorting Layers defined by the user will appear in alphanumeric order; however, system layers will maintain their current, logical order.
1.23.5 Common Actix licensing The licensing system has changed. The new system will be common within all Actix software. Currently Actix Analyzer and Cellopt AFP/MDA and Actix Switch Adapter use the same licensing. For older versions of Cellopt, the old licensing system will still be supported.
2 R e s o l ve d i s s u e s
2.1 Issues resolved in 3.14.15
2.1.1 Maximum separation doesn t work for split sectors The model preparation relies on so called "confirmed plan entries". These are frequency associations to radios that will be checked and validated before optimization takes place, i.e. invalid frequencies, which e.g. violate some maximum separation constraint or something else, will not be saved as confirmed plan entry but rather be removed. These removed plan entries won't be considered any longer for subsequent narrowing down of the available frequencies due to the maximum separation constraint. Hence, the plan entry of fixed radios should remain instead of being removed due to constraint violation in order to be properly considered. 2.1.2 Optimization with user-defined MALs returns ArrayIndexOutOfBoundsException Certain configurations may have led to incorrectly initialized optimizer data structures, when user-defined MALs are used, which caused an array access out of bounds. This issue has been fixed. 2.1.3 Synth Hopping Separation settings cause problems There was a bug in the internal model preparation step performed in advance of an optimization attempt that caused different kinds of groups to be mixed up by using maximum separation group IDs and treating them as radio group IDs. 2.1.4 Optimizer incorrectly reports No available spectrum A bug during optimizer initialization caused an incorrect response concerning the check for available spectrum under certain conditions when spare planning was not used. This issue has been fixed. 2.1.5 Incorrect parsing of interference threshold The threshold value of the filter Disable interference relations with co-values less than or equal to was not parsed correctly, which may have led to unexpected modification of the value when repeatedly switching to the Options for Frequencies dialog. This bug was fixed.
10
2.2.2 Assignment of layer unassigned in Category HSN leads to zero being set as value Instead of setting the value to zero (which would mean that the hopping sequence is cyclic) no value is set, when the layer unassigned is selected, now. 2.2.3 Export of Radio Editor failed due to unhandled number format In case of floating point values greater than or equal to 1,000.0 the export failed due to the thousands separator which was not taken into account when trying to convert the number. 2.2.4 Wrong position of radios when importing Planet 5 projects Although the frequency and the control radio attribute have been imported, properly, the order of the radios (in their parent sector) did not match their order in the Planet 5 project data. The order defined in the Planet project is preserved, now.
11
Invalid histograms (referring to unknown sectors) are dropped while processing. A bug prevented the removal of those invalid histograms and caused the observed unpredictable results due to a race condition, and this has now been fixed. Please note that non-unique sector names at a particular site are likely to cause problems because Cellopt AFP tries to find corresponding sectors using a combination of site/sector name, and the IDs used in the model and the measurement file generally differ from each other.
12
13
2.9.9 Fixed locale problem When adding a new site in Dutch OS, AFP was not interpreting lat-long values correctly. This is now fixed.
14
15
2.17.2 Optimization error (SF50181) AFP was failing to optimize when the project contained One Set and Adhoc, and MCRB radios. It has now been fixed.
16
17
2.24.2 iDEN set planning unassigned sector is sue Another issue fixed with set planning was that some sets were not recognized correctly, and as a result, some radios become unassigned. 2.24.3 Server shutdown problem after histogram import The server was not shutting down properly while exiting Cellopt AFP after histograms created by ASA were imported. This is now fixed. 2.24.4 Problem activating license when Analyzer also installed There was a problem reactivating a license using Activation wizard if Actix Analyzer was also installed with legacy licensing (i.e. not Activation). This is now fixed.
18
3 Known Issues
3.1.1 Exporting a Project Template without first closing AFP causes a crash After creating a Project Template, you must close Cellopt AFP before exporting the template. This issue is scheduled to be fixed in the next release. 3.1.2 Sector-based tab-delimited import / export of radios and sets The sector-based tab-delimited (import / export) feature is not designed to work with set planning. It is not possible to specify that a radio is assigned a frequency from a set. 3.1.3 Project scalability issue It is a known issue that the amount of memory that Cellopt AFP can use is limited by the 32-bit Java virtual machine. Some configurations will increase the available memory for Cellopt. This is done with the xmx flag inside the <installation directory>\conf\settings.xml file.
The default value is set to 800Mb as seen in the picture (indicated by Xmx800M). The value can be increased to around 1400Mb, depending on the local computer configuration. Much higher values than this are currently not allowed by 32-bit Java.
19
With this configuration change, the maximum number of radios can be around 25000, and even up to 50000. 3.1.4 Large reports issue There is an issue with large reports in the frequency analysis when displaying this on screen. When a very large report is displayed with thousands of lines, it might cause the client and server to disconnect and hang the application. 3.1.5 Unicode Fonts Exporting reports to PDF format renders all non-Western characters as hashes. There is an issue with applying fonts correctly in this format. 3.1.6 The User Databases (Projects) are not remove d when uninstalling Cellopt AFP The Cellopt AFP uninstaller does not remove the databases (projects) from the directory. To free up hard drive space, these can be removed manually. The location for the database is now in the All Users\Application Data: C:\Documents and Settings\All Users\Application Data\Actix\Cellopt AFP\3.X or 3.12 3.1.7 Uninstall may take longer on some systems 3.1.8 Copy Project from AFP Control Panel does not work Using Copy Project from Control Panel > Project Management > Copy project produces a crash with an error message similar to this: Model with id 15 does not exist The workaround for this issue is to export the project to file and copy the AFP3 XML file using Windows Explorer. 3.1.9 Creating a project using a template does not work in all instances When creating a new project from a project template that includes Interference Lists, and then importing an afp3 XML project that does not include an Interference List, the project creation fails. The workaround for this issue is to close the newly created blank project before importing the afp3 project. This forces the DB to update, then you can open the blank project and import the afp3 project file without errors. 3.1.10 Reactivation of licenses after upgrading to AFP 3.14.9 If a local license activation server is used, the information for the activation server has to be entered again after upgrading to version 3.14.9.
20
Clicking Next now would cause a communication error due to missing information about the license activation server this information was erased during the upgrade. Instead, click Back.
21
This opens the dialog where license activation server information can be entered:
22
4 R e l e as e H i s t o r y
Date
Apr-2010 May-2010 June-2010 July-2010 Aug-2010 Sep-2010 Nov-2010 May-2011 June-2011 Aug-2011 Oct-2011 Jan-2012 Mar-2012 Jul-2012 Oct-2012 Jan-2012
Version
AFP3.14.0 AFP3.14.1 AFP3.14.2 AFP3.14.3 AFP3.14.4 AFP3.14.5 AFP3.14.6 AFP3.14.7 AFP3.14.8 AFP3.14.9 AFP3.14.10 AFP3.14.11 AFP3.14.12 AFP3.14.13 AFP3.14.14 AFP3.14.15
New Features
X X X X X X
Resolved Issues
X X X X
23