Hi Bob,

Thanks for this confirmation.  I'm using 7.4.1.

For my other question, is there a limitation of $ABBR REPLACE which prevents 
its use for parameters like F1 and ALAG1?

Thanks,

Bill

> On Jan 24, 2018, at 00:43, Bauer, Robert <[email protected]> wrote:
> 
> This bug has been  fixed since NONMEM 7.4
>  
>  
> Bug #1, nm730_bug_list.pdf in https://nonmem.iconplc.com/nonmem730
> Two variables with names longer than six characters, and identical in the 
> first six characters, defined in $PK, and used in $DES, will be seen as the 
> same variable.  Use variable names that differ in the first six characters. 
> This occurs in NONMEM 7.1.0, 7.1.2, 7.2.0, and 7.3.0.  A workaround is to 
> move all assignment statements for variables whose first 6 characters match 
> to $DES.
>  
> 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]
> www.iconplc.com
>  
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Bill Denney
> Sent: Tuesday, January 23, 2018 4:40 PM
> To: Luann Phillips
> Cc: nmusers
> Subject: RE: [NMusers] $ABBR REPLACE Limitations?
>  
> Hi Luann,
>  
> I’m not having similar problems with other parameters with >6 characters.  I 
> had a similar issue with ALAG1, so I think that there are limitations on what 
> types of variables you can remap.  (Perhaps Allison or Bob could confirm?)
>  
> Thanks,
>  
> Bill
>  
> From: Luann Phillips [mailto:[email protected]] 
> Sent: Tuesday, January 23, 2018 3:51 PM
> To: Bill Denney <[email protected]>
> Cc: nmusers <[email protected]>
> Subject: Re: [NMusers] $ABBR REPLACE Limitations?
>  
> Bill,
>  
> I know at one time NM had a bug (haven't checked to see if it has been fixed) 
> that would cause variables with the first 6 characters the same to be 
> interpreted as the same variable even when later characters differed. I 
> wonder if this is a similar issue?
> Have you tried a shorter variable name, such as FCD1GUT=F1?
>  
> Just a thought,
> Luann
>  
> From: "Bill Denney" <[email protected]>
> To: "nmusers" <[email protected]>
> Sent: Tuesday, January 23, 2018 2:15:32 PM
> Subject: [NMusers] $ABBR REPLACE Limitations?
>  
> Hi,
>  
> I’m working in NONMEM 7.4.1 with a model where I need to track 4 drugs 
> simultaneously.  To increase the model quality, I’m making heavy use of $ABBR 
> REPLACE to keep track of THETA, ETA, and CMT numbers.  I traced an issue with 
> my model where there was no gradient on a bioavailability term to the fact 
> that this substitution didn’t seem to be working:
>  
> $ABBR REPLACE FCMTD1GUT=F1
> …
> $PK
> …
> FCMTD1GUT = THETA(1)
>  
> FCMTD1GUT didn’t seem to be effectively replaced to F1, so the 
> bioavailability parameters had no effect.  When I changed it to just directly 
> name F1, it worked as expected.
>  
> $PK
> …
> F1 = THETA(1)
>  
> It’s not obvious from the $ABBR REPLACE section of the manual that this is a 
> limitation of $ABBR REPLACE.  Is this an issue or am I missing something?
>  
> Thanks,
>  
> Bill
>  
> <image001.jpg>William S. Denney, PhD
> Chief Scientist, Human Predictions LLC
> +1-617-899-8123
> [email protected]
> This e-mail communication is confidential and is intended only for the 
> individual(s) or entity named above and others who have been specifically 
> authorized to receive it. If you are not the intended recipient, please do 
> not read, copy, use or disclose the contents of this communication to others. 
> Please notify the sender that you have received this e-mail in error by 
> replying to the e-mail or by calling +1-617-899-8123. Please then delete the 
> e-mail and any copies of it. Thank you.
>  
> 
> 
> 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 the 
> 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 plc 
> 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 
> 

Reply via email to