From: "Paul Hutson" prhutson@pharmacy.wisc.edu
Subject: [NMusers] MSFI issue - apparent state: unit 3 named
Date: Tue, December 28, 2004 4:48 pm
I must admit to just now trying to re-run a fit using $MSFI under g77 and WFN.
I get the following message from the compiler:
"start: end of file
apparent state: unit 3 named MSF1
lately reading sequential unformatted external IO
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
The control stream for my run that yielded this is fairly long, so I added
MSFO=msf1 into the
CONTROL3.ctl (.for) stream, then tried to use the msf1 file to continue the
fit. I got the same message.
Clearly I am doing something fundamentally wrong. Can anyone offer a
suggestion? Thanks
Paul control streams follow
first
$PROBLEM THEOPHYLLINE SINGLE SUBJECT DATA
$INPUT DOSE=AMT TIME CP=DV
$DATA ..\DATA3
$SUBROUTINES ADVAN2
$PK
CALLFL=1
KA=THETA(1)
K=THETA(2)
SC=THETA(3)
$ERROR
Y=F+ERR(1)
$THETA (0,1.7) (0,.102) (0,29)
$ESTIMATION MAXEVAL=2 PRINT=2 MSFO=MSF1
$COVR
then,
$PROBLEM THEOPHYLLINE SINGLE SUBJECT DATA
$INPUT DOSE=AMT TIME CP=DV
$DATA ..\DATA3
$MSFI MSF1
$SUBROUTINES ADVAN2
$PK
CALLFL=1
KA=THETA(1)
K=THETA(2)
SC=THETA(3)
$ERROR
Y=F+ERR(1)
;$THETA (0,1.7) (0,.102) (0,29)
$ESTIMATION MAXEVAL=999 PRINT=2 MSFO=MSF2
$COVR
Paul Hutson, Pharm.D.
Associate Professor (CHS)
UW School of Pharmacy
777 Highland Avenue
Madison, WI 53705-2222
Tel: (608) 263-2496
FAX: (608) 265-5421
Pager: (608) 265-7000, #7856
MSFI issue - apparent state: unit 3 named
From: "Bachman, William (MYD)" bachmanw@iconus.com
Subject: RE: [NMusers] MSFI issue - apparent state: unit 3 named
Date: Tue, January 4, 2005 11:16 am
Paul,
Your control3 example ran without error on my system (gcc version 3.2 (mingw
special 20020817-1) and -O optimization).
Bill
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/
From: "Paul Hutson" prhutson@pharmacy.wisc.edu
Subject: Re: [NMusers] MSFI issue - apparent state: unit 3 named
Date: Tue, January 4, 2005 5:43 pm
Nick and Bill:
The inadequate path description was indeed the problem. An easy but
embarrassing fix.
Thanks
Paul
_______________________________________________________