RE: What does nonmem do after iteration stops? --> Workaround

From: "Eleveld, DJ" d.j.eleveld@anest.umcg.nl Subject: RE: [NMusers] What does nonmem do after iteration stops? --> Workaround Date: Fri, June 3, 2005 1:54 pm Thanks to everyone for thier thoughtful suggestions. The delay seems to be related to the table step. The tables are fairly large (about 700k) and are written directly to the hard drive. If I remove the $TABLE lines then nonmem exits soon after it stops iterating as expected. Interestingly, if the FILE option isnt used, i.e. the table is written to the output file, then there is no delay. I will use this method as a work-around. I also tried POSTHOC without any tables and there was no delay. So I think problems with POSTHOC can be ruled out. The delay seems to happen *before* the writing of the table files. When a run was 'stuck', I didnt see any of the table files open. So I dont think the file access is simply too slow. Possibly the compiler/os has some issues with opening files under certain conditions. I am using Open Watcom 1.0 and Win 98. I will try to update to Open Watcom 1.3 and see if that helps. Thanks very much, Doug