Journal of Applied Mathematics

Volume 2012 (2012), Article ID 946893, 21 pages

doi:10.1155/2012/946893

Research Article

An Interior Point Method for Solving Semidefinite Programs Using Cutting Planes and Weighted Analytic Centers

John Machacek¹ and Shafiu Jibrin²

¹Department of Computer Science and Engineering, University of Minnesota, Minneapolis, MN 55455, USA

²Department of Mathematics and Statistics, Northern Arizona University, Flagstaff, Arizona 86011-5717, USA

Received 11 October 2011; Revised 10 May 2012; Accepted 24 May 2012

Academic Editor: James Buchanan

Copyright © 2012 John Machacek and Shafiu Jibrin. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

Abstract.

We investigate solving semidefinite programs (SDPs) with an interior point method called SDP-CUT, which utilizes weighted analytic centers and cutting plane constraints. SDP-CUT iteratively refines the feasible region to achieve the optimal solution. The algorithm uses Newton’s method to compute the weighted analytic center. We investigate different stepsize determining techniques. We found that using Newton's method with exact line search is generally the best implementation of the algorithm. We have also compared our algorithm to the SDPT3 method and found that SDP-CUT initially gets into the neighborhood of the optimal solution in less iterations on all our test problems. SDP-CUT also took less iterations to reach optimality on many of the problems. However, SDPT3 required less iterations on most of the test problems and less time on all the problems. Some theoretical properties of the convergence of SDP-CUT are also discussed.

1. Introduction

We consider the semidefinite programming problem (SDP) as in [1]:

where . Also, , , and each is an symmetric matrix. The constraint is known as a linear matrix inequality or LMI. For a given matrix , denotes that is positive semidefinite. The notation is used when a matrix is positive definite. Semidefinite Programs (SDPs) are convex optimization problems [2], and they generalize many other convex optimization problems including linear programming. SDPs have applications in engineering and combinatorial optimization and other fields (see [2, 3]).

The dual of problem (1.1) is the optimization problem [1]:

In the above, denotes the matrix dot product. If and are matrices of size , then , where Tr denotes the trace. We let for all the feasible region and for all the interior of the feasible region. The set is precisely the set of all strictly feasible points. Let be the optimal solution to the primal problem (1.1), and let be the optimal solution to the dual problem (1.3). The duality gap is zero if either SDP (1.1)-(1.2) or its dual (1.3)–(1.5) is strictly feasible [2].

Several interior point methods have been developed for solving SDPs (see [2, 4, 5]). When developing our interior point method in this paper, we assume a strictly feasible interior point is known. There exist methods for finding feasible or near feasible points (see [6–8]). The algorithm we develop uses cutting planes and weighted analytic centers, and it iteratively refines the feasible region until the weighted analytic center approaches the optimal solution. We call our algorithm SDP-CUT. The cutting plane technique was pioneered by Gomory [9], Kelley [10], and also Cheney and Goldstein [11] for solving integer programming problems. An algorithm similar to our SDP-CUT for linear programs (LPs) was proposed by Renegar in his 1988 paper [12].

SDP-CUT is implemented using Newton’s method and different line search techniques. We found that Newton’s method with exact line search is the best implementation of our algorithm. The effects of a weight vector on the algorithm are also studied. A larger weight yields a faster and more accurate solution in theory, but in practice, too large a weight may cause numerical errors. We also experienced numerical errors in computing the Hessian matrices in SDP-CUT, when solving very large problems.

Since finding an interior point for an SDP problem is equivalent to solving another SDP problem, we decided to consider test problems with a known interior point and used that point as a starting point for SDP-CUT. We find SDPT3 to be an ideal method for comparison with SDP-CUT because it is known to be efficient and it allows the user to input a starting point. We found SDP-CUT was closer to the actual solution than SDPT3 for the initial iterations on all our test problems. SDP-CUT seems to slow down during later iterations to reach optimality. On the other hand, SDPT3 took less time on all the problems and less iterations on most of them. All codes were written in MATLAB version 7.9.0.

