NONMEM Users Network Archive

Hosted by Cognigen

Re: Use AND to ignore rows for input dataset

From: Mark Tepeck <mark.tepeck>
Date: Mon, 23 Dec 2019 10:50:01 -0800

Hi Bob,

Thank you so much for your feedback. I am so glad to see that NONMEM 7.5
offers a full treatment to this issue, which would definitely improve
end-user experience.

I can find other guides but VIII at the root folder of
https://nonmem.iconplc.com/?token=8D25A977-25B2-11ea-A324-005056911489.
Would you please direct me to the right link to the latest version of guide
VIII?

Have a good holiday,

Mark

On Fri, Dec 20, 2019 at 10:42 AM Bauer, Robert <Robert.Bauer
wrote:

> Mark:
>
> The best solution would be if an additional ignore filtering can be done
> within a code record, so any degree of elaborate filtering can be done.
> For example:
>
>
>
> $INFN
>
> DATA_IGNORE=0
>
> IF(SEX==1 .AND. BW<30) DATA_IGNORE=1
>
> IF(AGE>10 .AND. AGE<70) DATA_IGNORE=1
>
> IF(GEN1==3 .OR. GEN2==10 .AND. GEN3>20) DATA_IGNORE=1
>
>
>
> This can be available in the next version NONMEM 7.5
>
>
>
> Guide VIII is kept up to date with the version. The date of guide VIII i=
s
> January 2018.
>
>
>
>
>
> 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
>
> Robert.Bauer
>
> www.iconplc.com
>
>
>
> *From:* Mark Tepeck <mark.tepeck
> *Sent:* Tuesday, December 17, 2019 8:21 PM
> *To:* Nmusers <nmusers
> *Cc:* Bauer, Robert <Robert.Bauer
> *Subject:* Re: [NMusers] Use AND to ignore rows for input dataset
>
>
>
> Hi Bob,
>
> Thanks for providing the solution applicable to some cases. Meanwhile,
> I would like to share my thoughts on this issue. My sole purpose is to
> make NONMEM even better.
>
> 1. Use of OR alone may be subject to a very limited utility. Actually,
> my scenario is way more complicated. E.g. I want to exclude the
> year-span between (10,18) and (60,70) from the pool of (0,90). I
> cannot find a solution with ACCEPT/OR for this case.
>
> 2. Implicit/default use of OR is quite counter-intuitive and could
> raise the NONMEM learning curve. As we all know, AND (instead of OR)
> is the widely implemented default operator, E.g., Google search and
> programming languages (like R package dplyr/filter). NONMEM developers
> may consider following this general practice.
>
> 3. A lot of solutions provided on this platform come from the Guide
> -VIII. They are still useful but seems cumbersome from the current
> perspective. While we stick to a six-year-old guide, we entered a new
> era of machine learning, artificial intelligence, self-driving car,
> smart phones, etc, technologies are evolving quickly to become much
> easier than ever to use. Maybe, we can make NONMEM more user-friendly
> as well by solving this long-standing issue. 😊 With this fixed=
,
> IGNORE can serve as a universal filtering command.
>
> I really appreciate your input and feel free to correct me if I am wrong.
>
> Mark
>
>
>
>
>
> ICON plc made the following annotations.
> -------------------------------------------------------------------------=
-----
>
> This e-mail transmission may contain confidential or legally privileged
> information that is intended only for the individual or entity named in t=
he
> e-mail address. If you are not the intended recipient, you are hereby
> notified that any disclosure, copying, distribution, or reliance upon the
> contents of this e-mail is strictly prohibited. If you have received this
> e-mail transmission in error, please reply to the sender, so that ICON pl=
c
> can arrange for proper delivery, and then please delete the message.
>
> Thank You,
>
> ICON plc
> South County Business Park
> Leopardstown
> Dublin 18
> Ireland
> Registered number: 145835
>
>

Received on Mon Dec 23 2019 - 13:50:01 EST

The NONMEM Users Network is maintained by ICON plc. Requests to subscribe to the network should be sent to: nmusers-request@iconplc.com.

Once subscribed, you may contribute to the discussion by emailing: nmusers@globomaxnm.com.