Re: MSFI issue - apparent state: unit 3 named

From: "Nick Holford" n.holford@auckland.ac.nz Subject: Re: [NMusers] MSFI issue - apparent state: unit 3 named Date: Tue, January 4, 2005 4:19 pm Paul, I suspect the error message is caused because NONMEM cannot find the MSF file. It is important under WFN that you take care with the path needed to find the MSFI file. Because WFN uses a sub-directory for the NONMEM run it needs to have an explicit path to the sub-directory containing the MSFO output file. Assuming you do a run with name run1 using WFN and it produces an MSF file run1.msf in the directory run1.g77 (the default directory name used by WFN) then when you try to read the MSF file with a control stream file called run2 then it should contain: $MSFI ..\run1.g77\run1.msf You can use the WFN command nmmsf run1 to create a suitable control stream for doing a msfi run. This will create the $MSFI path for you as well as remove the unneeded $THETA etc records. Nick -- Nick Holford, Dept Pharmacology & Clinical Pharmacology University of Auckland, 85 Park Rd, Private Bag 92019, Auckland, New Zealand email:n.holford@auckland.ac.nz tel:+64(9)373-7599x86730 fax:373-7556 http://www.health.auckland.ac.nz/pharmacology/staff/nholford/