2. Weighted Analytic Center

This section discusses weighted analytic center as given in [13] and how to compute it. Other notions of weighted center for semidefinite programming are described in [14].

Given a weight vector , the weighted barrier function for our system of LMIs (1.2) is defined as follows:

Note that as approaches the boundary of the feasible region, approaches . We assume the set is linearly independent. The function is analytic and strictly convex over (see [13, 15]). The weighted analytic center is defined to be . We call the analytic center, where . In the case of linear constraints and some other more general LMIs, each weight pushes the analytic center away from the boundary of the corresponding constraint. The gradient and the Hessian are given by the following: for and

We will use the following specific example, SDP (2.3), to describe our method:

Weighted analytic centers for the LMI system (1.2) can be computed with the WAC-NEWTON algorithm described below. (Algorithm 1).

INPUT: point , weight vector , tolerance , and maximum

number of iterations

Set

while    do

    1.Compute the direction vector

    2.Compute the Newton decrement

    3.Compute stepsize

    4.

    if    then

        break while

    5.

OUTPUT:

Algorithm 1: WAC-NEWTON.

An efficient way to calculate the search vector in WAC-NEWTON is by finding the Cholesky factorization of and using it to solve the linear system . This is how is calculated in the SDP-CUT algorithm to be discussed in the next section and throughout this paper. Figure 1 shows the contours of , the effect of the weight vector on the barrier function, and the weighted analytic center. The figure uses the feasible region defined by SDP (2.3) and the associated barrier function. The weight of 3 on constraint (1) pushes the analytic center away from the boundary of constraint (1).

Figure 1: contours and with various weights .

3. The SDP-CUT Algorithm

This section describes the development of SDP-CUT. We also discuss WAC-NEWTON*, which implements Newton’s method for finding the weighted analytic center for the new system defined in SDP-CUT. The section finishes with algorithms for computing the Newton stepsize (CONSTANT, ELS, and BACKTRACKING).

Refer again to the example SDP (2.3). Here, we illustrate one iteration of SDP-CUT. Figure 2 shows the setup. We have the feasible region, an initial point , and a cutting constraint of the form that accompanies the point. Figure 3 shows the movement of the point to , the (weighted) analytic center of our new feasible region made up of the the cutting constraint and the original LMI constraints. Figure 3 also has the contour lines of the barrier function. The weight on the cutting constraint can be changed from 1 to other larger values.

Figure 2: The first cutting constraint and an initial point .

Figure 3: The weighted analytic center of new feasible region.

Given a system of LMI’s (1.2) and an objective function as in the primal SDP problem (1.1), we can numerically solve the problem by iteratively reducing the feasible set. Denote the current feasible region determined by our system of LMIs by , and suppose we know a strictly feasible point in . Initially, we set . We can find a new feasible region , where for all, . We do this by adding a new constraint cut . The is added to to ensure that is “strictly feasible” in the new system. Given weight , we define a new barrier function to account for this new constraint:

The gradient and the Hessian for this new barrier function are given by the following: for and :

Remark 3.1. Note that in the definition of in (3.1), weight is used on the original LMI constraints. The weight is used only on the new cutting constraint in order to push our point toward the optimal solution. (see Algorithm 2).

INPUT: , weight , , , and

Set

While    do

    1.Compute cutting plain constraint

    2.Let be the of new system with barrier function

    (3.1) to be computed by WAC-NEWTON* starting from the point

    Compute

    if    then

        break while

    3.

OUTPUT: ,

Algorithm 2: SDP-CUT.

If successful, SDP-CUT terminates with an optimal solution and optimal objective function value . Rather than moving the plane in Step 1 of SDP-CUT, the point could also be moved in the direction of to obtain a different starting point for some small , instead of . However, this can be problematic as we approach the optimal solution and the feasible region gets small. The point may pass over the entire remaining feasible region and thus fail to be feasible. If instead, we move the plane as originally suggested in SDP-CUT, will always be strictly feasible. Note that since the objective is to maximize and is an interior point, then is a feasible direction from .

We denote by WAC-NEWTON*, the WAC-NEWTON algorithm applied to (3.1) for determining in the SDP-CUT algorithm. WAC-NEWTON* will return the weighted analytic center of the current feasible region, which will be our next iterate for SDP-CUT. In WAC-NEWTON*, the stepsize can be computed in a variety of different ways as discussed in the next section.

3.1. Line Searches: Computing the Newton Stepsize in WAC-NEWTON* Algorithm

We describe different options for computing the Newton stepsizes in the WAC-NEWTON* algorithm. The algorithm first computes the direction vector . The Newton stepsize determines how far we should move in the direction of from the point .

The pure Newton’s method uses a constant stepsize . We will refer to this method of choosing the stepsize as “CONSTANT.” The CONSTANT algorithm has the advantage of not using computational time in deciding what stepsize to use. The disadvantage of Newton’s method with CONSTANT is that it usually results in the need to perform more iterations of WAC-NEWTON*, and it is possible to move out the feasible region. To get with exact line search, we solve the one-dimensional optimization problem:

where . Solving (3.4) is relatively easy and may cut the number of WAC-NEWTON* iterations in SDP-CUT, which are computationally harder in comparison

Let . Then

Let and . Then

Also,

Let be an eigenvalue of . Then

The function is convex function over , and the exact stepsize can be found using the Newton’s method. Equations (3.7) and (3.9) give two different ways of computing , when finding the exact stepsize. If one decides to use (3.7), the first and second derivatives of are required and given by

If (3.9) is used, the derivatives are simply given by

We will use ELS-MAT to denote the exact line search computations done using (3.7), and ELS-EIG if computations are done from (3.9).

In addition to constant stepsize = 1 and exact line search, another way that was considered in computing the Newton stepsize was backtracking. This method involves starting with a stepsize >= 1 and then, decreasing the stepsize until a stopping condition is met (see [5, 16]). This technique guarantees a sufficient decrease in , often starting from , in practice. (see Algorithm 3).

    INPUT: 0    1 and 0    0.5

    Set  = 1

    while  () > (0) + γ

    OUTPUT:

Algorithm 3: Backtracking.

It is known that Newton’s method converges quadratically close to the solution. In our case, WAC-NEWTON* converges rapidly for starting points that are not close to the boundary of the feasible region . Sometimes, we encounter difficulty when the starting point is too close to the boundary. Note that each time we make a new cut, our starting point is near the boundary. It is also the case, when SDP-CUT iterates approaches optimality. When close to the boundary, our direction vector often is very small, and thus a stepsize of may not make much progress. So, in these cases, the CONSTANT stepsize may spend many iterations, while making little progress, and each iteration wasting gradient and Hessian computations. Using the ELS algorithm, we find the proper stepsize and move out of this problem area in just one iteration. Consider the plots in Figure 4, which show the situation described above. Here, again, we are using SDP Example 2.3 and the point shown in Figure 2.

Figure 4: Need for different stepsizes.

As we can see from Figure 4 on the left, the best choice of stepsize is much greater than . In Figure 4 on the right, we can see that we have now moved into an area where a stepsize of is reasonable. BACKTRACKING will not help with this problem. BACKTRACKING only helps when the optimal stepsize is less than . If we try to adapt BACKTRACKING to help in the circumstance described above, we must initialize the BACKTRACKING stepsize to a large number, which creates two problems. First, when the optimal stepsize is close to , or smaller, we will waste time backtracking. Secondly, if we use a large initial stepsize, this may cause BACKTRACKING to send our point outside the feasible region, causing our algorithm to diverge. As it will be further shown in the next section, it does appear that ELS has a positive effect on SDP-CUT, while BACKTRACKING does not. Figure 5 has plots comparing how far CONSTANT and ELS move our point towards the optimal solution at each iteration. The plots highlight the “wasted iteration” problem with CONSTANT, which occurs when the optimal stepsize ismuch great than .

