Closed billdenney closed 5 years ago
Perhaps more importantly, the execute
suggests that it did not complete (the .lst file isn't copied into the directory with the .mod file).
I just encountered this issue again with the following estimation lines:
$EST METHOD=ITS NITER=50 file=run13_its.ext
$EST METHOD=NUTS NBURN=200 NITER=500 PRINT=1 OLKJDF=3.0 file=run13.ext
Can you provide any guidance on how to help track down the problem or to work around the issue?
The new model also has the following apparent issue that I believe is NONMEM-related:
/tmp/modelfit_dir1/NM_run1>if [ -e psn.xml ];then cat psn.xml;else echo \<nofile/\>; fi
duplicate attribute at line 10993, column 73, byte 620886:
nm:oaccept='0.500000000000000' nm:osample_m1='-1' nm:osample_m2='-1' nm:osample_m3='-1' nm:massreset='-1'
nm:madapt='-1' nm:nuts_mass='b' nm:nuts_transform='0' nm:kappa='1.00000000000000'
nm:nuts_delta='0.800000000000000' nm:nuts_gamma='5.000000000000000E-02' nm:nuts_transform='0'
========================================================================^
nm:ttdf='0.00000000000000' nm:olkjdf='3.00000000000000' nm:ovarf='1.00000000000000'
nm:slkjdf='0.00000000000000' nm:svarf='1.00000000000000' nm:nuts_test='0' nm:nuts_maxdepth='10'
at /usr/lib/x86_64-linux-gnu/perl5/5.22/XML/Parser.pm line 187.
Elapsed postprocess time in seconds: 0.24
Elapsed finaloutput time in seconds: 0.02
#CPUT: Total CPU Time in Seconds, 30050.907
NONMEM run failed. Check the lst-file in NM_run1 for errors
Not restarting this model.
F:1 ..
execute done
I can reproduce your first problem now and it might be an issue with the PsN lst-file parser.
The workaround for a regular execute is to copy the lst-file and/or other resultfiles yourself from the NM_run1 directory and don't care about the PsN error message if you are confident that the estimation was fine.
I haven't seen your "duplicate attribute" error before. It seem to come from when NONMEM tries to create its xml results file. You could try the option -xmloff to NM-TRAN and see if that fixes the error.
It was easy to fix. You can patch it yourself by checking the commit above.
Thanks!
I confirmed with Bob that the XML issue is a NONMEM issue. It may be fixed in 7.4.3 (I will update my NONMEM version to check after the current set of projects quiets down).
I have a model with 2 estimation steps: FOCEI followed by NUTS.
According to the .lst file, it appeared to complete successfully:
The info that shows up under what I think is that section is: