RE: [EXTERNAL] Continuation of "What does "Second Error signal from LINV1PD: 129"
For parallel mode you need to issue a
sig subject
in your run directory
Robert J. Bauer, Ph.D.
Senior Director
Pharmacometrics R&D
ICON Early Phase
731 Arbor way, suite 100
Blue Bell, PA 19422
Office: (215) 616-6428
Mobile: (925) 286-0769
[email protected]<mailto:[email protected]>
http://www.iconplc.com/
Quoted reply history
From: Leonid Gibiansky <[email protected]>
Sent: Friday, September 16, 2022 5:42 PM
To: Bauer, Robert <[email protected]>; nmusers <[email protected]>
Subject: Re: [EXTERNAL] [NMusers] Continuation of "What does "Second Error
signal from LINV1PD: 129"
Thank you, Bob!
Ctl-T command is not working in parallel mode (on my Windows 10 system)
but it worked perfectly fine in the single-processor mode.
Thank you
Leonid
On 9/16/2022 5:21 PM, Bauer, Robert wrote:
> Leonid:
> You can enter ctrl-T to see OFV outputs of each subject, and you can
> note which of the subjects is issuing an LNV1PD: 129 error. The error
> issues first, then the subject number is shown.
>
> Robert J. Bauer, Ph.D.
> Senior Director
> Pharmacometrics R&D
> ICON Early Phase
> 731 Arbor way, suite 100
> Blue Bell, PA 19422
> Office: (215) 616-6428
> Mobile: (925) 286-0769
> [email protected]<mailto:[email protected]>
> <mailto:[email protected]>
> http://www.iconplc.com
> http://www.iconplc.com http://www.iconplc.com
>
> -----Original Message-----
> From: [email protected]<mailto:[email protected]>
> <mailto:[email protected]>
> <[email protected]<mailto:[email protected]>> On Behalf
> Of Leonid Gibiansky
> Sent: Friday, September 16, 2022 12:57 PM
> To: nmusers <[email protected]<mailto:[email protected]>>
> Subject: [EXTERNAL] [NMusers] Continuation of "What does "Second Error
> signal from LINV1PD: 129"
>
> Hi Nick and Bob,
>
> There was a thread in 2010 about LINV1PD: 129 error, see below.
> Is it possible to get ID(s) of the subject(s) with the problem or
> extract any other useful information to debug the issue? I am using
> ADVAN5 with LAPLACIAN option (with PROTECT), are there any tricks that
> would help to avoid or debug the problem? The iterations move forward in
> spite of multiple error messages that continue to appear through the
> whole run, and the model provided the parameters and predictions, and
> even completed the covariance step but it would be helpful to find out
> what causes the error.
>
> Thank you
> Leonid
>
> ===================================================================
> Nick:
> It means that a positive definiteness correction on the eta Hessian
> matrix of a particular individual at a particular iteration was not
> successful, but NONMEM goes ahead anyway. If it happened on an
> intermediate iteration, and the error signal was not continually
> repeated, then NONMEM managed to get through the numerical rough spot,
> and there is not likely a systematic issue to the problem.
>
>
> Robert J. Bauer, Ph.D.
> ______________________________
> Sent: Friday, November 19, 2010 7:16 PM
> To: nmusers
> Subject: [NMusers] What does "Second Error signal from LINV1PD: 129"
> mean?
>
>
> Hi,
> I'm using NM7.1.2
> $EST MAX=9990 NOABORT NSIG=3 SIGL=9 PRINT=1 METHOD=CONDITIONAL LAPLACIAN
> SLOW $SUBR ADVAN6 TOL=6 Predictions are made using F_FLAG=0 and F_FLAG=1
>
> I get this message I have never seen before. It happens with one
> particular model that is closely related to others that run Ok. The
> model with this error seems to run Ok and produces plausible parameters.
> What does this message mean?
>
> Second Error signal from LINV1PD: 129
>
> Nick
>
>
>