Figure 5: The “wasted iteration” problem.

4. Experiment I: SDP-CUT Implementations

We have implemented SDP-CUT in four ways, varying in how the Newton stepsize is computed: CONSTANT, ELS-MAT, ELS-EIG, and BACKTRACKING. We will compare the performance of these four implementations against various test problems. For each problem, the SDP-CUT parameters were set at , , , and .

4.1. Performance as Varies

Here, we left the number of variables constant at and varied the number of constraints from 2 to 10. The matrices have their sizes fixed at for all . For each value of , 10 SDP problems were randomly generated, and SDP-CUT was used to solve each problem. The number of SDP-CUT iterations (which we also call WAC-NEWTON* iterations) and run time for SDP-CUT were recorded for each problem. Figures 6 and 7 give plots of the averages with on the horizontal axis. The vertical axis in Figure 6 contains the total SDP-CUT iterations. In Figure 7, the vertical axis gives the total run time of SDP-CUT in seconds.

Figure 6: SDP-CUT iterations against the number of constraints .

Figure 7: Time as it varies with the number of constraints .

Figure 6 shows there is not a correlation between the number of LMI constraints and the number of SDP-CUT iterations (WAC-NEWTON* iterations) needed to find the optimal solution. Figure 6 also shows that ELS-EIG and ELS-MAT both effectively reduce the number of SDP-CUT iterations needed, while BACKTRACKING has about the same number of iterations as CONSTANT. Figure 7 shows that in the case of , ELS-MAT and ELS-EIG run the fastest, while BACKTRACKING runs far slower than anything else. Time increases as increases due to the gradient and Hessian computations. As we can see in formulas (3.2) and (3.3), for each constraint, we must perform matrix inverses, dot products, and multiplications. This makes each iteration computationally harder, but does not affect the iterations needed as is seen in Figure 6. BACKTRACKING’s time increases the most with due to the eigenvalue computation needed for the stopping condition. BACKTRACKING performs these extra computations, but SDP-CUT does not benefit from them, and consequently BACKTRACKING has the highest run time.

4.2. Performance as Varies

Here, we left the number of constraints constant at and varied the number of variables from 2 to 10. The matrices sizes were set at for all . For each value of , 10 SDP problems were randomly generated, and SDP-CUT was used to solve each problem. The number of SDP-CUT iterations (WAC-NEWTON* iterations) and run time for SDP-CUT were recorded for each problem. Figures 8, 9, and 10 are plots of the averages with on the horizontal axis. The vertical axis contains the SDP-CUT iterations (WAC-NEWTON* iterations) needed in Figure 8. The vertical gives the run time of SDP-CUT in seconds in Figure 9. There is also a third plot, Figure 10, which shows on the horizontal axis and the average time required to perform an iteration of SDP-CUT on the vertical axis.

Figure 8: SDP-CUT iterations against the number of variables .

Figure 9: SDP-CUT time as it varies with the number of variables .

Figure 10: Time required to perform an iteration of SDP-CUT.

Figure 8, again, shows that ELS-EIG and ELS-MAT are effective in reducing the number of SDP-CUT iterations needed, while BACKTRACKING fails to reduce the number of iterations needed. Figure 8 also shows a positive correlation between the number of SDP-CUT iterations (WAC-NEWTON* iterations) and . From Figure 9, we see that the exact line search reduces the total time needed for our algorithm, especially as gets larger. This is important, because as grows, the number of SDP-CUT iterations and the time required per iteration both increase (see Figure 10). For small , CONSTANT is quicker per SDP-CUT iteration, but as grows there is no noticeable difference in the time per iteration between CONSTANT or either ELS implementation. This is because the computations needed for the optimization problem (3.4) becomes so small compared to the computations need to compute and .

