Re: Use AND to ignore rows for input dataset
Since nowadays most datasets include a header line, IGNORE=@ (or something
along those lines) is almost always used in control streams. Since ACCEPT and
IGNORE cannot be used in the same $DATA record, the suggested technique is
seldom usable in my experience.
Quoted reply history
________________________________
From: [email protected] <[email protected]> on behalf of
Bauer, Robert <[email protected]>
Sent: Monday, December 16, 2019 17:39
To: Nmusers <[email protected]>
Subject: RE: [NMusers] Use AND to ignore rows for input dataset
Guide VIII suggests the following:
Suppose it is desired that records be dropped that satisfy the logical ".AND."
of several conditions. This can be implemented by using an ACCEPT list with the
negations of the conditions. For example, suppose that records to be ignored
are those having GEN=1 .AND. AGE > 60. This may be done as follows:
ACCEPT=(GEN.NE.1,AGE.LE.60)
Robert J. Bauer, Ph.D.
Senior Director
Pharmacometrics R&D
ICON Early Phase
820 W. Diamond Avenue
Suite 100
Gaithersburg, MD 20878
Office: (215) 616-6428
Mobile: (925) 286-0769
[email protected]<mailto:[email protected]>
http://www.iconplc.com/
From: [email protected] <[email protected]> On Behalf Of
Sebastien Bihorel
Sent: Monday, December 16, 2019 12:39 PM
To: Mark Tepeck <[email protected]>; Nmusers <[email protected]>
Subject: Re: [NMusers] Use AND to ignore rows for input dataset
I would second that feature request!
________________________________
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> on behalf
of Mark Tepeck <[email protected]<mailto:[email protected]>>
Sent: Monday, December 16, 2019 15:16
To: Nmusers <[email protected]<mailto:[email protected]>>
Subject: [NMusers] Use AND to ignore rows for input dataset
Hi Colleagues,
Although there are many workarounds to manage the input datasets for NONMEM,
use of IGNORE would be a very handy solution. However, I am surprised to see
that AND is not supported by NONMEM. e.g. IGNORE=(CMT.EQ.1, AND CMT.EQ.2 )
would throw an error. In contrast, NONMEM use OR for IGNORE=(CMT.EQ.1,
CMT.EQ.2 ) by default, which is quite different for the common practice of
software.
I am wondering if the AND feature has been or will be implemented in the
last/future NONMEM version.
Thank you,
Mark