mpslst = .False. ! Or = .True.
Call e04mzf(infile,maxn,maxm,maxnnz,xbldef,xbudef,mpslst,n,m,nnz,iobj, &
if (ifail == 1 .Or. ifail == 2 .Or. ifail == 3) then
! not enough memory, allocate bigger arrays as given in m, n, nnz
! and call e04mzf again
else if (ifail >= 4 .And. ifail <= 16) then
! mps input file formating error
else if (ifail == 17) then
! wrong arguments to e04mzf
else if (ifail == 0) then
! data successfully read, call solver
mpslst = 0 ! or = 1
Call e04mxf(infile,maxn,maxm,maxnnz,maxncolh,maxnnzh,maxlintvar,mpslst, &
if (ifail == 2) then
! not enough memory, allocate bigger arrays as given in m, n, nnz, ncolh,
! nnzh, lintvar and call e04mxf again
else if (ifail >= 3 .And. ifail <= 35) then
! MPS input file formatting error
else if (ifail == 36) then
! wrong input argument
else if (ifail=-999) then
! internal memory allocation error
else if (ifail == 0 .Or. ifail == 1) then
! data successfully read (with possible warning)
start = 'C'
xs(j) = min(max(0.0_nag_wp,bl(j)),bu(j))
istate(j) = 0.0_nag_wp
! call solver
e04mxf has extended the functionality of e04mzf and the interface has changed substantially. If there are Integer variables, a quadratic part of the objective function or OBJSENSE section (see Section 3.1 in e04mxf), e04mxf will read them and return them in the new arguments (lintvar, intvar, ncolh, nnzh, h, irowh, iccolh and minmax), with e04mzf these caused a file formatting error. The new routine e04mxf might also accept a slightly misformatted input file and return a warning .
The type of the argument mpslst has changed from logical to integer.
The parameters xbldef and xbudef of e04mzf were removed and fixed in e04mxf to their default values and , respectively. Note that value within bounds is interpreted in our solvers as (unconstrained).
The routine may be called by the names e04mzf or nagf_opt_qpconvex1_sparse_mps.
e04mzf reads Linear Programming (LP) or Quadratic Programming (QP) problem data from an external file which is prepared in standard or compatible MPSX (see IBM (1971)) input format and then initializes (the number of variables), (the number of general linear constraints), the matrix , and the vectors , and (stored in row iobj of ) for use with e04nkf, which is designed to solve problems of the form
For LP problems, . For QP problems, you must set (see Section 5) and provide a subroutine to e04nkf to compute for any given vector . The optional parameter Maximize may be used to specify an alternative problem in which the objective function is maximized (see Section 12.1 in e04nkf/e04nka).
MPSX input format
The input file of data may only contain two types of lines:
1.Indicator lines (specifying the type of data which is to follow).
2.Data lines (specifying the actual data).
The input file must not contain any blank lines. Any characters beyond column 80 are ignored. Indicator lines must not contain leading blank characters (in other words they must begin in column 1). The following displays the order in which the indicator lines must appear in the file:
The ‘user-supplied name’ specifies a name for the problem and must occupy columns . The name can either be blank or up to a maximum of characters.
A data line follows the same fixed format made up of fields defined below. The contents of the fields may have different significance depending upon the section of data in which they appear.
The names and codes consist of ‘alphanumeric’ characters (i.e., a–z, A–Z, –, , , , blank ( ), :, $ or full stop (.) only) and the names must not contain leading blank characters. Values are read using Fortran format . This allows values to be entered in several equivalent forms. For example, , , and all represent the same number. It is safest to include an explicit decimal point.
Note that in order to ensure numeric values are interpreted as intended, they should be right-justified in the -character field, with no trailing blanks. This is because in some situations trailing blanks may be interpreted as zeros and this can dramatically affect the interpretation of the value. This is relevant if the value contains an exponent, or if it contains neither an exponent nor an explicit decimal point. For example, the fields
may be interpreted as and respectively (where % denotes a blank). The actual behaviour is system-dependent.
Comment lines are allowed in the data file. These must have an asterisk (*) in column 1 and any characters in columns 2–80. In any data line, a dollar sign ($) as the first character in Field 3 or 5 indicates that the information from that point through column 80 consists of comments.
Columns outside the six fields must be blank, except for columns 72–80, whose contents are ignored by the routine. These columns may be used to enter a sequence number. A non-blank character outside the predefined six fields and columns 72–80 is considered to be a major error (; see Section 6), unless it is part of a comment.
ROWS Data Lines
These lines specify row (constraint) names and their inequality types (i.e., , or ).
defines the constraint type. It may be in column 2 or column 3.
free row, that is no constraint. It may be used to define the objective row.
greater than or equal to (i.e., ).
less than or equal to (i.e., ).
exactly equal to (i.e., ).
defines the row name.
Row type N stands for ‘Not binding’, also known as ‘Free’. It can be used to define the objective row. The objective row is a free row that specifies the vector in the linear objective term . It is taken to be the first free row, unless some other free row name is specified by the names array (see Section 5). Note that is assumed to be zero if (for example) the line
(where % denotes a blank) appears in the ROWS section of the MPSX data file, and the row name DUMMYROW is omitted from the COLUMNS section.
COLUMNS Data Lines
These lines specify the names to be assigned to the variables (columns) in the general linear constraint matrix , and define, in terms of column vectors, the actual values of the corresponding matrix elements.
gives the name of the column associated with the elements specified in the following fields.
contains the name of a row.
used in conjunction with Field 3 contains the value of the matrix element.
is optional (may be used like Field 3).
is optional (may be used like Field 4).
Note that only the nonzero elements of and need to be specified in the COLUMNS section, as any zero elements of are removed and any unspecified elements of are assumed to be zero. In addition, any nonzero elements in the th column of must be grouped together before those in the th column, for . Nonzero elements within a column may however appear in any order.
RHS Data Lines
This section specifies the right-hand side values of the general linear constraint matrix (if any). The lines specify the name to be given to the right-hand side (RHS) vector along with the numerical values of the elements of the vector, which may appear in any order. The data lines have exactly the same format as the COLUMNS data lines, except that the column name is replaced by the RHS name. Only the nonzero elements need be specified. Note that this section may be empty, in which case the RHS vector is assumed to be zero.
RANGES Data Lines (optional)
Ranges are used for constraints of the form , where both and are finite. The range of the constraint is . Either or must be specified in the RHS section and must be defined in this section. The data lines have exactly the same format as the COLUMNS data lines, except that the column name is replaced by the RANGES name.
BOUNDS Data Lines (optional)
These lines specify limits on the values of the variables ( and in ). If the variable is not specified in the bound set then it is automatically assumed to lie between default lower and upper bounds (usually and ). Like an RHS column which is given a name, the set of variables in one bound set is also given a name.
specifies the type of bound or defines the variable type.
free variable ( to )
lower bound is
upper bound is . This is the default variable type.
identifies a name for the bound set.
identifies the column name of the variable belonging to this set.
identifies the value of the bound; this has a numerical value only in association with LO, UP, FX in Field 1, otherwise it is blank.
is blank and ignored.
is blank and ignored.
Note that if RANGES and BOUNDS sections are both present, the RANGES section must appear first.
IBM (1971) MPSX – Mathematical programming system Program Number 5734 XM4 IBM Trade Corporation, New York
1: – IntegerInput
On entry: the unit number associated with the MPSX data file.
2: – IntegerInput
On entry: an upper limit for the number of variables in the problem.
3: – IntegerInput
On entry: an upper limit for the number of constraints (including the objective row) in the problem.
4: – IntegerInput
On entry: an upper limit for the number of nonzeros (including the objective row) in the problem.
5: – Real (Kind=nag_wp)Input
On entry: the default lower bound to be used for the variables in the problem when none is specified in the BOUNDS section of the MPSX data file. For a standard LP or QP problem xbldef would normally be set to zero.
6: – Real (Kind=nag_wp)Input
On entry: the default upper bound to be used for the variables in the problem when none is specified in the BOUNDS section of the MPSX data file. For a standard LP or QP problem xbudef would normally be set to ‘infinity’ (i.e., ).
7: – LogicalInput
On entry: if , a listing of the input data is sent to the current advisory message unit (as defined by x04abf). This can be useful for debugging the MPSX data file. If , no listing is produced.
8: – IntegerOutput
On exit: , the actual number of variables in the problem.
9: – IntegerOutput
On exit: , the actual number of general linear constraints in the problem (including the objective row).
10: – IntegerOutput
On exit: the actual number of nonzeros in the problem (including the objective row).
11: – IntegerOutput
On exit: if , row iobj of is a free row containing the nonzero coefficients of the vector .
If , the coefficients of are assumed to be zero.
If , no such row was found and the routine terminates with or (see Section 6).
12: – IntegerOutput
On exit: . For QP problems, ncolh is the number of leading nonzero columns of the Hessian matrix and must, therefore, be set before calling e04nkf.
13: – Real (Kind=nag_wp) arrayOutput
On exit: the nonzero elements of , ordered by increasing column index.
14: – Integer arrayOutput
On exit: the row indices of the nonzero elements stored in a.
15: – Integer arrayOutput
On exit: a set of pointers to the beginning of each column of . More precisely,
contains the index in a of the start of the th column, for . Note that and .
16: – Real (Kind=nag_wp) arrayOutput
17: – Real (Kind=nag_wp) arrayOutput
On exit: bl contains the vector (the lower bounds) and bu contains the vector (the upper bounds), for all the variables and constraints in the following order. The first n elements of each array contain the bounds on the variables and the next m elements contain the bounds for the linear objective term and the general linear constraints (if any). Note that an ‘infinite’ lower bound is indicated by , an ‘infinite’ upper bound by and an equality constraint by . (The lower bound for , stored in , is set to . The corresponding upper bound, stored in , is set to xbudef.)
Note that e04mzf uses an ‘infinite’ bound size of in the definition of and . In other words, any element of greater than or equal to will be regarded as (and similarly any element of less than or equal to will be regarded as ). If this value is deemed to be ‘inappropriate’, you are recommended to reset the value of the optional parameter Infinite Bound Size and make any necessary changes to bl and/or bu before calling e04nkf.
18: – Character(1)Output
On exit: and an internal Crash procedure will be used by e04nkf to choose an initial basis.
19: – Character(8) arrayInput/Output
On entry: a set of names associated with the MPSX form of the problem.
Must contain either the name of the problem or be blank.
Must contain either the name of the objective row or be blank (in which case the first objective free row is used).
Must contain either the name of the RHS set to be used or be blank (in which case the first RHS set is used).
Must contain either the name of the RANGE set to be used or be blank (in which case the first RANGE set (if any) is used).
Must contain either the name of the BOUNDS set to be used or be blank (in which case the first BOUNDS set (if any) is used).
On exit: a set of names associated with the problem as defined in the MPSX data file as follows:
Contains the name of the problem (or blank if none).
Contains the name of the objective row (or blank if none).
Contains the name of the RHS set (or blank if none).
Contains the name of the RANGE set (or blank if none).
Contains the name of the BOUNDS set (or blank if none).
20: – IntegerOutput
On exit: , the total number of variables and constraints in the problem.
21: – Character(8) arrayOutput
On exit: the MPSX names of all the variables and constraints in the problem in the following order. The first n elements contain the MPSX names for the variables and the next m elements contain the MPSX names for the objective row and general linear constraints (if any). Note that the MPSX name for the objective row is stored in .
22: – Real (Kind=nag_wp) arrayOutput
On exit: a set of initial values for the variables and constraints in the problem. More precisely,
, for .
23: – Integer arrayOutput
On exit: a set of initial states for the variables and constraints in the problem. More precisely,
if and otherwise, for .
24: – IntegerInput/Output
On entry: ifail must be set to , or to set behaviour on detection of an error; these values have no effect when no error is detected.
A value of causes the printing of an error message and program execution will be halted; otherwise program execution continues. A value of means that an error message is printed while a value of means that it is not.
If halting is not appropriate, the value or is recommended. If message printing is undesirable, then the value is recommended. Otherwise, the value is recommended. When the value or is used it is essential to test the value of ifail on exit.
On exit: unless the routine detects an error or a warning has been flagged (see Section 6).
6Error Indicators and Warnings
If on entry or , explanatory error messages are output on the current error message unit (as defined by x04aaf).
Errors or warnings detected by the routine:
Note: the error exits to are caused by having either a corrupt or a nonstandard MPSX data file. Refer to Section 3 for a detailed description of the MPSX format which can be read by e04mzf. If , the last line of printed output refers to the line in the MPSX data file which contains the reported error.
Too many rows. Limit is , but the actual number required is .