4.3. Performance as Varies

Here, we left the number of constraints constant at and the number of variables fixed at . We varied the matrix sizes from 5 to 60. The number of SDP-CUT iterations (WAC-NEWTON* iterations) and run time were recorded for each problem. Below are plots of the averages with on the horizontal axis. The vertical axis in Figure 11 contains the total SDP-CUT iterations (WAC-NEWTON* iterations) used to solve the problem. In Figure 12, the vertical axis gives the total run time of SDP-CUT in seconds. There is also a third plot, Figure 13, which shows on the horizontal axis and the time required to perform an iteration of SDP-CUT on the vertical axis.

Figure 11: SDP-CUT iterations with matrix size.

Figure 12: SDP-CUT time as it varies with matrix size.

Figure 13: Time required to perform an iteration of WAC-NEWTON*.

Figure 11, again, shows that ELS reduces the required number of SDP-CUT iterations (WAC NEWTON* iterations). However, as the size of the constraint matrices becomes large, the computations needed for the exact line search grow. Figure 12 shows the ELS-MAT is the fastest in the range of matrix sizes we tested. Unlike our other experiments, CONSTANT beats ELS-EIG. The reason for this is that the time per iteration of ELS-EIG grows very rapidly as is seen in Figure 13. This occurs because the computation of eigenvalues becomes increasingly difficult as the matrix grows in size.

ELS appears to be the best implementation of SDP-CUT. ELS is very effective in reducing the number of WAC NEWTON* iterations needed. ELS-MAT outperformed ELS-EIG in general. The eigenvalues allow for fast computation of the gradient and Hessian of once the eigenvalues are obtained (see (3.12) and (3.13)). However, the large cost of computing the eigenvalues outweighs this benefit, especially as the matrices become large. ELS-MAT uses a slower means of computing the gradient and Hessian of , but has no eigenvalue calculation overhead (see (3.10) and (3.11)). The slowest operation needed is matrix inversion. Matrix inversion becomes harder as the matrices get large, but it scales much better than finding the eigenvalues. It is conceivable that very large matrix situations could arise in which both ELS-EIG and ELS-MAT are too expensive; in this case it may be best to use CONSTANT. We were unable to find any cases in our test problems in which BACKTRACKING was beneficial. From now onwards, SDP-CUT will always refer to SDP-CUT with ELS-MAT implementation.

4.4. Convergence and the Weight , Leveling Off Effect

Increasing the weight will decrease the number of SDP-CUT iterations needed to find the optimal solution. A larger weight will also allow us to get closer to the optimal solution. However, if becomes too large, numerical errors will prevent convergence. Here, we will discuss the role plays in the rate of convergence, as well as how large we can make before SDP-CUT fails. Figure 4 graphically demonstrates the convergence of SDP-CUT on our example (SDP (2.3)) as the weight varies.

From the plots in Figure 14, we can visibly see that by increasing the weight, SDP-CUT moves toward the optimal solution faster. In attempts to see how fast SDP-CUT converges and what effect the weight has, we performed the following experiment. We ran SDP-CUT on the example and kept track of the iterates at each iteration. Below is a plot of shown on a scale against iterations as we varied the weight , where is the optimal solution. We see in Figure 15 that the distance from the estimate to the actual solution decreases exponentially, and linearly when shown on the scale. We found that in most cases our implementation of SDP-CUT breaks down around .

Figure 14: Convergence of SDP-CUT for and .

Figure 15: Convergence for various weights on a scale.

As we can see, increasing the weight means quicker convergence. However, Figure 15 only shows the first 10 iterations. As we approach the optimal solution, the rate of convergence slows and “levels off.” This is caused by the feasible region becoming very small and by moving the cutting constraint back by , and thus the SDP-CUT iterates stay in approximately the same place. This problem is demonstrated in Figure 16. We see that larger weights allow us to get closer to the optimal solution, but even with a larger weight our convergence “levels off.”

