Central Force Optimization Applied to the PBM Suite of Antenna Benchmarks ()
1. Introduction
The PBM suite is a set of typical “real-world” engineering problems developed by Pantoja, Bretones and Martin. These problems do not have known solutions. They are designed to test the effectiveness of antenna optimization algorithms using the Numerical Electromagnetics Code as an external modeling engine. A major concern whenever external modeling is required with a stochastic optimizer is having to make multiple runs to evaluate how effective the optimizer is, but not so with a deterministic optimizer.
Central Force Optimization (CFO) [1]-[4] is a deterministic gradient-like multi-dimensional search and optimization metaheuristic based on the metaphor of gravitational kinematics. It comprises two simple equations, and because the law of gravity is deterministic, so too is CFO, unlike many nature-inspired algorithms that are fundamentally stochastic.
In this paper, CFO is applied to the PBM suite and its results compared to published performance data for other optimization algorithms. CFO acquits itself quite well. CFO’s gradient-like nature is discussed, and it is speculated that a “generalized hyperspace derivative” might be defined for optimization problems as a new mathematical construct based on the Unit Step function. What appears to be a sufficient but not necessary condition for local trapping of CFO, oscillation in the probe average distance curve, is discussed in the context of the theory of gravitational “resonant returns” that gives rise to strikingly similar oscillatory curves. It is suggested that this theory may be applicable to CFO as an aid to understanding trapping and to developing effective mitigation techniques, possibly based on a concept of “energy” in CFO space. It also is suggested that CFO may be re-formulated as a “total energy” model by analogizing conservation of energy for orbiting masses in physical space.
This paper serves several purposes. The primary purpose is to report CFO’s performance against the PBM suite. Results from algorithms πCFO and πGASR are compared to the published PBM data and to CFO implemented without π fractions. π fractions are used to inject pseudorandomness into an algorithm and are discussed in detail. The comparison data are quite good. They demonstrate the general utility of π fractions in global search and optimization, in particular in rendering deterministic an otherwise probabilistic algorithm.
The secondary purposes of this paper are i) to describe the CFO metaheuristic and to present its basic equations; ii) to suggest the possibility of a new mathematical construct, a “hyperspace directional derivative” based on the Unit step function; iii) to discuss the strikingly similar appearance of velocity curves for NEOs (Near Earth Objects in gravitationally trapped close encounters) with CFO’s average probe distance curves; iv) to suggest the possibility of using probe total “energy” as a measure of local trapping; and v) to suggest the possibility of re-formulating CFO using a conservation of energy model.
CFO was introduced as a novel metaheuristic [1] that was applied to two problems in applied electromagnetics (EM): i) designing an equalizer for the canonical Fano Load; and ii) synthesizing a linear dipole array. CFO’s results were compared to data from several other algorithms, and it also was tested against many benchmark functions with analytically known maxima. The results suggested that CFO merited further development as a promising and robust optimization methodology, which indeed has been the case. CFO has been used to synthesize linear and circular antenna arrays, and it performed very well compared to the Quadrature Programming Method (QPM), to a Particle Swarm Optimization (PSO) algorithm, and to a Genetic Algorithm (GA) as reported in [5]. Even though CFO is perhaps not as well developed as many of the widely used evolutionary algorithms (EAs), it nevertheless has shown very robust performance and considerable promise for future development as discussed below.
An important consideration in implementing CFO algorithms is the inclusion of some measure of pseudorandomness because doing so evidently improves decision space (DS) exploration. To that end, π fractions are applied to a version called πCFO and its performance is compared to the GA called πGASR using the PBM suite [6] as the test platform.
The PBM paper [6] describes its purpose as follows: “This paper presents a new test suite formed not by artificial analytical functions but by a set of numerical electromagnetic problems aimed at facilitating the comparison of the performance of different EAs when they are applied in computational electromagnetics.”
The PBM suite is specifically designed to objectively evaluate the performance of EAs used to solve complex “real world” EM problems. Representative, not exhaustive, examples of such algorithms might include: PSO-based array synthesis [7]; swarm intelligence optimization of layered media [8]; GA antenna modeling [9]; array design using GAs, and memetic and tabu search algorithms [10]; crack detection using a finite-difference frequency domain/PSO methodology [11]; Vee-dipole optimization using a bacteria foraging algorithm [12]; and GA-optimized MRI coil design [13]. These are the kinds of problems PBM is meant to address by objectively evaluating how well the associated optimizers perform. CFO is a candidate algorithm.
EAs solve these problems by “evolving” solutions that are unavailable analytically or numerically. The plethora of nature-inspired EAs makes comparison very difficult without a standardized set of benchmarks for testing, which is why the PBM suite was developed PBM is based on the Numerical Electromagnetics Code (NEC) [14] and addresses this need for standardized testing of EA’s that are applied to optimized antenna design. It therefore is also a useful tool for evaluating how well CFO performs.
An EA’s performance is measured in two ways: (i) by its effectiveness (accurately locating global maxima, values and locations) and (ii) by its efficiency (locating global maxima with minimum computational effort). An algorithm that fails to accurately locate global maxima obviously fails to accomplish its intended purpose and consequently is ineffective. EAs that are, on a relative basis, computationally intensive are less desirable than ones requiring fewer calculations. This paper uses these performance measures to compare CFO to the four EAs discussed in [6]. The results are, for the most part, very encouraging. CFO performs very well compared to the PBM EAs, and in many cases much better. But CFO does suffer limitations, primarily a consequence of its being deterministic, which renders it prone to local trapping.
Because this paper touches on several topics, it is organized as follows.
1. Introduction
2. PBM Benchmarks: Overview & NEC4
2.1. The PBM Problems
2.2. NEC4 Validation
3. CFO Performance Summary
3.1. Effectiveness
3.2. Efficiency
4. Pseudorandom CFO Using Pi Fractions
4.1. π fractions
4.2. Utility of π fractions in CFO
5. Algorithms Compared
6. Comparison Results
7. The CFO Metaphor
7.1. CFO, NEOs and Energy
7.2. CFO Equations
7.3. New “Hyperspace Directional Derivative”
7.4. CFO Parameters
8. Why a Deterministic Optimizer?
9. Conclusion
Appendix A: PBM Benchmarks—Geometries & Landscapes
Appendix B: CFO Pseudocode
2. PBM Benchmarks: Overview and NEC4
2.1. The PBM Problems
The PBM suite comprises five antenna problems designed to test an EA’s effectiveness and efficiency. They do not have known analytical solutions although, of course, the two-dimensional (2D) topologies can be visualized. Table 1 lists the suite’s properties. In each case, the objective is to maximize the antenna’s directivity (“fitness”). Four of the problems are 2D, while the fifth is
[
is the number of dipole elements in a collinear array]. The 2D problem topologies (“landscapes”) are plotted in the Appendix to illustrate the nature and complexity of the decision space. Problems #1 and #4 are unimodal with a single global maximum. The first problem is “lumpy” with strong local maxima, whereas the fourth is “smooth”. Problem #2 is “noisy” in a complex landscape with large amplitude nearby local maxima. The third problem’s topology is extremely multimodal with four global maxima. Problem #5 is a unimodal high-dimensionality problem that optimizes the element spacing of an
-element collinear dipole array.
Table 1. Properties of the PBM benchmark problems.
PBM Benchmark # |
Problem Characteristics (in each case objective is to maximize directivity) |
1 |
Variable length center-fed dipole. 2D, unimodal, single global maximum, strong local maxima. |
2 |
Uniform 10-element array of center-fed
-dipoles. 2D, added Gaussian noise, single global maximum, multiple strong local maxima. |
3 |
8-element circular array of center-fed
-dipoles. 2D, highly multimodal, four global maxima. |
4 |
Vee Dipole. 2D, unimodal, single global maximum, “smooth” landscape. |
5 |
Collinear
-element array of center-fed
-dipoles.
, unimodal, single global maximum. |
2.2. NEC4 Validation
Because the PBM problems do not have analytic solutions, in [6] they were solved numerically using the Numerical Eletromagnetics Code (“NEC”). Anecdotally, NEC is considered by many engineers to be the “gold standard” for wire structure EM modeling, but it must be used correctly. The first step in evaluating CFO’s performance therefore is validation of the published PBM results. The five PBM benchmark antennas were modeled using the Numerical Electromagnetics Code Version 4.1 Double Precision (NEC4.1D) [14], which may be (probably is) a different version of NEC than the one used in [6]. The segmentation and wire radii used in [6] were replicated. More detailed discussion of the PBM problems and NEC4 input and output files are available online at the following website: https://app.box.com/s/j6km9sy4udstujy5fx9e40p6ci70qs85. Each PBM antenna was modeled using the coordinates for the maxima reported in [6]. In several cases, they were estimated from graphical data and, as a consequence, are necessarily approximate. Table 2(a) and Table 2(b) summarize the results. In the “Domain” column,
and
, respectively, refer to the abscissa and ordinate; λ is the wavelength;
is the problem’s dimensionality; and
and
, respectively, are the maximum directivities from the PBM paper and as computed by NEC4.1D for this paper.
While the general conclusion is that NEC4 essentially recovers the PBM results, there are some noteworthy differences. For problems #1 and #2, NEC4’s computed directivities are slightly less than PBM’s. For problems #3 and #4, they are lower by wider margin. The best agreement is on problem #5 where the NEC4 and PBM data show very good agreement. What accounts for these discrepancies is not clear. There are several possible explanations, ranging from possibly different versions of NEC to compiler differences in creating the executables to slight differences in the antenna models, for example, source modeling (NEC4 excitation was modeled following the guidelines for the “EX0” card [14] (Part I, p. 48 et seq.). These differences between the PBM results and NEC4 notwithstanding, the validation test shows that NEC4 can be used effectively to assess CFO’s performance against the PBM benchmarks, and that CFO should recover maxima with similar amplitudes at about the same points in DS.
Table 2. (a). PBM and NEC4 Results for Benchmarks #1-4; (b) PBM and NEC4 Results for Benchmark #5.
(a) |
Problem # |
PBM |
NEC4 |
Domain |
|
|
x |
|
1 |
|
2.58λ |
0.63 |
3.32 |
3.2 |
2 |
|
~5.85λ(1) |
π/2 |
~18.3 |
18.11 |
3 |
|
0.5, 1.5, 2.5, 3.5 |
π/2 |
~7.05 |
6.15 |
4 |
|
1.5λ |
0.834 |
~5.8 |
4.8 |
(b) |
Problem # |
# Dipoles |
|
Domain |
|
|
|
5 |
6 |
5 |
|
0.99λ |
~11.25(2) |
11.22 |
5 |
10 |
9 |
|
0.99λ |
~19 |
19.10 |
5 |
16 |
15 |
|
0.99λ |
~31 |
30.97 |
5 |
24 |
23 |
|
0.99λ |
~47 |
46.88 |
Note: (1) Values marked with ~ are estimated from Figure 6, Figure 9 or Figure 11 in [6]; (2) Values marked with ~ are estimated from Figure 13 in [6].
3. CFO Performance Summary
3.1. Effectiveness
This section summarizes CFO’s performance (Appendix A contains detailed discussions of each benchmark). CFO’s effectiveness is measured by how accurately it locates the PBM maxima (coordinates and maxima values, that is, best fitnesses). Table 3 summarizes the coordinate results and Table 4 the fitnesses (“∆” denotes difference in values). Inspection of these tables shows that the agreement generally is quite good.
Turning to Table 3, for 2D problems #1 through #4, respectively, the coordinates agree to within (1.12%, 1.9%), (1.26%, 0.89%), (3.95%, 0.16%), and (0.03%, 14.75%) [relative to PBM’s coordinates]. The only significant disagreements are in the abscissas for problem #3 and the ordinates for problem #4. In the case of problem #3, the location of the global maximum at
,
is known analytically. No computed value was reported in [6], so that the true degree of agreement is not known. For problem #4, the discrepancy in the inner angle
may be a result of modeling differences, or possibly using different versions of NEC. Of course, from a practical (read “engineering”) point of view, agreement to within about 15% probably is acceptable. NEC4 guidelines suggest that an Average Gain Test (AGT) value within about 15% indicates a good EM model. All models discussed here meet that test. For problem #5, the dipole separation for maximum directivity agreed to within 1% for all array sizes, which is quite good. If the 24-element array, for which
, is excluded, then the agreement is even better, to within 0.7%.
Table 3. Comparison of PBM and CFO maxima coordinates.
PBM Problem # |
PBM Coordinates |
CFO Coordinates |
∆ |
|
|
|
|
|
|
1 |
2.58λ |
0.63 |
2.55088λ |
0.61805 |
0.02912λ |
0.01195 |
2a [no noise] |
~5.85λ |
π/2 |
5.92359λ |
1.55685 |
-0.07359λ |
0.01395 |
2b [noise] |
nr(1) |
nr |
6.93601λ |
1.54721 |
--- |
--- |
3 |
0.5 |
π/2 |
0.48024 |
1.57327 |
0.01976 |
-0.00247 |
4 |
1.5λ |
0.834 |
1.49520λ |
0.71098 |
0.00048λ |
0.12302 |
--- |
|
|
|
5 |
0.99λ |
0.98310λ – 1λ |
0.01λ |
Notes: (1) Not reported in [6].
Table 4 compares CFO’s and PBM’s best fitnesses as measured by the difference of directivities,
. The differences are 3.43%, 0.36%, 27.74%, and 1.47%, respectively, for problems #1 through #4 [relative to PBM values]. The agreement is quite good, except for problem #3, which would be troublesome but for the data in Table 2(a). NEC4 returned a directivity 6.15 at the points
,
, instead of 7.05 as reported in [6]. If, in fact, 6.15 is the correct value, then the difference decreases to a more modest 5.47%. At a minimum, there appears to be a question concerning the accuracy of the result reported in [6], and CFO’s overall performance suggests that it accurately located the first global maximum for problem #3 after all. On problem #5 the directivity values are in excellent agreement across all array sizes. The differences range from only 0.08% (
) to 0.52% (
). In this case CFO recovered the PBM’s suite best fitnesses with very high accuracy.
Table 4. Comparison of PBM and CFO best fitnesses.
PBM Problem # |
CFO Results |
|
∆
|
|
|
|
1 |
2.55088λ |
0.61805 |
3.20627 |
3.32 |
0.11373 |
2a (without noise) |
5.92359λ |
1.55685 |
18.3654 |
18.3(1) |
−0.0654 |
2b (with noise) |
6.93601λ |
1.54721 |
18.6880 |
nr(2) |
nr |
3 |
0.48024 |
1.57327 |
6.48634 |
7.05(1) |
0.56366 |
4 |
1.49520λ |
0.71098 |
5.71479 |
5.8(1) |
0.08521 |
--- |
|
--- |
--- |
--- |
5 (6 el) |
0.99105λ |
11.2202 |
~11.25(3) |
0.0298 |
5 (7 el) |
0.98310λ |
13.1826 |
nr |
--- |
5 (10 el) |
0.99421λ |
19.0985 |
~19(2) |
-0.0985 |
5 (13 el) |
0.99629λ |
25.0611 |
nr |
--- |
5 (16 el) |
0.98958λ |
30.9742 |
~31(2) |
0.0258 |
5 (24 el) |
1.00000λ |
46.8813 |
~47(2) |
0.1187 |
Notes: (1) Values marked with are estimated from the figures in [6]. (2) nr – not reported in [6]. (3) Values marked with ~ are estimated from Figure 13 in [6].
These data show that CFO essentially accurately recovered the global maximum for every one of the five PBM benchmark problems, with the caveat that it located only one of the four maxima for problem #3. This performance is better than any of the algorithms reported in [6]. None of those algorithms achieved 100% effectiveness. CFO therefore is very effective against the PBM antenna benchmarks.
3.2. Efficiency
An EA’s efficiency is measured by how computationally intensive it is. As the detailed results below show, CFO generally converges quickly, at least to the vicinity of a global maximum if trapping has not occurred. After its usually rapid rise, the best fitness often continues to increase, but much slower pace with only slight additional gains.
Here, efficiency is measured by the total number of calculations (objective function evaluations) required for the best fitness to saturate. The PBM paper examines four algorithms: i) GA-FPC, ii) μGA, iii) GA-RC, and iv) PSO (see [6] for details). The first three are GA variants, while the fourth is a particle swarm. Because these algorithms are stochastic, each one was run twenty times to develop statistics. The “mean hit time” in Table II in [6] is the average generation number at which the global maximum was located. Thus, the average number of function evaluations is the product of mean hit time and the population size. Table 5 shows this measure for the PBM algorithms, along with the total number of objective function evaluations for saturation of CFO’s best fitness [
, where
is the CFO step at which the fitness saturated, and
is the number of CFO “probes” (see §7.2)]. In Table 5, the best values are shown in bold red font, the second best in bold blue.
On problem #1 CFO performed much better than all the other algorithms, requiring only 60 calculations to locate the global maximum compared to 1530 for the next best algorithm, PSO. On problem #2, without and with noise, CFO did not perform as well as GA-FPC and μGA by a factor of about 2 to 3. CFO was on par with GA-RC, and it did substantially better than PSO. For problem #3, CFO out-performed all the algorithms except PSO, whose performance was about 17% better. Two different CFO initial probe distributions were used on problem #4, with the result that CFO’s performance was comparable to GA-FPC’s, and quite a bit better than μGA’s and GA-RC’s by at least a factor of 2. Compared to PSO, however, CFO did not do as well by a factor of about 3. Problems #5a and 5b in [6] (Table II) are 7 and 13 element collinear arrays, respectively [6] (p. 1119). For problem #5a CFO was nearly 15 times more efficient than the next most efficient algorithm, PSO. On problem #5b, CFO was more than 12 times more efficient, again compared to PSO.
Table 5. CFO efficiency (# function evaluations).
Problem # |
CFO
|
Results from PBM Paper [6], Table II (mean hit time x population) |
GA-FPC |
μGA |
GA-RC |
PSO |
1 |
60 |
3140 |
5065 |
8920 |
1530 |
2a [no noise] |
1320 |
360 |
450 |
1400 |
2280 |
2b [with noise] |
768 |
3 |
1050 |
1940 |
1685 |
5040 |
900 |
4 |
1488(1) 1155 |
1300 |
3125 |
3800 |
330 |
5a |
72 |
1220 |
1700 |
nr(2) |
1050 |
5b |
144 |
3480 |
5695 |
nr |
1770 |
Notes: (1) Different initial probe distributions; (2) Not reported in [6].
CFO therefore more than holds its own in terms of computational efficiency, especially for an algorithm that is not as highly developed as those reported in [6]. Out of six problems, CFO performed the best on three, out-performing the other algorithms by a very wide margin. On problem #3, CFO turned in the second best result, but it was close to the best efficiency. On problem #4, CFO was the second best performer. And on problem #2 it was the third most efficient algorithm. Across the six problems, CFO was best on three and second best on two. PSO turned in the next best overall performance, placing first on two problems and second on three. On the one problem where CFO did not finish in the top two, it was the third best. Thus, CFO has clearly proven to be very competitive in terms of efficiency.
4. A Pseudorandom CFO Using π Fractions
An important consideration in global search and optimization (GSO) is uniformity in randomly generated sample points because how well the decision space is sampled hangs in the balance. Sample points should be generated using a truly uniformly distributed random variable calculated from a probability distribution, but most pseudo random sequence generators fall short because their points in fact are not uniformly distributed (see the detailed discussion in [15]).
Design and optimization (D&O) problems in applied EM, in particular antenna D&O, often rely on global search and optimization metaheuristics based on Nature-inspired metaphors. Because these algorithms are inherently stochastic each run produces different results. These uncertain outcomes can be mitigated by pseudo randomly sampling the decision space. The π fractions provide a method for creating deterministic uniformly distributed decision space sample points.
4.1. π Fractions
The π fractions comprise a set of random numbers extracted from the mathematical constant π that are uniformly distributed on the interval [0,1). They are generated by the Bailey, Borwein, Plouffe (BBP) hexadecimal digit extraction algorithm [16]. In an inherently deterministic algorithm like CFO, the π fractions can improve DS exploration by adding a measure of pseudorandomness [17]. Used in an inherently stochastic algorithm like πGASR [15] the π fractions render an otherwise stochastic algorithm effectively deterministic.
A major advantage of determinism is that every optimization run with the same setup yields precisely the same results. This characteristic allows the algorithm designer to quickly and with certainty evaluate the effects of changes such as different run parameters or different fitness functions. By contrast, such evaluations using a stochastic algorithm require many independent runs, often hundreds or even thousands, to generate adequate statistics, and even then the results are imprecise because of their statistical nature. Having to make so many runs can be a very serious limitation in real-world optimization problems, especially ones that require relatively long-running external modeling engines such as NEC with highly segmented antennas [17].
Alternatives to the π fraction approach include using a compiler’s built-in random number generator or a separately coded routine employing the same “seed” value on successive runs in order to generate a repeatable sequence of ostensibly “random” numbers. These approaches, however, run the risk of creating undesirable bi-dimensional correlations in high dimensionality decision spaces, an effect seen, for example, in Halton and van der Corput low-discrepancy sequences [18] [19]. In many cases, the correlations are visually striking as seen in [20] [21]. In contrast, undesirable correlations in the π fractions are readily avoided by not using them in their order of occurrence [15].
In the present work, algorithms πCFO and πGASR [15] both employ the following π fraction pseudocode instead of using a compiler’s built-in random number generator. This procedure generates random real numbers a ≤ ri < b and mitigates the correlation problems discussed above (note that initialization values are completely arbitrary). Algorithm πGASR is based on the modified GA described in [22] to which π fractions have been added.
πi : {π fractions in order of occurrence; i=1,.., Nπ} Initialize: Nπ ← 215,830 : init1 ← 17 init2 ← 22 : inc ← 5 : i ← init1 Procedure Rπ: generates a random number in [a,b) using π fractions ri = a + (b-a) πi i ← i + inc if i > Nπ
i ← init2 End Pseudocode for π Fraction Random Numbers used in Algorithms πCFO and πGASR |
4.2. Utility of π Fractions in CFO
Under certain conditions, CFO is prone to trapping at local maxima or global maxima (for functions like PBM #3 that have multiple global maxima). When this happens oscillation in
(average distance, CFO probe with the best fitness and all other probes, see §7.2) appears to be a sufficient but not necessary indicator. Typically, the oscillation in Davg is on a plateau-like region, often flat but not necessarily. An example of this effect is seen in the 30-dimensional (
) Step function which is a standard benchmark defined as
,
,
. The Step is unimodal and highly discontinuous. In this paper, the usual global maximum of zero has been offset from the origin to the point
where
. Perspective plots of the 30-D step appear in Figure 1(a) and Figure 1(b) (entire domain and region of global maximum, respectively).
Using a π fraction IPD appears to defeat local trapping as shown in the
plots in Figure 2(a) and Figure 2(b) using, respectively, a uniform on-axis probe IPD and a random π fraction IPD. The oscillation associated with trapping is quite apparent in Figure 2(a), but none is evient in Figure 2(b). The first plot comprises two oscillatory plateaus connected by a substantial jump in Davg. But in contrast no such oscillation is evident in Figure 2(b).
(a)
(b)
Figure 1. (a) 2-D Step over domain; (b) 2-D Step near global max.
5. Algorithms Compared
Data from three algorithms, CFO, πCFO, and πGASR are compared to the published PBM data. The PBM suite was initially studied using completely deterministic CFO without π fraction pseudorandomness, although a measure of pseudorandomness was otherwise introduced as described in [23]. Initial probe accelerations were set to zero, the Repositioning Factor (
) was initialized and incremented deterministically, and a deterministic “Probe Line” Initial Probe Distribution (IPD) was used (for details see [23]). By contrast, the present version, πCFO, is pseudorandomized using π fractions to compute the initial probe accelerations,
, and the IPD. Run parameters were the same as in [15] with DS shrinking and early termination checking. Only one πCFO run was made for each benchmark because with π fractions algorithm remains completely deterministic.
The second randomized algorithm applied to PBM is πGASR (Genetic Algorithm with Sibling Rivalry, discussed in detail in [15]). Because the original GASR is inherently stochastic, calls to the compiler’s built-in random number generator were replaced by the π fraction procedure described above (run parameters otherwise the same as in [15]). The best πGASR fitness over multiple runs is reported here because the very purpose of using π fractions is to eliminate true randomness by replacing it with deterministic pseudorandomness.
(a)
(b)
Figure 2. (a) Uniform IPD; (b) π fraction IPD.
6. Comparison Results
Table 6 compares the best fitness results for algorithms CFO, πCFO and πGASR to the published PBM data. While there are slight differences, overall the maximum directivity data are quite similar for all five problems. Consistency is very high on PBM #5 and somewhat lower on the others. In all cases, the best fitness is close to the reported PBM data, but, as pointed out above, some (minor) questions arise concerning the accuracy of some of the published PBM results. A fair reading of these data is that all the tested algorithms provide maximum directivities close to the actual maxima, and that the π fraction approach is effective in making stochastic πGASR deterministic so that only a single run is actually required instead of many.
Table 6. Best fitness.
PBM Benchmark |
Maximum Directivity |
PBM |
CFO |
πCFO |
πGASR |
1 |
3.32 |
3.20627 |
3.24340 |
3.25837 |
2a (no noise) |
18.3(1) |
18.3654 |
18.2810 |
17.9473 |
2b (noisy) |
nr(2) |
18.6880 |
19.7609 |
18.8314 |
3 |
7.05(1) |
6.48634 |
6.57766 |
6.57658 |
4 |
5.8(1) |
5.71479 |
5.29663 |
5.29663 |
5 (6 el) |
~11.25(3) |
11.2202 |
11.2202 |
11.2202 |
5 (7 el) |
nr |
13.1826 |
13.0918 |
13.1826 |
5 (10 el) |
~19(2) |
19.0985 |
19.0985 |
19.0985 |
5 (13 el) |
nr |
25.0611 |
25.0035 |
25.0035 |
5 (16 el) |
~31(2) |
30.9742 |
30.9742 |
30.9742 |
5 (24 el) |
~47(2) |
46.8813 |
46.8813 |
46.8813 |
Notes: (1) Values estimated from the figures in [6]; (2) nr – not reported in [6]; (3) Values marked with ~ are estimated from Figure 13 in [6].
Coordinates for the best fitnesses are shown in Table 7. These data also show a high degree of consistency between the tested algorithms except for πGASR on PBM #2a where the
coordinate is different from the other two algorithms’. This disagreement also shows up to a lesser degree in πGASR’s maximum directivity in Table 2. On PBM #5 the dipole element separations are all close to 0.99λ with the greatest variability returned by algorithm πCFO. The differences in
, however, have no effect on the best fitness as seen in the remarkably consistent data in Table 6.
Table 7. Best fitness coordinates.
PBM Benchmark |
PBM |
CFO |
πCFO |
πGASR |
|
|
|
|
|
|
|
|
1 |
2.58λ |
0.63 |
2.5509λ |
0.6181 |
2.5896 |
0.6195 |
2.5845 |
0.6198 |
2a (no noise) |
~5.85λ |
1.5730 |
5.9236λ |
1.5569 |
5.9246 |
1.5554 |
6.9270 |
1.5467 |
2b (noisy) |
nr(1) |
nr |
6.9360λ |
1.5472 |
5.8877 |
1.5560 |
9.8907 |
1.5230 |
3 |
0.5 |
1.5730 |
0.4802 |
1.5733 |
2.4806 |
1.5611 |
1.5201 |
1.5704 |
4 |
1.5λ |
0.834 |
1.4952λ |
0.7110 |
1.4913 |
0.7176 |
1.4942 |
0.7317 |
Min/Max
|
5 |
0.99λ |
0.983/1λ |
0.974/1.199λ |
0.987/1λ |
Notes: (1) nr – not reported in [6].
π fractions have been shown to be an effective approach to mitigating the inconsistency inherent in stochastic global search and optimization. Here, the case for using π fractions is made by way of example using the PBM antenna benchmarks as representative real-world problems requiring an external modeling engine for fitness calculation. Stochastic algorithms require multiple runs to build meaningful statistics, often runs numbering in the hundreds or more. This requirement usually is not a limitation when optimizing analytical benchmarks because fast built-in routines are used, but it easily becomes a very significant impediment when a long-running external modeling engine is required as is often the case for real-world problems. π fractions address this concern by rendering deterministic (pseudorandom) an otherwise probabilistic optimizer so that only a single run is required. π fractions also are useful in inherently deterministic algorithms by injecting a measure of pseudorandomness that may improve an algorithm’s ability to explore the decision space.
7. The CFO Metaphor
There are many nature-inspired search and optimization EAs, as examples metaheuristics based on animal and insect behaviour, human population behaviour, or physical processes such as water drop pooling. Most of these algorithms are fundamentally stochastic because the processes they analogize are inherently random. In fact, their ability to locate maxima derives from this inherent randomness. Without it, these EAs cannot function, they fail completely.
CFO, by contrast, is completely deterministic because it is based on the metaphor of gravitational kinematics, the branch of physics that computes the motion of masses moving solely under the influence of gravity. Because gravity is deterministic, so too is CFO. This feature is a significant improvement over stochastic algorithms. Every CFO run with the same setup parameters returns precisely the same results. But, of course, as with all deterministic methodologies, the downside is a tendency for CFO to become trapped at local maxima. In fact, the two major issues in CFO’s further development appear to be (1) finding effective ways of mitigating trapping and (2) establishing a precise methodology for specifying run parameters. This section describes CFO’s basic equations and discusses these issues, in particular oscillation in
(defined below) as a harbinger of trapping and recent results in the astronomy literature that may be useful in understanding this phenomenon.
Even though CFO is fundamentally deterministic, the algorithm designer is free to inject some randomness if doing so improves performance. When local trapping occurs, pseudorandom perturbation of CFO’s “probe” distribution may mitigate the trapping. The judicious injection of some measure of randomness has not been investigated here, but it has been used in other CFO implementations with very good results [23]. The author emphasizes CFO’s deterministic nature because CFO is one of very few algorithms that provide true reproducibility and control over computed results. This characteristic may be especially useful in parameter-tuning implementations in which CFO’s run parameters are adjusted using real-time feedback such as discussed in [24]. Some CFO implementations may benefit from a pseudorandom component, and that possibility certainly merits consideration. In fact, in [23] it is recommended for all CFO implementations.
7.1. CFO, NEOs and Energy
This section asks an interesting question, but does not answer it: Is there a connection between the orbital trajectories of Near Earth Objects (NEOs) and CFO? The basis for this question is an obvious similarity between the required velocity curve to avoid Earth collision with an NEO and CFO’s “average distance” plot. The possibility of a connection is entirely speculative, and it is raised to hopefully encourage the research that may resolve it.
An NEO, for example a large asteroid, approaching planet Earth can become gravitationally “trapped” for a while. As a general rule, in the absence of friction or some other energy dissipation mechanism, an object’s trajectory will depend only upon its (constant) total energy. Recent work on gravitational “resonant returns” [25], however, shows that certain objects closely approaching the Earth can exchange energy with the planet without dissipation and, for some time at least, become gravitationally trapped in a tight orbit. If the orbit is such that the object passes through a small region of space known as a “keyhole”, then a collision with the Earth may occur. NEO’s not entering the keyhole cannot collide.
Many NEO’s are asteroids that fall into this category and can be quite large, for example Apophis with approximate dimensions 340 × 450 meters. If an object of solid rock with those dimensions impacts the Earth the result likely is catastrophic, possibly cataclysmic. One way to avoid such an encounter is to “nudge” the object into a different orbit by slightly changing its velocity. Extending the model in [25] Schweikart et al. [26] calculate the required velocity change for asteroid Apophis to avoid the keyhole. Figure 2 in [26], reproduced below with permission, plots the velocity change
required to modify the Apophis’ trajectory to avoid a collision with Earth as a function of when the encounter occurs (Figure 3).
Figure 3. Reproduction of Figure 2 in Schweickart [16].
The Apophis
plot is particularly interesting because of its unusual structure, two oscillatory plateau-like regions separated by a rapid rise in
. The oscillatory behaviour is a direct result of actual gravitational trapping in the physical Universe. An example is the MOID (Minimum Orbital Intersection Distance) plot in Figure 4 in [25] which shows a similar oscillatory behavior. When MOID is zero impact occurs.
Figure 4.
, 2D step function.
The CFO-NEO nexus is a strikingly similar appearance of some of CFO’s
plots. An example is provided by the two-dimensional Step function
,
whose
curve (average distance, CFO probe with the best fitness and all other probes) along with perspective views of the 2D Step.
Not only is the structural similarity between the Apophis
plot and CFO’s
self-evident, it is quite remarkable and not limited only to the cutves’ appearances. The Apophis
and the resulting distance nudge
are proportional, that is
,
being the time, the epoch of encounter, while the Step’s
is essentially the same quantity where the CFO run step number is in effect the time. Thus, the relationship between gravitational trapping in the real Universe and trapping near a maximum in metaphorical CFO space appears to be more than simply visual similarity. In the author’s opinion it is difficult to imagine that the Apophis curve, which is based on actual NEO gravitational trapping, and the CFO
curve, which is based on the metaphor of gravitational kinematics, are not manifestations of the same or, at a minimum, very similar underlying phenomena. Although admittedly speculative, the author believes that this similarity is compelling evidence of the validity of CFO’s gravitational metaphor, and that it might point the way to techniques for mitigating trapping. In particular, the analysis of Valsecchi et al. [25] may be directly applicable to improving CFO so that it avoids local trapping.
Another possible application of the conservative energy exchange between a small object and a larger gravitating mass in a trapping encounter is using the object’s total energy,
, as a measure of trapping. This suggestion, too, is speculative in nature, but it reflects what appears t be a strong correlation between real gravitational kinematics and CFO’s metaphorical search methodology. If the effect of gravitational trapping is to modify
, then with a suitable definition of energy in CFO space
may become a key factor in signalling trapping and possibly providing a mitigation mechanism simply by increasing its value. It may also be possible to re-formulate the basic CFO equations in terms of an energy model. Whether or not this approach has any merit is a question for researchers far more capable than the author, one that he hopes will be pursued.
7.2. The CFO Equations
CFO addresses the following problem: Locate the global maxima of the objective function
defined on the decision space (DS)
,
, the
being decision variables, where
the coordinate number, and
the space’s dimensionality (number of coordinates). Fitness refers to the value of
at the point
. The objective function’s topology, which is unknown, may be continuous or discontinuous, highly multimodal or unimodal, and possibly subject to a set of constraints
among the decision variables. While many optimization algorithms search for minima, CFO searches for maxima, that is, minimizing
.
CFO “flies” a group of “probes” through DS. Their trajectories are computed from the equations of motion for each probe’s acceleration and position vector. These equations are derived by generalizing Newton’s universal law of gravitation and law of motion from three-dimensional physical space to metaphorical
-dimensional “CFO space.” The resulting equations are [1]-[4]:
(1)
(2)
The probe number is
, and the time step (iteration) number is
, where
and
are the total number of probes and the total number of time steps, respectively.
is “probe”
’s acceleration at time step (iteration)
.
is its position vector at step
, where the
are probe
’s coordinates at step
, and
is the unit vector along the
axis. Note that the version of eq. (2) in [1] contains a “velocity” term not included in the CFO formulation in [3]. The velocity term was dropped because including it actually impeded convergence (reasons unknown). In [1], however, this term already had been set to zero as a matter of convenience, so that from the outset it never was required, and consequently is no longer included.
CFO “flies” its
probes through the decision space as a function of time (iteration number) along trajectories calculated using equations (1) and (2). A new probe distribution is computed at each step, and at the location of each probe the objective function’s fitness is computed. For example, at time step
at probe
’s location, the fitness is
. Note that
does not mean “mass” (see [1] for a discussion of the symbology). Each of the other probes has a fitness
, associated with it at step
.
The function
in eq. (1) is the Unit Step function,
. Following standard notation, the magnitude of vector
is
, where the
are its scalar components.
is CFO’s “gravitational constant,” and
the “time” interval between steps during which the acceleration is constant. It is important to remember that this terminology is chosen solely to reflect CFO’s gravitational metaphor, as is the factor
in eq. (2), and beyond that there is no significance to the nomenclature.
and
are the CFO exponents. While
and
have direct analogs in the equations of motion for gravitationally controlled real masses moving through physical space, there is no analog in Nature for
and
. They are included to provide added flexibility in how CFO is implemented by giving the algorithm designer the freedom to change how CFO’s “gravity” varies with mass or distance, or both, in order to achieve a more effective algorithm. Of course,
and
are perfectly acceptable parameters in metaphorical “CFO space,” because there gravity can be whatever the designer wants it to be.
The Unit Step function in eq. (1) is extremely important because it creates positive-definite CFO mass. Under the gravitational analogy on which CFO is based objects in CFO space have “mass” just as they do in the physical Universe. But unlike real objects, mass in CFO space is a user-defined function of the objective function’s fitness (not necessarily the fitness value itself). The problem is, depending on how the user defines that function, the mass can be positive or negative. And negative mass leads to serious problems!
In this paper CFO “mass,” by definition, is
, that is, the difference in fitness values raised to the
power multiplied by the Unit Step. The difference of fitnesses intuitively seems to be a good measure of how much “gravitational” influence the value of the objective function at one point in the decision space should have on a probe at another point in the space, but other choices certainly are possible. The exponent
is optional, giving the algorithm designer added flexibility as discussed above. In marked contrast, with the difference of fitnesses definition, the Unit Step is an essential element, because without it the mass could be negative depending on which fitness is greater. In the real world, gravity always is attractive because mass is positive. Negative mass creates a repulsive gravitational force that flies probes away from maxima, instead of the positive gravitational force required to fly probes toward them. This is just the opposite of what CFO is intended to do. The Unit Step solves the negative mass problem by creating positive-definite CFO mass and, consequently, a positive gravitational force that is always attractive.
A frequently used measure of how well CFO’s probes have clustered at a maximum is the average distance between the probe with the best fitness and all the other probes, normalized to the size of the decision space (length of the principal diagonal), that is,
where
is the number of the probe with the best fitness,
is the diagonal length, and
is probe
’s position vector at step
. Plotting
as a function of the time step is helpful in showing how the probe distribution evolves. As pointed out in §4.1, oscillation in
appears to be a sufficient but not necessary condition for local trapping of CFO’s probe with the best fitness.
7.3. A New “Hyperspace Directional Derivative”?
The Unit Step introduced in the definition of mass in §7.2 may be important in another, purely mathematical way. It may be the basis for defining a new type of “hyperspace directional derivative.” This idea is entirely speculative because no such mathematical operator currently exists, but the author believes it merits consideration if it is shown to be widely useful in addressing high-dimensionality optimization problems generally. In Nature, gravity is a conservative vector force field that produces “action at a distance”. While its fundamental equations are vector in nature, gravity also can be calculated as the gradient of a scalar potential function, just as the electric field is derived from an electric potential. The general notion of a “gradient” also applies in CFO space, but to some degree its utility depends on how mass is defined. For example, in this CFO implementation with
, the difference in fitness values divided by the distance between probes is essentially the square of the average slope, that is, the square of a derivative. When the Unit Step is included, this term, in a general sense, may be thought of as a sort of “generalized derivative”. However, with entirely different CFO mass definitions, or the present definition with different exponent values, this generalization may not be as apparent or compelling; but in this case it seems both clear and appropriate. This observation suggests the possibility of defining a new mathematical construct, a “hyperspace directional derivative”, that includes the Unit Step so that it always points towards an objective function’s maxima. The author makes this suggestion entirely on a speculative basis. As with the “energy” notions discussed in §7.1, whether or not this suggestion makes any sense is a question left to the mathematicians who hopefully will pursue CFO’s further development.
7.4. CFO Parameters
The CFO implementation described in this paper requires seven user-specified run parameters:
,
,
,
,
,
, and
. They are all defined above, except
, the “repositioning factor.” The probe initial acceleration could be used as an eighth parameter, but it is zero for all runs reported here.
is an algorithmic element and has nothing to do with fundamental CFO theory. For the specific CFO implementation used in this paper,
addresses the problem of errant probes. When equations (1) and (2) in §7.2 are used to compute a probe distribution, some “errant” probes may end up outside DS. When that happens the question is, how to get them back? There are many possibilities. For example, the decision space boundary could be made “reflecting” (probes bouncing back into the decision space) or “absorbing” (probes extinguished and replaced with a new ones), and so on. Another possibility is randomly re-initializing the errant probes’ locations, and most of these were tried during CFO’s early development. After evaluating various approaches a simple entirely empirical scheme was developed and is used here “
repositioning” where
is the “repositioning parameter”.
On a coordinate-by-coordinate basis, probes flying out of DS are placed a fraction,
, of the distance between the probe’s starting coordinate and the corresponding boundary coordinate. But because there is no obvious way to assign a value to
, the following simple, deterministic, perhaps clumsy, but workable approach was taken. At each step, the current and previous four fitness values were stored in a 5-element array.
started at a value of 0.5 and was incremented by 0.005 whenever the absolute value of the difference between 5th array element and elements 3, 4, and 5 differed by less than 0.0005. If incrementing
in this manner results in
, then it was reset to the starting value, and this procedure repeated with the then current probe distribution. If the data reported here are used for validation, it is important to note that the five saved fitness values are not necessarily sequential because of how the array index was computed (see pseudocode in Appendix B has details), which then affects when
is incremented.
’s starting value and increment, and the fitness tolerance were determined empirically, that is, on a trial and error basis, as are all CFO parameters used in this and the other CFO papers.
Of all the CFO parameters,
and
seem to have the greatest effect by far on the algorithm’s performance. The sensitivity to
is what led to the empirical scheme described above. Changing
generally improves convergence, because doing so avoids or terminates local trapping (this effect discovered empirically). The number of probes,
, determines how well the decision space is sampled, that is, how much information CFO has about the objective function at the start of a run. Numerical testing shows that CFO’s convergence frequently is a sensitive function of how many initial probes are deployed. Another related non-numerical factor is where the initial probes are placed. As some of the cases in §6 show, changing the initial probe distribution may make the difference between capturing the global maximum or missing it.
The question of how best to assign values to CFO’s run parameters is very important, yet it remains unanswered. At this point, there is no methodology to do that. Like most EAs, actually using the algorithm for a specific problem or class of problems, that is, setting up and making many runs, results in the user’s learning how to make best use of the algorithm, so specifying run parameters is done empirically. Some parameter values work better than others, and the experience gained by making many runs is reflected in the user’s choice of parameters in subsequent ones.
Of course, the result is that the user de facto becomes a part of the algorithm because every run includes a degree of subjectivity. Needless to say, it would be better to implement an EA using an objective methodology to specify run parameters, but there presently is none for CFO, or for that matter for most EAs. One significant advantage that CFO offers is its determinism. Results that are reproducible from one run to the next coupled with CFO’s frequently rapid convergence, even if to a local maximum, lend CFO to implementations that perform real-time parameter adjustments in response to a feedback mechanism. This sort of Reactive Search [24] may be particularly appropriate for CFO because the algorithm is fast and deterministic. It consequently is an extension that deserves consideration.
8. Why a Deterministic Optimizer?
When it comes to selecting an optimization program there are countless algorithms to choose from, almost all of which are stochastic in nature. The number of effective fundamentally deterministic algorithms is actually quite limited (see for example [27] for a list). In addition, an important distinction must be drawn between benchmark test functions and real-world problem objective functions, the kind of fitness functions that practicing engineers routinely face.
Real-world problems usually require a two-step solution whereas benchmark problems require only one. Optimization algorithms are almost always evaluated against benchmark suites for the very reason that the solutions are known in advance. An algorithm’s effectiveness is measured by the quality of its solutions (how close it comes to the known answers) and by the required computational effort (typically number of function evaluations). At no point is the fitness function itself an unknown, but this is almost always the case in real-world problems. As a consequence, the user, that is, the practicing engineer, must define a suitable objective function before any optimization can be done, and this added requirement makes solving the problem much harder because not all objective functions are well-behaved or for that matter yield good results even if they are. This dichotomy can be illustrated with a straight-forward example problem.
When the very form of the objective function is unknown the entire optimization process must be repeated for every candidate function. While this is not a fundamental limitation, as a practical matter in many real-world cases it turns out to be one that simply cannot be overcome because, again as a practical matter, computation times frequently become too long. Evaluating a benchmark test function like the Step is straightforward and quick because it requires only built-in functions (summation, floor, exponentiation), but real problems usually are quite different.
Real-world problems often require an external “modeling engine” that is frequently far more computationally intensive than using built-in functions. In antenna D&O, for example, Finite Element and Method of Moments codes are popular with their attendant long run times. And this limitation renders statistical evaluations of candidate fitness functions completely impractical. As an example, the run time for the 7303-segment vehicle-mounted antenna model shown in Figure 5 was 369 seconds on a 2.30GHz 8-core Core i7-3610QM machine using a multithreaded version of the Numerical Electromagnetics Code (NEC4/MP, [14]) under 64-bit Windows 7 [17]. An optimization run requiring, say, 1000 evaluations would take more than 102 hours, well over 4 days! And this must be repeated for each candidate fitness function!
Knowing that an algorithm is effective against the Step Function tells the practitioner absolutely nothing about how to formulate useful fitness functions and whether or not the algorithm will work well against those functions whatever form they may take. Stochastic algorithms make answers to this and related questions very difficult and consequently are frequently not well-suited to solving the real-world problems routinely encountered by practicing engineers. CFO solves addresses this dilemma, and π fractions offer the potential of turning purely stochastic algorithms into pseudorandom, hence deterministic, ones.
Figure 5. Vehicle-mounted antenna.
9. Conclusions
This paper describes Central Force Optimization, a deterministic, Nature-inspired evolutionary search and optimization metaheuristic that embraces the metaphor of gravitational kinematics. It reports the results of testing CFO against the PBM suite of antenna benchmarks. CFO acquits itself quite well, in many respects better than the more established EAs analyzed in the PBM paper [6]. CFO located all global maxima, even in a noisy decision landscape, and it did so with excellent efficiency. CFO generally performed better than the algorithms reported in [6].
This paper also highlights the striking similarity between velocity curves for Near Earth Objects in close encounters with planet Earth and CFO’s average distance curves in the presence of local trapping. The nature of these plots suggests that oscillation is a sufficient but not necessary condition for local trapping, and that the theory of gravitational “resonant returns” might be of use in better understanding and perhaps mitigating trapping.
The concept of “energy” in the gravitational metaphor was discussed, and suggestions made for its use as a test for local trapping and possibly a trapping mitigation mechanism. Also discussed was the possibility that CFO could be re-formulated on the basis of a “total energy” model.
Finally, this paper suggests the possibility of a new mathematical construct, a hyperspace “directional derivative” based on the Unit Step function that always points towards a function’s maxima. This idea is admittedly entirely speculative in nature because no such mathematical operator currently exists, yet the author believes it does merit consideration by mathematicians far more capable than he.
Acknowledgements
The author thanks the reviewers for their helpful comments that have improved this exposition. The author also wishes to acknowledge the following individuals who in various ways at various times have helped bring CFO to the attention of the optimization community. If CFO continues to realize what appears to be its considerable potential in no small measure it will be due to their interest and encouragement: Emeritus Professor Kusum Deep, Department of Mathematics, Indian Institute of Technology, Roorkee; Professor Mario Pavone, Department of Mathematics, University of Catania, Sicily, Italy; Professor Zhihua Cui, Taiyuan University of Science and Technology, Division of System Simulation and Computer Application, Taiyuan, Shanxi, China; Professor Nihad Dib, Department of Electrical Engineering, Jordan University of Science and Technology, Irbid, Jordan. If, on the other hand, CFO fails to meet this expectation then the responsibility is entirely the author’s.
Appendix A: PBM Benchmarks—Geometries, Landscapes & NEC4 Files
This section describes each PBM benchmark antenna and, for the 2D cases, its decision space using a perspective view of the topology. Additional perspective plots and projections onto the decision space’s principal planes as well as samples of the NEC4 input/output files used to generate the plots and to validate NEC4 are available online at the URL cited below.
A.1. Benchmark #1: Variable Length Center-Fed Dipole
The antenna geometry for Problem #1 is shown in Figure A1. The objective is to maximize a center-fed dipole’s directivity,
, as a function of its total length,
, and the polar angle,
. A perspective view of the 2D landscape appears in Figure A2 with additional plots available online at https://app.box.com/s/j6km9sy4udstujy5fx9e40p6ci70qs85 (the online data also include sample NEC4.1D input/output files). The topology is smoothly varying with a single global maximum and two local maxima of similar amplitude.
Figure A1. Dipole.
Figure A2. Benchmark #1 topology, perspective view.
A.2. Benchmark #2: Uniform Dipole Array
The problem #2 antenna is the uniform array of half-wave dipoles shown in Figure A3. All elements are center-fed with in-phase equal amplitude sources. The standard right-handed Cartesian coordinate system used by NEC4 is also shown, as are the polar angle
and azimuth angle
. The objective is to maximize directivity
in the plane
as a function of element separation
and polar angle
without and with the presence of additive Gaussian noise. Figure A4(a) shows the landscape without noise, and Figure A4(b) with it. Following [6], noise is generated by adding to the NEC4-computed directivity a normally distributed zero-mean, 0.2-variance random variable
, here computed using the Box Muller method [28] [29] as:
, where
and
, respectively, are the mean (zero) and standard deviation (0.4472), and
and
are random variables uniformly distributed on [0,1].
and
are generated using the compiler’s internal RND function [30] seeded with the CFO run’s start time.
![]()
Figure A3. Uniform array of half-wave center-fed in-phase dipoles.
(a)
(b)
Figure A4. (a). Uniform half-wave dipole array without noise, perspective view; (b) Uniform dipole array with additive gaussian noise, perspective view.
A.3. Benchmark #3: Circular Array of Half-Wave Dipoles
The antenna for problem #3 is the circular array of half-wave dipoles shown in Figure A5. The array comprises eight dipoles parallel to the z-axis uniformly deployed on a one-wavelength radius circle. All elements are center-fed by equal-amplitude sources; but, following [6], the phase varies as
,
. The unit-amplitude excitation therefore is
. The objective is to maximize the directivity
in the plane
as a function of the dimensionless phase parameter
and the polar angle
. The range for
produces the four global maxima at
seen in the perspective topology plot in Figure A6.
A.4. Benchmark #4: Vee Dipole
The Vee-dipole antenna for benchmark #4 is shown in Figure A7. The antenna comprises two arms of length
with inner angle
connected by a feed segment of length
fed at its midpoint. The objective is to maximize the directivity
along the +X-axis as a function of the total dipole length
and the inner half-angle
with
. Topology of benchmark #4’s decision space appears in Figure A8. This objective function is unimodal with a single global maximum at
. The surface is smoothly varying without pronounced local maxima.
Figure A5. Circular array of half-wave dipoles (1λ radius).
Figure A6. Circular array landscape, perspective view.
Figure A7. Vee dipole.
Figure A8. Vee dipole decision space topology, perspective view.
A.5. Benchmark #5: N-element Collinear Dipole Array
Benchmark #5 is a collinear array of
half-wave dipoles as shown in Figure A9. All elements are center-fed in-phase with equal amplitudes sources. The objective is to maximize directivity
in the plane
as a function of the element center-to-center spacings
. Because there are
spacings in an
array, the dimensionality of this problem is
, unlike the previous four benchmarks each of which is 2D. As discussed at length in [6], maximum directivity occurs at
independent of the number of elements, that is, with all dipoles spaced
regardless of the array size. Of course, the value of the directivity does depend on the array size, increasing approximately in proportion to the length.
Figure A9. Nel-element collinear dipole array.
Appendix B: CFO Pseudocode
As discussed in §7.4 specifying run parameters is an important consideration in setting up a CFO run. Some of that discussion is consequently repeated here. A CFO run requires seven user-specified parameters:
,
,
,
,
,
, and
, some of which appear to be more important than others. A possible eighth parameter is the initial probe acceleration, which is set to zero for all runs reported here and consequently is not included in this list. Constant values for
and
combine multiplicatively in a single coefficient, but of course these parameters could be separated and varied during a run. For the runs reported here,
because this value seems to provide good results for many test functions and may be good default values. In this paper, there is no change in fitness value or average probe distance between steps 0 and 1 because the initial acceleration is set to zero.
CFO is a simple algorithm that is easily implemented. These are the basic steps:
(a) compute initial probe positions and corresponding objective function fitnesses and assign initial accelerations
(b) successively compute each probe’s new position using equation (2) §7.2 based on previously computed accelerations using equation (1) §7.2
(c) verify that each probe is located inside the decision space, making corrections as required
(d) update fitness at each new probe position
(e) compute accelerations for the next time step using new positions
(f) loop over time steps or until termination criterion is met.
While the initial acceleration is zero for runs reported here, a non-zero value would “fly” probes in the directions of the accelerations at step 0 which may or may not improve performance. Because CFO may fly probes outside the DS domain into regions of unallowable solutions, any errant probes should be returned to the decision space. There are many possible retrieval schemes, and the one used here is simple and deterministic as described below and in §7.4. The repositioning factor,
, which is used to return errant probes, in fact is one of CFO’s most important parameters. When and how it should be changed are unanswered questions. The simple approach below seems to provide good results, and it was chosen solely for that reason.
Note that all CFO parameters presently are chosen on an empirical basis, that is, by “trial and error” because there is no methodology at this point for specifying their values. This question remains a pressing one in CFO’s further development. The parameter values that have been used provide good results for the purpose of demonstrating CFO’s effectiveness and efficiency as an optimization metaheuristic against the PBM suite, but these are not necessarily the best values.
CFO pseudocode is as follows with values for
and
are those used in this paper as shown:
(1) Data Structures
(A) Create arrays
[position vectors],
[accelerations],
,
,
[probe #, coordinate #, time step #]
(B) Create fitness array
(C) Create array of last
best fitnesses
(2) Initialization
At time step
:
(A) (i) Uniform probes on each coordinate axis (note:
, # probes/dimension, user-specified).
For
to
,
to
:
(A) (ii) Probes slightly off decision space diagonal
For
to
,
to
:
(A) (iii) Uniform 2D grid
,
; For
to
,
to
:
,
,
(A) (iv) Other user-specified probe distribution [Note—This option used for this paper]
(B) Initial acceleration
(C) Initial fitness
,
,
,
(D) Saved Fitnesses & Fitness Tolerance
,
,
(E) Initial Reposition Factor & Increment
(3) Time Loop (
)
(A) Saved Fitness Array Index:
; If
then
Important Note: Saved fitnesses are not necessarily sequential as a result of how s is calculated, which affects when Frep is incremented See discussion in §4.4.
New Probe Positions
For
to
,
to
:
(a)
(b) Retrieve errant probes as required (Note: For Repositioning Factor,
, see Formato [2]-[4])
If
then
If
then
(B) Update Fitness Matrix
For
to
:
If
then
&
(C) Update Reposition Factor
If
,
, then
If
then
(D) Update Accelerations
For
to
,
to
:
where
(E) Increment
, and repeat from (3)(A) until
or other stopping criterion has been met.