NONMEM Error on SAEM but not FOCEI
Clearly a bug in the $ABBR PROTECT processor. The NMTRAN interpreter removes
the *EXP(0) (because it does not modify the equation), which messes up $ABBR
PROTECT process. This occurs only with EXP(0), but not EXP(1) EXP(2), etc.
Work-arounds are:
KA = TVKA *EXP(-0)
or
ZERO=0.0
KA = TVKA *EXP(ZERO)
Robert J. Bauer, Ph.D.
Senior Director
Pharmacometrics R&D
ICON Early Phase
731 Arbor way, suite 100
Blue Bell, PA 19422
Office: (215) 616-6428
Mobile: (925) 286-0769
[email protected]<mailto:[email protected]>
http://www.iconplc.com/
Quoted reply history
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf
Of Mark Sale
Sent: Friday, January 26, 2024 10:59 AM
To: Leonid Gibiansky
<[email protected]<mailto:[email protected]>>; Jeroen
Elassaiss-Schaap (PD-value B.V.)
<[email protected]<mailto:[email protected]>>; Elashkar, Omar I.
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: [EXTERNAL] RE: [NMusers] NONMEM Error on SAEM but not FOCEI
An interesting undocumented feature of PROTECT. If you have EXP(0), e.g.,
KA = TVKA *EXP(0)
The fortran translation in this case apparently is:
KA=TVKA*PEXP(*)B000092
Which then throws a syntax error.
Doesn't happen without
$ABBR PROTECT
Not sure if that counts as a bug, but does prohibit using PROTECT in automated
methods to run models with/without BSV, or at least makes it a little more
difficult.
Mark Sale M.D.
Vice President
Integrated Drug Development
[email protected]<mailto:[email protected]>
Remote-Forestville CA
Office Hours 9 AM - 5 PM Eastern Time
+1 302-516-1684
http://www.certara.com