e04rdc reads in a linear semidefinite programming problem (SDP) from a file in sparse SDPA format and returns it in the form which is usable by functions e04rac (initialization), e04rec (linear objective function), e04rnc (linear matrix constraints), e04svc (solver) and e04rzc (deallocation) from the NAG optimization modelling suite.
The function may be called by the names: e04rdc or nag_opt_sdp_read_sdpa.
3Description
e04rdc is capable of reading linear semidefinite programming problems (SDP) from a text file in sparse SDPA format. The problem is captured and returned in the following form:
(1)
where denotes symmetric matrices and is a vector. The expression stands for a constraint on the eigenvalues of a symmetric matrix , namely, all the eigenvalues should be non-negative, i.e., the matrix should be positive semidefinite.
Please note that this form covers even general linear SDP formulations with multiple linear matrix inequalities and a set of standard linear constraints. A set of linear matrix inequalities
(2)
can be equivalently expressed as one matrix inequality (1)(b) in the following block diagonal form where the matrices create the diagonal blocks of :
In addition, notice that if all matrices belonging to the same block, say block , are themselves diagonal matrices (or have dimension ), the associated matrix inequality
(3)
actually defines a standard linear constraint
where and columns of the matrix are formed by the diagonals of matrices and , respectively. Precisely, and .
Alternatively, e04sac may be used to read the data file directly into a handle of the NAG optimization modelling suite.
3.1Sparse SDPA file format
The problem data is written in an ASCII input file in the SDPA sparse format which was first introduced in Fujisawa et al. (1998).
In the description below we follow closely the specification from Borchers (1999).
The format is line oriented. If more elements are required on the line they need to be separated by a space, a tab or any of the special characters ‘,’, ‘(’, ‘)’, ‘{’ or ‘}’. The file consists of six sections:
1.Comments. The file can begin with an arbitrary number of lines of comment. Each line of comment must begin with ‘"’ or ‘*’.
2.The first line after the comments contains integer , the number of variables. The rest of this line is ignored.
3.The second line after the comments contains integer , the number of blocks in the block diagonal structure of the matrices. Additional text on this line after is ignored.
4.The third line after the comments contains a vector of integers that give the sizes of the individual blocks. Negative numbers may be used to indicate that a block is actually a diagonal submatrix. Thus a block size of ‘’ indicates a block in which only the diagonal elements are nonzero.
5.The fourth line after the comments contains an -dimensional real vector defining the objective function vector .
6.The remaining lines of the file contain nonzero entries in the constraint matrices, with one entry per line. The format for each line is
where is the number of the matrix to which this entry belongs and specifies the block number within this matrix. Together, they uniquely identify the block . Integers and are one-based indices which specify a location of the entry within the block. Note that since all matrices are assumed to be symmetric, only entries in the upper triangle of a matrix should be supplied. Finally, should give the real value of the entry in the matrix. Precisely, .
In the text below and in the file listing (filelst) we use the word ‘token’ as a reference to a group of contiguous characters without a space or any other delimeters.
3.2Recommendation on how best to use e04rdc
(a)The input file with the problem needs to be opened for reading by x04acc ().
Setting might help with possible file formatting errors.
(b)Unless the dimension of the problem (or its overestimate) is known in advance, initially call e04rdc with , and . In this case, the exact size of the problem is computed and returned in nvar, nblk and nnz. No other data will be stored and the arrays cvec, nnza, irowa, icola, a, blksizea will not be referenced and may be NULL.
Then the exact storage can be allocated and the file reopened. When e04rdc is called for the second time, the problem is read in and stored in appropriate arrays.
(c)A typical sequence of calls to solve the problem read in by e04rdc might be as follows. First, an empty handle needs to be initialized by e04rac with nvar variables. This should be followed by calls to e04recande04rnc to formulate the objective function and the constraints, respectively. The arguments of both functions use the same naming and storage as in e04rdc so the variables can be passed unchanged; only dima in e04rnc is new and should be equal to
sum . nnzasum in e04rnc is the same as nnz in e04rdc. You may at this point want to modify option settings using e04zmc. If dual variables (Lagrangian multipliers) are required from the solver, sufficient space needs to be allocated. The size is equal to the sum of the number of elements of dense triangular matrices for each block. For further details, see the argument ua in the solver e04svc. The solver should be called and then followed, finally, by a call to e04rzc to deallocate memory associated with the problem.
4References
Borchers B (1999) SDPLIB 1.2, A Library of semidefinite programming test problems Optimization Methods and Software11(1) 683–690 http://euler.nmt.edu/~brian/sdplib/
Fujisawa K, Kojima M and Nakata K (1998) SDPA (Semidefinite Programming Algorithm) User's Manual Technical Report B-308 Department of Mathematical and Computing Sciences, Tokyo Institute of Technology.
5Arguments
1: – Nag_FileIDInput
On entry: the file identifier associated with the sparse SDPA data file. Note: that the file needs to be opened in read mode by x04acc with .
2: – IntegerInput
On entry: the upper limit for the number of variables in the problem. If , cvec and nnza will not be referenced and may be NULL.
Constraint:
.
3: – IntegerInput
On entry: the upper limit for the number of matrix constraints (i.e., the number of diagonal blocks within the matrix). If , blksizea will not be referenced and may be NULL.
Constraint:
.
4: – IntegerInput
On entry: the upper limit on the sum of nonzeros in all matrices
, for and . If , irowa, icola and a will not be referenced and may be NULL.
Constraint:
.
5: – IntegerInput
On entry: if , a listing of the input data is sent to stdout. This can be useful for debugging the data file.
If , no listing is produced.
6: – Integer *Output
7: – Integer *Output
8: – Integer *Output
On exit: the actual number of the variables , matrix constraints and number of nonzeros of the problem in the file. This also indicates the exact memory needed in cvec, nnza, irowa, icola, a and blksizea.
9: – doubleOutput
On exit: , for , stores the dense vector of the linear objective function. If , cvec is not referenced and may be NULL.
10: – IntegerOutput
On exit: , for , stores the number of nonzero elements in matrices . If , nnza is not referenced and may be NULL.
11: – IntegerOutput
12: – IntegerOutput
13: – doubleOutput
On exit: irowa, icola and a store the nonzeros in the upper triangle of matrices
, for , in the coordinate storage, i.e.,
are one-based row indices, are one-based column indices and are the values of the nonzero elements, for . See Section 9. If , the arrays are not referenced and may be NULL.
14: – IntegerOutput
On exit: , for , stores the sizes of the diagonal blocks in matrices from the top to the bottom. If , blksizea is not referenced and may be NULL.
15: – NagError *Input/Output
The NAG error argument (see Section 7 in the Introduction to the NAG Library CL Interface).
6Error Indicators and Warnings
NE_ALLOC_FAIL
Dynamic memory allocation failed.
See Section 3.1.2 in the Introduction to the NAG Library CL Interface for further information.
NE_BAD_PARAM
On entry, argument had an illegal value.
NE_DIAG_ELEMENTS
Invalid structural data found on line .
The specified element belongs to a diagonal block but is not diagonal.
The row index is and column index is .
NE_DUPLICATE_ELEMENT
An entry in the constraints with , , row index and column index was defined more than once. All entries need to be unique.
NE_FILE_INCOMPLETE
A premature end of the input stream. The part defining the dimensions of the blocks was not found.
A premature end of the input stream. The part defining the nonzero entries was not found.
A premature end of the input stream. The part defining the number of blocks was not found.
A premature end of the input stream. The part defining the number of variables was not found.
A premature end of the input stream. The part defining the objective function was not found.
NE_FILEID
On entry, .
Constraint: .
NE_INT
An invalid number of blocks was given on line .
The number stated there is and needs to be at least .
An invalid number of variables was given on line .
The number stated there is and needs to be at least .
NE_INT_ARG
On entry, .
Constraint: .
On entry, .
Constraint: .
On entry, .
Constraint: .
NE_INT_ARRAY
An invalid size of the block number was given on line .
The number stated there is and needs to be nonzero.
An internal error has occurred in this function. Check the function call and any array sizes. If the call is correct then please contact NAG for assistance.
See Section 7.5 in the Introduction to the NAG Library CL Interface for further information.
NE_INVALID_CS
Invalid structural data found on line .
The given column index is out of bounds, it must respect the size of the block. Its value must be between and (inclusive).
Invalid structural data found on line .
The given row index is out of bounds, it must respect the size of the block. Its value must be between and (inclusive).
Invalid structural data found on line .
The specified nonzero element is not in the upper triangle.
The row index is and column index is .
NE_INVALID_FORMAT
The token on line at position to was not recognized as a valid integer.
The token on line at position to was not recognized as a valid real number.
The token on line starting at position was too long and was not recognized.
NE_NO_LICENCE
Your licence key may have expired or may not have been installed correctly.
See Section 8 in the Introduction to the NAG Library CL Interface for further information.
NE_NOT_READ_FILE
The input stream seems to be empty. No data was read.
This might indicate a problem with opening the file, check that x04acc was used correctly.
NE_OUT_OF_RANGE
Invalid structural data found on line .
The given block number is out of bounds. Its value must be between
and
(inclusive).
Invalid structural data found on line .
The given matrix number is out of bounds. Its value must be between
and
(inclusive).
NE_READ_ERROR
Reading from the stream caused an unknown error on line .
NE_WRONG_NUM_TOKENS
Not enough data was given on line specifying block sizes.
Expected
tokens but found only .
Not enough data was given on line specifying nonzero matrix elements.
Expected tokens but found only .
Not enough data was given on line specifying the objective function.
Expected tokens but found only .
7Accuracy
Not applicable.
8Parallelism and Performance
Background information to multithreading can be found in the Multithreading documentation.
e04rdc is not threaded in any implementation.
9Further Comments
The following artificial example demonstrates how the elements of matrices are organized within arrays nnza, irowa, icola and a. For simplicity let us assume that , and . Please note that the values of the elements were chosen to ease readability rather than to define a valid problem.
All matrices have to be symmetric and, therefore, only the elements in the upper triangles are stored. The table below shows how the arrays would be populated.
Imagine that we want to store the following problem in a file in the SDPA format.
There are two variables () in the problem. One linear matrix constraint and one block of linear constraints can be formed as (1) with two diagonal blocks (). Both blocks have dimension but the first one (defining linear constraints) is only diagonal, thus the sizes will be stated as .
The problem can be rewritten as
where
The optimal solution is with the objective function value . The optimal Lagrangian multipliers (dual variables) are , and .
See also e04rac for links to further examples in the suite.