Figure 16: The “leveling off” effect.

One way to get closer to the optimal solution before the weighted analytic centers start to “levels off,” is to use a smaller . The difficulty with decreasing is if becomes too small, our SDP-CUT iterates come too close to the boundary, giving rise to “numerical problems,” especially in computing the Hessian matrices. We found that SDP-CUT worked with , but failed when in example SDP (2.3). The “numerical problems” are due to the fact that near the boundary, one of the LMI constraint matrices is near-singular, and we need to compute matrix inverses. Figure 17 shows what the “leveling off” effect looks like over the feasible region of SDP problem (2.3). Notice that the sequence of iterates , from SDP-CUT, reaches a limit before it reaches the boundary of the region.

Figure 17: The “leveling off” effect zoomed in on feasible region.

5. Experiment II: SDP-CUT versus SDPT3

In this section, the algorithms SDP-CUT and the well-known SDPT3 [17] method are compared on a variety of SDP test problems. Since SDPT3 is known to be efficient, we also used it to find the best possible estimation of the actual optimal objective function values. Another reason for using SDPT3 is its flexibility to allow the user to input a starting point.

For the experiment, we tested 20 SDP problems and solved each with SDP-CUT and SDPT3. Each SDP problem was randomly generated, where the dimension and number of constraints are random integers on the intervals and respectively. The size of each LMI is a random integer on . The values of and are listed in the table below. The values of are not given because they are too many. For example, SDP 1 has . The problems were generated in a way that makes the origin, an interior point for all of them. For all problems, we used tolerances , , , and a weight of was used with SDP-CUT. For the first 10 test problems, the iteration limit was . For the remaining 10 problem, the iteration limit is raised to . We record the total iterations performed for each algorithm as well as the time taken. The last two columns of the table below show the error in the calculated optimal objective function value compared to the actual value obtained from SDPT3 with no restriction on the number of iterations. In the table below, the suffixescut and SDPT3 are used to distinguish between values pertaining to SDP-CUT and SDPT3, respectively. , , and are used to denote the number of iterations, time, and absolute error, respectively. For example, .

We see in Table 1 that after 5 iterations, SDP-CUT gives a more accurate answer in all the first 10 test problems. However, if allowed to run for more iterations all the algorithms successfully found the optimal solutions, but SDPT3 took less number of iterations to reach optimality in 6 out of the 10 problems. Also SDPT3, took less time in all the 20 test problems. We believe the difference in times is partly because SDPT3 has over the years been optimized to run efficiently, while SDP-CUT is at a beginning of its development. It is interesting to note that SDP-CUT took fewer iterations in 4 out of the 10 problems.

Table 1: Data for experiment II: SDP-CUT versus SDPT3.

SDP

1
20
6
5
5
2.6842
0.1134
0.0814
0.8222

2
12
17
5
5
3.2816
0.0954
0.0126
0.7291

3
18
15
5
5
5.0180
0.0905
0.1053
0.1361

4
13
2
5
5
0.5383
0.0732
0.0116
0.0721

5
2
5
5
5
0.0714
0.0600
0.0000
0.0011

6
4
7
5
5
0.2779
0.0814
0.0006
0.1159

7
3
19
5
5
0.4144
0.0766
0.0001
0.4938

8
15
5
5
5
1.5041
0.0969
0.0423
0.1689

9
5
2
5
5
0.1164
0.0603
0.0013
0.5072

10
20
12
5
5
5.2449
0.0906
0.1425
1.3682

11
4
2
10
12
0.1457
0.1324
0
0

12
4
3
8
12
0.1536
0.1322
0
0

13
16
5
20
13
4.8852
0.1791
0
0

14
18
9
25
14
12.1776
0.2330
0
0

