RE: Wrong columns in $TABLE output

From: Robert Bauer Date: October 29, 2019 technical Source: mail-archive.com
Dear nmusers: In response to Tim Waterhouse’s observation, when LVR is set with $SIZES to a value greater than 93, NMTRAN provides the incorrect index numbers to the advanced diagnostic items (CWRES, CPRED, NPDE, etc.) requested by the user on $TABLE. This results in diagnostic items being printed that were not requested by the user. For a fix for this, please read item 10 listed in nm743_bug_list.pdf located at https://nonmem.iconplc.com/nonmem743 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/
Quoted reply history
From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tim Waterhouse Sent: Friday, October 18, 2019 7:26 AM To: [email protected]<mailto:[email protected]> Subject: [NMusers] Wrong columns in $TABLE output Dear nmusers, I'm running into a problem where NONMEM is giving me the wrong columns in the table output for a particular model. E.g. if I request CWRESI as an item in $TABLE, it will return CPREDI. CWRES becomes CPRED, NPDE becomes EIPRED, and so on. It's a fairly large BAYES model, with 27 THETAs, 32 OMEGAs (including IOV on several parameters), plus priors. If I simplify the model slightly by removing a few parameters NONMEM will give me the correct table columns. What might be causing this issue? Many thanks in advance, Tim
Oct 18, 2019 Tim Waterhouse Wrong columns in $TABLE output
Oct 18, 2019 Robert Bauer RE: Wrong columns in $TABLE output
Oct 29, 2019 Robert Bauer RE: Wrong columns in $TABLE output