Colleagues
My apologies — my question reflected a (complicated) error on my part. NMTRAN
/ NONMEM were doing the correct thing.
Of note, Leonid proposed using .EQN — that does not appear to be necessary.
Dennis
Dennis Fisher MD
P < (The "P Less Than" Company)
Phone / Fax: 1-866-PLessThan
n (a1 ==a2) is FALSE.
>
> Regards,
> Sergei Leonov
> ICON Innovation Center
>
> From: owner-nmus...@globomaxnm.com [mailto:owner-nmus...@globomaxnm.com] On
> Behalf Of Bill Denney
> Sent: Thursday, August 24, 2017 6:45 PM
> To: Dennis Fisher; nmusers@globomaxnm.com
ssion (a1 ==a2) is FALSE.
Regards,
Sergei Leonov
ICON Innovation Center
From: owner-nmus...@globomaxnm.com [mailto:owner-nmus...@globomaxnm.com] On
Behalf Of Bill Denney
Sent: Thursday, August 24, 2017 6:45 PM
To: Dennis Fisher; nmusers@globomaxnm.com
Subject: RE: [NMusers] Use of ACCEPT in $DATA
Similar to Bill, I also have an inelegant, but workable, solution, which is
to brute force the ignore times by templating them in R.
For example, you can use a simple glue template to churn out ignore
statements. For simplicity this could then be then just copied into control
streams.
Hi Dennis,
I don’t have an elegant solution for you (and I’ve been pining for the use
of combined Boolean operations like “TIME.GT.5.9.AND.TIME.LT.6.1” for a
long time).
An inelegant solution could be to run the model once with a write statement
to see if you can identify the value like
from the manual:
"When the IGNORE option is used to filter records from the input file,
the .EQ., =, .NE., and /= symbols perform literal string comparisons. To
provide a numerical equality comparison, use .EQN. for numerical equals,
and .NEN. for numerical not equals."
May be there is a