15
20
15
22
12
19.7580
0.1971
0
0

16
15
15
19
12
10.4692
0.2117
0
0

17
10
8
14
12
2.2191
0.1759
0
0

18
13
7
16
11
3.4501
0.1647
0
0

19
2
20
8
11
0.4571
0.1552
0
0

20
5
18
9
10
1.0308
0.1747
0
0

We need to do more work to make SDP-CUT more efficient. We noticed that the Hessian matrix in SDP-CUT is prone to errors in the case of problems that are very large. In those cases, loses its positive definiteness and thus its Cholesky factorization is not possible. That is the main reason why we could not run SDP-CUT on the SDP test problems at SDPLIB [18]. For example, SDP-CUT was not successfully in solving of SDPLIB, due to numerical problems when computing the Hessian matrices. This problem has variables and constraints. However, SDP-CUT was successful in solving , but with .

6. Convergence of SDP-CUT

Let be the sequence of estimates for generated by SDP-CUT. Let be the feasible region after -cuts. Thus, is the weighted analytic center of for all . Let be the sequence defined by .

The following theorem shows that when and are both small, then is also small. Note that when becomes very small, SDP-CUT is no longer making progress on the objective function values. This is especially true in the case of “leveling off” effect discussed in Section 4. This also indicates that our stopping criterion does not always mean convergence to the optimal solution.

Theorem 6.1. If , then .

Proof. Assume and use the Cauchy-Schwartz Inequality

How close we can get to the optimal solution depends on the parameters and . As becomes smaller we are able to obtain smaller regions, which allows SDP-CUT to get closer to the optimal solution. For a given region, a larger causes SDP-CUT push the estimate of the optimal solution further in the direction. For any choice of iterate , if we consider its limit as , we should be able to push as close to the optimal solution as we like. In practice, both the decrease and cause numerical problems. A question we propose is: in the limit as , how many iterations of SDP-CUT are needed for convergence?

Since the cutting plane is a linear constraint, it is possible that only one iteration is needed as (at least in some cases). Consider the following SDP (LP) example:

The feasible region of this example is given in Figure 18. Consider the point in the feasible region and the cutting constraint through this point. Also, consider the corresponding barrier function (3.1) and its gradient (3.2). At the weighted analytic center, the gradient is zero. This gives

It is clear from Figure 18 that the weighted analytic center has a negative value. So, the above equations show that the weighted analytic center is

We see that the weighted analytic center converges to the optimal solution as . This example suggests the following conjecture.

Figure 18: Feasible region of LP and the cut through the point .

Conjecture 6.2. SDP-CUT converges to as .

6.1. Scaling the Vector

Theorem 6.1 shows the dependence of on . Here, we will consider the effect of scaling on SDP-CUT. If we scale by such that we are now trying to optimize , we do not change the optimal solution . We will compare how close SDP-CUT gets when optimizing for various values of . Figure 19 is a plot of the results on the vertical axis and the scaling factor is on the horizontal axis. We used example SDP (2.3) with , , . We can see in Figure 19 that scaling the objective vector by a factor does have a positive effect on the accuracy of SDP-CUT.

Figure 19: The effect of scaling .

7. Conclusion

We have developed and studied a new interior point method, SDP-CUT, for solving SDPs. We found that implementing SDP-CUT using Newton’s method with exact line search, in general, gives the best performance. SDP-CUT appears to be very effective in getting into the neighborhood of the optimal solution as seen in problems 1–10 in Table 1. However, there is the “leveling off” effect shown in Figure 16. Future work on SDP-CUT can involve investigating Conjecture 6.2. Implementations that can handle a larger weight or smaller will result in better performance.

