search

metrumresearchgroup / bbi

Next generation modeling platform
https://metrumresearchgroup.github.io/bbi/docs
12 stars 2 forks source link

Notify that NONMEM terminated by FNLETA #172

Open kylebaron opened 4 years ago

kylebaron commented 4 years ago

As a user, I'd like to know when the nonmem run is terminated by FNLETA

This isn't uncommon ... the run goes fine and everything gets logged to the lst file, but you don't get table files. You will see 0PROGRAM TERMINATED BY FNLETA in the .lst file but not PRDERR. Otherwise, you will see the error message starting with 0PRED EXIT CODE = 1 in 1PRDERR

0PROGRAM TERMINATED BY FNLETA
0PRED EXIT CODE = 1
0INDIVIDUAL NO.     161   ID= 1.00212309100000E+10   (WITHIN-INDIVIDUAL) DATA REC NO.   2
 THETA=
  3.69E+00   6.75E+00   9.31E+00   7.03E+00   2.13E-01   2.04E+00   1.93E+00   8.95E-02   2.30E+00   7.77E-01
 -1.62E-01   2.61E-01  -5.51E-01  -5.30E-02
 ETA=
 -7.62E-01   8.14E-02  -2.14E-01   2.32E+00   1.46E-03  -2.48E-04  -3.22E-01  -1.46E-01  -4.04E-01
 OCCURS DURING SEARCH FOR ETA AT A NONZERO VALUE OF ETA
 K32, OR K42 IS TOO CLOSE TO AN EIGENVALUE
0PROGRAM TERMINATED BY FNLETA
 MESSAGE ISSUED FROM TABLE STEP
1THERE ARE ERROR MESSAGES IN FILE PRDERR
 #CPUT: Total CPU Time in Seconds,     7022.914
Stop Time:
Tue Aug  4 12:07:56 EDT 2020
seth127 commented 4 years ago

To clarify, when this happens, will you always have the 0PROGRAM TERMINATED BY FNLETA line, and then potentially also have the PRDERR line, but potentially not?

kylebaron commented 4 years ago

Good point; I can't say that you always have PRDERR file