$SIZES
Array sizes for NONMEM and PREDPP.
|
|
Discussion
$SIZES is optional. If present, it must precede the first $PROBLEM or
$SUPER record.
Certain constants are used in NM-TRAN, NONMEM and PREDPP. With NONMEM
7.2 and higher, the user may override many of the constants with the
$SIZES record.
See the discusion of sizes for a discussion of how these constants are determined, and how they are communicated to NONMEM and PREDPP. (See SIZES,FSIZES,PRSIZES)
Any non-zero value (0 values are ignored) specified on the $SIZES record overrides both the
default and the value that NM-TRAN would have specified. As of NONMEM 7.3, as an alternative to modifying
sizes.f90 to very large maximum sizes, you can tell NMTRAN the maximum
size that may be needed by specifying a $SIZES constant as a negative
value. Thus, a user can give NMTRAN permission to deal with all problems that have data input files that have up to 1000 data items, and
up to 150 ETAs and EPSILONs, and up to 200 THETAs, by the following:
|
|
but the values of these constants when the NONMEM executable is constructed will be only what is needed for the particular problem. In contrast,
|
|
will result in sizing the NONMEM executable with these values, and won't make a "tailor fit". This would result in a very large executable regardless of the model size. Thus,
|
|
tells NMTRAN that you may need as many as 1000 data items in a data file, whereas
|
|
tells NMTRAN that you need exactly that size.
List of $SIZES Record Options and Their Default Values
|
|
See resource/SIZES.f90 for additional constants that may be set with $SIZES.
(See SIZES, FSIZES, PRSIZES).