Another area for improvement is the stopping criteria. Currently, the stopping criteria is , which lets us know if we are no longer making progress. However, this does not always guarantee optimality of the solution. We have also shown that scaling the objective vector by some factor could allow SDP-CUT to give a better solution. Also, it is important to investigate how to make all the other components of SDP-CUT work well and efficiently. For example, we would like to find a way to compute the Hessian more efficiently and without errors. The way we compute the stepsizes in Newton’s method is an area that requires further attention. The exact line search we preferred over the others is probably too expensive and a better way may be possible. These improvements would allow us to test SDP-CUT on larger problems and compare it with other methods. It is also of interest to study what kind of problems SDP-CUT would work well or fail.

Acknowledgment

The first author would like the thank the National Science Foundation (NSF) for the opportunity to start initial work on this paper through their funding of the Research Experience for Undergraduates (REU) program at Northern Arizona University.

References

S. Jibrin, Redundancy in Semidefinite Programming: Detection and Elimination of Redundant Linear Matrix Inequalities, VDM, Saarbrucken, Germany, 2009.

L. Vandenberghe and S. Boyd, “Semidefinite programming,” SIAM Review, vol. 38, no. 1, pp. 49–95, 1996.

L. Vandenberghe and S. Boyd, “Applications of semidefinite programming,” Applied Numerical Mathematics, vol. 29, no. 3, 1999.

F. Alizadeh, “Interior point methods in semidefinite programming with applications to combinatorial optimization,” SIAM Journal on Optimization, vol. 5, no. 1, pp. 13–51, 1995.

S. Boyd and L. Vandenberghe, Convex Optimization, Cambridge University Press, New York, NY, USA, 2004.

R. J. Caron, T. Traynor, and S. Jibrin, “Feasibility and constraint analysis of sets of linear matrix inequalities,” INFORMS Journal on Computing, vol. 22, no. 1, pp. 144–153, 2010.

J. W. Chinneck, “The constraint consensus method for finding approximately feasible points in nonlinear programs,” INFORMS Journal on Computing, vol. 16, no. 3, pp. 255–265, 2004.

W. Ibrahim and J. W. Chinneck, “Improving solver success in reaching feasibility for sets of nonlinear constraints,” Computers & Operations Research, vol. 35, no. 5, pp. 1394–1411, 2008.

R. E. Gomory, “Outline of an algorithm for integer solutions to linear programs,” Bulletin of the American Mathematical Society, vol. 64, no. 5, pp. 275–278, 1958.

J. E. Kelley, Jr., “The cutting-plane method for solving convex programs,” Journal of the Society for Industrial and Applied Mathematics, vol. 8, no. 4, pp. 703–712, 1960.

E. W. Cheney and A. A. Goldstein, “Newton's method for convex programming and Tchebycheff approximation,” Numerische Mathematik, vol. 1, no. 1, pp. 253–268, 1959.

J. Renegar, “A polynomial-time algorithm, based on Newton's method, for linear programming,” Mathematical Programming, vol. 40, no. 1–3, pp. 59–93, 1988.

I. S. Pressman and S. Jibrin, “The weighted analytic center for linear matrix inequalities,” Journal of Inequalities in Pure and Applied Mathematics, vol. 2, no. 3, article 29, 2002.

C. B. Chua, “A new notion of weighted centers for semidefinite programming,” SIAM Journal on Optimization, vol. 16, no. 4, pp. 1092–1109, 2006.

S. Jibrin and J. W. Swift, “The boundary of weighted analytic centers for linear matrix inequalities,” Journal of Inequalities in Pure and Applied Mathematics, vol. 5, no. 1, article 14, 2004.

J. Nocedal and S. J. Wright, Numerical Optimization, Springer, New York, NY, USA, 2nd edition, 2006.

K. C. Tutuncu and M. J. Todd, On the Implementation and Usage of SDPT3-a Matlab Software Package for Semidefinite-Quadratic-Linear Programming Version 4, 2006.

B. Borchers and L. Vandenberghe, “SDPLIB 1.2, a library of semidefinite programming test problems,” Optimization Methods and Software, vol. 11-12, no. 1–4, pp. 683–690, 1999.